Dear Andrei > Dear Hans-J, could you please clarify your terminology? What do you mean > by 'automatically update' in above paragraph? Which one of the following > do you mean: > > 1. I have <package> version 1 and expected version 2~bpo from backports > to be installed
What I meant was "I have <package> bla-3.0 installed (from debian/stable) and expected version 4~bpo from wheezy-backports upgraded. > > As per default configuration of backports (priority 100) 1 will *not* > happen unless you use '-t backports', but 2 will. > Hmm, so I should use another syntax??? > > [1] please avoid using 'update' instead of 'upgrade' in a Debian > context, but rather stick to the meanings corresponding to > 'apt-get update' 'apt-get upgrade'. > Of course, my fault. I meant upgrade not update. I was not precise! > Hope this helps, > Andrei Dear Lisi > Sorry, I don't understand this. What do you mean by "appeared in > aptitude"?? I am using the ncurses-gui of aptitude. In this gui the packages appear. > And "did it manually"? Could you tell us clearly and specifically what you > did and what happened, preferably with quotes from the command line. With "manually", I meant, that I walked with the cursor to all the packages and its libs by pressing "+" and "-" to mark them as install or remove. I know, the dependencies should be fullfilled by aptitude automatically, but this worked not well. I had to fine tune a little bit. > As I said, backported packages will both update and upgrade, when there is > an upgrade available in backports. It should, but did not. I think, it is, because wheezy-backports got a lower pinning ranking. Regards Hans -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201305201205.53978.hans.ullr...@loop.de
