Bug#1142073: runit: uninstallable with systemd-sysv:amd64=261.1-2

Control: tags -1 patch

Hi,

there is a MR on salsa to fix this bug
https://salsa.debian.org/systemd-team/systemd/-/merge_requests/334

Best,
Lorenzo

On Wed, 15 Jul 2026 13:23:21 +0200 lorenzo <[email protected]> wrote:
> Control: reassign -1 systemd-sysv 261~rc1-1
> Control: affects -1 runit runit-run socklog-run
> 
> 
> On Tue, 14 Jul 2026 23:21:13 +0200
> Jan Braun <[email protected]> wrote:
> 
> > Package: runit
> > Version: 2.3.1-4
> > Severity: grave
> > Justification: renders package unusable
> 
> I think this belongs to systemd/systemd-sysv, it introduced the
> regression in runit, see
> 
> > 
> > https://salsa.debian.org/systemd-team/systemd/-/commit/61d6ecf0a0b33456121f6b830e70ff76d1520c85
> and
> https://salsa.debian.org/systemd-team/systemd/-/commit/e53db5cc8ff7da2a62a9b2f841144b9a1873dc76
> 
> reason for RC-level severity in systemd/systemd-sysv: policy 7.4. ,
> violation of "should"
> 
> "Neither Breaks nor Conflicts should be used unless two packages
> cannot be installed at the same time or installing them both causes
> one of them to be broken or unusable. Having similar functionality or
> performing the same tasks as another package is not sufficient reason
> to declare Breaks or Conflicts with that package."
> 
> Note that sysuser-helper 1.6 does not ship /usr/bin/systemd-sysusers,
> nor has a diversion or an alternative in place.
> the code injected in postinstall calls /usr/bin/systemd-sysusers as
> first option and only when /usr/bin/systemd-sysusers is not found,
> falls back on minsysusers. So when systemd is installed
> /usr/bin/systemd-sysusers from systemd is used.
> 
> > 
> > Dear Maintainer,
> > 
> > runit Depends: sysuser-helper (>= 1.6)
> > systemd-sysv:amd64=261.1-2 Conflicts: sysuser-helper
> 
> > 
> > Hence, runit (and runit-run) can no longer be installed on a systemd
> > machine running testing:
> 
> also socklog-run
> 
> > 
> > | $ sudo apt-get install runit
> > | Reading package lists... Done
> > | Building dependency tree... Done
> > | Reading state information... Done
> > | Solving dependencies... Error!
> > | Some packages could not be installed. This may mean that you have
> > | requested an impossible situation or if you are using the unstable
> > | distribution that some required packages have not yet been created
> > | or been moved out of Incoming.
> > | The following information may help to resolve the situation:
> > |