Summary: | Uresolvable block: eselect-java and eselect-maven | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Joerg Schaible <joerg.schaible> |
Component: | [OLD] Java | Assignee: | Java team <java> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | eric.chatellier, gentoo |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Joerg Schaible
2014-03-11 08:03:53 UTC
I'm seeing this as well. For now, I was able to work around this and allow other pending updates to emerge by doing this: $ echo app-admin/eselect-java >> /etc/portage/package.mask This reduces the symptom to just the following warning: WARNING: One or more updates have been skipped due to a dependency conflict: dev-java/java-config:2 (dev-java/java-config-2.2.0::gentoo, ebuild scheduled for merge) conflicts with <dev-java/java-config-2.2 required by (dev-java/oracle-jdk-bin-1.7.0.51-r1::gentoo, installed) My local maven ebuilds created the block. After adjusting them properly to depend either on eselect-maven or eselect-java, emerge is able to resolve the block on its own. I did not have any custom java ebuilds on my system. To recover from this, I had to manually un-merge maven-bin and eselect-maven, then do a @world update to pull in the new eselect-java, then re-install maven-bin. |