1 |
On 09/08/03 Andy Arbon wrote: |
2 |
|
3 |
> -----BEGIN PGP SIGNED MESSAGE----- |
4 |
> Hash: SHA1 |
5 |
> |
6 |
> Hello, |
7 |
> |
8 |
> Please see this command and it's output: |
9 |
> - ---------------------------------- |
10 |
> zoidberg ara # emerge -pU world |
11 |
> |>> --upgradeonly implies --update... adding --update to options. |
12 |
> |
13 |
> These are the packages that I would merge, in order: |
14 |
> |
15 |
> Calculating world dependencies ...done! |
16 |
> [ebuild U ] sys-libs/db-4.0.14-r2 [3.2.9-r7] |
17 |
> [ebuild U ] net-misc/dhcpcd-1.3.22_p4-r1 [1.3.22_p4] |
18 |
> |
19 |
> Note this last line >| |
20 |
> [ebuild U ] media-video/nvidia-kernel-1.0.4363-r3 [1.0.4496-r1] |
21 |
> - -------------------------------------------- |
22 |
> |
23 |
> Is this the correct behaviour? The nvidia-kernel ebuild was (most |
24 |
> likely) orignally installed from ~x86, though I normally stick to x86, |
25 |
> but even so, are there any situations where Portage should say it is |
26 |
> going to upgrade a package (not downgrade) to an ebuild with a lower |
27 |
> version number as indicated above? |
28 |
|
29 |
Did you change kernels after installing nvidia-kernel? If yes it is a |
30 |
SLOT change and portage displays it as a upgrade. There are some patches |
31 |
in bugzilla to display these different from upgrades, I hope one of them |
32 |
gets incorporated into portage soon (SLOTs have more problems, but these |
33 |
need time). |
34 |
|
35 |
Marius |
36 |
|
37 |
-- |
38 |
Public Key at http://www.genone.de/info/gpg-key.pub |
39 |
|
40 |
In the beginning, there was nothing. And God said, 'Let there be |
41 |
Light.' And there was still nothing, but you could see a bit better. |