Your message dated Mon, 17 Jul 2017 15:06:31 -0400
with message-id
<CAAfdZj8NLjv7wuy+hYgTbdyodfa=v7GjwXwbSO6LK30N6=p...@mail.gmail.com>
and subject line Re: Bug#849284: insserv: fopen(/etc/insserv.conf): No such
file or directory
has caused the Debian Bug report #849284,
regarding insserv: fopen(/etc/insserv.conf): No such file or directory
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
849284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849284
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: insserv
Version: 1.16.0-5
# grep -B 2 insserv.conf /var/log/apt/term.log
Selecting previously unselected package ppp.
Preparing to unpack .../1065-ppp_2.4.7-1+4_amd64.deb ...
insserv: fopen(/etc/insserv.conf): No such file or directory
--
Setting up acpi-fakekey (0.142-8) ...
Created symlink /etc/systemd/system/sockets.target.wants/acpi-fakekey.socket →
/lib/systemd/system/acpi-fakekey.socket.
insserv: fopen(/etc/insserv.conf): No such file or directory
--
Setting up perforate (1.2-5.1) ...
Setting up pcmciautils (018-8) ...
insserv: fopen(/etc/insserv.conf): No such file or directory
--
Setting up exim4-base (4.88~RC6-1) ...
exim: DB upgrade, deleting hints-db
insserv: fopen(/etc/insserv.conf): No such file or directory
--
Setting up at (3.1.20-3) ...
Created symlink /etc/systemd/system/multi-user.target.wants/atd.service →
/lib/systemd/system/atd.service.
insserv: fopen(/etc/insserv.conf): No such file or directory
--
Setting up smartmontools (6.5+svn4324-1) ...
Created symlink /etc/systemd/system/multi-user.target.wants/smartd.service →
/lib/systemd/system/smartd.service.
insserv: fopen(/etc/insserv.conf): No such file or directory
--
Setting up libgraphite2-3:amd64 (1.3.9-2) ...
Setting up rsync (3.1.2-1) ...
insserv: fopen(/etc/insserv.conf): No such file or directory
insserv: fopen(/etc/insserv.conf): No such file or directory
--
Created symlink /etc/systemd/system/sockets.target.wants/acpid.socket →
/lib/systemd/system/acpid.socket.
Created symlink /etc/systemd/system/paths.target.wants/acpid.path →
/lib/systemd/system/acpid.path.
insserv: fopen(/etc/insserv.conf): No such file or directory
--
Removing obsolete dictionary files:
Created symlink /etc/systemd/system/multi-user.target.wants/postgresql.service
→ /lib/systemd/system/postgresql.service.
insserv: fopen(/etc/insserv.conf): No such file or directory
--
Setting up resolvconf (1.79) ...
Created symlink /etc/systemd/system/sysinit.target.wants/resolvconf.service →
/lib/systemd/system/resolvconf.service.
insserv: fopen(/etc/insserv.conf): No such file or directory
--- End Message ---
--- Begin Message ---
Version: 1.49
On Wed, 28 Dec 2016 11:21:32 +0100 Petter Reinholdtsen <p...@hungry.com>
wrote:
>
> Control: reassign -1 init-system-helpers
> Control: found -1 1.46
>
> [積丹尼 Dan Jacobson]
> > We see the problem only occurs between the time insserv has been
> > unpacked, and when it is finally set up.
>
> Right. The I suspect the problem is in update-rc.d from
> init-system-helpers, using the existence of insserv to decide if it
> should be used, while it should look for both insserv in PATH and
> /etc/insserv.conf before using it. This was not really a problem when
> insserv was installed by debootstrap, but installing it later with lots
> of other packages will expose it.
>
> I suspect something like this will solve it (untested patch):
Thanks for the patch. I have modified it a bit and applied in 1.49.
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
