Bug#535442: postgresql: Broken upgrade when using insserv

[Kel Modderman]

Hi Martin,

CC changed to something which will reach Petter and I (initscripts-ng-devel),
your original mail seemed to escape into a crack.

On Sunday 05 July 2009 22:48:04 Martin Pitt wrote:
> Hello Petter, hello Kel,
> 
> I'm afraid I need your advice here.
> 
> Jeremy Lal [2009-07-02 10:02 +0200]:
> > With insserv package installed, and postgresql 8.3 installed,
> > i can't install the postgresql-8.4 package, see the aptitude log below.
> > Also AFAIR this problem did not happen during 8.2 -> 8.3 migration.
> >
> > insserv: script postgresql-8.4: service postgresql already provided!
> > insserv: exiting now!
> > dpkg : erreur de traitement de postgresql-8.4 (--configure) :
> >  le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
> 
> Indeed, postgresql 8.3 has
> 
> # Provides:             postgresql postgresql-8.3
> 
> while postgresql-8.4 has
> 
> # Provides:             postgresql postgresql-8.4
> 
> This was actually deliberate, so that dependencies can be formed both
> for version specific servers as well as "any postgresql". Is insserv
> designed to not get along with multiple packages providing the
> same service, or is this a bug? The LSB spec [1] doesn't say anything
> about requiring the Provides: names to be unique?

insserv is designed to not support multiple scripts claiming to provide
the same service. See #474515 for a previous discussion about it.
Should it be that way? dunno for sure.

System (or Virtual) facilities can be used for this purpose, though these
seem to be reserved for things defined in the LSB spec. insserv(8) describes
how they work.

> 
> Thanks,
> 
> Martin
> 
> [1] http://refspecs.freestandards.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/initscrcomconv.html
> 

Thanks, Kel.