Bug #2754
closed
The 2.4 rudder-jetty package fails to use chkconfig and fails to install
Added by Matthieu CERDA over 12 years ago.
Updated over 9 years ago.
Description
The 2.4 rudder-jetty package fails to use chkconfig and fails to install:
insserv: Service slapd has to be enabled to start service jetty
It is because rudder-inventory-ldap is installed after rudder-jetty, thus breaking dependencies.
We need to use insserv -f instead of chkconfig for a more laxist dependency checking.
- Status changed from In progress to Pending technical review
- % Done changed from 0 to 100
Applied in changeset commit:fa36934c52c0b67436b5e7cc798d644810ce0e0e.
Ouch, i'm not sure that this issue was for the 2.4 branch. The problem is present on 2.3 too and using zypper with non-intneractive mode result in error when install rudder-jetty.
- Target version changed from 2.4.0~beta3 to 2.3.9
Nicolas PERRON wrote:
Ouch, i'm not sure that this issue was for the 2.4 branch. The problem is present on 2.3 too and using zypper with non-intneractive mode result in error when install rudder-jetty.
Hmmm... ok, I saw that this commit has been reported to 2.3 branch
- Status changed from Pending technical review to Discussion
This fix is not appropriate for this problem. As described in #2883, the dependency explicited by the LSB header in jetty's init script is correct: starting jetty before slapd will not work.
This problem also occurs on Debian, as pointed out in #2730.
I'm going to revert this change and mark this as a duplicate of #2730 (that bug has all the logic about this described in it).
- Status changed from Discussion to Rejected
- Project changed from Rudder to 34
- Category deleted (
11)
- Project changed from 34 to Rudder
- Category set to Packaging
Also available in: Atom
PDF
Updated by Matthieu CERDA 
Updated by Nicolas PERRON 
Updated by Jonathan CLARKE 
Updated by