Re: Cleaning up after an aborted upgrade

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I had the same thing happen on an F22->F23 upgrade.  Essentially you have to figure out which F24 packages got installed, and remove them by hand.  😖

Then you can resume the upgrade.  Make sure the fedora-release-24 package is already installed before you continue!

--
Kevin J. Cummings
kjchome@xxxxxxxxxxx
cummings@xxxxxxxxxxxxxxxxxx
cummings@xxxxxxxxxxxxxxxxxxxxxxx
Registered Linux User #1232
(http://www.linuxcounter.net/)


> On Sep 6, 2016, at 19:32, CLOSE Dave <Dave.Close@xxxxxxxxxxxxxxxxxx> wrote:
> 
> I have a machine where I tried to do a system-upgrade from F23 to F24. 
> The download portion worked fine but after the reboot, the upgrade 
> process aborted. I'd like to know why, but first I need to clean up the 
> mess so I can try it again. Right now I have 4782 total packages 
> installed including 1490 fc24 packages. I haven't checked all of them 
> but it appears that all are paired with the same fc23 package.
> 
> Trying to repeat the download step, I get this result.
> 
> # dnf --allowerasing -y system-upgrade download --releasever 24
> Last metadata expiration check: 0:23:15 ago on Tue Sep  6 15:53:47 2016.
> Dependencies resolved.
> Error: The operation would result in removing the following protected 
> packages: systemd.
> 
> Evidently, there are two systemd packages installed:
> 
> # rpm -q systemd
> systemd-222-14.fc23.x86_64
> systemd-229-13.fc24.x86_64
> 
> No new kernel was installed and the machine is running fine as F23. But 
> I'd like to get it upgraded...
> 
> I tried using "dnf history rollback" but that didn't work, reporting "A 
> transaction cannot be undone". Since dnf won't erase the extra stuff, I 
> can probably do it with something like, "rpm erase --force $(rpm 
> -qa|grep fc24)" but that seems iffy. Better suggestions are very welcome.
> -- 
> Dave Close
> --
> users mailing list
> users@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe or change subscription options:
> https://lists.fedoraproject.org/admin/lists/users@xxxxxxxxxxxxxxxxxxxxxxx
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux