On Fri, Jun 23, 2023 at 01:30:30AM +0200, Thorsten Glaser wrote: > On Thu, 22 Jun 2023, David Griffith wrote: > > > This was prompted when I found that rsyslog stopped working on Bullseye when > > upgraded to Bookworm. What sort of depenency would you suggest to implement > > the following? > > “Read the release notes.”
What part of the release notes are you referring to? It might be useful to reference that specifically, in addition to the pointer. Nothing relevant is obvious here for rsyslogd: https://www.debian.org/releases/bookworm/amd64/release-notes/index.en.html We probably want to avoid nasty surprises. I haven't upgraded my servers to Bookworm yet, but scanning the release notes, nothing there would indicate to me that my logging services were about to break. David's suggestion of requiring orphan-sysvinit-scripts seems like a sensible solution that will prevent outages. Let's posit, for instance, that there's a hospital somewhere using Debian for some of their infrastructure, and running sysvinit because they require reliable systems. It would seem responsible to not arbitrarily let logging break on an upgrade. That's not what people expect from Debian. -- Mason Loring Bliss ma...@blisses.org Ewige Blumenkraft! awake ? sleep : random() & 2 ? dream : sleep; -- Hamlet, Act III, Scene I
signature.asc
Description: PGP signature
