Your message dated Fri, 16 Dec 2016 06:11:42 +0100
with message-id <[email protected]>
and subject line Re: sysv-rc: error during upgrade due to systemd timeout
has caused the Debian Bug report #816868,
regarding sysv-rc: error during upgrade due to systemd timeout
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 [email protected]
immediately.)


-- 
816868: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816868
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sysv-rc
Version: 2.88dsf-59.3
Severity: normal


Got this today while upgrading:

Preparing to unpack .../sysv-rc_2.88dsf-59.3_all.deb ...
Unpacking sysv-rc (2.88dsf-59.3) over (2.88dsf-59.2) ...
Setting up sysvinit-utils (2.88dsf-59.3) ...
Setting up sysv-rc (2.88dsf-59.3) ...
Processing triggers for systemd (228-2) ...
Failed to execute operation: Connection timed out
dpkg: error processing package systemd (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 systemd
E: Sub-process /usr/bin/dpkg returned an error code (1)
Failed to perform requested operation on package.  Trying to recover:
Setting up libquadmath0:i386 (5.3.1-10) ...
[lots more "Setting up" messages, none related to sysv]

I've no idea what, exactly, it's complaining about.

The sysv-rc package itself claims to be installed okay and of the correct
version when queried with "dpkg -s", although I haven't yet actually
tried rebooting.


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 4.3.0-1-686-pae (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages sysv-rc depends on:
ii  debconf [debconf-2.0]  1.5.58
ii  init-system-helpers    1.29
ii  insserv                1.14.0-5.3
ii  startpar               0.59-3
ii  sysvinit-utils         2.88dsf-59.3

Versions of packages sysv-rc recommends:
ii  lsb-base  9.20150917

Versions of packages sysv-rc suggests:
pn  bum  <none>

-- debconf information:
  sysv-rc/unable-to-convert:
  sysv-rc/convert-legacy: true

--- End Message ---
--- Begin Message ---
On Sat, 5 Mar 2016 18:46:45 -0500 Farmbuyer <[email protected]> wrote:
> Package: sysv-rc
> Version: 2.88dsf-59.3
> Severity: normal
> 
> 
> Got this today while upgrading:
> 
> Preparing to unpack .../sysv-rc_2.88dsf-59.3_all.deb ...
> Unpacking sysv-rc (2.88dsf-59.3) over (2.88dsf-59.2) ...
> Setting up sysvinit-utils (2.88dsf-59.3) ...
> Setting up sysv-rc (2.88dsf-59.3) ...
> Processing triggers for systemd (228-2) ...
> Failed to execute operation: Connection timed out
> dpkg: error processing package systemd (--configure):
>  subprocess installed post-installation script returned error exit status 1
> Errors were encountered while processing:
>  systemd
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> Failed to perform requested operation on package.  Trying to recover:
> Setting up libquadmath0:i386 (5.3.1-10) ...
> [lots more "Setting up" messages, none related to sysv]
> 
> I've no idea what, exactly, it's complaining about.
> 
> The sysv-rc package itself claims to be installed okay and of the correct
> version when queried with "dpkg -s", although I haven't yet actually
> tried rebooting.
> 
> 
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (500, 'testing')
> Architecture: i386 (i686)
> 
> Kernel: Linux 4.3.0-1-686-pae (SMP w/1 CPU core)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: sysvinit (via /sbin/init)

If /sbin/init is the active init, the systemd trigger should be a NOP.

If you have a /run/systemd/system directory but systemd is not the
actual init, then something is messed up on your systemd.



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply via email to