Re: Bug#228878: libtomcat4-java: should have a dependency on java-virtual-machine
josh buhl wrote:
Here's the deal: I have Sun's j2sdk1.4.2_01 installed. That pretty much
takes care of all the java dependencies, but since it's not a debian
package, none of the debian java stuff knows about it. I don't want to
install any of the packages that provide java2-runtime, since I've
already got the real deal. However, any package that depends on
java2-runtime or j2re1.4 for example refuses to install, although they
would run fine if they would install themselves. It seems that
installing the java-virtual-machine-dummy package should convince all
other packages that their dependencies are covered. That's what it's
there for.
The latest libtomcat4-java package has this dependency removed (for
different reasons) but this won't help you since all other Java library
packages that libtomcat4-java depnds on still have a dependency on
java2-runtime which can't be satisfied on your system.
No I can't. It reports unmet dependencies, saying it depends either on
java2-runtime, j2re1.4 or j2re1.3. See above.
So how did you satisfy tomcat4's dependency on java-virtual-machine? You
need to install some Debian package that provides j-v-m.
Actually, when I come to think of it since it's just a library, I don't
see why libtomcat4-java should worry about whether java2-runtime or
j2re1.4 is installed or not.
That's actually exactly my opinion. But some people on the debian-java
mailing list have a different opinion. Maybe they want to continue the
discussion with you (CC-ing debian-java)?
All I'm saying is that there should be some dummy package which users
who have sun's sdk or jre installed can install, to tell other debian
packages that these dependencies are all taken care of. I thought that's
You can use equivs for that. See README.Debian in java-common for details.
what java-virtual-machine-dummy was for, and if that is indeed correct,
then packages like libtomcat4-java should be just as happy with the
dummy as with sablevm (the debian default providing java2-runtime.)
The dummy packages have been removed from unstable and should also be
removed from testing. But this is not going to happen since it's the
only package there that provides java2-runtime and the Debian archive
maintainance scripts won't allow unresolved dependencies in testing.
Stefan
Reply to: