Created attachment 680513 [details] Tail of fedupdebug.log Description of problem: "fedup-cli --network 18 --debuglog fedupdebug.log" ends badly with Python stack trace, duplicated in fedupdebug.log. Tail of 7000-line log file attached later. Version-Release number of selected component (if applicable): "fedup --version" hangs. "rpm -q fedup" sez: fedup-0.7.2-1.fc17.noarch. Does that help? How reproducible: On my Atom box, run fedup and it works. On wife's identical box, run fedup and it barfs. Steps to Reproduce: 1. Damifino Actual results: Python barf. Expected results: Silent operation w.o. errors in log. Reboot, wait a few hours and it works!
call(["selinuxenabled"]) ... OSError: [Errno 2] No such file or directory Looks like your system doesn't have the "selinuxenabled" command. If that's the case, do: yum install libselinux-utils and the upgrade should be able to proceed. There should be a fedup bugfix release that will run without the "selinuxenabled" command soon. Does that fix the problem?
Alas, libselinux-utils was installed on both machines: $ rpm -q libselinux-utils libselinux-utils-2.1.12-7.fc18.x86_64 $ which selinuxenabled /usr/sbin/selinuxenabled Identical (similar) results on either machine.
Call off the hounds (at least for now). On my machine, to run fedup-cli, I did a simple 'su' to escalate my privileges. It worked because /usr/sbin was somehow in my path. On my wife's machine, I used the same procedure, but /usr/sbin had gone missing from her path. The 'which selinuxenabled' above was done as me, logged into her machine. Logged in as her, it didn't work. A simple 'su -' before 'fedup-cli ...' did the trick. Fortunately, the packages were cached and except for 64 packages which must have changed in the interim, no tedious download was required. Thanks for the hint, and please close this bug as bogus.
Thanks for the info - and I'm glad you found a workaround. Fedup commit 3bec5d4 should also fix this: https://github.com/wgwoods/fedup/commit/3bec5d4 It'll be in the next fedup build.
fedup-0.7.3-0.git20130128.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/fedup-0.7.3-0.git20130128.fc17
fedup-0.7.3-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/fedup-0.7.3-1.fc17
Package fedup-0.7.3-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing fedup-0.7.3-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-3956/fedup-0.7.3-1.fc17 then log in and leave karma (feedback).
fedup-0.7.3-3.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/fedup-0.7.3-3.fc18
fedup-0.7.3-3.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/fedup-0.7.3-3.fc17
fedup-0.7.3-4.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/fedup-0.7.3-4.fc17
fedup-0.7.3-4.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/fedup-0.7.3-4.fc18
fedup-0.7.3-4.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/fedup-0.7.3-4.fc19
fedup-0.7.3-4.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
fedup-0.7.3-5.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/fedup-0.7.3-5.fc17
fedup-0.7.3-4.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
fedup-0.7.3-5.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.