Description of problem: Trying to use fedup. Version-Release number of selected component: fedup-0.7.3-4.fc19 Additional info: reporter: libreport-2.1.10 cmdline: /usr/bin/python /usr/bin/fedup-cli --iso /home/ricardo/Descargas/Fedora-20.iso executable: /usr/bin/fedup-cli kernel: 3.11.10-301.fc20.x86_64 runlevel: unknown type: Python uid: 0 Truncated backtrace: commandline.py:197:device_setup:NameError: global name 'message' is not defined Traceback (most recent call last): File "/usr/bin/fedup-cli", line 181, in <module> main(args) File "/usr/bin/fedup-cli", line 86, in main device_setup(args) File "/usr/lib/python2.7/site-packages/fedup/commandline.py", line 197, in device_setup message('--iso: '+_('Unable to open %s') % args.iso) NameError: global name 'message' is not defined Local variables in innermost frame: args: Namespace(cacheonly=False, clean=None, clean_metadata=False, debuglog='/var/log/fedup.log', device=None, expire_cache=False, instrepo=None, iso='/home/ricardo/Descargas/Fedora-20.iso', loglevel=30, network=None, reboot=False, repos=[], skipbootloader=False, skipkernel=False, skippkgs=False) e: CalledProcessError()
Created attachment 837869 [details] File: backtrace
Created attachment 837870 [details] File: environ
Should be fixed by commit cd2ac9d: https://github.com/wgwoods/fedup/commit/cd2ac9d This will be in the next version of fedup.
*** Bug 1082261 has been marked as a duplicate of this bug. ***
fedup-0.8.1-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/fedup-0.8.1-1.fc19
fedup-0.8.1-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/fedup-0.8.1-1.fc20
Package fedup-0.8.1-1.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing fedup-0.8.1-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-7085/fedup-0.8.1-1.fc19 then log in and leave karma (feedback).
fedup-0.8.1-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
fedup-0.9.0-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/fedup-0.9.0-1.fc19
fedup-0.9.0-2.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/fedup-0.9.0-2.fc19
fedup-0.9.0-2.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.