Hi Lorenzo,

On Mon, Sep 25, 2023 at 11:35:58PM +0200, Lorenzo wrote:
> Just to avoid any misunderstanding: this discussion has nothing to do
> with this bug (duplicate triggers) except that is about usrmerge and
> runit; I'm discussing here only because you said you need a public
> record.

Yeah. I was still having the triggers as context.

> Perhaps I read your willingness to reply to questions in a too
> extensive way; if that's the case please say so and please let me know
> the following two things:
> * When the file move moratorium is going to be lifted? one week, two
>   week from now?

Lifting it like flipping a boolean very much does not work. It needs to
be lifted progressively. The state of the moratorium shall be documented
at https://wiki.debian.org/UsrMerge. At present, we very much still
support split-/usr, because buildds are still unmerged. It is unclear
how long it takes to update debootstrap in bookworm to create merged
buildd chroots. That's the event you are probably interested in. You may
want to subscribe to #1050868 or look closer when this gets closed. For
the time being, we've started moving systemd units, but that shouldn't
break split-/usr systems.

> * Are essential files (like /bin/sh) going to be moved first or last?
>   when they are expected to be moved from now?

In between. Once debootstrap is updated, I'll be focusing on essential.
Until then, we can convert systemd units, because that also works on
split-/usr systems such as buildds. In terms of package counts, systemd
units are half the problem.

> > Imposing such triggers on every runit user seems
> > unreasonable to me.
> I'm confused here, I never talked about triggers..

I'm still trying to figure out why there is a trigger interest in
/usr/bin and whether that needs fixing.

> Confused as above here; there is nothing in src:runit right now that is
> specific to merged or unmerged; triggers in this bug have nothing to do
> with merged or unmerged system, they are part of runit infrastructure
> for services ( a replacement for debheper snippets + runit-helper code
> + update-rc.d + invoke-rc.d ).

This paragraph reduces confusion on my side. In that case, you probably
should duplicate the triggers.

> I suspect we are both reading between the lines of each other the wrong
> way at this point..

Thanks for trying to understand me. I hope we're back on the same page
now.

Helmut

Reply via email to