Am 17.04.25 um 21:37 schrieb Paul Gevers:
Hi Michael,Thanks for reaching out. It's been a long time since I looked at dbconfig-common (and I'm not the author), so things are extremely rusty.On 17-04-2025 20:28, Michael Biebl wrote:kim.iserv.dev ~ # LC_ALL=C dpkg --configure -a Setting up rsyslog-pgsql (8.2302.0-1+deb12u1) ... dbconfig-common: writing config to /etc/dbconfig-common/rsyslog-pgsql.conf Not replacing deleted config file /etc/rsyslog.d/pgsql.confAre you sure that rsyslog-pgsql can handle an absent config file? ^^
If /etc/rsyslog.d/pgsql.conf is missing, rsyslog should just (re)start without the pgsql module being loaded, i.e. this functionality would simply be absent.
Remember that debian policy says that package have to respect the removal of a configuration file by the sys-admin, so dbconfig-common does that and it seems that it registered the file with ucf earlier and now thinks that it was removed.dbconfig-common: flushing administrative passwordBecause it seems like dbconfig-common exited gracefully here. So, I'm wondering if the failure happens during dbconfig-common or afterwards.Maybe you can try what happens if you install rsyslog-pgsql and opt-out of dbconfig-common help (I recall that's the first question).
It would indeed be good to see at which step exactly the postinst is failing.
Kim-Alexander, can you add a "set -x" right at the top to the scripts in /var/lib/dpkg/info/rsyslog-pgsql.p*
OpenPGP_signature.asc
Description: OpenPGP digital signature
