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:

| $ 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:
|
| The following packages have unmet dependencies:
|  runit : Depends: sysuser-helper (>= 1.6) but it is not going to be installed
| E: Unable to satisfy dependencies. Reached two conflicting assignments:
|    1. sysuser-helper:amd64 is selected for install because:
|       1. runit:amd64=2.3.1-4 is selected for install
|       2. runit:amd64 Depends sysuser-helper (>= 1.6)
|    2. sysuser-helper:amd64 is available in versions 1.6.0, 2.0.3
|       but none of the choices are installable:
|       - sysuser-helper:amd64=1.6.0 is not selected for install because:
|         1. systemd-sysv:amd64 is selected for install
|         2. systemd-sysv:amd64 is available in versions 261.1-2, 257.13-1~deb13u1, 257.8-1~deb13u2, 261.1-3
|            [selected systemd-sysv:amd64=261.1-2 for install]
|         3. systemd-sysv:amd64=261.1-2 Conflicts sysuser-helper
|            [selected systemd-sysv:amd64=261.1-2]
|         For context, additional choices that could not be installed:
|         * In systemd-sysv:amd64 is available in versions 261.1-2, 257.13-1~deb13u1, 257.8-1~deb13u2, 261.1-3:
|           - systemd-sysv:amd64=257.13-1~deb13u1 is not selected for install
|           - systemd-sysv:amd64=257.8-1~deb13u2 is not selected for install
|           - systemd-sysv:amd64=261.1-3 is not selected for install
|       - sysuser-helper:amd64=2.0.3 is not selected for install
| $

Since I have no idea about sysuser-helper, I'm tentatively reporting
this against runit. Please reassign to/yell at systemd-sysv as
appropriate. ;)

Thank you for maintaining runit.
cheers,
    Jan

Quite. It looks like a serious bug in systemd-sysv to me. This prevents
any package built to use sysuser-helper from being installed with
systemd for no stated technical reason. That conflicts list is grossly
excessive.

https://salsa.debian.org/systemd-team/systemd/-/commit/61d6ecf0a0b33456121f6b830e70ff76d1520c85

Control: reassign -1 systemd-sysv 261~rc1-1
Control: affects -1 runit runit-run socklog-run

I think this belongs to systemd/systemd-sysv, it introduced the
regression in runit, see
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.

also socklog-run

Dear systemd maintainers,
to address this, please either remove the conflicts with sysuser-helper
or (better, IMHO) use a versioned conflicts sysuser-helper >= 2.0.0~

Lorenzo

Hi,

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

Best,
Lorenzo