Hi Helmut, On Sat, 18 Nov 2023 17:40:23 +0100 Helmut Grohne <hel...@subdivi.de> wrote:
First the actionable part: > Is there actually any issue with promoting the change from > experimental to unstable? Yes: the version in experimental is definitely RC buggy, for reasons unrelated to usrmerge > If you lack a sponsor, I am willing to help > out once to get this fixed. Thanks, really appreciated: I prepared a runit_2.1.2-54+usrmerge runit upload targeted at unstable with two commits backported, you can find it on mentors https://mentors.debian.net/package/runit/ dget -x https://mentors.debian.net/debian/pool/main/r/runit/runit_2.1.2-54+usrmerge.dsc and on salsa (usrmerge branch) https://salsa.debian.org/debian/runit/-/tree/usrmerge?ref_type=heads let me know if something else is needed for this upload. Now the annoying part: > it still affects > trixie and sid, so by raising it to serious, we get rid of the bug in > trixie before too long (either via upload or autoremove). > [...] However, runit's triggers do > not work anymore. That's a serious bug and we're tracking it like > that. I disagree about the severity (it should be assessed by looking at the broken feature that is provided by the trigger) and especially I disagree that the malfunction of this specific feature should cause the removal of runit from testing (and the same goes for any other alternative init system). I'm stopping here as I think you don't want to spend further time on this bug since it can be fixed with an upload, but I can elaborate if you want me to. Best Regards, Lorenzo > > Helmut > > >
