On Mon, Jul 29, 2024 at 01:13:10 +0200, Vincent Lefevre wrote:
> On 2024-07-28 14:13:09 +0000, Michael Kjörling wrote:
> > And posting on debian-user with a bombastic Subject line which implies
> > that this is a widespread issue when it really only seems to exist in
> > Unstable is, quite frankly, in my opinion at best dishonest.
>
> No, the breakage was done *on purpose* (together with the lack
> of announcement).
All I can tell you is that you should post bug reports on things that
you believe are broken. (Yes, I know you've already made some. If there
are more issues that you feel are not addressed, then maybe you should
post more.)
Ranting on debian-user is extremely unlikely to get anything changed.
You might warn other users that there's an issue, which can be a great
service to the community, but having done that already, continuing to
harp on the same issue repeatedly seems less than productive.
In the interests of posting something *useful*, here's a timeline.
As I understand it, here's what's happened so far:
2024-06-23: bug #1074156 filed against package procps
procps: Depend or Recommend linux-sysctl-defaults
Bug fixed by upload, closed.
2024-07-11: procps (unstable) upload: /etc/sysctl.conf is "removed"
(but not when upgrading)
Closes #1074156
2024-07-12: bug #1076190 filed against package systemd
Installs dangling symlink /etc/sysctl.d/99-sysctl.conf
Bug fixed by upload, closed.
2024-07-24: systemd (unstable) upload: /etc/sysctl.d/99-sysctl.conf
symlink is removed (for upgrades also)
Closes #1076190
2024-07-26: this thread is started on debian-user
2024-07-26: bug #1077184 filed against package systemd
systemd: /etc/sysctl.conf is no longer read
Bug marked as wontfix, closed.
2024-07-26: bug #1077187 filed against package procps
procps: please drop/replace the obsolete sysctl.conf(5) man page
Still open.
