Version-Release number of selected component:
cmdline: /usr/bin/python /usr/bin/fedup-cli --network 18 --debuglog fedupdebug.log --instrepo http://dl.fedoraproject.org/pub/alt/qa/fedup/f18-RC4/x86_64/
download.py:210:download_packages:TypeError: 'NoneType' object is not iterable
Traceback (most recent call last):
File "/usr/bin/fedup-cli", line 330, in <module>
File "/usr/bin/fedup-cli", line 275, in main
pkgs = download_packages(f)
File "/usr/bin/fedup-cli", line 61, in download_packages
File "/usr/lib/python2.7/site-packages/fedup/download.py", line 210, in download_packages
if set(updates) != set(pkgs):
TypeError: 'NoneType' object is not iterable
Local variables in innermost frame:
self: <fedup.download.FedupDownloader object at 0x2651390>
callback: <fedup.textoutput.DownloadCallback instance at 0x28de878>
Created attachment 679474 [details]
Created attachment 679475 [details]
Created attachment 679476 [details]
Created attachment 679477 [details]
> kernel: 3.7.2-201.fc18.x86_64
-> Isn't this a duplicate of bug 880987 ?
Seems that way - 3.7.2-201.fc18.x86_64 is the F18 kernel, after all.
Can one of the reporters please:
1) check /etc/fedora-release - does it say "Fedora release 18 (Spherical Cow)"?
2) try `yum upgrade` - does it say "Nothing to upgrade" (or similar)?
Obviously I still need a better error message here, so this is still a real bug, but I'd like to be sure this is what's going on.
Can you also attach your fedupdebug.log?
*** Bug 880987 has been marked as a duplicate of this bug. ***
fedup-0.7.3-0.git20130128.fc17 has been submitted as an update for Fedora 17.
I was attempting to upgrade 18 to 19.
OS Release: Fedora release 18 (Spherical Cow)
fedup-0.7.3-1.fc17 has been submitted as an update for Fedora 17.
Should I file another report for 18 to 19?
* 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:
then log in and leave karma (feedback).
Created attachment 717600 [details]
I just had this crash when trying to upgrade Fedora 18 to Fedora 19. Attached is the relevant debug log
...with what version of fedup? It should be fixed in 0.7.3, which is currently in updates-testing.
http://koji.fedoraproject.org/koji/buildinfo?buildID=402988 seemed to fix the error on F18.
fedup-0.7.3-3.fc18 has been submitted as an update for Fedora 18.
fedup-0.7.3-3.fc17 has been submitted as an update for Fedora 17.
fedup-0.7.3-4.fc17 has been submitted as an update for Fedora 17.
fedup-0.7.3-4.fc18 has been submitted as an update for Fedora 18.
fedup-0.7.3-4.fc19 has been submitted as an update for Fedora 19.
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.
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.