Control: tag -1 -moreinfo
Control: tag -1 confirmed
On 12/2/20 9:30 PM, Jamie Heilman wrote:
>
> The only way to avoid the problem is to avoid having the
> runit-systemd.postrm script from runit-systemd <= 2.1.2-36 run after
> runit-run is installed. You could introduce a new version of a
> more-o
On 12/2/20 5:15 AM, Jamie Heilman wrote:
> debconf: delaying package configuration, since apt-utils is not installed
> (Reading database ... 25354 files and directories currently installed.)
> Removing runit-systemd (2.1.2-36) ...
> Selecting previously unselected package runit-run.
> (Reading da
Lorenzo wrote:
> Yes you are right, this is the issue: I see from you output
> that you have a hook or some setting that automatically purge
> packages after removal. Am I correct?
No, purging packages is a normal part of using Debian. It's not a
special hook, it's just a completely normal admini
Control: tag -1 moreinfo
Hi,
On 12/1/20 8:26 AM, Jamie Heilman wrote:
> Package: runit
> Version: 2.1.2-38
>
> The runit-run package fails to enable the runit.service unit during
> installation on systems that use systemd. This is surprising behavior
> that isn't documented in the NEWS file (if
Lorenzo wrote:
> at this point 'systemctl status runit.service' shows the service as
> active and enabled, and i can also see the runsvdir process with
> pstree.
>
> A few wild guess on why the service is not enabled for you:
>
> * Maybe you disabled the service at some point before the upgrade?
Package: runit
Version: 2.1.2-38
The runit-run package fails to enable the runit.service unit during
installation on systems that use systemd. This is surprising behavior
that isn't documented in the NEWS file (if it was even intentional)
and leaves folks with a previously working setup w/runit-s
6 matches
Mail list logo
