Re: [gentoo-dev] /etc/portage/package.unmask not working as expected

[Paul de Vrieze]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 25 September 2003 11:51, Martin Lesser wrote:
> 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

db-4.0 and db-4.1 are NOT compatible. Applications linked against 4.0 will not 
work with 4.1, so they need to be slotted differently.


>
> 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.

db-4.1 is masked in the profiles

>
> 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?

See above. Putting =sys-libs/db-4.1.* in /etc/portage/package.unmask should 
work

Paul

- -- 
Paul de Vrieze
Gentoo Developer
Mail: pauldv@g.o
Homepage: http://www.devrieze.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/csfWbKx5DBjWFdsRAqwdAJ9sgogIXJ9Fi3O07m7jF6oN62lMjACg1ps0
pfkDxtqdT3Lhk4RKkXt7iww=
=bGtc
-----END PGP SIGNATURE-----


--
gentoo-dev@g.o mailing list