Bug 231591
Summary: | gcc-java dependent on eclipse-ecj via /usr/share/java/eclipse-ecj.jar | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Paul Dickson <paul> |
Component: | yum | Assignee: | Jeremy Katz <katzj> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | jakub, james.antill, pekkas, pmatilai, tim.lauridsen |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | 3.2.8-2 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-03-12 13:59:05 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: |
Description
Paul Dickson
2007-03-09 06:37:54 UTC
It is completely intentional that gcc-java now depends on eclipse-ecj.jar. My point is that yum wasn't pulling in eclipse-ecj.jar. gcc was failing to updated because of a dependency on /usr/share/java/eclipse-ecj.jar. I've hit this recently on Fedora 7 install, and F7 updates have stalled for about two weeks because this dependency isn't satisfied properly in yum. One potential source of problem may have been that it seems I had an old version of eclipse-ecj rpm (3.2.2-14.fc7) sitting on /var/cache/yum/fedora/packages directory for some reason (maybe from an older update attempt). I wonder if that was messing up the update for some reason. After manually installing it and rerunning yum update, the first thing yum did was download eclipse-ecj 3.2.2-15.fc7. I think this is a problem so re-opening. What version of yum do you have installed? It's impossible to say for sure because yum was upgraded in the same ago, but if I'd have to guess, I'd say it was 3.2.2 because I recall that was the next-to-latest yum update that was pushed to updates/updates-testing. okay - this was most likely a file lookup problem in 3.2.2. I've recently tested non-primary-file-dep look ups and found them working properly. If you find a problem in yum 3.2.8 or above please file a new bug. Thanks |