Package: postgresql-common
Version: 225+deb11u1
Severity: normal
User: debian...@lists.debian.org
Usertags: adequate obsolete-conffile
X-Debbugs-Cc: t...@mirbsd.de
After upgrading…
Unpacking postgresql-common (225+deb11u1) over (225) ...
… adequate reports:
postgresql-common: obsolete-conffile /etc/apt/apt.conf.d/01autoremove-postgresql
The file however begins with:
// NO NOT EDIT!
// File maintained by /usr/share/postgresql-common/pg_updateaptconfig.
My suspiction here is that the file once was a conffile but is now
generated by that script, but the conffile removal was not correctly
done.
It’d probably be best to remove the conffile and name the file that
the script generates differently, so that problem cannot occur.
-- System Information:
Debian Release: 11.8
APT prefers oldstable-updates
APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500,
'oldstable-proposed-updates'), (500, 'oldoldstable-updates'), (500,
'oldoldstable-proposed-updates'), (500, 'oldoldstable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-26-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)
Versions of packages postgresql-common depends on:
ii adduser 3.118+deb11u1
ii debconf [debconf-2.0] 1.5.77
ii lsb-base 11.1.0
ii perl 5.32.1-4+deb11u2
ii postgresql-client-common 225+deb11u1
ii ssl-cert 1.1.0+nmu1
ii ucf 3.0043
Versions of packages postgresql-common recommends:
ii e2fsprogs 1.46.2-2
ii logrotate 3.18.0-2+deb11u2
Versions of packages postgresql-common suggests:
ii libjson-perl 4.03000-1
-- Configuration Files:
/etc/apt/apt.conf.d/01autoremove-postgresql changed:
// NO NOT EDIT!
// File maintained by /usr/share/postgresql-common/pg_updateaptconfig.
//
// Mark all PostgreSQL packages as NeverAutoRemove for which PostgreSQL
// clusters exist. This is especially important when the "postgresql" meta
// package changes its dependencies to a new version, which might otherwise
// trigger the old postgresql-NN package to be automatically removed, rendering
// the old database cluster inaccessible.
APT
{
NeverAutoRemove
{
"^postgresql.*-13";
};
};
/etc/sysctl.d/30-postgresql-shm.conf changed:
kernel.shmmax=268435456
-- debconf information:
postgresql-common/ssl: true
* postgresql-common/obsolete-major:
postgresql-common/catversion-bump:
