On Friday, February 13, 2009 07:27:04 Thomas Sachau wrote:
> Guillaume Castagnino schrieb:
> > Hi,
> >
> > I noticed this in hardened profile :
> > # Mask off anything greater than glibc-2.6.x for now.
> > # 2009-02-11 gengor
> >
> >> =sys-libs/glibc-2.7
> >
> > Is there any good (means "critical") reason for this downgrade ?
> > Because it causes problem with some packages that needs higher glibc
> > version. For example :
> > - iproute2 needs >=glibc-2.7
> >
> >
> >
> > ('installed', '/', 'sys-libs/glibc-2.9_p20081201-r1', 'nomerge') pulled
> > in by
> >
> > >=sys-libs/glibc-2.7 required by ('installed', '/', 'sys-
> >
> > apps/iproute2-2.6.28', 'nomerge')
> > (and 12 more)
> >
> >
> > Thanks for your feedback
> >
> > Regards,
> > Guillaume
>
> I talked to gengor yesterday, so i just copy some lines from IRC:
>
> Feb 12 21:34:28 <gengor> Tommy[D]: because I haven't tested it against
> stable + stable kernel. Feb 12 21:37:57 <gengor> its safe because stable
> glibc (2.6.1) doesn't take advantage of any new API's between 2.6.{25,26}
> -> 2.6.27. I don't know about the newer glibc though, hence the mask. Feb
> 12 21:38:54 <gengor> it was fine to leave it that way when glibc was
> unstable (because those who run unstable should know what they are doing
> and be running unstable kernel too). But they're moving on glibc-2.8
> stabilization right now.
> Feb 12 21:40:33 <gengor> and there are still some minor lingering issues
> w/
> 2.6.27 and 2.6.28 so I don't want to mark it stable yet. Although we're
> getting to the point 2.6.26 is becoming out of date, not getting updates
> from mainline and I don't have time for a bunch of backports this time
> around - so my hand may be forced at some point.
In the future please refrain from cutting and pasting select bits of
conversation from IRC out of context. Or any IRC conversation for that
matter. You don't even realize that the bits you selected for cut/paste
don't even make sense w/o the other parts of the conversation. This is very
fscking rude.
To OP: If you've already upgraded your glibc then you've package.keyworded
it, so why not just package.unmask it as well? You're not forced to
downgrade.
