i had to drop keywords on commons-compress as it has a new dependency which is not yet keyworded.
Unable to check for sanity: > package masked: www-servers/tomcat-10.0.4
Unable to check for sanity: > no match for package: www-servers/tomcat-10.0.4
Unable to check for sanity: > package masked: www-servers/tomcat-10.0.5
Unable to check for sanity: > no match for package: www-servers/tomcat-10.0.5
Unable to check for sanity: > package masked: www-servers/tomcat-10.0.6
Unable to check for sanity: > package masked: www-servers/tomcat-10.0.8
I’m actually not sure if I can do this. OpenJDK 11 isn’t keyworded on x86 and there aren’t any binaries available to bootstrap. We may have to drop the keywords on x86?
well, in fact none of those packages needs java 11. only dev-java/eclipse-ecj needs java 11, but only for compilation, not runtime. and neither repoman nor pkgcheck complain on eclipse-ecj for unsatisfied dep. and even tomcat:9 depends on that version of eclipse-ecj and nothing is reported. so i suppose it should be fine, at least from the point of view of the checks.
(In reply to Miroslav Šulc from comment #10) > well, in fact none of those packages needs java 11. only > dev-java/eclipse-ecj needs java 11, but only for compilation, not runtime. > and neither repoman nor pkgcheck complain on eclipse-ecj for unsatisfied > dep. and even tomcat:9 depends on that version of eclipse-ecj and nothing is > reported. so i suppose it should be fine, at least from the point of view of > the checks. But how can I test it the first time in that case? I can’t compile it, right?
hm, i guess you are right. so thank you for minding this bug, lets let it open until it's resolved somehow :-)
Unable to check for sanity: > no match for package: www-servers/tomcat-10.0.8