1 |
I use sys-libs/db-4.1.24.ebuild without problems and put it into my |
2 |
local ebuilds-tree where I marked it as stable (KEYWORDS="x86"). I also |
3 |
want to use db-4.1.X in SLOT="4" (instead of "4.1") for sys-libs/db so I |
4 |
don't have to play with the current 4.0.14-release. Additionally I put |
5 |
>=sys-libs/db-4.1.20 |
6 |
into /etc/portage/package.unmask |
7 |
|
8 |
Now I have two problems: |
9 |
|
10 |
1. An "emerge -Up world" leads to |
11 |
[ebuild UD] sys-libs/db-4.0.14-r2 [4.1.24] |
12 |
|
13 |
but an downgrade should IMO not happen if I use the '-U' switch. |
14 |
|
15 |
2. If I put |
16 |
<sys-libs/db-4.1.20 |
17 |
into /etc/portage/package.mask |
18 |
|
19 |
emerge -Up world |
20 |
tells me that all ebuilds for sys-libs/db are masked. |
21 |
|
22 |
etcat -v db|grep sys-libs/db says |
23 |
|
24 |
* sys-libs/db : |
25 |
.... |
26 |
[M I] sys-libs/db-4.1.24 (4) |
27 |
.... ^^^ |
28 |
This should not happen due to unmasking as described above. |
29 |
|
30 |
Is that a bug or did I miss something? |
31 |
|
32 |
Martin |
33 |
|
34 |
-- |
35 |
gentoo-dev@g.o mailing list |