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
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
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)
--
__
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
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
5 matches
Mail list logo
