I upgraded my laptop from fedora 18 to fedora 19. After reboot there are only f18 kernels and the kernel panic on boot. I booted up with f19 rescue disk and when I chroot /mnt/sysroot I get lots of GLIBC_2.17 not found. Here's what I think happened. I use a local mirror of fedora that I built with reposync. I just discovered the group files were not coming across do to a change in xpath. I think it fedup didn't install the "core" group as a brand new pxe install was complaining that the "core" group was missing. I'm in a situation where I can't even run ls or boot, or yum upgrade the system. My fix is going to be to copy the /lib, /bin, etc directories from the rescue boot disk, then (re)install all core packages. So I have a workaround. So the enhancement/bug I'm looking to be changed in fedup... Can we add something into fedup so that it won't even begin the upgrade if the core files to boot the system are not in place?
If glibc was missing, you should have had *tons* of warning/error messages from fedup before the upgrade. Did you not get any error messages? For what it's worth, the next release of fedup will definitely warn you if there are dependency problems with the upgrade. The last messages look like this: WARNING: problems were encountered during transaction test: broken dependencies cups-filters-1.0.38-2.fc19.x86_64 requires poppler-0.22.1-4.fc19.x86_64 ghostscript-cups-9.07-15.fc19.x86_64 requires ghostscript-9.07-15.fc19.x86_64 Continue with the upgrade at your own risk. which should prevent this kind of thing from happening to others, I hope. Did you not see any error messages? Can you attach your fedup.log?
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days