Description of problem: fedup picked up some package conflicts when I ran "fedup --network 21 --product=nonproduct", emitted the warning advising against proceeding with the update, but configured the update to happen on next boot anyway. Version-Release number of selected component (if applicable): How reproducible: Once, but that was annoying enough... Steps to Reproduce: 1. Run fedup on a system with some packages that conflict with new F21 packages 2. Reboot the system 3. Actual results: System proceeds with the upgrade to F21, despite fedup advising against it Expected results: When fedup found a problem, I expected it to *not* configure the update for next boot, and instead require me to opt into forcing it. Additional info: I didn't read the details of the initial error message from fedup - I assumed it hadn't scheduled the upgrade to proceed (since it was advising against that), and just shut the machine down, intending to look into the problem later. I was very surprised to find my machine halfway through the upgrade progress when I came back to it after switching it on this morning.
The next fedup release will at least have improved warnings/error messages in these cases - see bug 1098886 for details. I'm also planning to change the behavior so that you must run something like: fedup reboot to actually start the upgrade, but that code hasn't been written yet.
That sounds like a good improvement, thanks!
So yeah, fedup 2.x will have separate "download"/"setup" and "reboot" commands, so this won't happen in the future. As for the current version, the fix to bug 1098886 at least tells you how to abort the upgrade by running `fedup --resetbootloader`. That's about the best we can do here, I think.
fedup-0.9.2-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/fedup-0.9.2-1.fc20
fedup-0.9.2-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/fedup-0.9.2-1.fc21
fedup-0.9.2-1.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/fedup-0.9.2-1.fc22
Package fedup-0.9.2-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing fedup-0.9.2-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-6467/fedup-0.9.2-1.fc20 then log in and leave karma (feedback).
fedup-0.9.2-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
fedup-0.9.2-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
I ran into some network problems that prevented fedup from finding all the packages it needed to upgrade from F21 to F22, and the updated error message was exactly the prompt I needed to remind me to explicitly abort the upgrade attempt. Thanks!