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 > ArchLinux > ArchLinux General Discussion

 
 
LinkBack Thread Tools
 
Old 07-07-2012, 03:35 PM
Arno Gaboury
 
Default Glibc 2.16.0-2 and /lib problem : the answer ;)

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.
 
Old 07-07-2012, 04:00 PM
Jonathan Hudson
 
Default Glibc 2.16.0-2 and /lib problem : the answer ;)

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 ...
 
Old 07-07-2012, 04:09 PM
Jonathan Hudson
 
Default Glibc 2.16.0-2 and /lib problem : the answer ;)

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.
 
Old 07-07-2012, 04:18 PM
Jan Steffens
 
Default Glibc 2.16.0-2 and /lib problem : the answer ;)

On Sat, Jul 7, 2012 at 6:09 PM, Jonathan Hudson <jh+arch@daria.co.uk> wrote:
> 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.

You used --force (-f) again. http://i.imgur.com/5Zd1w.png
 
Old 07-07-2012, 04:21 PM
Jonathan Hudson
 
Default Glibc 2.16.0-2 and /lib problem : the answer ;)

On Sat, 7 Jul 2012 18:18:28 +0200, Jan Steffens wrote:

>On Sat, Jul 7, 2012 at 6:09 PM, Jonathan Hudson <jh+arch@daria.co.uk> wrote:
>> 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.
>
>You used --force (-f) again. http://i.imgur.com/5Zd1w.png
>


I did NOT.
 
Old 07-07-2012, 04:25 PM
Arthur Titeica
 
Default Glibc 2.16.0-2 and /lib problem : the answer ;)

On Saturday 07 July 2012 18:18:28 Jan Steffens wrote:
> On Sat, Jul 7, 2012 at 6:09 PM, Jonathan Hudson <jh+arch@daria.co.uk> wrote:
> > 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.
>
> You used --force (-f) again. http://i.imgur.com/5Zd1w.png

I didn't but it still failed. mc came to rescue as for creating the /lib
symlink because

# ln -s /usr/lib /lib
bash: /bin/ln: No such file or directory

Anyway, here's my pacman log

[2012-07-07 19:11] Running 'pacman -Syu --ignore glibc'
[2012-07-07 19:11] synchronizing package lists
[2012-07-07 19:11] starting full system upgrade
[2012-07-07 19:11] upgraded lib32-glibc (2.16.0-1 -> 2.16.0-2)
[2012-07-07 19:11] Running 'pacman -Suy'
[2012-07-07 19:11] synchronizing package lists
[2012-07-07 19:11] starting full system upgrade
[2012-07-07 19:11] error: problem occurred while upgrading glibc
[2012-07-07 19:11] call to execv failed (No such file or directory)
[2012-07-07 19:11] upgraded glibc (2.16.0-1 -> 2.16.0-2)
[2012-07-07 19:20] Running 'pacman -Suy'
[2012-07-07 19:20] synchronizing package lists
[2012-07-07 19:20] starting full system upgrade
[2012-07-07 19:21] Running 'pacman -S glibc'
[2012-07-07 19:21] Generating locales...
[2012-07-07 19:21] en_US.UTF-8... done
[2012-07-07 19:21] en_US.ISO-8859-1... done
[2012-07-07 19:21] Generation complete.
[2012-07-07 19:21] upgraded glibc (2.16.0-2 -> 2.16.0-2)

--
Arthur Titeica
 
Old 07-07-2012, 05:15 PM
"Jérôme M. Berger"
 
Default Glibc 2.16.0-2 and /lib problem : the answer ;)

fredbezies wrote:
> Well, Tom gave the answer. Boot on rescue-CD / rescue USB-key.
>
> Remove /lib.
>
Careful about that! The current stable kernel (3.4.4-2) still has
its modules in /lib/modules/ so if you remove /lib you may not be
able to boot!

> 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.
>
+1

Jerome
--
mailto:jeberger@free.fr
http://jeberger.free.fr
Jabber: jeberger@jabber.fr
 
Old 07-07-2012, 05:32 PM
Geert Hendrickx
 
Default Glibc 2.16.0-2 and /lib problem : the answer ;)

On Sat, Jul 07, 2012 at 17:21:24 +0100, Jonathan Hudson wrote:
> On Sat, 7 Jul 2012 18:18:28 +0200, Jan Steffens wrote:
> >You used --force (-f) again. http://i.imgur.com/5Zd1w.png
>
>
> I did NOT.


Was /lib your current working dir when you ran pacman?
Or did any other process have it open so it could not be removed?


Geert


--
geert.hendrickx.be :: geert@hendrickx.be :: PGP: 0xC4BB9E9F
This e-mail was composed using 100% recycled spam messages!
 
Old 07-07-2012, 05:53 PM
Jonathan Hudson
 
Default Glibc 2.16.0-2 and /lib problem : the answer ;)

On Sat, 7 Jul 2012 19:32:57 +0200, Geert Hendrickx wrote:

>On Sat, Jul 07, 2012 at 17:21:24 +0100, Jonathan Hudson wrote:
>> On Sat, 7 Jul 2012 18:18:28 +0200, Jan Steffens wrote:
>> >You used --force (-f) again. http://i.imgur.com/5Zd1w.png
>>
>>
>> I did NOT.
>
>
>Was /lib your current working dir when you ran pacman?
>Or did any other process have it open so it could not be removed?
>
>
> Geert
>

Post event it's hard to tell. I previously removed obsolete
firmware, modules and udev directories, then ran the commands from a
previous thread (cut and paste, no --force).

# pacman -Syu --ignore glibc
# pacman -S glibc

The current directory was NOT /lib, and as the system is now pretty
much as loaded as prior, fuser /usr/lib (or /lib) shows no results.

-jh
 
Old 07-07-2012, 07:15 PM
Lukas Fleischer
 
Default Glibc 2.16.0-2 and /lib problem : the answer ;)

On Sat, Jul 07, 2012 at 06:53:21PM +0100, Jonathan Hudson wrote:
> On Sat, 7 Jul 2012 19:32:57 +0200, Geert Hendrickx wrote:
>
> >On Sat, Jul 07, 2012 at 17:21:24 +0100, Jonathan Hudson wrote:
> >> On Sat, 7 Jul 2012 18:18:28 +0200, Jan Steffens wrote:
> >> >You used --force (-f) again. http://i.imgur.com/5Zd1w.png
> >>
> >>
> >> I did NOT.
> >
> >
> >Was /lib your current working dir when you ran pacman?
> >Or did any other process have it open so it could not be removed?
> >
> >
> > Geert
> >
>
> Post event it's hard to tell. I previously removed obsolete
> firmware, modules and udev directories, then ran the commands from a
> previous thread (cut and paste, no --force).
>
> # pacman -Syu --ignore glibc
> # pacman -S glibc
>
> The current directory was NOT /lib, and as the system is now pretty
> much as loaded as prior, fuser /usr/lib (or /lib) shows no results.

What's the output of `grep '^lib' /var/lib/pacman/local/*/files`?

>
> -jh
>
>
 

Thread Tools




All times are GMT. The time now is 01:27 PM.

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