1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
| |>|>When I run emerge -up world I get the following: |
5 |
| |>|> |
6 |
| |>|>[ebuild UD] sys-devel/perl-5.6.1-r7 [5.8.0-r3] |
7 |
| |>|>[ebuild UD] app-crypt/gnupg-1.0.7 [1.2.1-r0] |
8 |
| |>|>[ebuild UD] net-www/mozilla-1.0.1-r3 [1.2.1-r1] |
9 |
| |>|> |
10 |
| |>|>These are masked packages that I installed earlier today. These |
11 |
are not |
12 |
| |>|>the only masked packages that I currently have installed, but it's |
13 |
what |
14 |
| |>|>I've installed today. Is it a coincidence that these are packages |
15 |
| that I |
16 |
| |>|>just installed (and there's something special about them), or could |
17 |
| this |
18 |
| |>|>be something that recently changed in Portage (the "D" is new to me) ? |
19 |
|
20 |
|
21 |
This is the normal course of events when you do something like this: |
22 |
|
23 |
ACCEPT_KEYWORDS="~x86" emerge some-masked-package |
24 |
|
25 |
then |
26 |
|
27 |
emerge -up world |
28 |
|
29 |
At this point, Portage pretends the masked version of |
30 |
'some-masked-package' does not exist and wants to install the highest |
31 |
versioned installable candidate. |
32 |
|
33 |
The D means downgrade, I assume. |
34 |
|
35 |
Ideally, Portage wouldn't want to downgrade these packages. I think the |
36 |
"sticky flags" feature being worked on will solve this problem. |
37 |
|
38 |
A workaround is to inject the lower versions so Portage believes they |
39 |
are already installed: |
40 |
|
41 |
emerge -i sys-devel/perl-5.6.1-r7 app-crypt/gnupg-1.0.7 |
42 |
net-www/mozilla-1.0.1-r3 |
43 |
|
44 |
- - Robert |
45 |
-----BEGIN PGP SIGNATURE----- |
46 |
Version: GnuPG v1.1.90-nr1 (Windows XP) |
47 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
48 |
|
49 |
iD8DBQE9/R1Abv6Y11NqSv8RAqbmAJ9VF1Y/kmn54lvDsBNbZvGRtTCVGACgzcWx |
50 |
on6ojrFMoMlII20NV+2DVGo= |
51 |
=qf1t |
52 |
-----END PGP SIGNATURE----- |
53 |
|
54 |
|
55 |
-- |
56 |
gentoo-dev@g.o mailing list |