I’m not sure who to blame here, but someone should get drawn and quartered.
I’m working on setting up Azureus Vuze to run headless on yawl while I’m not around. To test it, I decided to install and run it on clipper.
Things were going quite well – with aptitude installing Vuze fine. I had to run java-update-alternatives to make sure I had the right JVM:
dbs@clipper:/usr/bin$ sudo update-java-alternatives -l java-6-sun 63 /usr/lib/jvm/java-6-sun dbs@clipper:/usr/bin$ sudo update-java-alternatives --set java-6-sun
Then, Vuze wouldn’t start:
dbs@clipper:~$ vuze exec: 11: /usr/lib/jvm/java-6-openjdk/jre/bin/java: not found
“Oh no, they didnt….”
They did. The vuze script starts up the azureus startup script, which is hardcoded to the java-6-openjdk java path:
dbs@clipper:/usr/bin$ head -5 azureus #!/bin/sh JAVA='/usr/lib/jvm/java-6-openjdk/jre/bin/java -Xmx1024M'
This isn’t hard to fix, it’s just a quick edit to the startup script – but cmon package maintainers. Get a grip here. The whole java-alternatives stuff is specifically made to avoid this sort of crap. Get it together!
