touch-packages team mailing list archive

[Steve Langasek <steve.langasek@xxxxxxxxxxxxx>]

The error in the log is:

Setting up initscripts (2.88dsf-41ubuntu18) ...
insserv: warning: script 'S99teamviewer' missing LSB tags and overrides
insserv: warning: script 'cron' missing LSB tags and overrides
insserv: Default-Start undefined, assuming empty start runlevel(s) for script `cron'
insserv: Default-Stop  undefined, assuming empty stop  runlevel(s) for script `cron'
insserv: warning: script 'teamviewer_start' missing LSB tags and overrides
insserv: There is a loop between service rc.local and procps if started
insserv:  loop involving service procps at depth 2
insserv:  loop involving service udev at depth 1
insserv: There is a loop at service rc.local if started
insserv: Starting teamviewer_start depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting teamviewer_start depends on rc.local and therefore on system facility `$all' which can not be true!
<snip>
insserv: Max recursions depth 99 reached
insserv:  loop involving service hddtemp at depth 1
<snip>
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header

This is caused by a non-Ubuntu init script on your system,
/etc/init.d/teamviewer_start, which is not an LSB init script, which
prevents the system from calculating boot ordering on upgrade.

So your non-Ubuntu init script is archaic and doesn't work right on a
recent system - however, Ubuntu should handle this more gracefully on
upgrade, rather than breaking the upgrade in the middle.

Dimitri, do you have any insight into how this should be handled?  I'm
sure it wasn't the intention to have systems with non-Ubuntu init
scripts fail to upgrade, but I don't remember what the plan was for
handling this case.

** Changed in: sysvinit (Ubuntu)
     Assignee: (unassigned) => Dimitri John Ledkov (xnox)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1440180

Title:
  package initscripts 2.88dsf-41ubuntu18 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in sysvinit package in Ubuntu:
  New

Bug description:
  I have no idea. The seems to have failed. If 1/99 fails, this is my
  second of two that has failed. Why am I 1/10000?

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: initscripts 2.88dsf-41ubuntu18
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  Uname: Linux 3.13.0-48-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: amd64
  Date: Fri Apr  3 15:16:04 2015
  DuplicateSignature: package:initscripts:2.88dsf-41ubuntu18:subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error exit status 1
  InstallationDate: Installed on 2014-08-09 (237 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
  SourcePackage: sysvinit
  Title: package initscripts 2.88dsf-41ubuntu18 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to utopic on 2015-04-03 (0 days ago)
  mtime.conffile..etc.default.rcS: 2014-08-08T23:23:35.190844

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1440180/+subscriptions