package runit 2.1.2-3ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #1656732 reported by George Kontis
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
runit (Ubuntu)
New
Undecided
Unassigned

Bug Description

replacing systemd with upstart and runit gave this error

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: runit 2.1.2-3ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
AptOrdering:
 fgetty: Install
 runit: Install
 fgetty: Configure
 runit: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Mon Jan 16 05:08:49 2017
Dependencies:
 fgetty 0.7-1
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu5
 libgcc1 1:6.0.1-0ubuntu1
DuplicateSignature:
 package:runit:2.1.2-3ubuntu1
 Setting up runit (2.1.2-3ubuntu1) ...
 start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
 dpkg: error processing package runit (--configure):
  subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2016-11-24 (52 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt 1.2.18
SourcePackage: runit
Title: package runit 2.1.2-3ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
George Kontis (giormatsis) wrote :
Revision history for this message
Hans Joachim Desserud (hjd) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1448164, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.