Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#30906 - [glibc] Major problems after last update
Attached to Project:
Arch Linux
Opened by Piotr Żurek (Phitherek_) - Sunday, 29 July 2012, 09:37 GMT
Last edited by Pierre Schmitz (Pierre) - Sunday, 29 July 2012, 09:48 GMT
Opened by Piotr Żurek (Phitherek_) - Sunday, 29 July 2012, 09:37 GMT
Last edited by Pierre Schmitz (Pierre) - Sunday, 29 July 2012, 09:48 GMT
|
DetailsDescription:
During update, glibc tries to substitute /lib directory with a file, which prevents it from updating. After forcing its update, it causes major problems, such as inability to run any command, kernel panic and inability to run mount and udevadm during early boot due to missing symlinks and segfault error. Additional info: glibc 2.16.0-2 Steps to reproduce: 1. Run an update on a system with glibc version before 2.16.0-2 2. Try to run any command and to reboot the system |
This task depends upon
Comment by Simon Gomizelj (simongmzlj) -
Sunday, 29 July 2012, 09:40 GMT
So failing to read instructions is a bug now? They explictly said *not* to use --force, which is pretty much a warrenty breaker in the first place.