Bug 1885771
Summary: | Could not execute retire: 'NoneType' object has no attribute 'is_retired' | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Miro Hrončok <mhroncok> |
Component: | fedpkg | Assignee: | Ondřej Nosek <onosek> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 32 | CC: | carl, cqi, dennis, jkeating, lsedlar, onosek, s |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | fedpkg-1.40-1.fc33 fedpkg-1.40-1.fc32 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-12-07 01:20:00 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Miro Hrončok
2020-10-06 21:10:09 UTC
May I retire the package manually, or do you need it unretired to be able to reproduce? I believe I can reproduce it even retired. But if you are not in a hurry, please, retire it by the end of today. I am not in a hurry - the package was never built, so retiring it now or later doesn't really make any difference. Since I cannot retire it accidentally, I won't retire it today. Thanks I've retired the package now. I ran into this same bug today. I requested a new repo for an EPEL7-only package, and thus I tried to immediately retire the master branch with no spec file. [carl@tassadar:~/packaging/fedora/python3-mod_wsgi]$ rpm -q fedpkg fedpkg-1.39-1.fc33.noarch [carl@tassadar:~/packaging/fedora/python3-mod_wsgi]$ fedpkg retire 'EPEL7-only package' Could not execute retire: 'NoneType' object has no attribute 'is_retired' As a workaround, git rm all the files, create and git add dead.package with the reason and commit this with the reason as a commit message. Going to be released in rpkg-1.62-1 FEDORA-2020-3c9702ca4d has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-3c9702ca4d FEDORA-2020-36f82ae84e has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-36f82ae84e FEDORA-2020-3c9702ca4d has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-3c9702ca4d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-3c9702ca4d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-36f82ae84e has been pushed to the Fedora 32 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-36f82ae84e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-36f82ae84e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-3c9702ca4d has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2020-36f82ae84e has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report. |