| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Hello, |
| 5 |
|
| 6 |
Please see this command and it's output: |
| 7 |
- ---------------------------------- |
| 8 |
zoidberg ara # emerge -pU world |
| 9 |
|>> --upgradeonly implies --update... adding --update to options. |
| 10 |
|
| 11 |
These are the packages that I would merge, in order: |
| 12 |
|
| 13 |
Calculating world dependencies ...done! |
| 14 |
[ebuild U ] sys-libs/db-4.0.14-r2 [3.2.9-r7] |
| 15 |
[ebuild U ] net-misc/dhcpcd-1.3.22_p4-r1 [1.3.22_p4] |
| 16 |
|
| 17 |
Note this last line >| |
| 18 |
[ebuild U ] media-video/nvidia-kernel-1.0.4363-r3 [1.0.4496-r1] |
| 19 |
- -------------------------------------------- |
| 20 |
|
| 21 |
Is this the correct behaviour? The nvidia-kernel ebuild was (most likely |
| 22 |
) orignally installed from ~x86, though I normally stick to x86, but |
| 23 |
even so, are there any situations where Portage should say it is going |
| 24 |
to upgrade a package (not downgrade) to an ebuild with a lower version |
| 25 |
number as indicated above? |
| 26 |
|
| 27 |
Thanks, |
| 28 |
|
| 29 |
Andy |
| 30 |
|
| 31 |
|
| 32 |
-----BEGIN PGP SIGNATURE----- |
| 33 |
Version: GnuPG v1.2.2 (GNU/Linux) |
| 34 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 35 |
|
| 36 |
iD8DBQE/XLvoX3TTUvZURBERAge/AJ9ncg2Qvc1jMvNPH+hthTOWegg7nwCfZMq1 |
| 37 |
VmSTv5bM6VFeQR97CyJ/QRA= |
| 38 |
=8XqD |
| 39 |
-----END PGP SIGNATURE----- |
| 40 |
|
| 41 |
|
| 42 |
-- |
| 43 |
gentoo-dev@g.o mailing list |
Archives