Your message dated Sat, 02 Feb 2019 10:26:18 +0000
with message-id <e1gpsv9-0004f4...@eggs.gnu.org>
and subject line Re: Bug#738775: insserv: Insserv 1.16 tries to connect to 
systemd even though system is running on sysv-init
has caused the Debian Bug report #738775,
regarding insserv: Insserv 1.16 tries to connect to systemd even though system 
is running on sysv-init
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.)


-- 
738775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738775
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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 did you do (or not do) that was effective (or
     ineffective)?
   Dist-upgraded to experimental, initscrpts install failed with error.
   Tried to install any available verion of initscripts, all failed in the same 
manner.
   Forcefully removed initscripts, forcefully downgraded insserv to 1.14.
   Installing initscripts now worked.

   * 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.

   * What outcome did you expect instead?
   insserv should not fail when it cannot connect to systemd and systemd is not 
running as PID 1.
   Instead it should talk to sysv-init or whatever else it supports.


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.13.0-rc8 (SMP w/8 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages insserv depends on:
ii  libc6        2.18-0experimental1
ii  libdbus-1-3  1.8.0-1

insserv recommends no packages.

Versions of packages insserv suggests:
ii  bootchart2  0.14.4-3

-- debconf information:
  insserv/enable: false

--- End Message ---
--- Begin Message ---
Since 1.18.0-1 (1.18.0-2 in unstable) debian packaging patch-out
integration with systemd, thus closing this bug.

Dear submitter, if you can somehow reproduce this bug with current
version of insserv, feel free to reopen this bug.
-- 
        Note, that I send and fetch email in batch, once every 24 hours.
                 If matter is urgent, try https://t.me/kaction
                                                                             --

--- End Message ---

Reply via email to