On Fri, Nov 22, 2024 at 01:56:30PM +0100, Chris Hofstaedtler wrote: > 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? >...
Because that's what they get installed by us when they want to run git-daemon. Different from systemd, runit can also monitor services without being PID 1. Users who want to run git-daemon currently get systemd starting runit (runit recommends runit-run), which then monitors git-daemon. If runit is not in trixie, your change breaks git-daemon for these users. For most users a systemd unit would be a better solution than the indirect monitoring through runit. Merging git-daemon-sysvinit into git-daemon-run (and using /etc/default/git-daemon for all init systems) might also be a good idea. > Chris cu Adrian
