You are not logged in.
Hello!
I am just buff when I see:
$ apt install -V --assume-no tomcat10
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
tomcat10 : Depends: systemd (>= 238) but it is not installable or
systemd-tmpfiles
Recommends: libtcnative-1 (>= 1.2.18) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.Not to mention, that I've run apt update directly before.
Anone an idea?
Thanks,
Manfred
Offline
I try to avoid running Tomcat natively even if I can.
For me, it is much better to use a Docker image with Tomcat, eventually modify it, and then run the applications there. Tomcat running natively is subject to all sorts of interferences, version conflicts etc, in principle the runtime behavior may be affected by even small system modifications. And, at least over some years of use, problems are likely to occur. As long as you can build the packages to run (in a pinch, you can setup a Java container for that), there is very little fuzz running Tomcat that way.
It is also a safe way to work if you, like me, build packages to be deployed at production servers running Docker. (Or Podman, or...)
Offline