You are not logged in.
Pages: 1
Today (2010-04-19), I run pacman -Syu to upgrade packages (from testing) in a (gnu) screen session as usual.
But when upgrading glibc (glibc-2.11.1-3-x86_64.pkg.tar.xz), error occurs:
Proceed with installation? [Y/n]
checking package integrity...
(34/34) checking for file conflicts [########################################################################################] 100%
( 1/34) upgrading linux-api-headers [########################################################################################] 100%
( 2/34) upgrading glibc [----------------------------------------------------------------------------------------] 0%
reopen fifo /tmp/screens/S-ffjia/2319.pts-1.southpark: No such file or directory
bash: /usr/bin/whoami: No such file or directory
bash: /bin/hostname: No such file or directory
bash: /usr/bin/tty: No such file or directory
bash: /usr/bin/basename: No such file or directory
And now I cannot use any command (including pacman) or start any new application. The entire system (except this pre-opend firefox) is broken
What can I do? Is there any way to avoid using livecd or usb flash drive to solve this problem?
Thanks in advcance
Offline
Ok, I'll reboot, and boot from usb drive, try to downgrade glibc....
Offline
pacman -r /mnt/root downgrade successfully, but I still don't know why this happened?
I am not sure this can be reproduced or not
Offline
Well glad you fixed it, but the mystery of the reproducibility remains until you actually tried it. You know how to fix it, so what's holding you back?
Also, moving to the appropriate location - this is x86_64 not i686.
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline
Due to this problem, I cannot even do a clean reboot, I'm concerned about data security.
Today, I try to update glibc and a bunch new packages, after re-generating locale, everything seems fine now.
I'm very confused .... and I cannot find other archers experiencing this problem
Offline
Lesson to learn here:
Don't mess with arch's file and directory structure unless you know what you're doing and are willing to accept the consequences.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
Lesson to learn here:
Don't mess with arch's file and directory structure unless you know what you're doing and are willing to accept the consequences.
Interesting... I have no idea where you got that lesson from...
Offline
Lesson to learn here:
Don't mess with arch's file and directory structure unless you know what you're doing and are willing to accept the consequences.
I did not mess with file structure, dude. I just upgraded some packages
Offline
did not mess with file structure, dude. I just upgraded some packages ... (from testing) ...
from the testing
It happens from time to time with beta code . be warned .
and "glibc " to boot that is one thing YOU DO NOT MESS WITH
that is like changing the version C:\\WINDOWS/system32\msvcrt.dll on a running system
Celestia maps
http://celestiamotherlode.net/catalog/s … ator_id=10
Offline
Woo... more misinformation... Now we should not do a "pacman -Syu" if we are using [testing] because it is beta code. Because an update was all that was done here. It is not as if he just went randomly deleting files on his system.
glibc in [testing] is compiled from the same code as glibc in [core], it is just built with a newer gcc. It is quite clear that a system upgrade was done and something went wrong with the glibc part. Unless you have an idea of what caused the crash of screen and thus killing of pacman during a glibc upgrade, do not just make up a reason.
Offline
from the testing
It happens from time to time with beta code . be warned .
and "glibc " to boot that is one thing YOU DO NOT MESS WITHthat is like changing the version C:\\WINDOWS/system32\msvcrt.dll on a running system
Then, I should never upgrade glic from testing?
I check the glibc.install file, no diff found with previous version
Offline
R00KIE wrote:Lesson to learn here:
Don't mess with arch's file and directory structure unless you know what you're doing and are willing to accept the consequences.Interesting... I have no idea where you got that lesson from...
From personal experience
There is a good chance that the OP changed something and forgot about it or didn't even consider the change as important. Glibc updates are spaced in time and it may seem that a small change is safe when it isn't.
In my case I have messed with /lib64 and the result was similar, that is why I said messing with arch's file and directory structure is a bad idea.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
Pages: 1