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#30135 - [glibc] glibc should depend on kernel
Attached to Project:
Arch Linux
Opened by Florian Mutter (elmulator) - Monday, 04 June 2012, 10:16 GMT
Last edited by Allan McRae (Allan) - Monday, 04 June 2012, 10:33 GMT
Opened by Florian Mutter (elmulator) - Monday, 04 June 2012, 10:16 GMT
Last edited by Allan McRae (Allan) - Monday, 04 June 2012, 10:33 GMT
|
DetailsDescription:
Today I updated an old machine of mine. Pacman suggested to first update pacman to version 4. While doing this it updated glibc to the latest version (2.15-10). This glibc version requires some newer kernel than mine (I'm not sure which version I have installed, maybe something like 2.6.27) but does not depend on it (meaning pacman depend here). After that update the system was totally broken and useless and reporter "FATAL: Kernel too old" for every command and right at boot time. I think this could be avoided by requiring the appropriate kernel version when installing glibc. This can also happen if someone decides just to install a new version of glibc without updating the hole system. A way to fix this is to try to find an old glibc package and try to install it from a live cd or something. I didn't try that yet and this is not an acceptable solution. For most people the system is dead and needs to be reinstalled. Additional info: glibc 2.15-10 Steps to reproduce: Find a machine running a 4 or so year old version of archlinux and follow the advice pacman gives you. |
This task depends upon
Closed by Allan McRae (Allan)
Monday, 04 June 2012, 10:33 GMT
Reason for closing: Not a bug
Additional comments about closing: We do not support old systems
Monday, 04 June 2012, 10:33 GMT
Reason for closing: Not a bug
Additional comments about closing: We do not support old systems
Comment by Pierre Schmitz (Pierre) -
Monday, 04 June 2012, 10:23 GMT
We simply do not support updating such old installs.
Comment by Florian Mutter (elmulator) -
Monday, 04 June 2012, 10:26 GMT
In that case you should probably add a version check to pacman or something and prevent the use of pacman on old systems. Just breaking the users system does not seem like a good practice. How should I know that my system was too old to upgrade?