Re: glibc update refusing to proceed. File ownership problem

I am Gianluca wrote:

Is there a way to recognise which files I moved? They were about 15.

You have posted your find-output for /lib. So move everything back that is owned by glibc. To get a working system again, a symlink from /lib/ld-linux.so.2 to /usr/lib/ld-2.16.so is probably enough, but then you will have errors when upgrading glibc. If you force the update then, it could work, but I don't know if that is a good idea.

Re: glibc update refusing to proceed. File ownership problem

I have my own way of solving the problem:try to:1. pacman -Syu --ignore glbc2. cp /lib/* /usr/lib/ (or copy with mc, if you have a directory with files in )3. pacman -S --force glibc

what do you think about it?

Why would you do this given that the wiki explicitly says NOT to force the upgrade of glibc?

Even if it works now, it will not be as clean and I'm guessing could give you issues later because you will have moved a bunch of stuff from /lib/ to /usr/lib/ rather than taking care of it properly. For example, you will have moved /lib/modules/, files left over from packages you no longer have installed, stuff from AUR which has not been properly updated...

Re: glibc update refusing to proceed. File ownership problem

progandy wrote:

I am Gianluca wrote:

Is there a way to recognise which files I moved? They were about 15.

You have posted your find-output for /lib. So move everything back that is owned by glibc. To get a working system again, a symlink from /lib/ld-linux.so.2 to /usr/lib/ld-2.16.so is probably enough, but then you will have errors when upgrading glibc. If you force the update then, it could work, but I don't know if that is a good idea.

Ok. Now the problem is how move everything back to /lib?I couldn't start any program except LibreOffice. So, I've restarted the system thinking that I could use the console. Unfortunately I've encountered a kernel panic during the boot.

Note that pacman is aliased to pacmatic so I used \pacman to get the original command. (pacmatic follows pacman and also says apache-ant.)

I don't understand why. It is very odd. Perhaps somebody who knows something about pacman could explain it?

EDIT: Note that my upgrade was perfectly smooth. I did need to read the notes on the Developers' wiki and use a couple of the techniques there, but nothing untoward happened and the final upgrade of glibc proceeded without incident. Machine rebooted fine afterwards. System seems happy. (Or no more unhappy than before, anyway. )

Re: glibc update refusing to proceed. File ownership problem

cfr wrote:

because you will have moved a bunch of stuff

Im not moved - im a copy. if you moved files from /lib to somewhere - it will break the system, because system will "lost" files from /lib, because, after upgrade glibc -system will be search lib's in /usr/lib, because after upgrade /lib will be a symlink to /usr/lib.if you copy files, then, after "upgrade glibc with --force" the pacman also will removed /lib and create "lib -> /usr/lib", but in this case, system can find required libraries in /usr/lib.

Re: glibc update refusing to proceed. File ownership problem

killer1804 wrote:

cfr wrote:

because you will have moved a bunch of stuff

Im not moved - im a copy. if you moved files from /lib to somewhere - it will break the system, because system will "lost" files from /lib, because, after upgrade glibc -system will be search lib's in /usr/lib, because after upgrade /lib will be a symlink to /usr/lib.if you copy files, then, after "upgrade glibc with --force" the pacman also will removed /lib and create "lib -> /usr/lib", but in this case, system can find required libraries in /usr/lib.

Yes, but post-upgrade they have effectively been moved. So instead of clearing up the contents of /lib/modules or files from ufw/hal/udev-compat, for example, you will have moved everything to /usr/lib/. You are effectively chucking your neglected laundry into a cupboard rather than doing the washing. The room will look just as tidy but your smelly socks are still there somewhere.

Re: glibc update refusing to proceed. File ownership problem

I am Gianluca wrote:

progandy wrote:

I am Gianluca wrote:

Is there a way to recognise which files I moved? They were about 15.

You have posted your find-output for /lib. So move everything back that is owned by glibc. To get a working system again, a symlink from /lib/ld-linux.so.2 to /usr/lib/ld-2.16.so is probably enough, but then you will have errors when upgrading glibc. If you force the update then, it could work, but I don't know if that is a good idea.

Re: glibc update refusing to proceed. File ownership problem

cfr wrote:

The room will look just as tidy but your smelly socks are still there somewhere.

Yes, but we can do something like "pacman -Qo /lib/* | grep -v glibc", uninstall (whis pacman -R %pakegename%) all non glib's librarys, and install them later, if we will need. Before copying glibc's librarys we can delet all garbage from /lib.I know the official way to upgrade glibc, but it was not help for me. Im delete all, other than glibc's libraries from /lib - but pacman still tell me "/lib is exists...", so that upgrading gone with the problems for me.

Re: glibc update refusing to proceed. File ownership problem

killer1804 wrote:

Yes, but we can do something like "pacman -Qo /lib/* | grep -v glibc", uninstall (whis pacman -R %pakegename%) all non glib's librarys, and install them later, if we will need. Before copying glibc's librarys we can delet all garbage from /lib.

That is much better but I didn't see you mention this step originally. Unless I missed it, my objection was primarily to your instructions as stated.

I know the official way to upgrade glibc, but it was not help for me. Im delete all, other than glibc's libraries from /lib - but pacman still tell me "/lib is exists...", so that upgrading gone with the problems for me.

That suggests something odd was happening. If you'd uninstalled whatever had stuff under /lib except glibc, what exactly was it complaining about? Did you have stuff which wasn't owned at all? (I did and I dealt with those files on a case-by-case basis.)

The point is that you shouldn't NEED to force the upgrade of glibc so if you are finding you can't upgrade otherwise, there has to be some reason for that and I think it would be better to address that issue rather than utilising your work around. I accept that your solution is better than most of the other things which people have arbitrarily tried but I don't think it is as satisfactory as following the procedures suggested in the wiki and taking the time to figure out any wrinkles.

Re: glibc update refusing to proceed. File ownership problem

Re: glibc update refusing to proceed. File ownership problem

Alternatively, if you want a more "safe" method, you can examine the content of the folder and remove the packages. In my case, the content belonged to packages "linux" and "nvidia", which I solved using:

Re: glibc update refusing to proceed. File ownership problem

Arctus wrote:

Alternatively, if you want a more "safe" method, you can examine the content of the folder and remove the packages. In my case, the content belonged to packages "linux" and "nvidia", which I solved using:

Re: glibc update refusing to proceed. File ownership problem

cfr wrote:

That suggests something odd was happening. If you'd uninstalled whatever had stuff under /lib except glibc, what exactly was it complaining about? Did you have stuff which wasn't owned at all? (I did and I dealt with those files on a case-by-case basis.)

Well...now I think the problem was that I did not delete the directory "modules" from /lib.Im try to "pacman -S glibc", but take an pacman's error "/lib is exists"After that i take a mistake - i moved stuff from /lib to /usr/lib and broke my Arch.After that im boot up from my usb-disk and make a symlink from /usr/lib to /lib, boot to arch and make pacman -S glibc, pacman tell me something like "libc-2.16.so is exist", and im do "pacman -S --force glibc" - now its will work, but were problems whis kde - kde's settings is gone to default.Now all seems fine, and work properly After that im login to my test machine and try solution, which suggested.Upgrading system on test machine will passed with no problems.

Re: glibc update refusing to proceed. File ownership problem

Hi again (my previous post was by guest53290),everything is ok now! I booted an live cd and did a pacman -r /mnt -U /var/cache/pacman/pkg/glibc-2.16.0-2-x86_64.pkg.tar.xz rebooted and now more kernel panic!Cheers