glibc update refusing to proceed. File ownership problem

webmasteryoda · 2012-07-20 22:33:55

jasonwryan wrote:

webmasteryoda wrote:
Nope. This one isnt. Look again.
/lib/ld-lsb.so.3 is owned by ld-lsb 3-3
So, what do I have to do with this file? I tried to move it to another directory, but that didnt solved my problem.

It's an AUR package. Unistall it, finish the upgrade and then rebuild it.

That solved my problem. Thanks!

nomorewindows · 2012-07-20 22:35:51

webmasteryoda wrote:

Nope. This one isnt. Look again.
/lib/ld-lsb.so.3 is owned by ld-lsb 3-3
So, what do I have to do with this file? I tried to move it to another directory, but that didnt solved my problem.
pacman -Su gives me:
error: failed to commit transaction (conflicting files)
glibc: /lib exists in filesystem
Errors occurred, no packages were upgraded.

pacman -R ld-lsb
(Don't worry if you don't have the package file, it might need an update, but in either case, it will just be reinstalled after the glibc gets placed where it belongs).
Don't forget to put it back.

webmasteryoda · 2012-07-20 22:38:44

nomorewindows wrote:

webmasteryoda wrote:
Nope. This one isnt. Look again.
/lib/ld-lsb.so.3 is owned by ld-lsb 3-3
So, what do I have to do with this file? I tried to move it to another directory, but that didnt solved my problem.
pacman -Su gives me:
error: failed to commit transaction (conflicting files)
glibc: /lib exists in filesystem
Errors occurred, no packages were upgraded.
pacman -R ld-lsb
(Don't worry if you don't have the package file, it might need an update, but in either case, it will just be reinstalled after the glibc gets placed where it belongs).
Don't forget to put it back.

Yap. As I already said, that solved my problem. Thanks mate. Arch is fully updated again

nomorewindows · 2012-07-20 22:40:40

Nasenbaer wrote:

Hi,
I have a huge problem with my arch linux system (amd64). I upgraded my packages and glibc had a conflict, therefore I tried to upgrade it alone. So I did
$ pacman -Su glibc
and got the message that it can't be updated, because /lib already exists. So i thought "yeah I know that /lib exists, whatever .." and did
$ pacman -Suf glibc
and the update went fine I thought. But since that time I can not run any command. All daemons, which where already up, were still working but I can not run a command and can't connect via ssh etc.
So I hard-resetted the system and tried to boot arch linux again. Now I get a kernel panic because /sbin/init wasn't found. The problem is, that init is still there (checked it using a rescue-CD).

Any hints how I can proceed without having to backup the system and every config file by hand and reinstalling arch?

What does it show in your /lib now and is it a symlink?
You can probably use the LiveCD to run pacman again.
Also do a pacman -Qk glibc on your regular installation to see if there are any missing files.

cfr · 2012-07-20 23:51:57

I don't understand one thing, cfr told me to uninstall var/cache/pacman/pkg/glibc-2.16.0-1-i686.pkg.tar.xz. If I do it I wouldn't be able to find it 2 steps later for install the package another time.

I suggested *uninstalling* it - not removing it: that shouldn't remove the package from the cache - just from the system. Of course, you need to be booted from a live USB/CD to do this. Then you remove the symlink. Then you reinstall 2.16.0-1 from the package in the cache. This will recreate the directory /lib (rather than the symlink) and replace the original glibc files. Then you reboot and upgrade. At that point, everything should be as pacman expects so the upgrade should work fine.

EDIT: You probably could install 2.16.0-2 if the package is already on your system. Reboot and then run pacman -S glibc just to make sure. In that case, you probably don't need to remove the symlink.

Last edited by cfr (2012-07-20 23:55:11)

ecion · 2012-07-21 06:37:45

Hi guys, can I have some help with this one, please.
When running pacman -syu I get

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

I followed this wiki article; https://wiki.archlinux.org/index.php/De … iki:usrlib
On the final pacman -Su command I get the same error message.

Following the wiki, I ran grep '^lib/' /var/lib/pacman/local/*/files and get this back.

/var/lib/pacman/local/glibc-2.16.0-1/files:lib/
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/ld-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/ld-linux.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libBrokenLocale-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libBrokenLocale.so.1
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libSegFault.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libanl-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libanl.so.1
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libc-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libc.so.6
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libcidn-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libcidn.so.1
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libcrypt-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libcrypt.so.1
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libdl-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libdl.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libm-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libm.so.6
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libmemusage.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnsl-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnsl.so.1
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_compat-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_compat.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_db-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_db.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_dns-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_dns.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_files-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_files.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_hesiod-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_hesiod.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_nis-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_nis.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_nisplus-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_nisplus.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libpcprofile.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libpthread-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libpthread.so.0
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libresolv-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libresolv.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/librt-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/librt.so.1
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libthread_db-1.0.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libthread_db.so.1
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libutil-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/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

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

error: cannot determine ownership of directory '/lib'
/lib/libnss_files.so.2 is owned by glibc 2.16.0-1
/lib/ld-linux.so.2 is owned by glibc 2.16.0-1
/lib/libnsl.so.1 is owned by glibc 2.16.0-1
/lib/libpthread.so.0 is owned by glibc 2.16.0-1
/lib/libdl-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/libresolv.so.2 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/libcidn.so.1 is owned by glibc 2.16.0-1
/lib/libmemusage.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_nisplus.so.2 is owned by glibc 2.16.0-1
/lib/libc.so.6 is owned by glibc 2.16.0-1
/lib/libcrypt.so.1 is owned by glibc 2.16.0-1
/lib/libm-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/libnss_compat-2.16.so is owned by glibc 2.16.0-1
/lib/libm.so.6 is owned by glibc 2.16.0-1
/lib/libpthread-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/libnsl-2.16.so is owned by glibc 2.16.0-1
/lib/libnss_hesiod.so.2 is owned by glibc 2.16.0-1
/lib/libcrypt-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/libutil.so.1 is owned by glibc 2.16.0-1
/lib/libutil-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/libSegFault.so is owned by glibc 2.16.0-1
/lib/libanl.so.1 is owned by glibc 2.16.0-1
/lib/libnss_hesiod-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/libnss_dns.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/libnss_db.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/libpcprofile.so is owned by glibc 2.16.0-1
/lib/libc-2.16.so is owned by glibc 2.16.0-1
/lib/librt.so.1 is owned by glibc 2.16.0-1
error: cannot determine ownership of directory '/lib/udev'
error: cannot determine ownership of directory '/lib/udev/rules.d'
/lib/udev/rules.d/90-hal.rules is owned by hal 0.5.14-6
/lib/libnss_nis.so.2 is owned by glibc 2.16.0-1
/lib/libnss_files-2.16.so is owned by glibc 2.16.0-1
/lib/libanl-2.16.so is owned by glibc 2.16.0-1
/lib/libBrokenLocale.so.1 is owned by glibc 2.16.0-1
error: cannot determine ownership of directory '/lib/modules'
error: cannot determine ownership of directory '/lib/modules/2.6.34-ARCH'
/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

But I dont know what I'm suppose to do with these files, the wiki article isn't clear.
I'm assuming i need to sort out the file thats own by hal. I understand from the wiki that hal is no longer supported, but I cannot remove it because thunar-vfs depends upon it.

Last edited by ecion (2012-07-21 06:40:34)

jasonwryan · 2012-07-21 06:48:25

ecion wrote:

I understand from the wiki that hal is no longer supported, but I cannot remove it because thunar-vfs depends upon it.

Well, it seems your choice is a simple one...

arieaja123 · 2012-07-21 07:04:03

I just followed the tutorial from the link http://
allanmcrae.com,
then, when I do the command 'pacman-Su' and comes the error as below.

error: GPGME error: Inappropriate ioctl for device
error: glibc: missing required signature
error: failed to commit transaction (invalid or
corrupted
package (PGP signature))
Errors occurred, no packages were upgraded.

I've been doing the command "pacman-key --init ',
then I do the command' pacman-Su '. But appear the
same error.

then, what should I do ?

Last edited by arieaja123 (2012-07-21 07:05:40)

LinuxFrenzy · 2012-07-21 07:12:14

Did you even do the next command?. pacman-key --populate archlinux

jasonwryan · 2012-07-21 07:12:56

Read this page to the end: https://wiki.archlinux.org/index.php/Pacman-key

Merging with the glbc stickied thread

arieaja123 · 2012-07-21 07:36:19

LinuxFrenzy wrote:

Did you even do the next command?. pacman-key --populate archlinux

Ok, i will test it tonight. I can't test it now, because I have not internet connections

PhotonX · 2012-07-21 09:14:09

Reporting from a sinking ship:

I successfully upgraded glibc on one install using this hint: https://bbs.archlinux.org/viewtopic.php … 9#p1129679

Now I wanted to make the same on the other install. But it failed somehow and now I don't even having a bash:

[photon@photon-desktop ~]$ sudo cp -r /lib/* /usr/lib/
[photon@photon-desktop ~]$ sudo mv /lib /bak_lib
[photon@photon-desktop ~]$ sudo ln -s /usr/lib /lib
bash: /usr/bin/sudo: Datei oder Verzeichnis nicht gefunden
[photon@photon-desktop ~]$ sudo su
bash: /usr/bin/sudo: Datei oder Verzeichnis nicht gefunden
[photon@photon-desktop ~]$ su
bash: /bin/su: Datei oder Verzeichnis nicht gefunden
[photon@photon-desktop ~]$ ls
bash: /bin/ls: Datei oder Verzeichnis nicht gefunden

I'll try to switch to TTY now, but don't have much hope. What did I screw up?

edit: As suspected, I couldn't log in in the TTY with agetty being not found. Where the heck are all bash commands?

edit2: Here's what the "Tab" completion gives:

$ cd bin/
awk              dnsdomainname    lsblk            pwd
bash             echo             mbchk            rm
bashbug          false            mkdir            rmdir
cat              findmnt          mknod            sed
chgrp            fusermount       more             sh
chmod            gawk             mount            stty
chown            groups           mountpoint       su
cp               hostname         mv               sync
dash             keyctl           netstat          tar
date             kill             pidof            true
dd               ln               ping             ulockmgr_server
df               login            ping6            umount
dmesg            ls               ps               uname

So either the tab completion is outdated or something other is wrong...

edit3: I can't even launch executables from my home dir which are surely still there. So it's not that all bash commands are gone but that they all cannot be executed.

Last edited by PhotonX (2012-07-21 09:24:06)

fatboy · 2012-07-21 09:25:38

PhotonX wrote:

[photon@photon-desktop ~]$ sudo cp -r /lib/* /usr/lib/
[photon@photon-desktop ~]$ sudo mv /lib /bak_lib

This is where the mistake is. Instead of manually moving lib and trying to create symlinks, the wiki guide should have been followed.

PhotonX · 2012-07-21 09:30:57

Oh, I see... Now, how do I fix this? I can't do anything from within the system and I suppose that if I chroot in it the result will be the same. So I have only file operations left which can be executed from within another system. I could just rename bak_lib to lib again, but will this help?

fatboy · 2012-07-21 09:33:08

Yes, I think renaming bak_lib to lib will help. Also perhaps you should remove (from /usr/lib) what was copied from /lib into /usr/lib before proceeding.

Last edited by fatboy (2012-07-21 09:37:46)

shiker · 2012-07-21 09:35:06

hi, posting my results, the conflicting packages were related to googleearth and gnomad2, and as for files, the whole directory modules and udev

whats i did was to remove those 2 dirs and:

pacman -R libnjb gnomad2
pacman -R ld-lsb google-earth

after that, i just reinstalled linux (the kernel)
pacman -S linux
just in case i'll restart to see if everything went ok

I am Gianluca · 2012-07-21 10:23:23

nomorewindows wrote:

First, are you running this from busybox or actually booting your system?
Hmm...unxz isn't in the initramfs, so unless there is xz compression support in the kernel itself, it would still be safe to try. I know for sure tar isn't available. Is your kernel/initramfs even have anything in the /lib directory? The newly built kernel with all of the glibc has been moved into /usr/lib.
The busybox method may not work too good, the LiveCD/USB/PXE may unfortunately be the only solution out of this. Even an old one with xz support either through tar or unxz/xz will get you something. You don't have to have the latest archiso to recover your system.
How are you getting the package file without mounting your /boot and root filesystem(s)?
Obviously you are using something to post on the bbs. Whatever you're using, could aid you in producing a LiveCD/USB,etc. if needed.

I run the system in this way:

1. Boot into GRUB and add "break=postmount" to the line that starts with "kernel"
2. Wait until you get dropped into a root shell
3. mount -o remount,rw /new_root
4. cd new_root

This get me in a shell with read-write access. By the way, I don`t have `sudo`, `pacman` and so on.
I`ve downloaded an ArchLinux ISO and today I`m going to create a bootable ISO. I`ve never recover my system through a LiveUSB, is there a guide somewhere?
To post on the forum I`m using my BlackBerry, although it`s anything but comfortable browse the forum by its small screen.

PhotonX · 2012-07-21 10:49:50

Thanks, I could update glibc now.

nomorewindows · 2012-07-21 11:35:29

I am Gianluca wrote:

nomorewindows wrote:
First, are you running this from busybox or actually booting your system?
Hmm...unxz isn't in the initramfs, so unless there is xz compression support in the kernel itself, it would still be safe to try. I know for sure tar isn't available. Is your kernel/initramfs even have anything in the /lib directory? The newly built kernel with all of the glibc has been moved into /usr/lib.
The busybox method may not work too good, the LiveCD/USB/PXE may unfortunately be the only solution out of this. Even an old one with xz support either through tar or unxz/xz will get you something. You don't have to have the latest archiso to recover your system.
How are you getting the package file without mounting your /boot and root filesystem(s)?
Obviously you are using something to post on the bbs. Whatever you're using, could aid you in producing a LiveCD/USB,etc. if needed.
I run the system in this way:
1. Boot into GRUB and add "break=postmount" to the line that starts with "kernel"
2. Wait until you get dropped into a root shell
3. mount -o remount,rw /new_root
4. cd new_root
This get me in a shell with read-write access. By the way, I don`t have `sudo`, `pacman` and so on.
I`ve downloaded an ArchLinux ISO and today I`m going to create a bootable ISO. I`ve never recover my system through a LiveUSB, is there a guide somewhere?
To post on the forum I`m using my BlackBerry, although it`s anything but comfortable browse the forum by its small screen.

This will be your better bet:
https://wiki.archlinux.org/index.php/In … _a_USB_key
Notice that cfr responded back to you and has said the same thing.

Strike0 · 2012-07-21 13:27:59

nomorewindows wrote:

I am Gianluca wrote:
I`ve downloaded an ArchLinux ISO and today I`m going to create a bootable ISO. I`ve never recover my system through a LiveUSB, is there a guide somewhere?
To post on the forum I`m using my BlackBerry, although it`s anything but comfortable browse the forum by its small screen.
This will be your better bet:
https://wiki.archlinux.org/index.php/In … _a_USB_key
Notice that cfr responded back to you and has said the same thing.

Correct me if wrong please: Rather than installing Arch on a USB I think cfr (#230) meant using any Arch liveISO and then "chroot"-ing to the broken system. The wiki would be: https://wiki.archlinux.org/index.php/Chroot
You do the steps until before network/resolv.conf mentioned there, then you have the root console you need on the broken system to use pacman with the existing cache of packages.

Nasenbaer · 2012-07-21 14:08:12

Isola wrote:

First of all: Don't use --force!
Second: Read this for possible solutions
https://wiki.archlinux.org/index.php/De … iki:usrlib
And third: Setup a RSS reader so you don't miss those important announcements in the future!
http://www.archlinux.org/news/the-lib-d … a-symlink/

Thanks for the links. System runs flawlessly again. And I set up the feed to (hopefully) not get into such trouble in future.

nomorewindows · 2012-07-21 14:20:18

Strike0 wrote:

nomorewindows wrote:
I am Gianluca wrote:
I`ve downloaded an ArchLinux ISO and today I`m going to create a bootable ISO. I`ve never recover my system through a LiveUSB, is there a guide somewhere?
To post on the forum I`m using my BlackBerry, although it`s anything but comfortable browse the forum by its small screen.
This will be your better bet:
https://wiki.archlinux.org/index.php/In … _a_USB_key
Notice that cfr responded back to you and has said the same thing.
Correct me if wrong please: Rather than installing Arch on a USB I think cfr (#230) meant using any Arch liveISO and then "chroot"-ing to the broken system. The wiki would be: https://wiki.archlinux.org/index.php/Chroot
You do the steps until before network/resolv.conf mentioned there, then you have the root console you need on the broken system to use pacman with the existing cache of packages.

Yeah, even an old iso will/should work.
I think they even had a install USB image as well as an ISO.
So LiveCD/USB/PXE whatever it takes to get in there.
If you're using an archiso, pacman is on there, and you don't have to chroot. Just have to know how to use pacman. If it's a kernel you're having then yeah, you need to chroot.
I'm vaguely familiar with the busybox method, I haven't used the break parameter, but in my experience, if it's not on the initramfs or a mountable partition it needs a RescueCD of some ssort.

azripah · 2012-07-21 21:36:07

Yeah, disregard my post. Despite some googling, I only found this thread as mine was merged.

@carukia

A link rather than a condescending remark was the appropriate response.

Last edited by azripah (2012-07-21 21:43:41)

carukia · 2012-07-21 21:38:50

There's countless threads about this. Reading them would be a good idea.

jasonwryan · 2012-07-21 21:39:28

You have removed your linker. The wiki page has a couple of solutions to fix your issue.

Lesson to learn: only ever use the --force if you are explicitly told to so so.

Merging with the stickied glibc thread

Arch Linux

#251 2012-07-20 22:33:55

Re: glibc update refusing to proceed. File ownership problem

#252 2012-07-20 22:35:51

Re: glibc update refusing to proceed. File ownership problem

#253 2012-07-20 22:38:44

Re: glibc update refusing to proceed. File ownership problem

#254 2012-07-20 22:40:40

Re: glibc update refusing to proceed. File ownership problem

#255 2012-07-20 23:51:57

Re: glibc update refusing to proceed. File ownership problem

#256 2012-07-21 06:37:45

Re: glibc update refusing to proceed. File ownership problem

#257 2012-07-21 06:48:25

Re: glibc update refusing to proceed. File ownership problem

#258 2012-07-21 07:04:03

Re: glibc update refusing to proceed. File ownership problem

#259 2012-07-21 07:12:14

Re: glibc update refusing to proceed. File ownership problem

#260 2012-07-21 07:12:56

Re: glibc update refusing to proceed. File ownership problem

#261 2012-07-21 07:36:19

Re: glibc update refusing to proceed. File ownership problem

#262 2012-07-21 09:14:09

Re: glibc update refusing to proceed. File ownership problem

#263 2012-07-21 09:25:38

Re: glibc update refusing to proceed. File ownership problem

#264 2012-07-21 09:30:57

Re: glibc update refusing to proceed. File ownership problem

#265 2012-07-21 09:33:08

Re: glibc update refusing to proceed. File ownership problem

#266 2012-07-21 09:35:06

Re: glibc update refusing to proceed. File ownership problem

#267 2012-07-21 10:23:23

Re: glibc update refusing to proceed. File ownership problem

#268 2012-07-21 10:49:50

Re: glibc update refusing to proceed. File ownership problem

#269 2012-07-21 11:35:29

Re: glibc update refusing to proceed. File ownership problem

#270 2012-07-21 13:27:59

Re: glibc update refusing to proceed. File ownership problem

#271 2012-07-21 14:08:12

Re: glibc update refusing to proceed. File ownership problem

#272 2012-07-21 14:20:18

Re: glibc update refusing to proceed. File ownership problem

#273 2012-07-21 21:36:07

Re: glibc update refusing to proceed. File ownership problem

#274 2012-07-21 21:38:50

Re: glibc update refusing to proceed. File ownership problem

#275 2012-07-21 21:39:28

Re: glibc update refusing to proceed. File ownership problem

Board footer