You are not logged in.

#1 2012-10-06 11:40:47

Lina
Member
Registered: 2012-10-06
Posts: 5

glibc update problem

Hey guys,

the problem started with the /lib to /usr/lib switch. I tried to update the system according to the instructions in the wiki article. Unfortunately, I saw another post first which just told me only to ignore gclib. As I got errors in result, I downloaded the curl libraries manually and copied them into /usr/lib. This might cause(?) the final error below.

The second turn to run "pacman -Su" revealed that I still had packages owning files in /lib, namely owned by the kernel. As the wiki stated "These packages need rebuilding so as not to include the /lib directory", I ran "pacman -Syu linux" which failed with the error message that "libc.so.4 was not a symlink" (or something similar).
(Probably a stupid move to update the kernel like that...O.o)

When I tried to reboot to continue the analysis today, the root partition could not be found. I used a live usb stick and tried to proceed according to this post:
https://wiki.archlinux.org/index.php/Pa … onger_boot.

Running arch-chroot works fine. When I try to get pacman to update with "pacman -Syu mkinitcpio systemd linux --ignore glibc" (I added the ignore due to the above problem), I get:

/tmp/alpm_wJUITN/.INSTALL: line 2: systemd-tmpfiles: command not found
error: command failed to execute correctly
Idconfig: /usr/lib/libcurl.so.4 is not a symbolic link

I'm not sure that the curl message is related to the systemd error. Where should the symlink point to?

Last edited by Lina (2012-10-06 12:44:43)

Offline

#2 2012-10-06 12:42:01

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 4,310

Re: glibc update problem

Lina wrote:
/tmp/alpm_wJUITN/.INSTALL: line 2: systemd-tmpfiles: command not found
error: command failed to execute correctly
Idconfig: /usr/lib/libcurl.so.4 is not a symbolic link

I'm not sure that the curl message is related to the systemd error. Where should the symlink point to?

lib]$ ls -l |grep libcurl
-rw-r--r--  1 root root   792722 Jul 27 23:42 libcurl.a
lrwxrwxrwx  1 root root       16 Jul 27 23:41 libcurl.so -> libcurl.so.4.2.0
lrwxrwxrwx  1 root root       16 Jul 27 23:41 libcurl.so.4 -> libcurl.so.4.2.0
-rwxr-xr-x  1 root root   385640 Jul 27 23:42 libcurl.so.4.2.0

my curl Version        : 7.27.0-1 .


Booting with apg Openrc, NOT systemd.
Automounting : not needed, i prefer pmount
Aur helpers : makepkg + my own local repo === rarely need them

Online

#3 2012-10-07 14:34:26

Lina
Member
Registered: 2012-10-06
Posts: 5

Re: glibc update problem

Hey,

thank you. I fixed the symlinks. So the remaining tasks for me are 1) to get the remaining files out of lib and 2) afterwards update kernel and mkinitcpio to get the system running again. I tried the following for 1):

find /lib -exec pacman -Qo -- {} + | grep -v glibc
error: cannot determine ownership of directory /lib
/lib/cpp is owned by gcc-multilib 4.7.0-6
grep '^lib/' /var/lib/pacman/local/*/files | grep -v glibc
/var/lib/pacman/local/gcc-multilib-4.7.0.6/files:lib/
/var/lib/pacman/local/gcc-multilib-4.7.0.6/files:lib/cpp

Following the wiki instructions, I tried to update multilib:

pacman -S gcc-multilib
...
error: ...(conflicting files)
glibc: /lib exists in the filesystem
filesystem: /var/lock exists in filesystem
filesystem: /var/run exists in filesystem

And I'm back to the glibc error. How can I update multilib?

Last edited by Lina (2012-10-07 16:34:34)

Offline

#4 2012-10-07 16:37:27

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 5,363

Re: glibc update problem

-Sdd gcc-multilib

?

man pacman

Sakura:-
Mobo: ASUS P8Z77-V PRO // Processor: Intel Core i7-3770K 3.4GHz // GFX: nVidia GeForce GTX 970 Ti // RAM: 32GB (4x 8GB) Corsair DDR3 (@ 2133MHz) // Storage: 1x 3TB Seagate SATAII 5x 1TB Samsung SATAII, 2x 120GB Corsair SSD

Offline

#5 2012-10-08 08:26:22

Lina
Member
Registered: 2012-10-06
Posts: 5

Re: glibc update problem

Sorry, badly phrased. What I meant was: Is it a good idea to ignore the dependency check? From your answer, I assume, it's ok and went ahead.

On the first attempt, I got the /var/lock and /var/run error. Other users with the same problem (e.g. Matthias https://bbs.archlinux.de/viewtopic.php?id=21678) recommended to just remove them. Afterwards, the update went through without any problems. Thank you!

Offline

#6 2012-10-08 09:26:20

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 5,363

Re: glibc update problem

Lina wrote:

What I meant was: Is it a good idea to ignore the dependency check?

In a normal scenario, no. But in this case, yes. You are (were) in a catch-22 situation where you can't update your system because you haven't updated your system. So to get out of that loop, you need to remove the problematic package from the equation (either by removing the package, or by updating it separately). So long as you end up with a fully updated system, that's all that really matters.


Glad you got it sorted.


Sakura:-
Mobo: ASUS P8Z77-V PRO // Processor: Intel Core i7-3770K 3.4GHz // GFX: nVidia GeForce GTX 970 Ti // RAM: 32GB (4x 8GB) Corsair DDR3 (@ 2133MHz) // Storage: 1x 3TB Seagate SATAII 5x 1TB Samsung SATAII, 2x 120GB Corsair SSD

Offline

Board footer

Powered by FluxBB