glibc update refusing to proceed. File ownership problem

Katherine1 · 2012-07-14 18:38:31

So, I'm attempting to update glibc, and everything has been cleared out of /lib except the glibc libraries. According to "find /lib -exec pacman -Qo -- {} +" everything inside /lib is owned by glibc, but /lib is unowned. When I attempt to update, I receive the error: "glibc: /lib exists in filesystem"

How can I fix this?

Allan · 2012-07-14 18:41:45

Did you do the grep line from the wiki?

Potomac · 2012-07-14 21:27:33

I have the same problem,

I have follow the wiki by using these 2 commands :

pacman -Syu --ignore glibc
then
pacman -Su

but the last command always gives me an error :

"error: failed to commit transaction (conflicting files)
glibc: /lib exists in filesystem
Errors occurred, no packages were upgraded."

the grep line :
grep '^lib/' /var/lib/pacman/local/*/files

this grep shows me that glibc-2.16.0-1 package uses the /lib folder,

how can I fix my problem ?

Last edited by Potomac (2012-07-14 21:28:13)

cfr · 2012-07-14 21:32:03

@Potomac

Did you skip

find /lib -exec pacman -Qo -- {} +

and, if not, what results did you get?

Potomac · 2012-07-14 21:36:54

I have the same result like Katherine1 :

/lib --> no owner

but everything inside the /lib folder is owned by glibc with a lot of files ( /lib/ld-linux.so.2, /lib/libpcprofile.so etc... )

I have followed the guide and I don't understand why the update doesn't work

Potomac · 2012-07-14 21:44:48

for your information archlinux is installed in virtualbox ( virtual machine ) and I use vboxguest additions modules ( the Oracle version, manually installed, not the archlinux package version ),

I have uninstalled "virtualbox guest addition modules" but I still have the problem with glibc, it's impossible to do the update with pacman

Last edited by Potomac (2012-07-14 22:17:08)

Stribog.ua · 2012-07-14 22:04:22

I had the same issue. The problem was in lib32-glibc.
So, update lib32-glibc first - https://bbs.archlinux.org/viewtopic.php … 1#p1129601

Potomac · 2012-07-14 22:09:37

I don't have "lib32-glibc" in my system ( archlinux 32 bit ), pacman doesn't find this package when I type :

pacman -S lib32-glibc

but I found the solution !!

the solution is to move the /lib/modules folder in a backup folder, in order to have only the files owned by glibc :

mv /lib/modules /home/potomac/backup

it's the only way if I want to update glibc

Last edited by Potomac (2012-07-14 22:45:19)

jasonwryan · 2012-07-15 00:30:23

Stickied until this works its way through the system...

nomorewindows · 2012-07-15 00:46:00

I had a real irritable one, whereas I had to remove the lib directory itself (glibc was the owner of the files directly under /lib). Wouldn't even let me execute any commands on the shell then. Of course, it wouldn't reboot. Thanks to PXE booting, I could mount the drives, finish running pacman -Su and be on my way.

Hy Ginsberg · 2012-07-15 00:49:40

Hi all. I followed the instructions in the DeveloperWiki for upgrading glibc, and found that hal owned the file /lib/udev/rules.d/90-hal.rules. I moved it to /usr/lib by hand (maybe a mistake) and removed the /lib/udev and /lib/udev/rules.d directories. But that is not good enough, because pacman still thinks that hal has some ownership of /lib. Pacman reports:

pacman -Qo /lib
error: cannot determine ownership of '/lib'

and

grep '^lib/' /var/lib/pacman/local/*/files

yields

/var/lib/pacman/local/glibc-2.15-11/files:lib/
/var/lib/pacman/local/glibc-2.15-11/files:lib/ld-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/ld-linux.so.2
/var/lib/pacman/local/glibc-2.15-11/files:lib/libBrokenLocale-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libBrokenLocale.so.1
/var/lib/pacman/local/glibc-2.15-11/files:lib/libSegFault.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libanl-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libanl.so.1
/var/lib/pacman/local/glibc-2.15-11/files:lib/libc-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libc.so.6
/var/lib/pacman/local/glibc-2.15-11/files:lib/libcidn-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libcidn.so.1
/var/lib/pacman/local/glibc-2.15-11/files:lib/libcrypt-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libcrypt.so.1
/var/lib/pacman/local/glibc-2.15-11/files:lib/libdl-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libdl.so.2
/var/lib/pacman/local/glibc-2.15-11/files:lib/libm-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libm.so.6
/var/lib/pacman/local/glibc-2.15-11/files:lib/libmemusage.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnsl-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnsl.so.1
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_compat-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_compat.so.2
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_db-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_db.so.2
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_dns-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_dns.so.2
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_files-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_files.so.2
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_hesiod-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_hesiod.so.2
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_nis-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_nis.so.2
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_nisplus-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_nisplus.so.2
/var/lib/pacman/local/glibc-2.15-11/files:lib/libpcprofile.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libpthread-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libpthread.so.0
/var/lib/pacman/local/glibc-2.15-11/files:lib/libresolv-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libresolv.so.2
/var/lib/pacman/local/glibc-2.15-11/files:lib/librt-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/librt.so.1
/var/lib/pacman/local/glibc-2.15-11/files:lib/libthread_db-1.0.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libthread_db.so.1
/var/lib/pacman/local/glibc-2.15-11/files:lib/libutil-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libutil.so.1
/var/lib/pacman/local/hal-0.5.14-6/files:lib/
/var/lib/pacman/local/hal-0.5.14-6/files:lib/udev/
/var/lib/pacman/local/hal-0.5.14-6/files:lib/udev/rules.d/
/var/lib/pacman/local/hal-0.5.14-6/files:lib/udev/rules.d/90-hal.rules

So, no surprise (in retrospect), I didn't fool pacman by moving the files by hand.

And so the bottom line, I still can't install glibc. The rest of my system is upgraded -- pacman -Syu shows only glibc out of date. Any suggestions as to how to proceed would be much appreciated.

- Hy

fatboy · 2012-07-15 00:53:26

Hy Ginsberg wrote:

/var/lib/pacman/local/hal-0.5.14-6/files:lib/
/var/lib/pacman/local/hal-0.5.14-6/files:lib/udev/
/var/lib/pacman/local/hal-0.5.14-6/files:lib/udev/rules.d/
/var/lib/pacman/local/hal-0.5.14-6/files:lib/udev/rules.d/90-hal.rules

Try removing hal for now, then after the update reinstall it
EDIT: Also the file manually moved may need to be deleted

Last edited by fatboy (2012-07-15 00:57:02)

jasonwryan · 2012-07-15 00:54:05

Merging with the glibc stickied thread...

nomorewindows · 2012-07-15 00:56:33

fatboy wrote:

Hy Ginsberg wrote:
/var/lib/pacman/local/hal-0.5.14-6/files:lib/
/var/lib/pacman/local/hal-0.5.14-6/files:lib/udev/
/var/lib/pacman/local/hal-0.5.14-6/files:lib/udev/rules.d/
/var/lib/pacman/local/hal-0.5.14-6/files:lib/udev/rules.d/90-hal.rules
Try removing hal for now, then after the update reinstall it
EDIT: Also the file manually moved may need to be deleted/moved back

Hal isn't even being used any longer.

ewaller · 2012-07-15 00:59:15

nomorewindows wrote:

[Hal isn't even being used any longer.

Over the course of the day, I have realized that, apparently, it is.

fatboy · 2012-07-15 01:00:06

nomorewindows wrote:

Hal isn't even being used any longer.

I don't know, he seems to have it installed - at least it's there in /var/lib/pacman/local/

nomorewindows · 2012-07-15 01:02:04

I still had it from some time ago, but if it is missing in the repos, and installed on the machine, it's still there. I still had hal on my machine and had to remove it.

nomorewindows · 2012-07-15 01:03:20

Hy Ginsberg wrote:

Hi all. I followed the instructions in the DeveloperWiki for upgrading glibc, and found that hal owned the file /lib/udev/rules.d/90-hal.rules. I moved it to /usr/lib by hand (maybe a mistake) and removed the /lib/udev and /lib/udev/rules.d directories. But that is not good enough, because pacman still thinks that hal has some ownership of /lib. Pacman reports:

pacman -Qo /lib
error: cannot determine ownership of '/lib'

and

grep '^lib/' /var/lib/pacman/local/*/files

yields

/var/lib/pacman/local/glibc-2.15-11/files:lib/
/var/lib/pacman/local/glibc-2.15-11/files:lib/ld-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/ld-linux.so.2
/var/lib/pacman/local/glibc-2.15-11/files:lib/libBrokenLocale-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libBrokenLocale.so.1
/var/lib/pacman/local/glibc-2.15-11/files:lib/libSegFault.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libanl-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libanl.so.1
/var/lib/pacman/local/glibc-2.15-11/files:lib/libc-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libc.so.6
/var/lib/pacman/local/glibc-2.15-11/files:lib/libcidn-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libcidn.so.1
/var/lib/pacman/local/glibc-2.15-11/files:lib/libcrypt-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libcrypt.so.1
/var/lib/pacman/local/glibc-2.15-11/files:lib/libdl-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libdl.so.2
/var/lib/pacman/local/glibc-2.15-11/files:lib/libm-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libm.so.6
/var/lib/pacman/local/glibc-2.15-11/files:lib/libmemusage.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnsl-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnsl.so.1
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_compat-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_compat.so.2
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_db-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_db.so.2
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_dns-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_dns.so.2
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_files-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_files.so.2
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_hesiod-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_hesiod.so.2
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_nis-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_nis.so.2
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_nisplus-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_nisplus.so.2
/var/lib/pacman/local/glibc-2.15-11/files:lib/libpcprofile.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libpthread-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libpthread.so.0
/var/lib/pacman/local/glibc-2.15-11/files:lib/libresolv-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libresolv.so.2
/var/lib/pacman/local/glibc-2.15-11/files:lib/librt-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/librt.so.1
/var/lib/pacman/local/glibc-2.15-11/files:lib/libthread_db-1.0.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libthread_db.so.1
/var/lib/pacman/local/glibc-2.15-11/files:lib/libutil-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libutil.so.1
/var/lib/pacman/local/hal-0.5.14-6/files:lib/
/var/lib/pacman/local/hal-0.5.14-6/files:lib/udev/
/var/lib/pacman/local/hal-0.5.14-6/files:lib/udev/rules.d/
/var/lib/pacman/local/hal-0.5.14-6/files:lib/udev/rules.d/90-hal.rules

So, no surprise (in retrospect), I didn't fool pacman by moving the files by hand.

And so the bottom line, I still can't install glibc. The rest of my system is upgraded -- pacman -Syu shows only glibc out of date. Any suggestions as to how to proceed would be much appreciated.

- Hy

It might be time for the LiveCD to the rescue! (even though you haven't messed up your machine---yet)
Removing the /lib directory in lieu of placing a sym-link for /usr/lib will in fact leave the machine hosed. Doesn't seem to be any way around it. Or removing the current glibc so that the new glibc can be installed will cause the same thing to happen. Mileage seems to vary.

Last edited by nomorewindows (2012-07-15 01:10:01)

Squiddles · 2012-07-15 01:06:35

So I read the wiki about the upgrade with /lib and glibc conflicting and I ran into such confliction during the second step.

pacman -Su

After running the first command listed, I get back:

error: cannot determine ownership of directory '/lib'
error: cannot determine ownership of directory '/lib/modules'
error: cannot determine ownership of directory '/lib/modules/extramodules-3.4-ARCH'
error: No package owns /lib/modules/extramodules-3.4-ARCH/fglrx.ko.gz
error: cannot determine ownership of directory '/lib/modules/extramodules-2.6.32-lts'
error: No package owns /lib/modules/extramodules-2.6.32-lts/fglrx.ko
error: cannot determine ownership of directory '/lib/modules/extramodules-3.2-ARCH'
error: No package owns /lib/modules/extramodules-3.2-ARCH/fglrx.ko
error: cannot determine ownership of directory '/lib/modules/3.0-ARCH'
error: No package owns /lib/modules/3.0-ARCH/modules.seriomap
error: No package owns /lib/modules/3.0-ARCH/modules.softdep
error: No package owns /lib/modules/3.0-ARCH/modules.alias.bin
error: No package owns /lib/modules/3.0-ARCH/modules.symbols
error: No package owns /lib/modules/3.0-ARCH/modules.alias
error: No package owns /lib/modules/3.0-ARCH/modules.symbols.bin
error: No package owns /lib/modules/3.0-ARCH/modules.dep
error: No package owns /lib/modules/3.0-ARCH/modules.pcimap
error: No package owns /lib/modules/3.0-ARCH/modules.inputmap
error: No package owns /lib/modules/3.0-ARCH/modules.isapnpmap
error: cannot determine ownership of directory '/lib/modules/3.0-ARCH/misc'
error: No package owns /lib/modules/3.0-ARCH/misc/vboxdrv.ko
error: No package owns /lib/modules/3.0-ARCH/misc/vboxnetadp.ko
error: No package owns /lib/modules/3.0-ARCH/misc/vboxnetflt.ko
error: No package owns /lib/modules/3.0-ARCH/misc/vboxpci.ko
error: No package owns /lib/modules/3.0-ARCH/modules.devname
error: No package owns /lib/modules/3.0-ARCH/modules.dep.bin
error: No package owns /lib/modules/3.0-ARCH/modules.ccwmap
error: No package owns /lib/modules/3.0-ARCH/modules.usbmap
error: No package owns /lib/modules/3.0-ARCH/modules.ieee1394map
error: No package owns /lib/modules/3.0-ARCH/modules.ofmap
error: cannot determine ownership of directory '/lib/modules/extramodules-3.3-ARCH'
error: No package owns /lib/modules/extramodules-3.3-ARCH/fglrx.ko
error: cannot determine ownership of directory '/lib/modules/3.2.6-2-ARCH'
error: No package owns /lib/modules/3.2.6-2-ARCH/modules.softdep
error: No package owns /lib/modules/3.2.6-2-ARCH/modules.alias.bin
error: No package owns /lib/modules/3.2.6-2-ARCH/modules.symbols
error: No package owns /lib/modules/3.2.6-2-ARCH/modules.alias
error: No package owns /lib/modules/3.2.6-2-ARCH/modules.symbols.bin
error: No package owns /lib/modules/3.2.6-2-ARCH/modules.dep
error: No package owns /lib/modules/3.2.6-2-ARCH/modules.builtin.bin
error: No package owns /lib/modules/3.2.6-2-ARCH/modules.devname
error: No package owns /lib/modules/3.2.6-2-ARCH/modules.dep.bin
error: cannot determine ownership of directory '/lib/modules/extramodules-3.1-ARCH'
error: No package owns /lib/modules/extramodules-3.1-ARCH/fglrx.ko
error: cannot determine ownership of directory '/lib/modules/3.0.21-1-lts'
error: No package owns /lib/modules/3.0.21-1-lts/modules.softdep
error: No package owns /lib/modules/3.0.21-1-lts/modules.alias.bin
error: No package owns /lib/modules/3.0.21-1-lts/modules.symbols
error: No package owns /lib/modules/3.0.21-1-lts/modules.alias
error: No package owns /lib/modules/3.0.21-1-lts/modules.symbols.bin
error: No package owns /lib/modules/3.0.21-1-lts/modules.dep
error: No package owns /lib/modules/3.0.21-1-lts/modules.builtin.bin
error: No package owns /lib/modules/3.0.21-1-lts/modules.devname
error: No package owns /lib/modules/3.0.21-1-lts/modules.dep.bin
error: cannot determine ownership of directory '/lib/modules/3.1.9-2-ARCH'
error: No package owns /lib/modules/3.1.9-2-ARCH/modules.seriomap
error: No package owns /lib/modules/3.1.9-2-ARCH/modules.pcimap
error: No package owns /lib/modules/3.1.9-2-ARCH/modules.inputmap
error: No package owns /lib/modules/3.1.9-2-ARCH/modules.isapnpmap
error: No package owns /lib/modules/3.1.9-2-ARCH/modules.ccwmap
error: No package owns /lib/modules/3.1.9-2-ARCH/modules.usbmap
error: No package owns /lib/modules/3.1.9-2-ARCH/modules.ieee1394map
error: No package owns /lib/modules/3.1.9-2-ARCH/modules.ofmap
/lib/libnsl-2.16.so is owned by glibc 2.16.0-1
/lib/librt-2.16.so is owned by glibc 2.16.0-1
/lib/libthread_db.so.1 is owned by glibc 2.16.0-1
/lib/libnss_dns.so.2 is owned by glibc 2.16.0-1
/lib/libcrypt.so.1 is owned by glibc 2.16.0-1
/lib/libnss_nis.so.2 is owned by glibc 2.16.0-1
/lib/libanl.so.1 is owned by glibc 2.16.0-1
/lib/ld-2.16.so is owned by glibc 2.16.0-1
/lib/libBrokenLocale-2.16.so is owned by glibc 2.16.0-1
/lib/librt.so.1 is owned by glibc 2.16.0-1
/lib/libcrypt-2.16.so is owned by glibc 2.16.0-1
/lib/libpcprofile.so is owned by glibc 2.16.0-1
/lib/libnss_hesiod.so.2 is owned by glibc 2.16.0-1
/lib/libnss_db-2.16.so is owned by glibc 2.16.0-1
/lib/libthread_db-1.0.so is owned by glibc 2.16.0-1
/lib/libnss_hesiod-2.16.so is owned by glibc 2.16.0-1
/lib/libc-2.16.so is owned by glibc 2.16.0-1
/lib/libnss_compat-2.16.so is owned by glibc 2.16.0-1
/lib/libnss_nis-2.16.so is owned by glibc 2.16.0-1
/lib/libc.so.6 is owned by glibc 2.16.0-1
/lib/libnsl.so.1 is owned by glibc 2.16.0-1
/lib/libnss_files-2.16.so is owned by glibc 2.16.0-1
/lib/libcidn-2.16.so is owned by glibc 2.16.0-1
/lib/libm-2.16.so is owned by glibc 2.16.0-1
/lib/libresolv-2.16.so is owned by glibc 2.16.0-1
/lib/libutil-2.16.so is owned by glibc 2.16.0-1
/lib/libpthread-2.16.so is owned by glibc 2.16.0-1
/lib/libdl-2.16.so is owned by glibc 2.16.0-1
/lib/libnss_dns-2.16.so is owned by glibc 2.16.0-1
/lib/libSegFault.so is owned by glibc 2.16.0-1
/lib/libpthread.so.0 is owned by glibc 2.16.0-1
/lib/libnss_files.so.2 is owned by glibc 2.16.0-1
/lib/libnss_nisplus-2.16.so is owned by glibc 2.16.0-1
/lib/libm.so.6 is owned by glibc 2.16.0-1
/lib/libanl-2.16.so is owned by glibc 2.16.0-1
/lib/libnss_nisplus.so.2 is owned by glibc 2.16.0-1
/lib/libBrokenLocale.so.1 is owned by glibc 2.16.0-1
/lib/libresolv.so.2 is owned by glibc 2.16.0-1
/lib/libnss_db.so.2 is owned by glibc 2.16.0-1
/lib/libutil.so.1 is owned by glibc 2.16.0-1
/lib/libdl.so.2 is owned by glibc 2.16.0-1
/lib/libnss_compat.so.2 is owned by glibc 2.16.0-1
/lib/libmemusage.so is owned by glibc 2.16.0-1
/lib/libcidn.so.1 is owned by glibc 2.16.0-1
/lib/ld-linux-x86-64.so.2 is owned by glibc 2.16.0-1

If I understand the wiki correctly. I can just move the files owned by glibck to /usr/lib and ignore the other files or delete them manually (which appears to primarily be the modules folder), right?

Hy Ginsberg · 2012-07-15 01:08:59

Thanks -- I removed hal and then finished the upgrade successfully. There was no issue of reinstalling hal -- seems the package doesn't even exist anymore. Thanks again.

- Hy

nomorewindows · 2012-07-15 01:13:39

It looks like moving the files to the /usr/lib directory before upgrading and removing any other possible conflicts will allow a successful upgrade.

fatboy · 2012-07-15 01:16:19

nomorewindows wrote:

It looks like moving the files to the /usr/lib directory before upgrading and removing any other possible conflicts will allow a successful upgrade.

I think if you do that glibc will stop working. It's much better to simply look at and remove all offending files/packages (other that glibc), update, then reinstall whatever is required.

Squiddles · 2012-07-15 01:32:28

nomorewindows wrote:

It looks like moving the files to the /usr/lib directory before upgrading and removing any other possible conflicts will allow a successful upgrade.

Well, after moving the files it appears as though I can't do anything. No programs launch and none of the terminal commands work. So I'm unsure what's going on now.

fatboy · 2012-07-15 01:46:39

Squiddles wrote:

nomorewindows wrote:
It looks like moving the files to the /usr/lib directory before upgrading and removing any other possible conflicts will allow a successful upgrade.
Well, after moving the files it appears as though I can't do anything. No programs launch and none of the terminal commands work. So I'm unsure what's going on now.

Yes, that's because almost everything depends on glibc, but by manually moving it you have broken it. Now it's time for some livecd wizardry I have no idea about.

Like I said before it's much simpler to just look at the extra files/packages (other than glibc), remove them, update, then reinstall whatever is necessary. It's all there in the wiki.

In your specific case the wiki even states that:

One common source of files in /lib is left overs from running depmod on a kernel update. For example:
error: No package owns /lib/modules/3.1.9-2-ARCH/modules.*
If no other files are in /lib/modules, you can safely remove that directory.

And as for fglrx, you simply remove catalyst, then reinstall it after the update.

Squiddles · 2012-07-15 01:51:27

fatboy wrote:

Squiddles wrote:
nomorewindows wrote:
It looks like moving the files to the /usr/lib directory before upgrading and removing any other possible conflicts will allow a successful upgrade.
Well, after moving the files it appears as though I can't do anything. No programs launch and none of the terminal commands work. So I'm unsure what's going on now.
Yes, that's because almost everything depends on glibc, but by manually moving it you have broken it. Now it's time for some livecd wizardry I have no idea about.
Like I said before it's much simpler to just look at the extra files/packages (other than glibc), remove them, update, then reinstall whatever is necessary. It's all there in the wiki.
In your specific case the wiki even states that:
One common source of files in /lib is left overs from running depmod on a kernel update. For example:
error: No package owns /lib/modules/3.1.9-2-ARCH/modules.*
If no other files are in /lib/modules, you can safely remove that directory.
And as for fglrx, you simply remove catalyst, then reinstall it after the update.

I suppose I need to use chroot and move some things around and try an update again and I've done all that I can do without rebooting the system. That I think I need some instruction on as I don't ever use it.

Arch Linux

#1 2012-07-14 18:38:31

glibc update refusing to proceed. File ownership problem

#2 2012-07-14 18:41:45

Re: glibc update refusing to proceed. File ownership problem

#3 2012-07-14 21:27:33

Re: glibc update refusing to proceed. File ownership problem

#4 2012-07-14 21:32:03

Re: glibc update refusing to proceed. File ownership problem

#5 2012-07-14 21:36:54

Re: glibc update refusing to proceed. File ownership problem

#6 2012-07-14 21:44:48

Re: glibc update refusing to proceed. File ownership problem

#7 2012-07-14 22:04:22

Re: glibc update refusing to proceed. File ownership problem

#8 2012-07-14 22:09:37

Re: glibc update refusing to proceed. File ownership problem

#9 2012-07-15 00:30:23

Re: glibc update refusing to proceed. File ownership problem

#10 2012-07-15 00:46:00

Re: glibc update refusing to proceed. File ownership problem

#11 2012-07-15 00:49:40

Re: glibc update refusing to proceed. File ownership problem

#12 2012-07-15 00:53:26

Re: glibc update refusing to proceed. File ownership problem

#13 2012-07-15 00:54:05

Re: glibc update refusing to proceed. File ownership problem

#14 2012-07-15 00:56:33

Re: glibc update refusing to proceed. File ownership problem

#15 2012-07-15 00:59:15

Re: glibc update refusing to proceed. File ownership problem

#16 2012-07-15 01:00:06

Re: glibc update refusing to proceed. File ownership problem

#17 2012-07-15 01:02:04

Re: glibc update refusing to proceed. File ownership problem

#18 2012-07-15 01:03:20

Re: glibc update refusing to proceed. File ownership problem

#19 2012-07-15 01:06:35

Re: glibc update refusing to proceed. File ownership problem

#20 2012-07-15 01:08:59

Re: glibc update refusing to proceed. File ownership problem

#21 2012-07-15 01:13:39

Re: glibc update refusing to proceed. File ownership problem

#22 2012-07-15 01:16:19

Re: glibc update refusing to proceed. File ownership problem

#23 2012-07-15 01:32:28

Re: glibc update refusing to proceed. File ownership problem

#24 2012-07-15 01:46:39

Re: glibc update refusing to proceed. File ownership problem

#25 2012-07-15 01:51:27

Re: glibc update refusing to proceed. File ownership problem

Board footer