Bug 879999
Summary: | eclipse-pdebuild fails with FileNotFoundException for genericTargets.xml | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Gerard Ryan <fedora> |
Component: | eclipse | Assignee: | Krzysztof Daniel <kdaniel> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | akurtako, andjrobins, jerboaa, kdaniel, mbenitez, msrb, overholt, rgrunber, swagiaal |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | icu4j-50.1.1-1.fc19 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-08-29 23:58:12 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: | |||
Bug Depends On: | 974108, 974112, 1000740 | ||
Bug Blocks: |
Description
Gerard Ryan
2012-11-25 23:20:07 UTC
I've restored javax.xml. This change cannot be done now - too many places to check. The build should work now. (In reply to comment #1) > I've restored javax.xml. This change cannot be done now - too many places to > check. The build should work now. Thanks a lot, it builds fine now: https://koji.fedoraproject.org/koji/buildinfo?buildID=367581 I'm seeing this again in Rawhide/f19, with eclipse >= 1:4.3.0-0.41 It's preventing me from using pdebuild to build packages. See: Rawhide: http://koji.fedoraproject.org/koji/taskinfo?taskID=5366642 F19: http://koji.fedoraproject.org/koji/taskinfo?taskID=5366602 *** Bug 962239 has been marked as a duplicate of this bug. *** sat4j-2.3.4-1.fc19,jsch-0.1.50-1.fc19,eclipse-4.3.0-0.45.git4bccf2.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/sat4j-2.3.4-1.fc19,jsch-0.1.50-1.fc19,eclipse-4.3.0-0.45.git4bccf2.fc19 Package sat4j-2.3.4-1.fc19, jsch-0.1.50-1.fc19, eclipse-4.3.0-0.45.git4bccf2.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 sat4j-2.3.4-1.fc19 jsch-0.1.50-1.fc19 eclipse-4.3.0-0.45.git4bccf2.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-8126/sat4j-2.3.4-1.fc19,jsch-0.1.50-1.fc19,eclipse-4.3.0-0.45.git4bccf2.fc19 then log in and leave karma (feedback). Package icu4j-50.1.1-1.fc19, eclipse-4.3.0-0.46.git4bccf2.fc19, sat4j-2.3.4-1.fc19, jsch-0.1.50-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 icu4j-50.1.1-1.fc19 eclipse-4.3.0-0.46.git4bccf2.fc19 sat4j-2.3.4-1.fc19 jsch-0.1.50-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-8126/icu4j-50.1.1-1.fc19,sat4j-2.3.4-1.fc19,jsch-0.1.50-1.fc19,eclipse-4.3.0-0.46.git4bccf2.fc19 then log in and leave karma (feedback). icu4j-50.1.1-1.fc19, eclipse-4.3.0-0.46.git4bccf2.fc19, sat4j-2.3.4-1.fc19, jsch-0.1.50-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. This is back again on rawhide. eclipse-4.3.0-0.61.git7bf397.fc20 at least, not sure about previous versions. It seems to happen most often at weekends, when I have time to work on stuff, and when there's nobody around to fix it :P Still broken? (In reply to Krzysztof Daniel from comment #10) > Still broken? I just tried in mock with version 4.3.0-0.64.git84cba7, still appears broken (I guess you know that though, since you added other bugs since you asked the question. I look forward to this being fixed :) I'm on it. Important bits are: !MESSAGE Unable to access file "plugins/org.glassfish.web.javax.servlet.jsp_2.2.6.jar!META-INF/MANIFEST.MF". which in says that symlink is broken, which happened due to the glassfish-jsp.jar rename. So, Gerard, this issue seems to be fixed now :-) Wouldn't it be simpler to move to the tycho build? (In reply to Krzysztof Daniel from comment #14) > So, Gerard, this issue seems to be fixed now :-) > > Wouldn't it be simpler to move to the tycho build? It's happening again! :) http://koji.fedoraproject.org/koji/taskinfo?taskID=5824649 I agree that tycho would be easier, but it seems that not all projects are using it yet :-/ Gerard, Please try eclipse-4.3.0-11.fc20 , whenever a dependency changes we need to rebuild in order to get p2 metadata regenerated. (In reply to Alexander Kurtakov from comment #16) > Gerard, > Please try eclipse-4.3.0-11.fc20 , whenever a dependency changes we need to > rebuild in order to get p2 metadata regenerated. That works great, thanks for the fix! :) Since most of the time that I have to work on Fedora stuff is at the weekends, that's when I run into these problems, and both you and Krzysztof would be online less. Would it be okay in those situations for me to find a provenpackager to kick off a rebuild in rawhide, rather than having to wait until the following week when you guys are around? (In reply to Gerard Ryan from comment #17) > Since most of the time that I have to work on Fedora stuff is at the > weekends, that's when I run into these problems, and both you and Krzysztof > would be online less. Or late in the evenings like right now, and it turns out that it needs to be rebuilt now, because of new jetty in rawhide today ;D I've pushed a rebuild here for now : http://koji.fedoraproject.org/koji/taskinfo?taskID=5843348 . Thanks Roland! I'll re-close this. I was wrong, this is still a problem. The regeneration of p2 metadata from the rebuild has fixed building with tycho, but building with pdebuild is still an issue. Comment #13 gave me an idea to check if any symlinks were broken and it turns out there are two. I've opened bug #1000740 for that. Working again, thanks. |