-
Bug
-
Resolution: Duplicate
-
Minor
-
None
-
ubuntu 16.04
While trying to test 2.107.3 I ran into the debian package not depending on any jre anymore.
I.e.:
1) apt-get install jenkins fails, jenkins can't be started because java NotFound
2) apt-get install default-jre-headless jenkins fails, systemd tries to start jenkins before installing the jre.
Requiring users to do 'apt-get install default-jre-headless' then 'apt-get install jenkins' is not the way package dependencies should work IMHO.
- duplicates
-
JENKINS-51253 jenkins_2.107.3_all.deb depends on java being installed but no longer has this explicit dependency
-
- Closed
-
[JENKINS-51226] debian package must depend on *some* jre
Description |
Original:
While trying to test 2.107.3 I ran into the debian package not depending on any jre anymore. I.e.: apt-get install default-jre-headless jenkins fails, systemd tries to start jenkins before installing the jre. Requiring users to do 'apt-get install default-jre-headless' then 'apt-get install jenkins' is not the way package dependencies should work ? |
New:
While trying to test 2.107.3 I ran into the debian package not depending on any jre anymore. I.e.: 1) apt-get install jenkins fails, jenkins can't be started because java NotFound 2) apt-get install default-jre-headless jenkins fails, systemd tries to start jenkins before installing the jre. Requiring users to do 'apt-get install default-jre-headless' then 'apt-get install jenkins' is not the way package dependencies should work IMHO. |
Link |
New:
This issue duplicates |
Resolution | New: Duplicate [ 3 ] | |
Status | Original: Open [ 1 ] | New: Closed [ 6 ] |