Bug 573941
Summary: | [abrt] crash in fedora-packager-0.4.1-1.fc12: fedora-packager-setup:114:main:NameError: global name 'certificate_expired' is not defined | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Stefan Schulze Frielinghaus <fedoraproject> | ||||
Component: | fedora-packager | Assignee: | Dennis Gilmore <dennis> | ||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | low | ||||||
Version: | 12 | CC: | alejandro.perez.torres, christoph.wickert, dennis, gui1ty, jhrozek, kylev, mads, ndbecker2, quentin, randyn3lrx, sochotni, srinivasa | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | ppc | ||||||
OS: | Linux | ||||||
Whiteboard: | abrt_hash:ea1231f6 | ||||||
Fixed In Version: | fedora-packager-0.4.2-1.fc12 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2010-04-09 04:26:15 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
Stefan Schulze Frielinghaus
2010-03-16 09:24:11 UTC
Created attachment 400409 [details]
File: backtrace
just commited the fix to git. will have an update out very soon *** Bug 574150 has been marked as a duplicate of this bug. *** How to reproduce ----- 1. just run it Comment ----- fedora-packager-setup crashes when trying to run it How to reproduce ----- 1. Remove old certificates, if any 2. Generate new user certificate in the account system 3. Attempt to run fedora-packager-setup fedora-packager-0.4.2-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/fedora-packager-0.4.2-1.fc13 fedora-packager-0.4.2-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/fedora-packager-0.4.2-1.fc12 fedora-packager-0.4.2-1.el5 has been submitted as an update for Fedora EPEL 5. http://admin.fedoraproject.org/updates/fedora-packager-0.4.2-1.el5 fedora-packager-0.4.2-1.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update fedora-packager'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/fedora-packager-0.4.2-1.fc13 *** Bug 575646 has been marked as a duplicate of this bug. *** fedora-packager-0.4.2-1.el5 has been pushed to the Fedora EPEL 5 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update fedora-packager'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/fedora-packager-0.4.2-1.el5 fedora-packager-0.4.2-1.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update fedora-packager'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/fedora-packager-0.4.2-1.fc12 I am seeing a different traceback after updating to 0.4.2-1: Traceback (most recent call last): File "/usr/bin/fedora-packager-setup", line 140, in <module> main() File "/usr/bin/fedora-packager-setup", line 114, in main if fedora_cert.certificate_expired(): File "/usr/lib/python2.6/site-packages/fedora_cert/__init__.py", line 66, in certificate_expired my_cert = _open_cert() File "/usr/lib/python2.6/site-packages/fedora_cert/__init__.py", line 36, in _open_cert my_cert = crypto.load_certificate(crypto.FILETYPE_PEM, raw_cert) OpenSSL.crypto.Error: [('PEM routines', 'PEM_read_bio', 'no start line')] On my laptop fedora-packager-setup runs without problems after updating. Nevermind, ~/.fedora.cert contained garbage from a failed download using wget. I replaced ~/.fedora.cert with the actual certificate and everything is working as expected. Sorry for the fuzz. (In reply to comment #14) > Nevermind, ~/.fedora.cert contained garbage from a failed download using wget. > I replaced ~/.fedora.cert with the actual certificate and everything is working > as expected. Sorry for the fuzz. Can you please file a new bug about this? The tool should never traceback, even on encountering an invalid input. (In reply to comment #15) > (In reply to comment #14) > > Nevermind, ~/.fedora.cert contained garbage from a failed download using wget. > > I replaced ~/.fedora.cert with the actual certificate and everything is working > > as expected. Sorry for the fuzz. > > Can you please file a new bug about this? The tool should never traceback, even > on encountering an invalid input. Done --> bug 577021 How to reproduce ----- 1.Just typed fedora-packager-setup in treminal 2. 3. How to reproduce ----- 1.try to executed 2.also exceuted fedora-cert that works but still same error 3. variable user_cert: exist that file other do not exist Comment ----- run command fedora-packager-setup Please ensure that you install the version in updates-testing and use that How to reproduce ----- 1. D/L client cert 2. Run fedora-packager-setup 3. (In reply to comment #20) > > How to reproduce > ----- > 1. D/L client cert > 2. Run fedora-packager-setup > 3. rpm -q fedora-packager fedora-packager-0.4.1-1.fc12.noarch Note that I had mistakenly d/l my client certificate and renamed it to .fedora-cert instead of .fedora.cert. please follow the instructions in comment 12 to update to the version in updates-testing that fixes the bug you are seeing. you can use fedora-cert to download a cert or the new version in 0.4.2 will do it for you. How to reproduce ----- 1. Run fedora-packger-setup with no ~/.fedora.cert How to reproduce ----- 1. Run fedora-packager-setup without file $HOME/.fedora.cert existing Comment ----- Problem is that the function exists in fedora_cert namespace. Changing to fedora_cert.certificate_expired() fixes things Please read the bug before posting. you need to update to 0.4.2 that is in updates-testing. Dennis, these comments were submitted throught ABRT, so people cannot look at the bug before posting. Time to file a feature request on ABRT I think. See bug 575396 "please check for duplicates before prompting for user input" fedora-packager-0.4.2-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report. *** Bug 580850 has been marked as a duplicate of this bug. *** fedora-packager-0.4.2-1.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report. fedora-packager-0.4.2-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report. |