On Fri, Nov 22, 2024 at 04:13:18AM +0200, Adrian Bunk wrote: > Package: git > Version: 1:2.45.2-1.1 > Severity: serious > X-Debbugs-Cc: Chris Hofstaedtler <z...@debian.org> > > git (1:2.45.2-1.1) unstable; urgency=medium > > * Non-maintainer upload. > * Demote "runit" dependency to Recommends. > Demoting Depends: runit to Recommends: should have no effect on default > installs (apt will install Recommends by default), and people wanting to > use runit should have it installed already. (Closes: #1078778) > > -- Chris Hofstaedtler <z...@debian.org> Sun, 13 Oct 2024 14:16:01 +0200 > > > The "should have no effect on default installs" claim > is only true when runit is part of the distribution. > > What ensures that runit is in trixie without the dependency?
Nothing, but why would anyone install runit integration packages if they are not using runit? The better solution would obviously be if runit would bring the runit integration code itself, like the sysvinit people now do. I think runit also started going down that route but is not there yet? > Without runit, this package is RC-buggy broken. So it was before. > Additionally, the change from 1:2.45.2-1.2 does not properly > handle the case when runit gets installed after git-daemon-run. Okay, I can try to look at that. > For historical reasons the git-daemon packages support being started > by either runit or sysvinit. > > The runit support was added before systemd even existed. > > Does it make sense to use runit for supervising a daemon > when systemd is the init system? No. > A systemd unit might be more useful than using runit. Obvious. But the runit people don't want systemd, they want runit. Chris
