On Wed, 12 Feb 2014 23:04:11 +0100 Petter Reinholdtsen wrote:
> [Jan Binder]
> >> I do not have systemd installed. Perhaps installing it is enough
> >> to confuse insserv to expect it to be running?
> > That might be enough.
>
> I found the trigger:
>
> root@mybox:~# strace -o
Am Dienstag, 18. Februar 2014, 00:20:40 schrieb Petter Reinholdtsen:
[Jan Binder]
Ok, here comes the make-testsuite output.
If debsums can be trusted, none of my initscripts were modified from
the packaged versions.
Thank you. Still not able to reproduce it with my locally built
[Jan Binder]
Ok, I agree that the systemd messages are gone with the SVN version
and were not fatal:
Good. I'll upload a les noisy version to experimental.
Setting up initscripts (2.88dsf-49) ...
insserv: FATAL: service dnsmasq is missed in the runlevels 2 3 4 5 to use
service
[Jan Binder]
Ok, here comes the make-testsuite output.
If debsums can be trusted, none of my initscripts were modified from
the packaged versions.
Thank you. Still not able to reproduce it with my locally built
insserv. No idea why. Will keep trying a bit more, but welcome
ideas. :)
--
I've tried to reproduce this part of your problem report:
* What was the outcome of this action?
Cannot install initscripts after installing insserv 1.16 because it
tries to connect to systemd which is present on the system but not
used as PID 1.
I have no problem installing initscripts or
Am Donnerstag, 13. Februar 2014, 11:11:26 schrieb Petter Reinholdtsen:
I've tried to reproduce this part of your problem report:
* What was the outcome of this action?
Cannot install initscripts after installing insserv 1.16 because it
tries to connect to systemd which is present on the
Package: insserv
Version: 1.16.0-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
* What led up to the situation?
After having installed insserv 1.16, installing any version of initscripts
leads to the error message shown in bug #738532.
* What exactly
Control: reassign 738532 insserv
Control: found 738532 1.16.0-1
[Jan Binder]
Dear Maintainer,
Thank you for your report. Very glad to have more testers of the new
insserv version. :)
* What led up to the situation?
After having installed insserv 1.16, installing any version of
Am Mittwoch, 12. Februar 2014, 22:04:20 schrieben Sie:
Control: reassign 738532 insserv
Control: found 738532 1.16.0-1
[Jan Binder]
Dear Maintainer,
Thank you for your report. Very glad to have more testers of the new
insserv version. :)
* What led up to the situation?
[Jan Binder]
I do not have systemd installed. Perhaps installing it is enough
to confuse insserv to expect it to be running?
That might be enough.
I found the trigger:
root@mybox:~# strace -o /tmp/foo insserv
root@mybox:~# grep systemd /tmp/foo
access(/bin/systemd, F_OK)= -1
Can you please test the svn version of the package available from
URL: svn://svn.debian.org/initscripts-ng/trunk/src/insserv and let
me know if it solve your problem? It improve the detection of systemd
and fix a buffer overflow.
It seem to work for me.
--
Happy hacking
Petter Reinholdtsen
Am Mittwoch, 12. Februar 2014, 23:49:50 schrieb Petter Reinholdtsen:
Can you please test the svn version of the package available from
URL: svn://svn.debian.org/initscripts-ng/trunk/src/insserv and let
me know if it solve your problem? It improve the detection of systemd
and fix a buffer
[Jan Binder]
I have trouble building a packge. It looks like the last patch just
fails:
Right. Conflict with the 190_disable_debug_output.patch patch. Sorry
for not noticing earlier, not quite sure how I managed to build
without discovering it myself.
Anyway, fixed in svn. Please try
13 matches
Mail list logo