Le 14/08/2014 14:46, Dirk Eddelbuettel a écrit : > Sorry if I missed something ere, and I rushed the email out as I am on my way > out of the door.
Ok, let me recap. r-base build depends on default-jdk. Today default-jdk is an alias for openjdk-7-jdk, it installs a symlink from /usr/lib/jvm/default-java to /usr/lib/jvm/java-7-openjdk-amd64. r-base keeps the path to openjdk-7 in its configuration (/usr/lib/jvm/java-7-openjdk-amd64), instead of /usr/lib/jvm/default-java, and this path is used to build rJava. The issue arises when the default-jdk package is updated and points to the next version of Java. Since rjava build depends on default-jdk, it pulls openjdk-8-jdk, but the r-base configuration still points to /usr/lib/jvm/java-7-openjdk-amd64. Since openjdk-7 hasn't been installed the build fails. I think there is an inconsistency, because if you build depend on default-jdk you should use /usr/lib/jvm/default-java. And if you need /usr/lib/jvm/java-7-openjdk-amd64 you should build depend on openjdk-7-jdk. I see 3 possible solutions: 1. Change r-base to keep the path to /usr/lib/jvm/default-java in its configuration instead of /usr/lib/jvm/java-7-openjdk-amd64. This fixes the issue once and for all. 2. Change r-base and rjava to build depend on openjdk-7-jdk instead of default-jdk. They'll have to be updated again later to build depend on openjdk-8. 3. Wait until OpenJDK 8 becomes the default version of Java in Debian and rebuild r-base and rjava. But the issue will reappear when we transition to openjdk-9. Which solution do you prefer? Emmanuel Bourg -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
