| Summary: | dev-java/commons-net-1.4.1-r1 emerge fails | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Chris Traylor <ctraylor> |
| Component: | [OLD] Java | Assignee: | Java team <java> |
| Status: | VERIFIED NEEDINFO | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Chris Traylor
2007-06-29 04:25:55 UTC
(In reply to comment #0) > > Actual Results: > tar: A lone zero block at 3060 > !!! ERROR: Package jakarta-oro-2.0 was not found! This is saying that you don't have jakarta-oro-2.0 installed but: elgeuse@pena ~ $ qdepends -d dev-java/commons-net dev-java/commons-net-1.4.1-r1: >=virtual/jdk-1.3 >=dev-java/ant-core-1.5.4 >=dev-java/jakarta-oro-2.0 >=dev-java/java-config-2.0.31 >=sys-apps/portage-2.1.2.7 >=dev-java/javatoolkit-0.2.0-r1 >=sys-apps/portage-2.1.2.7 dev-java/ant-core it is dependent on just fine. Please attach the output of emerge -pv commons-net and emerge -pv jakarta-oro > > !!! When you file a bug report, please include the following information: > GENTOO_VM=sun-jdk-1.5 CLASSPATH="" JAVA_HOME="/opt/sun-jdk-1.5.0.08" > JAVACFLAGS="-source 1.3 -target 1.3" COMPILER="" > and of course, the output of emerge --info Your sun-jdk is at least very much out of date: (1.5) 1.5.0.11 (~)1.5.0.11-r1 (~)1.5.0.12 Do you use emerge -uD world to update? Any it pulls in jakarta-oro in just fine here: pena commons-net # emerge -pv commons-net These are the packages that would be merged, in order: [ebuild N ] dev-java/jakarta-oro-2.0.8-r2 USE="-doc -examples -source" 338 kB [ebuild R ] dev-java/commons-net-1.4.1-r1 USE="-doc -examples -source" 0 kB please reope with info on what I asked betelgeuse@pena /usr/portage/profiles $ grep jakarta-oro -r . ./updates/2Q-2005:move dev-java/oro dev-java/jakarta-oro Hmm maybe you still have oro installed. So please post the output of qlist jakarta-oro before doing anything else. (In reply to comment #2) > betelgeuse@pena /usr/portage/profiles $ grep jakarta-oro -r . > ./updates/2Q-2005:move dev-java/oro dev-java/jakarta-oro > > Hmm maybe you still have oro installed. So please post the output of > qlist jakarta-oro before doing anything else. > You hit it right on the head. The output of qlist list showed some oro related files. The dependencies for commons-net did not include jakarta-oro, but emerging jakarta-oro separately seems to have resolved this bug. Thank you all for your help on this matter. (In reply to comment #3) > > You hit it right on the head. The output of qlist list showed some oro related > files. The dependencies for commons-net did not include jakarta-oro, but > emerging jakarta-oro separately seems to have resolved this bug. Thank you all > for your help on this matter. > jakarta-oro did not show up in the list because you had it installed. It's just that package moves were used in not the best way. They should only be used when you don't need to change the installed files (which is almost never the case of java packages) or can easily force people to update. I recommend running emerge -uD world to update in the future. If you don't you might bump into some other old artifacts like this. Don't you think that doing an emerge world (and the hours that it would take) is a bit overkill to upgrade a single piece of software that, obviously, is rarely, if ever used? It seems to me that a better solution would have been to block on jakarta-oro, if the old oro is installed. Perhaps display some output on the emerge of that package to give the user a clue as to the solution. That seems like a more "gentooish" way of doing things. Just my $0.02. The package move made the block quite impossible. Also, the block would not be processed at all without --deep. The only solution I see is upgrade all =dev-java/jakarta-oro-2.0* deps in the tree to >=dev-java/jakarta-oro-2.0.8-r2. But I don't think it's not worth it, and we can spend time more usefully. After all, upgrading your system frequently is also more "gentooish" than just one package after two years... (In reply to comment #5) > Don't you think that doing an emerge world (and the hours that it would take) > is a bit overkill to upgrade a single piece of software that, obviously, is > rarely, if ever used? It seems to me that a better solution would have been to > block on jakarta-oro, if the old oro is installed. > Please consider that we developers might sometimes actually know what we are doing. You might want to read up on what package moves do... No-one can't have had oro installed since mid 2005. jakarta-oro with oro files sure but not oro in the vdb sense. As I said earlier if you don't use emerge --deep while updating you will be hitting other problems too. |
