FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Gentoo > Gentoo Development

 
 
LinkBack Thread Tools
 
Old 02-11-2011, 07:50 AM
Sebastian Pipping
 
Default Downgrading glibc?

Hello!


In relation to bug 354395 [1] I would like to downgrade my glibc back to
2.12.2. Portage doesn't allow me to do that:

* Sanity check to keep you from breaking your system:
* Downgrading glibc is not supported and a sure way to destruction
* ERROR: sys-libs/glibc-2.12.2 failed (setup phase):
* aborting to save your system

Can anyone guide me or point me to a guide how to savely do that manually?

Thanks,



Sebastian


[1] https://bugs.gentoo.org/show_bug.cgi?id=354395
 
Old 02-11-2011, 08:22 AM
Diego Elio Pettenò
 
Default Downgrading glibc?

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://blog.flameeyes.eu/
 
Old 02-11-2011, 08:55 AM
Michael Haubenwallner
 
Default Downgrading glibc?

On 02/11/2011 09:50 AM, Sebastian Pipping wrote:
> In relation to bug 354395 [1] I would like to downgrade my glibc back to
> 2.12.2. Portage doesn't allow me to do that:
>
> * Sanity check to keep you from breaking your system:
> * Downgrading glibc is not supported and a sure way to destruction
> * ERROR: sys-libs/glibc-2.12.2 failed (setup phase):
> * aborting to save your system
>
> Can anyone guide me or point me to a guide how to savely do that manually?

While it actually would be interesting to see some downgrade path even for glibc,

> [1] https://bugs.gentoo.org/show_bug.cgi?id=354395

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 memmove where necessary?

/haubi/
--
Michael Haubenwallner
Gentoo on a different level
 
Old 02-11-2011, 09:12 AM
Diego Elio Pettenò
 
Default Downgrading glibc?

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 memmove where
> necessary?

That unless things start crashing down nobody will fix the issues at
all.

We're not talking a last minute change! memcpy() *always* documented not
to use overlapping memory areas.

--
Diego Elio Pettenò — Flameeyes
http://blog.flameeyes.eu/
 
Old 02-11-2011, 10:28 AM
Duncan
 
Default Downgrading glibc?

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 anything at all
> against the new version.

The glibc ebuild really needs an override, like the usual check for
I_KNOW_WHAT_I_AM_DOING_AND_WILL_KEEP_THE_PIECES_IF _IT_BREAKS or some such,
set in the environment. Failing to have such an override at all, seems
rather unGentooish to me.

Fortunately for me (I haven't upgraded to 2.13 yet, but ran into the need
to downgrade an ~arch version myself not long ago, I hadn't emerged
anything of major interest since so the warning was incorrect on its
face), Gentoo has a number of alternative methods to enforce one's will
over an obstinate system, if one believes it necessary. I think I copied
to my personal overlay and edited the ebuild there... after cursing the
fact that I couldn't simply set some sort of var to get the perfectly good
binpkg of the old version to install. The problem has since been fixed
and I've upgraded past it, since.

If that hadn't worked, I'd have tried the untar-the-binpkg-over-the-live-fs
thing. Either that, or the boot to backup snapshot, set ROOT
appropriately, and emerge from there.

--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
 

Thread Tools




All times are GMT. The time now is 09:32 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org