Olivier Galibert <galibert <at> pobox.com> writes:
> Please re-engage your brain. I usually update all the *other*
> applications and libraries that need to be compiled because of a new
> version and *then* I ask revdep-rebuild to recompile what is still
> broken. revdep-rebuild always recompiles the same version than what
> is currently installed, not the most up-to-date available one.
Then you should do those updates in one transaction, and the automatic
revdep-rebuild should happen at the end of the transaction, not in the middle.
(Of course, it gets more complicated because apps which are needed for the
remaining upgrades need to be working, so they might need a rebuild even during
the transaction, but that can be figured out programmatically too.)
> Everything is in that "not really supported though". I'm not too
> enthusiastic about having to go in front of and reboot the 200+
> computers we manage one by one with a usb key just to run anaconda
> upgrade.
Edit your /etc/apt/sources.list and/or /etc/apt/sources.list.d/*.list to point
to the newer Fedora, then run:
apt-get update
apt-get dist-upgrade
and you're running the new Fedora version. That can even be scripted for your
200+ computers (just use sed, cat and/or rm for the sources.list editing, then
apt-get update && apt-get -y dist-upgrade).
Kevin Kofler
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
