Ubuntu 12.04 to 14.04 upgrade fails - missing LSB comment in virtuoso-nepomuk

Bug #1389320 reported by Bruce Wolfe
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)
Triaged
Undecided
Unassigned

Bug Description

Upgrading to 14.04, error:

Could not install "kmod"

"subprocess installed post-installation script returned error exit status 1"

1. Ubuntu 14.04
2. kmod:
  Installed: 18-1ubuntu2
  Candidate: 18-1ubuntu2
  Version table:
 *** 18-1ubuntu2 0
        500 http://mirrors.us.kernel.org/ubuntu/ utopic/main amd64 Packages
        100 /var/lib/dpkg/status
3. Install correctly
4. Error, aborts upgrade, states will start "dpkg --configure -a"

description: updated
Revision history for this message
Bruce Wolfe (brucewolfe-sf) wrote :
Revision history for this message
Bruce Wolfe (brucewolfe-sf) wrote :

Possible solution: Find this working for some but not 'sysv-rc'.
http://askubuntu.com/questions/543857/getting-error-with-dpkg/544070#544070

Revision history for this message
Bruce Wolfe (brucewolfe-sf) wrote :

Solution in #2 works.
For some reason either there is an overwrite issue to /etc/init.d or there is a missing process to 'rm' items in this folder before upgrading each pkg.

summary: - Could not install kmod
+ Ubuntu 12.04 to 14.04 upgrade fails - missing LSB comment
Revision history for this message
Brian Murray (brian-murray) wrote : Re: Ubuntu 12.04 to 14.04 upgrade fails - missing LSB comment

From the log file:

Setting up openafs-client (1.6.9-2) ...
insserv: Script virtuoso-nepomuk is broken: missing end of LSB comment.
insserv: exiting now!
update-rc.d: error: insserv rejected the script header

Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:

  apport-collect 1389320

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

Changed in ubuntu-release-upgrader (Ubuntu):
status: New → Incomplete
summary: - Ubuntu 12.04 to 14.04 upgrade fails - missing LSB comment
+ Ubuntu 12.04 to 14.04 upgrade fails - missing LSB comment in virtuoso-
+ nepomuk
Revision history for this message
Bruce Wolfe (brucewolfe-sf) wrote : Re: [Bug 1389320] Re: Ubuntu 12.04 to 14.04 upgrade fails - missing LSB comment

Sure thing. Just to let you know, the latest kernel is causing bootup
problems. I had to boot using 3.13.0-40 in order to finish the upgrade. I
am waiting for the 800 files to finish downloading/installing. I'll update
the bug report.

On Wed, Nov 5, 2014 at 9:05 AM, Brian Murray <email address hidden> wrote:

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Please execute the following command, as it will
> automatically gather debugging information, in a terminal:
>
> apport-collect 1389320
>
> When reporting bugs in the future please use apport by using 'ubuntu-
> bug' and the name of the package affected. You can learn more about this
> functionality at https://wiki.ubuntu.com/ReportingBugs.
>
> ** Changed in: ubuntu-release-upgrader (Ubuntu)
> Status: New => Incomplete
>
> ** Summary changed:
>
> - Ubuntu 12.04 to 14.04 upgrade fails - missing LSB comment
> + Ubuntu 12.04 to 14.04 upgrade fails - missing LSB comment in
> virtuoso-nepomuk
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1389320
>
> Title:
> Ubuntu 12.04 to 14.04 upgrade fails - missing LSB comment in virtuoso-
> nepomuk
>
> Status in “ubuntu-release-upgrader” package in Ubuntu:
> Incomplete
>
> Bug description:
> Upgrading to 14.04, error:
>
> Could not install "kmod"
>
> "subprocess installed post-installation script returned error exit
> status 1"
>
> 1. Ubuntu 14.04
> 2. kmod:
> Installed: 18-1ubuntu2
> Candidate: 18-1ubuntu2
> Version table:
> *** 18-1ubuntu2 0
> 500 http://mirrors.us.kernel.org/ubuntu/ utopic/main amd64
> Packages
> 100 /var/lib/dpkg/status
> 3. Install correctly
> 4. Error, aborts upgrade, states will start "dpkg --configure -a"
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1389320/+subscriptions
>

Revision history for this message
Felix Geyer (debfx) wrote :

virtuoso-nepomuk contains the broken init script. The package has been removed after the precise release.

Adding a quirk to release-upgrader to remove the init script is the only option I can think of.
SRUing the package in precise wouldn't work since that won't affect systems that have been upgraded from precise to trusty.

Changed in ubuntu-release-upgrader (Ubuntu):
status: Incomplete → Triaged
Revision history for this message
Felix Geyer (debfx) wrote :

In one particular case a trusty->utopic failed because the virtuoso-nepomuk package was still present in rc state.

Revision history for this message
Laurence Gordon (larry-gordon) wrote :

It happened for my in an upgrade from 14.10 to 15.04. Adding the ending comment "### END INIT INFO
" fixed the issue.

So that this:

### BEGIN INIT INFO
# Provides: virtuoso
# Required-Start: $syslog
# Required-Stop: $syslog
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Start Virtuoso database server on startup
# Description: Start and stop the primary instance of Virtuoso running
# in /var/lib/virtuoso/db/. The first time this runs, it loads the
# Conductor administrative package.
###

Becomes this:

### BEGIN INIT INFO
# Provides: virtuoso
# Required-Start: $syslog
# Required-Stop: $syslog
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Start Virtuoso database server on startup
# Description: Start and stop the primary instance of Virtuoso running
# in /var/lib/virtuoso/db/. The first time this runs, it loads the
# Conductor administrative package.
### END INIT INFO

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.