Hello Bastian, CC'ing Petter for advice.
Bastian Blank [2010-08-06 16:32 +0200]: > Package: postgresql-common > Version: 110 > Severity: grave > > postgresql-common fails to upgrade: > | Setting up postgresql-client-common (110) ... > | Setting up postgresql-common (110) ... > | Installing new version of config file /etc/init.d/postgresql ... > | insserv: script postgresql: service postgresql already provided! > | insserv: exiting now! > | update-rc.d: error: insserv rejected the script header > | dpkg: error processing postgresql-common (--configure): > | subprocess installed post-installation script returned error exit status 1 > | Errors were encountered while processing: > | postgresql-common > > | # grep postgresql -r /etc/init.d | grep Provides > | /etc/init.d/postgresql:# Provides: postgresql > | /etc/init.d/postgresql-8.3:# Provides: postgresql postgresql-8.3 > > The old postgresql-8.3 init script, which is not considered to be broken > by the new postgresql-common, already provides postgresql. At this point I'm not quite sure what to do about this still. The current -8.3 and -8.4 already remove the init script and remove an unmodified one on upgrade (see #474515), and postgresql-common now ships a single one. I do not want to Breaks: older versions of -8.3, since that would break backportability. The common init script does not touch a cluster version if that version already has its own init script. So at this point I'm inclined to either reassign this to insserv (see the discussion in #474515), or mark as "wontfix". The former would probably be appropriate as well, since the nowhere the LSB specifies that Provides: must be unique. So this could hit more packages than just PostgreSQL. Thanks, Martin -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
signature.asc
Description: Digital signature
