| 1 |
Nelson wrote: |
| 2 |
>> This is strange, I just made a emerge sync and then a emerge |
| 3 |
>> --update world. |
| 4 |
>> I have still version 1.4.5. I use x86 (no ~x86). |
| 5 |
>> [...] |
| 6 |
>> Maybe have I to do an emerge -uD ? because I do only emerge --update ? |
| 7 |
>> |
| 8 |
> |
| 9 |
> I don't think that's the problem. To my knowledge the -D means update |
| 10 |
> related packages (it means "deep"). |
| 11 |
|
| 12 |
Half way right: in this case, gnupg-1.4.6 *is* a related package. If you |
| 13 |
have gnupg in world, and tell portage to --update world, it will update |
| 14 |
the highest slot version of gnupg, in this case 1.9. Only when you say |
| 15 |
--deep, it will go for the other slots, too, *if* something else still |
| 16 |
depends on them. |
| 17 |
|
| 18 |
See the original GLSAs for reference - the first GLSA used --update |
| 19 |
gnupg, the second corrected GLSA said --update =gnupg-1.4* or something |
| 20 |
equivalent (all from memory). |
| 21 |
|
| 22 |
Regards, |
| 23 |
T. |
| 24 |
-- |
| 25 |
gentoo-user@g.o mailing list |
Archives