Hi Niels,

On Sun, Feb 05, 2017 at 10:44:00AM +0000, Niels Thykier wrote:
> On Sat, 27 Aug 2016 20:16:57 +0300 Dmitry Bogatov <kact...@gnu.org> wrote:
> > Jan, could you please provide more information?  I did not follow. As
> Are there any news on this bug? It is listed as a possible blocker for
> the stretch release (being a RC bug in a key package).
> 
> If the bug is no longer reproducible, please consider either closing it
> or tagging it "moreinfo unreproducible" and downgrading it to important.

I guess it can be closed. I'm not sure, but I think I reassigned the bug
to runit after verifying that mongrel2-run calls update-service (from
the runit package) according to the documentation, without trying to
reproduce the bug myself.

Unfortunately, I didn't get Dimitrys mail asking for more info, as the
bug was already reassigned to runit, so the bts didn't send a copy to
me.

Andreas, you cloned #832656 and reassigned one of the clones to
mongrel2-run. Do you still remember if you verified that mongrel2 was
actually affected?

And even if mongrel2 was affected, as far as I understand the bug, it's
probably been fixed by the following change in runit 2.1.2-7:

  * Create /etc/runit/runsvdir/default directory and /etc/service directories
    as part of binary package, not in maintainer scripts. Empty directories are
    not pretty, but usually user installs some runscripts with 'runit' binary
    package, and will not notice issue.

Jan

Reply via email to