On Thursday 04 January 2007 18:01, Thomas Rösner wrote: > Nelson wrote:
> >> This is strange, I just made a emerge sync and then a emerge > >> --update world. > >> I have still version 1.4.5. I use x86 (no ~x86). > >> [...] > >> Maybe have I to do an emerge -uD ? because I do only emerge --update ? > >> > > > > I don't think that's the problem. To my knowledge the -D means update > > related packages (it means "deep"). > > Half way right: in this case, gnupg-1.4.6 *is* a related package. If you > have gnupg in world, and tell portage to --update world, it will update > the highest slot version of gnupg, in this case 1.9. Only when you say > --deep, it will go for the other slots, too, *if* something else still > depends on them. > > See the original GLSAs for reference - the first GLSA used --update > gnupg, the second corrected GLSA said --update =gnupg-1.4* or something > equivalent (all from memory). Problem resolved: I did know a emerge -uD world and it updated my gnupg version to 1.4.6. So from now I will any time use the arguments "-uD" when I'm updating Gentoo. Would it not be better if the deep update would be the default update? Because this is confusing (for non gentoo experienced users). By the way the emerge =app-crypt/gnupg-1.4.6 worked also before I did the deep update. So its also possible to manally update gnupg. Thanks very much for your support. -- E-Mail sent with anti-spam site TrashMail.net! Free disposable email addresses: http://www.trashmail.net/ -- gentoo-user@gentoo.org mailing list
