Note: Due to technical difficulties, the Archives are currently not up to date.
GMANE provides an alternative service for most mailing lists. c.f. bug 424647
I use sys-libs/db-4.1.24.ebuild without problems and put it into my
local ebuilds-tree where I marked it as stable (KEYWORDS="x86"). I also
want to use db-4.1.X in SLOT="4" (instead of "4.1") for sys-libs/db so I
don't have to play with the current 4.0.14-release. Additionally I put
>=sys-libs/db-4.1.20
into /etc/portage/package.unmask
Now I have two problems:
1. An "emerge -Up world" leads to
[ebuild UD] sys-libs/db-4.0.14-r2 [4.1.24]
but an downgrade should IMO not happen if I use the '-U' switch.
2. If I put
<sys-libs/db-4.1.20
into /etc/portage/package.mask
emerge -Up world
tells me that all ebuilds for sys-libs/db are masked.
etcat -v db|grep sys-libs/db says
* sys-libs/db :
....
[M I] sys-libs/db-4.1.24 (4)
.... ^^^
This should not happen due to unmasking as described above.
Is that a bug or did I miss something?
Martin
--
gentoo-dev@g.o mailing list
|
|
