I've got this bug for quite some times now. I wouldn't have thought it would last that much. So basically, if you (like me) are not using blackdown, you have an error in any 'emerge -up world' you could do because /usr/portage/net-misc/tightvnc/tightvnc-1.2.8.ebuild contains
I've got this bug for quite some times now. I wouldn't have thought it would last that much. So basically, if you (like me) are not using blackdown, you have an error in any 'emerge -up world' you could do because /usr/portage/net-misc/tightvnc/tightvnc-1.2.8.ebuild contains · java? ( || ( >=virtual/jdk-1.3.1-r7 >=virtual/jre-1.3.1-r7 ) )" Reproducible: Always Steps to Reproduce: 1.install ibm-jre (or jdk), dont have installed blackdown-1.3.1-r7 2.try to emerge or update tightvnc 3. Actual Results: it borks :) Expected Results: it handles fine that i dont have blackdown i understand tightvnc requires 1.3.1-r7 of blackdown and not anything before, but what for us using ibm ???
Created attachment 9683 [details, diff] Small simplistic patch Perhaps this is overly simplistc. I have not tested it as I do not use either tightvnc or ibms jdk/jre and have a slow computer so don't really have time to build them.
Thomas, please attach your /var/cache/edb/virtuals file to this bug... and also please give me the output of `java-config --list-available-vms` in a comment. Thank you.
Basically, the long & the short of it is -- your virtuals db is probably confused. I experienced this same problem, and was likely due to you unmerging a slot of a JDK from your system. It's a bug in portage, I have confirmed this. [1] Unmerging and remerging your JDKs [2] Manually fixing your /var/cache/edb/virtuals file to show: virtual/jdk dev-java/blackdown-jdk
Created attachment 12367 [details] /var/cache/edb/virtuals file as asked by absinthe@gentoo.org the output of java-config --list-available-vms is : bash-2.05b# java-config --list-available-vms [ibm-jdk-1.3.1] IBM JDK 1.3.1 (/etc/env.d/java/20ibm-jdk-1.3.1) (*) bash-2.05b#
Updated tightvnc to not dep on -r7. Which should fix your issue, at least, I walked through it here, given your configuration and all is good.
that's what i have asked since the beginning. Thanx a lot. I tested and it works fine. Now i wont have to remove it 'by hand' each time i rsyn.
