Fresh installation fails

Bug #2002583 reported by Guus Houtzager
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
perdition (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Hi,

There's a bug in the postinstall scripts in the Jammy version of Perdition which breaks new installations because "apt install perdition" fails. It's already fixed in the Kinetic version, but since Jammy is an LTS release, I think it would be good to backport the fix to Jammy.
Details:

Doing "apt install perdition":
...
Setting up perdition (2.2-3.1build3) ...
Failed to stop perdition.service: Unit perdition.service not loaded.
invoke-rc.d: initscript perdition, action "stop" failed.
dpkg: error processing package perdition (--configure):
 installed perdition package post-installation script subprocess returned error exit status 5
Processing triggers for libc-bin (2.35-0ubuntu3.1) ...
Errors were encountered while processing:
 perdition

The postinstall script does this:
# invoke-rc.d perdition stop
Failed to stop perdition.service: Unit perdition.service not loaded.
invoke-rc.d: initscript perdition, action "stop" failed.

This has been reported in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999659
This is the fix:

perdition (2.2-3.2) unstable; urgency=medium

  * Non-maintainer upload.
  * Add exit code true after invoke-rc.d in the files below (Closes: #999659).
    Thanks to Sergey Spiridonov.
    - perdition-ldap.postinst
    - perdition-ldap.prerm
    - perdition-mysql.postinst
    - perdition-mysql.prerm
    - perdition-odbc.postinst
    - perdition-odbc.prerm
    - perdition-postgresql.postinst
    - perdition-postgresql.prerm
    - perdition.postinst
    - perdition.preinst
    - perdition.prerm

 -- Marcos Talau <email address hidden> Thu, 31 Mar 2022 22:39:14 -0300

What this does is add "|| true" to a whole bunch of scripts including the postinst script which fixes the installation issue.

There's a workaround: after "apt install perdition" has failed, run "systemctl daemon-reload" and then "dpkg --configure -a" and everything is happy. Not so fun when you try to use automated installs though.
So can you please backport the the fix above to the Jammy version? Thanks!

Cheers,

Guus

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in perdition (Ubuntu):
status: New → Confirmed
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.