[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Seeking advise on buggy runit-systemd --> runit-run transition



Hi all,

in order to fix #953875 I recently merged two packages (runit-systemd +
runit-sysv) into a new one (runit-run).
But i didn't realize that runit-systemd and runit-run share the same
conffile and the same systemd service, so that when you purge
runit-systemd after installing runit-run, the runit-runs's systemd
service is automatically disabled. (#976187)

To fix this issue,a s suggested in the bug, I can reintroduce an
empty runit-systemd package with runit-run depends on it. Later I can
relax from depends to recommends.
Example
https://salsa.debian.org/Lorenzo.ru.g-guest/runit/-/commit/d514d00ef08aabc201b630c61afe10442ca3cbe3

* is there any better way to handle this?

* Do I have to go through NEW queue to reintroduce the runit-systemd
  package?

* runit-systemd and runit-sysv packages are still available in Sid: is
  some action expected on my side to remove the two packages from the
  archive when I think I'm done with the transition?

Regards,
Lorenzo


Reply to: