Summary: | emerge dev-java/ant-nodeps-1.8.1 - Invalid implementation version between Ant core and Ant optional tasks | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Stefan Sassenberg <stefan.sassenberg> |
Component: | [OLD] Java | Assignee: | Java team <java> |
Status: | RESOLVED INVALID | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | The requested build log |
Description
Stefan Sassenberg
2010-07-21 09:38:40 UTC
The problem becomes worse, because there is another package affected by this bug. I can't emerge projectx because of the same error: core : 1.8.1 in file:/usr/share/ant/lib/ant.jar optional: 1.7.1 in file:/usr/share/ant/lib/ant-nodeps.jar Emerging becomes more difficult on my system now. A workaround for that point could be to exclude packages from being upgraded or reemerged when emerging world, but I don't know how to accomplish that. (In reply to comment #0) What's this? Something's missing? > PORTDIR_OVERLAY="/var/lib/layman/enlightenment /var/lib/layman/zugaina /var And what does java-check-environment say? That's a little strange. In my /etc/make.conf there is PORTDIR_OVERLAY="/var/lib" source /var/lib/layman/make.conf and /var/lib/layman/make.conf is split up into several lines: PORTDIR_OVERLAY=" /var/lib/layman/enlightenment /var/lib/layman/zugaina $PORTDIR_OVERLAY " I didn't touch those files since april and it hasn't been a problem, but if you like I can remove the overlay lines from /etc/make.conf. My "Java environment is sane." Please emerge ant-nodeps like this: JAVA_PKG_DEBUG=1 emerge ant-nodeps and attach the build log Created attachment 241473 [details]
The requested build log
what does 'which ant' say? if /usr/bin/ant, can you attach it? the /usr/bin/ant our ant-core ebuild provides contains this: ANT_HOME="${EPREFIX}"/usr/share/ant-core yet in your output the ant home is /usr/share/ant and I don't see how it can happen unless your 'ant' is something else than our ebuild also what's your PATH variable? (In reply to comment #6) > what does 'which ant' say? Ok, problem solved. For some reason I can't remember (2009), I installed an ant package in /usr/local and had a symbolic link to the ant script in /usr/local/bin. I removed that link and everything is fine. Thank you very much for your help and sorry for the inconvenience. |