Bug 1047005
Summary: | [abrt] fedup: download.py:276:find_replacement:AttributeError: 'NoneType' object has no attribute 'pkgtup' | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Michael L <mdl-mailing> | ||||||||||
Component: | fedup | Assignee: | Will Woods <wwoods> | ||||||||||
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||
Priority: | unspecified | ||||||||||||
Version: | 19 | CC: | cblanks, collura, mstuff, tflink, wwoods | ||||||||||
Target Milestone: | --- | ||||||||||||
Target Release: | --- | ||||||||||||
Hardware: | x86_64 | ||||||||||||
OS: | Unspecified | ||||||||||||
URL: | https://retrace.fedoraproject.org/faf/reports/bthash/925f253e4b65e47aa2d90a389122e848a0156bb6 | ||||||||||||
Whiteboard: | abrt_hash:72a815fa1e9a0a79d808d3d0b225e511b6a29886 | ||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
Doc Text: | Story Points: | --- | |||||||||||
Clone Of: | Environment: | ||||||||||||
Last Closed: | 2015-02-18 11:19:25 UTC | Type: | --- | ||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||
Documentation: | --- | CRM: | |||||||||||
Verified Versions: | Category: | --- | |||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
Embargoed: | |||||||||||||
Attachments: |
|
Description
Michael L
2013-12-28 04:56:52 UTC
Created attachment 842589 [details]
File: backtrace
Created attachment 842590 [details]
File: environ
fedup fails *** First crash due to no /boot space left: https://retrace.fedoraproject.org/faf/reports/317083/ Tried to report a bug on that, but that failed too: --- Running report_uReport --- ('report_uReport' completed successfully) --- Running report_Bugzilla --- Logging into Bugzilla at https://bugzilla.redhat.com Invalid password or login. Please enter your BZ login: 'mstuff.nz' Invalid password or login. Please enter the password for 'mstuff.nz': '********' Checking for duplicates Creating a new bug fatal: RPC failed at server. There is no version named '%{bug_version}' in the 'Fedora' product. ('report_Bugzilla' exited with 1) --- Running report_EmergencyAnalysis --- Compressing data Sending /var/tmp/Python-2014-01-21-11:35:19-4363.tar.gz to https://retrace.fedoraproject.org/faf/dumpdirs/new/ Successfully sent /var/tmp/Python-2014-01-21-11:35:19-4363.tar.gz to https://retrace.fedoraproject.org/faf/dumpdirs/new/ *** Second crash due to something else - don't know what, but abrt provides this link to abrt server: https://retrace.fedoraproject.org/faf/reports/310483/ *** Attached fedup.log if it's not provided somewhere else already. Created attachment 853208 [details]
fedup.log
fedup.log attached as per above.
Really like some pointers on moving forward with fedup, thanks.
Fix committed upstream: https://github.com/wgwoods/fedup/commit/7972b6f The next version of fedup will contain this patch. If you can't wait, you could apply the patch manually by running: curl https://github.com/wgwoods/fedup/commit/7972b6f.diff | \ sudo patch -d/usr/lib/python2.7/site-packages/fedup -p2 If you do apply the patch manually, please let me know if it works. Hi, I am getting this same error attempting to upgrade to F20 from F19, using latest version of fedup. Created attachment 898397 [details]
fedup log
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. |