Package: postgresql-client-common Version: 170 Severity: normal Dear Maintainer,
Running a check that identifies conffiles that no longer are shipped by
a package I received an alert about /etc/postgresql-common/supported_versions
on some jessie systems. So that file had been provided by
postgresql-client-common in the past, but not longer.
Further investigation gave a picture of what had happened: Appearently
postgresql-client-common ships that file only in a backport version,
and indeed a backport for wheezy had been installed in the past, prior
to the jessie upgrade.
So technically this is in violation of policy 10.7.3 "Obsolete
configuration files without local changes should be removed by the
package during upgrade". It might be debatable whether this applies for
backport packages, and it's a "should" not a "must", yadda yadda. Can
we just agree this behaviour is somewhat confusing and certainly not
intended?
In other words, can you please check why this file is provided by a
backport version only and fix this in a sane way? Providing it also in
regular versions, never provide it, remove it in certain upgrade paths,
whatever?
FWIW, this still exists in version 170, I've checked using a local
backport for jessie.
Regards,
Christoph
-- System Information:
Debian Release: stretch/sid
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.1.14 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect
signature.asc
Description: Digital signature
