Package: postgresql-common
Version: 218
Severity: minor
User: debian...@lists.debian.org
Usertags: adequate obsolete-conffile
X-Debbugs-Cc: t...@mirbsd.de

[…]
Preparing to unpack .../30-postgresql-common_218_all.deb ...
Leaving 'diversion of /usr/bin/pg_config to /usr/bin/pg_config.libpq-dev by 
postgresql-common'
Unpacking postgresql-common (218) over (217) ...
[…]
Setting up postgresql-common (218) ...
Starting PostgreSQL 13 database server: main.
[…]
postgresql-common: obsolete-conffile /etc/apt/apt.conf.d/01autoremove-postgresql
postgresql-common: obsolete-conffile /etc/postgresql-common/createcluster.conf




Looking at these files, especially the first, I’m honestly not sure
whether I want to delete them. If they are not in the binary package
any more but used to be this is probably a bug?



-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'oldstable-updates'), (500, 
'buildd-unstable'), (500, 'unstable'), (500, 'oldstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.8.0-2-amd64 (SMP w/2 CPU threads)
Locale: LANG=C.UTF-8, 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
ii  debconf [debconf-2.0]     1.5.74
ii  lsb-base                  11.1.0
ii  perl                      5.30.3-4
ii  postgresql-client-common  218
ii  ssl-cert                  1.0.39
ii  ucf                       3.0043

Versions of packages postgresql-common recommends:
ii  e2fsprogs  1.45.6-1
ii  logrotate  3.16.0-3

Versions of packages postgresql-common suggests:
ii  libjson-perl  4.02000-2

-- 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/postgresql-common/createcluster.conf changed:
ssl = on
cluster_name = '%v/%c'
stats_temp_directory = '/var/run/postgresql/%v-%c.pg_stat_tmp'
log_line_prefix = '%%m [%%p] %%q%%u@%%d '
add_include_dir = 'conf.d'
include_dir '/etc/postgresql-common/createcluster.d'


-- debconf information:
* postgresql-common/ssl: true
* postgresql-common/obsolete-major:
  postgresql-common/catversion-bump:

Reply via email to