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#30683 - [glibc] PLEASE ENTER SUMMARY
Attached to Project:
Arch Linux
Opened by Eugene L (lava) - Sunday, 15 July 2012, 06:12 GMT
Last edited by Allan McRae (Allan) - Sunday, 15 July 2012, 06:52 GMT
Opened by Eugene L (lava) - Sunday, 15 July 2012, 06:12 GMT
Last edited by Allan McRae (Allan) - Sunday, 15 July 2012, 06:52 GMT
|
DetailsDescription:
Not sure if this bug relates to glibc package or pacman, but update of glibc was unsuccesfull this morning and have broke me the system. Additional info: * package version(s) glibc 2.16.0-2 Steps to reproduce: 1. Use ArchLinux x64 2. Be updated (I've had glibc 2.16.0-1 and all other stuff have been up-to-date til 14th of July) 3. Start upgrade: pacman -Syu ERROR: Directory 'lib' already exists 4. Remember thoose kind of errors usually being fixed with force: pacman -Syuf ERROR: [2012-07-15 08:12] error: problem occurred while upgrading glibc [2012-07-15 08:12] call to execv failed (No such file or directory) [2012-07-15 08:12] upgraded glibc (2.16.0-1 -> 2.16.0-2) # Other packages have not been updated # X doesn't start 5. Panic, reboot ERROR: Couldn't init kernel, says, there is no init Fixing: 1. Reboot to fallback init=/bin/bash 2. mount -o rw,remount /new_root 3. untar glibc-2.16.0-2 to /new_root (have overriden PATH and LD_LIBRARY_PATH to point at software (xz won't load wo LD_LIBRARY_PATH) in /new_root [chroot wasn't starting for some reason]) ERROR: Directory 'lib' already exists 4. cp -r <unpacked_glibc>/lib/* /new_root/lib/ # Success 5. Reboot # It works 6. Go to bugs.archlinux.org to see if someone has this problem, fill the ticket for glibc just in case if anyone meet similar issue and will look for solution. |
This task depends upon
Closed by Allan McRae (Allan)
Sunday, 15 July 2012, 06:52 GMT
Reason for closing: Not a bug
Additional comments about closing: -Syuf is pure stupidity
Sunday, 15 July 2012, 06:52 GMT
Reason for closing: Not a bug
Additional comments about closing: -Syuf is pure stupidity
> Of course, this is great, that in News this article has been covered.A
> But as for me, for example, it was unknown(!) because I hadn't read even
> RSS since yesterday's morning and today have done upgrade from the morning
> even before starting X.
> Is there any way to provide such CRITICAL info during upgrade? Because I
> just can assume, I will not be the only one. And I filed the ticket for
> other people to help them load their system again without re-installation.
> Therefore, thanks for quick responce, I very appreciate this and all the
> whole Arch community.
>
> Also, I see, I forgot to enter SUMMARY (what a shame for a developer).
> Can't you please change the summary to "Forced upgrade of glibc breaks the
> system"?
or you could comment on the bug...
and use pacmatic which does this... or subscribe to arch-dev-public, or
arch-announce which will email you with the news... or you can read the
news before you just use -f ... or send an email to arch-general
or subscribe to the new rss feed... or google your error