[arch-general] Glibc 2.16.0-2 and /lib problem : the answer ;)

Jonathan Hudson jh+arch at daria.co.uk
Sat Jul 7 12:09:57 EDT 2012

On Sat, 7 Jul 2012 17:00:06 +0100, Jonathan Hudson wrote:

>On Sat, 07 Jul 2012 17:35:56 +0200, Arno Gaboury wrote:
>>On 07/07/2012 05:27 PM, fredbezies wrote:
>>> Well, Tom gave the answer. Boot on rescue-CD / rescue USB-key.
>>> Remove /lib.
>>> And create a symlink : ln -sf /usr/lib lib
>>> I think there will be a lot of problem for a lot of users when glibc
>>> 2.16.0-x will be uploaded on core.
>>> Well, I think I have to do this mistake. I *do* know that forcing
>>> wasn't a good idea :|
>>As I will need to do the update too, can someone explain briefly  in 
>>this list what shoule be done to avoid such a situation?
>>TY in advance.
>It may still fail 
>error: extract: not overwriting dir with file lib
>error: problem occurred while upgrading glibc
>call to execv failed (No such file or directory)
>error: command failed to execute correctly
>error: could not commit transaction
>error: failed to commit transaction (transaction aborted)
>Errors occurred, no packages were upgraded.
>At this the machine is toast. Hope magic-sysreq is enabled, and you
>have rescue disk ...

Apologies, this was meant to be in reply to the "upgrade glibc last"
advice. Two systems upgraded, two failures ... not good.

More information about the arch-general mailing list