On Wed, Aug 27, 2025 at 11:21 AM Chris Hofstaedtler <[email protected]> wrote:
> OTOH given procps no longer ships the conffile, it should also not
> just leave an unowned conffile around. In this situation procps
> should probably leave a .dpkg-bak file if the conffile was modified.
> But this is also not the optimal result, as the file will not be
> read 8-)

This is exactly what actually has happened on my system during the
upgrade to trixie.

> IMO the best option is to put good, tested advice into the release
> notes and into NEWS.Debian of procps. Stable update for the
> NEWS.Debian change should also be uncontroversial in my opinion.

I think it is more important to publish the advice soon, than to have
perfect advice.

>From 
>https://salsa.debian.org/debian/procps/-/commit/77f54cb9d9951b193d2aaeb694e56061309eb3ef,
it seems that, by default, /etc/sysctl.conf contained nothing except
comments. So unless the handling of /etc/sysctl.conf during procps
upgrades is going to be changed, I think it is sufficient to note that
/etc/sysctl.conf will be removed (or renamed to disable it, if
changed), /etc/sysctl.d/99-sysctl.conf (compatibility symlink shipped
by systemd) will also be removed, and that users who have modified
their /etc/sysctl.conf are advised to copy their configuration to
/etc/sysctl.conf.d/ (and possibly restore the default
/etc/sysctl.conf, and reboot, so as to avoid potential issues with
duplicating the configuration).

Take this with a pinch of salt; I don't fully understand what I am
writing about.

--Samuel Plavec

Reply via email to