Due to portage changes Before: ~ % cat /var/db/pkg/dev-java/ant-core-1.9.2/DEPEND >=virtual/jdk-1.5 !dev-java/ant-tasks !dev-java/ant-optional >=dev-java/java-config-2.1.9-r1 >=dev-java/javatoolkit-0.3.0-r2 >=dev-lang/python-2.4 After re-emerging: ~ % cat /var/db/pkg/dev-java/ant-core-1.9.2/DEPEND || ( >=virtual/jdk-1.5 dev-java/gcj-jdk ) !dev-java/ant-tasks !dev-java/ant-optional >=dev-java/java-config-2.2.0-r3 >=dev-java/javatoolkit-0.3.0-r2
Please explain the problem and then the solution in clear terms.
I'm guessing this has something to do with Portage now defaulting to --dynamic-deps=n but I still don't know what you want us to do here? I believe it is acceptable to bump versions of existing dependencies within eclasses or something like that, I forget the exact rule.
Users (like me) can have DEPEND entries that were removed, it can be fixed with --changed-deps=y but Zac said to make revbump requests in 645284
Okay, so to be clear, it's the dev-lang/python dependency you're flagging up? Given that everyone has this anyway and Ant is well overdue a bump, I don't think this is really worth the extra dev time and user build time.
Yeah, with --dynamic-deps=n ant-core was wanting me to install the newest python, not too sure why my current version of python installed wasn't fulfilling it either. (I have 2.7 and 3.5 installed and it wanted 3.6 because of the stale entries)
ant-core-1.9.13 and ant-core-1.10.5 are now in the tree so the issue should be gone. once one of them gets stabilized, 1.9.2 will be removed. marking it as fixed as the issue should be gone with update to new version.
