On 2025-05-07 17:45:51 +0200, Michael Biebl wrote: > Am 07.05.25 um 15:28 schrieb Vincent Lefevre: > > On 2025-05-07 12:37:35 +0200, Chris Hofstaedtler wrote: > > > * Vincent Lefevre <vinc...@vinc17.net> [250507 11:06]: > > > > I can see in journalctl output: > > > > > > > > May 07 10:25:13 qaa systemd-sysv-generator[1476564]: SysV service > > > > '/etc/init.d/dictd' lacks a native systemd unit file, automatically > > > > generating a unit file for compatibility. > > > > May 07 10:25:13 qaa systemd-sysv-generator[1476564]: Please update > > > > package to include a native systemd unit file. > > > > May 07 10:25:13 qaa systemd-sysv-generator[1476564]: ! This > > > > compatibility logic is deprecated, expect removal soon. ! > > > > May 07 10:25:13 qaa systemd-sysv-generator[1476564]: SysV service > > > > '/etc/init.d/shellinabox' lacks a native systemd unit file, > > > > automatically generating a unit file for compatibility. > > > > May 07 10:25:13 qaa systemd-sysv-generator[1476564]: Please update > > > > package to include a native systemd unit file. > > > > May 07 10:25:13 qaa systemd-sysv-generator[1476564]: ! This > > > > compatibility logic is deprecated, expect removal soon. ! > > > > > > > > and the corresponding bugs 1039171 and 1039367 say: "This > > > > is in the process of being deprecated and will be removed > > > > by the time Trixie ships, so the remaining packages that > > > > ^^^^^^^^^^^^^^^^^^^^^^^^ > > > > ship init scripts without systemd units will stop working." > > > > > > > > What's the status of such packages? > > > > > > They have open bugs that need fixing. > > > > > > For example: > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039171 > > > > Yes, but then, shouldn't the severity be raised (as without > > a fix, they will no longer work in Trixie)? > > Trixie still ships the sysv-generator and we are pretty much in freeze right > now. > > So while I can't speak for Luca, I wouldn't expect that the sysv-generator > is going to be removed at this point in the release cycle or that there are > plans to do so. > > I read the bug report like this: By the time Trixie ships and once Forky > opens up for development, the sysv-generator is going to be removed. I.e. it > will be a change affecting Forky, not Trixie. > Which leaves us 2 years to fix the remaining stragglers.
OK, this wasn't clear and this was why I asked for the status of such package. I understood Chris's message as such bugs need fixing for Trixie. IMHO, "and will be removed after Trixie" would have been clearer if this is the intent. Then, I think that the message "SysV service [...] This compatibility logic is deprecated, expect removal soon." in the logs is unnecessary for Trixie. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)
