Bug 655576
| Summary: | [abrt] fedpkg-0.5.1.4-5.fc14: __init__.py:1210:gimmespec:FedpkgError: No spec file found. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Matthew Truch <matt> | ||||
| Component: | fedora-packager | Assignee: | Dave Cantrell <dcantrell> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 14 | CC: | dcantrell, dennis | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | abrt_hash:ca9f3706 | ||||||
| Fixed In Version: | fedora-packager-0.5.2.0-2.fc13 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-01-19 21:05:16 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: |
|
||||||
Created attachment 461861 [details]
File: backtrace
what's in the current working directory that you ran "fedpkg update" in? It sounds like there was no working files, no spec file or anything, for fedpkg to discover what package it's working on. Yes, I was one directory up from where I should have been (which I figured out after I had submitted the bug report since ABRT popped up). Ok, I think I have a duplicate of this bug somewhere, I"ll have to find it. Couldn't find a dupe, but is related to #656897 Found a fix for this upstream. fedora-packager-0.5.2.0-2.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/fedora-packager-0.5.2.0-2.el5 fedora-packager-0.5.2.0-2.fc13 has been submitted as an update for Fedora 13. https://admin.fedoraproject.org/updates/fedora-packager-0.5.2.0-2.fc13 fedora-packager-0.5.2.0-2.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/fedora-packager-0.5.2.0-2.fc14 fedora-packager-0.5.2.0-2.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: https://admin.fedoraproject.org/updates/fedora-packager-0.5.2.0-2.el5 fedora-packager-0.5.2.0-2.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report. fedora-packager-0.5.2.0-2.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.5.2.0-2.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report. |
abrt version: 1.1.13 architecture: x86_64 component: fedora-packager executable: /usr/bin/fedpkg kernel: 2.6.35.6-48.fc14.x86_64 package: fedpkg-0.5.1.4-5.fc14 reason: __init__.py:1210:gimmespec:FedpkgError: No spec file found. release: Fedora release 14 (Laughlin) How to reproduce: Try to run fedpkg update. time: 1290368167 uid: 500 backtrace ----- __init__.py:1210:gimmespec:FedpkgError: No spec file found. Traceback (most recent call last): File "/usr/bin/fedpkg", line 1086, in <module> args.command(args) File "/usr/bin/fedpkg", line 664, in update mymodule = pyfedpkg.PackageModule(args.path) File "/usr/lib/python2.7/site-packages/pyfedpkg/__init__.py", line 903, in __init__ self.spec = self.gimmespec() File "/usr/lib/python2.7/site-packages/pyfedpkg/__init__.py", line 1210, in gimmespec raise FedpkgError('No spec file found.') FedpkgError: No spec file found. Local variables in innermost frame: files: ['f12', 'f14', 'el4', 'f10', 'f13', 'master', 'el6', 'el5', 'f11'] self: <pyfedpkg.PackageModule instance at 0x1778e60> f: 'f11'