D. wrote:libc.so.6 was the problem for me as well. Removing it cleared the way for pacman. Now I'm just wondering what libc.so.6 was doing there...
Any chance that you had installed Matlab at some point? https://wiki.archlinux.org/index.php/Ma … s.2Ferrors
Good call. I have it installed at the moment, actually. Thanks!
]]>libc.so.6 was the problem for me as well. Removing it cleared the way for pacman. Now I'm just wondering what libc.so.6 was doing there...
Any chance that you had installed Matlab at some point? https://wiki.archlinux.org/index.php/Ma … s.2Ferrors
]]>allan m. is the maintainer for glibc. he's a very reasonable guy...does he recommend forcing?
DO NOT FORCE!!!!
You have some file you put in /lib64 causing the issues. "pacman -Qo /lib64/*" to find out what you need to remove.
]]>there is almost nothing in the /lib64/. directory on my system (only 3 files), but this sort of seems like a problem for which one should wait a little while rather than trying to guess a fix without better understanding what the maintainer had in mind.
but if anyone has gotten around the problem and suffered no ill effects, please let us know what you did...
Like you, I had almost nothing in /lib64 prior to this update. After moving those files and successfully updating glibc, my entire /lib64 directory is now symlinked to /lib. That's a big change.
Maybe my setup is unique for some reason, or this may be a big-ticket update that is discussed on the mailing list. I'm not able to consult it right now (and, truth be known, don't usually do so, since I get most of my Arch info right here on the forum these days).
Apparently the update doesn't expect to find anything in /lib64 and fails if it does.
]]>but if anyone has gotten around the problem and suffered no ill effects, please let us know what you did...
]]>You probably have some files in /lib64 that don't belong to the glibc package. Get rid of them. "pacman -Ql | grep /lib64" should tell you which package is at fault.
Spot on. I had some old kde4 files in there. I dropped kde several months back. Zapping that /lib64/kde4 directory solved the problem.
Thanks very much. The clouds have dissipated, the sun is shining, and all's right with the world.
Thread marked [SOLVED].
]]>in fact i suspect a great number of people are having the exact same problem. i'm sure it will right itself soon enough.
Yes, I imagine you're right. Arch's rolling release system is probably just passing through a brief zone of turbulence.
]]>and by the way i am having the same problem...
I'm so glad to hear that. Umm ... I don't mean that the way it sounds.
Maybe Allan will weigh in soon. Meanwhile, I'm sitting tight.
]]>error: extract: not overwriting dir with file lib64
error: problem occurred while upgrading glibc
It looks like overwriting that entire directory is a no-no. If other people are not getting this same error, though, I must have done something bizarre in the past. I have an evil alter-ego who sometimes gets on my machine late at night and tries to bork my system.
]]>