Bug#540982: postgresql-common: dependencies insufficient for ssl-cert group

2009-08-23 Thread Martin Pitt
Hello,

Mark Eichin [2009-08-11  0:01 -0400]:
 If postgresql-8.3 is going to include the dependency *anyway*,
 perhaps debbugs#498406 should just be reverted?

Indeed, right now the dropping to recommends doesn't bring any value.
Seems it's quite impossible to provide out-of-the-box SSL support and
at the same time make it possible to remove ssl-cert :-(

Martin

-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#540982: postgresql-common: dependencies insufficient for ssl-cert group

2009-08-10 Thread Mark Eichin
Package: postgresql-common
Version: 94lenny1
Severity: normal

The ssl-cert package creates the ssl-cert group in its postinst.

postgresql-common does:

if getent group ssl-cert /dev/null; then
adduser --quiet postgres ssl-cert
fi

to add the postgres user to this group, but only if it exists.

I believe this was introduced with

postgresql-common (92) unstable; urgency=low
  * Demote ssl-cert Depends: to Recommends:. (Closes: #498406)
 -- Martin Pitt mp...@debian.org  Sun, 16 Nov 2008 13:42:31 +0100

since policy says A package will not be configured unless all of the
packages listed in its `Depends' field have been correctly
configured. but it says no such thing about Recommends...

There's an attempt to fix this in:

postgresql-8.3 (8.3.4-2) unstable; urgency=medium
   * Add dependency to ssl-cert. This has always been implicitly there through
 postgresql-common, but when upgrading -8.3 and ssl-cert at the same time,
 apt does not ensure to configure ssl-cert before postgresql-8.3 if there
 is no direct dependency. (Closes: #501690)
-- Martin Pitt mp...@debian.org Sat, 11 Oct 2008 14:28:34 +0200

but I don't see any reason that would actually help, since the
postgresql-8.3 ordering is irrelevant, at least on fresh installs.

I've actually observed this in a lenny-based install:

 Setting up postgresql-client-common (94lenny1) ...
 Setting up postgresql-client-8.3 (8.3.7-0lenny1) ...
 Setting up postgresql-common (94lenny1) ...
 Setting up openssl-blacklist (0.4.2) ...
 Setting up ssl-cert (1.0.23) ...
 Setting up postgresql-8.3 (8.3.7-0lenny1) ...

that is, the inconsistency is real (I found this by looking at why an
upgraded system and a newly installed system differed.)  If
postgresql-8.3 is going to include the dependency *anyway*, perhaps
debbugs#498406 should just be reverted?

-- System Information:
Debian Release: 5.0.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org