Le vendredi 13 février 2009 18:48:03, Gordon Malm a écrit :
> On Friday, February 13, 2009 09:15:18 Guillaume Castagnino wrote:
> > In fact, no: glibc-2.9 was allready keyworded on hardened ~x86 in the
> > portage tree, and not masked until 2009-02-11.
> > So ~x86 hardened was naturally upgraded to glibc 2.9 without any
> > intervention.
>
> And naturally if you're running ~ARCH you should know how to
> manipulate /etc/portage.
>
> > I have no problem to package.unmask it, it's just to know what is the
> > reason for this mask :)
>
> Because sys-libs/glibc-2.8 is about to go stable and stable hardened is not
> ready for it.
>
> > But keep in mind that for ~x86 hardened, this mask has a dependency
> > problem, since ~x86 iproute2 depends on glibc that is now masked on
> > ~x86 hardened (and was not before 2009-02-11)
>
> So put sys-libs/glibc into /etc/portage/package.unmask.
Yes of course.
I perfectly know how to do to fix this problem *for me* as ~arch user for many
years.
But what I want to point, is that currently, depdency tree seems to be broken
for ~x86 : some packages in the ~x86 tree (iproute2 for example) ask for
package not available in ~x86 (glibc).
Doesn't it sounds wrong to have such situation in the official tree ?
Anyway, thanks for your work :)
--
Guillaume Castagnino
[email protected] / [email protected]
