Bug 758051
| Summary: | [abrt] jpackage-utils-1.7.5-15.fc16: maven_depmap.py:79:_get_jpp_from_filename:IOError: Jar path doesn't exist | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Alexander Kurtakov <akurtako> | ||||
| Component: | jpackage-utils | Assignee: | Stanislav Ochotnicky <sochotni> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 16 | CC: | akurtako, dbhole, rkennke | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i686 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | abrt_hash:a763b93041937610d010791fe6798a2ff8623486 | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-02-14 02:23:29 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: |
|
||||||
The new script was written by Stano. Re-assigning. Hmm, I don't know about catching this. I intentionally let the exception bubble up, but basically I want to see this backtrace when packaging that's why I've done it that way. Anyway, will look into a compromise I believe it was trying to add a depmap for a file that did not exist. Package: jpackage-utils-1.7.5-15.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Created attachment 615079 [details]
Patch to handle full path jar argument
This also happens when using %add_maven_depmap with a full path jar (to handle JNI jars). Adding a check against the provided path fix this issue in my case (see the patch).
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. 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 prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 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 to click on "Clone This Bug" and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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. Thank you for reporting this bug and we are sorry it could not be fixed. |
libreport version: 2.0.7 abrt_version: 2.0.6 cmdline: python -m /usr/share/java-utils/maven_depmap /home/akurtakov/rpmbuild/BUILDROOT/maven-release-2.2-3.fc17.noarch/usr/share/maven-fragments/maven-release /home/akurtakov/rpmbuild/BUILDROOT/maven-release-2.2-3.fc17.noarch/usr/share/maven-poms/JPP-maven-release.pom jar_missing_in_jar_paths executable: /usr/share/java-utils/maven_depmap.py kernel: 3.1.1-2.fc16.i686 reason: maven_depmap.py:79:_get_jpp_from_filename:IOError: Jar path doesn't exist time: Tue 29 Nov 2011 11:44:11 AM EET uid: 500 username: akurtakov backtrace: :maven_depmap.py:79:_get_jpp_from_filename:IOError: Jar path doesn't exist : :Traceback (most recent call last): : File "/usr/lib/python2.7/runpy.py", line 162, in _run_module_as_main : "__main__", fname, loader, pkg_name) : File "/usr/lib/python2.7/runpy.py", line 72, in _run_code : exec code in run_globals : File "/usr/share/java-utils/maven_depmap.py", line 205, in <module> : fragment = parse_pom(pom_path, jar_path) : File "/usr/share/java-utils/maven_depmap.py", line 127, in parse_pom : jpp_gid, jpp_aid = _get_jpp_from_filename(pom_file, jar_file) : File "/usr/share/java-utils/maven_depmap.py", line 79, in _get_jpp_from_filename : raise IOError("Jar path doesn't exist") :IOError: Jar path doesn't exist : :Local variables in innermost frame: :pom_path: '/home/akurtakov/rpmbuild/BUILDROOT/maven-release-2.2-3.fc17.noarch/usr/share/maven-poms/JPP-maven-release.pom' :pomname: 'JPP-maven-release.pom' :jar_path: 'jar_missing_in_jar_paths' comment: :Happened while building maven-release which happens to have wrong add_maven_depmap call. :There should be a way to catch the exception so abrt doesn't catch it.