Am 10.02.2012 18:49, schrieb Jef Spaleta: > On Fri, Feb 10, 2012 at 8:41 AM, Reindl Harald <h.reindl@xxxxxxxxxxxxx> wrote: >> no i can not because it is a one-shot thing to do "yum distro-sync" and so i >> had no time for a bugrport while other more important things like mysqld were >> horrible broken > > Let me strongly suggest, that unfiled problems will never get fixed > because you cannot assume your workflow is part of anyone elses > prerelease testing. > Let me further stridently suggest that if you or any user insist on > using an upgrade path which is stated as a matter of policy as > unsupported so this policy has to be adopted to the real life damned you can i imagine you upgrade a virtual production server with Preupgrade/Anaconda? this is only a bad joke while if Fedora put more care in yum-upgrade and supports it this does well while services are up i ahve done UNDRETS of dist-upgrades with yum while services were up and most time of prepare this is revert/change fedora mistakes made all the time and yes there are servers which can be down the 30 secods of the reboot as they do also on a normal kernel update Preupgrade/ANacodna is UNACCETABLE on any important machine because it is not controllable while yum is if oyu have a clone of your machine to test and playaround before go to the procution one these policies should corrected and whoever wrote them should come back to reality
Attachment:
signature.asc
Description: OpenPGP digital signature
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
