Bug#973671: do not depend on runit-init
socklog should not depend on runit at all. E.g. I start it with daemontools which is in all Stable/Testing/Unstable . And many others also run it this way, as runit was written as daemontools replacement in times when it was not opensourced yet. You should keep the dependencies just as they were in Gerrit Pape's version: --\ Depends --- adduser --- libc6 --\ Recommends --- ipsvd --- runit --- socklog-run It might recommend runit as the preferred way to run it, but not depend on it. I'm not sure why you had to break what has been working for many years ?! Why has Gerrit stepped down and stopped maintaining his own software ?
Bug#973671: do not depend on runit-init
On Sat, Nov 07, 2020 at 09:33:16AM +0100, Richard Lucassen wrote: > Hello Mathieu, > > > People expect services to start on package installation on Debian. > > Well, people who use socklog generally know what they're doing, so I > would not be too worried about that ;-) Indeed, I'll go with that. It turns out that the dependency or-group that I thought looked good will not work since apt will always try to install the first mentioned dependency mentioned. This is similar to #953875 in fact. I am turning this dependency into a weaker suggestion instead to make socklog installable everywhere. The drawback is that it may not automatically start, but realistically people who install socklog can be expected to know how to setup runit. Sorry for the email noise by the way, apparently the BTS scrubs the git repo on salsa and automatically posts stuff things here. Cheers, -- Mathieu Mirmont signature.asc Description: PGP signature
Bug#973671: do not depend on runit-init
Hello Mathieu, > People expect services to start on package installation on Debian. Well, people who use socklog generally know what they're doing, so I would not be too worried about that ;-) Richard (happy socklog user under sysV) -- ___ It is better to remain silent and be thought a fool, than to speak aloud and remove all doubt. +--+ | Richard Lucassen, Utrecht| +--+
Bug#973671: do not depend on runit-init
On Tue, Nov 03, 2020 at 01:37:01AM +, Jamie Heilman wrote: > socklog is now uninstallable on systems that don't use runit-init > which makes no sense. This program works without runit-init just > fine, there's no good reason for a hard dependency on runit-init. Yes you are right, this was not intentional. The dependency is "runit-init | runit-run" to make it installable regardless of how runit is launched in the system, however I just notice that "runit-run", which replaced both "runit-sysv" and "runit-systemd", is only in experimental and not in unstabled. I totally overlooked that, sorry. I can change the dependency to "runit-init | runit-run | runit-sysv | runit-systemd" to support all methods of running runit on a system. Would that work for you, or would it already be too restrictive for your use case? The alternative would be to only depend on "runit", however the service would not necessarily start when the package is installed. People expect services to start on package installation on Debian. Cheers, -- Mathieu Mirmont signature.asc Description: PGP signature
Bug#973671: do not depend on runit-init
Package: socklog Version: 2.1.0+repack-2 Severity: important socklog is now uninstallable on systems that don't use runit-init which makes no sense. This program works without runit-init just fine, there's no good reason for a hard dependency on runit-init. -- Jamie Heilman http://audible.transient.net/~jamie/
