On Saturday, February 12, 2011 00:37:12 Ryan Hill wrote:
> Tracker: https://bugs.gentoo.org/353816
typo; you meant:
https://bugs.gentoo.org/354107
-mike
signature.asc
Description: This is a digitally signed message part.
On Fri, 11 Feb 2011 16:24:14 +0100
Diego Elio Pettenò wrote:
> Il giorno ven, 11/02/2011 alle 14.23 +0100, Michael Haubenwallner ha
> scritto:
> >
> > But both that document as well as uncountable lines of source code are
> > rather old.
> > While the source code isn't that large a problem for G
On 02/11/2011 01:27 PM, Diego Elio Pettenò wrote:
> It should have been masked _beforehand_, masking it now is going to
> cause more trouble.
Portage will propose a downgrade of glibc on emerge-update-world, okay.
How bad would that be? Does it cause any other trouble?
> Remember: unless you're
On Fri, Feb 11, 2011 at 1:27 PM, Diego Elio Pettenò wrote:
>
> Il giorno ven, 11/02/2011 alle 13.06 +0100, Sebastian Pipping ha
> scritto:
> >
> > If anyone considers masking glibc 2.13 for now: please take my vote.
>
> It should have been masked _beforehand_, masking it now is going to
> cause mo
On 02/11/2011 11:12 AM, Diego Elio Pettenò wrote:
> Il giorno ven, 11/02/2011 alle 10.55 +0100, Michael Haubenwallner ha
> scritto:
>>
>> what do you think of working around the memcpy troubles with
>> glibc-2.13 by
>> simply redirecting memcpy to memmove within glibc, either
>> unconditionally or
Il giorno ven, 11/02/2011 alle 13.06 +0100, Sebastian Pipping ha
scritto:
>
> If anyone considers masking glibc 2.13 for now: please take my vote.
It should have been masked _beforehand_, masking it now is going to
cause more trouble.
Remember: unless you're able to rebuild everything that was b
Diego Elio Pettenò posted on Fri, 11 Feb 2011 10:22:44 +0100 as excerpted:
> Il giorno ven, 11/02/2011 alle 09.50 +0100, Sebastian Pipping ha
> scritto:
>>
>>
>> Can anyone guide me or point me to a guide how to savely do that
>> manually?
>
> There really isn't a safe way as soon as you built
Il giorno ven, 11/02/2011 alle 10.55 +0100, Michael Haubenwallner ha
scritto:
>
> what do you think of working around the memcpy troubles with
> glibc-2.13 by
> simply redirecting memcpy to memmove within glibc, either
> unconditionally or
> optional/temporary (via USE-flag?) until everyone uses m
Il giorno ven, 11/02/2011 alle 09.50 +0100, Sebastian Pipping ha
scritto:
>
>
> Can anyone guide me or point me to a guide how to savely do that
> manually?
There really isn't a safe way as soon as you built anything at all
against the new version.
--
Diego Elio Pettenò — Flameeyes
http://blo
