public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
Search results ordered by [date|relevance]  view[summary|nested|Atom feed]
thread overview below | download: 
* [gentoo-dev] /etc/portage/package.unmask not working as expected
@ 2003-09-25  9:51 99% Martin Lesser
  0 siblings, 0 replies; 1+ results
From: Martin Lesser @ 2003-09-25  9:51 UTC (permalink / raw
  To: gentoo-dev

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@gentoo.org mailing list


^ permalink raw reply	[relevance 99%]

Results 1-1 of 1 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2003-09-25  9:51 99% [gentoo-dev] /etc/portage/package.unmask not working as expected Martin Lesser

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox