Hi Tobias, hi Lorenzo. Tobias, thanks for looking into this sponsoring request! I appreciate it.
Tobias Frost - 11.05.24, 10:24:31 CEST: > On Tue, Apr 16, 2024 at 09:39:58AM +0200, Lorenzo wrote: > > Control: block -1 by 1067525 > > > > this fix need to go to unstable because elogind 255.4.1 is already > > there, but runit-services depends on runit > 2.1.2-56 (unstable is at > > 2.1.2-54) so 1067525 needs to be uploaded first or together with this > > one, otherwise runit-services is not installable > > Ok, just saw that one. > Please note that this fact must be stated in d/changelog, something like > "Upload to unstable." FWIW I run runit 2.1.2-59 and runit-services together with elogind 255.5-2 on two Devuan Ceres systems with KDE's Plasma desktop. One I had patched manually, but I made sure the package version of the run dir for elogind was installed after the upgrade. The other one was upgraded regularly from elogind 252 and older runit / runit-services packages. Runsvdir starts elogind correctly from the new path. I also reviewed the changes to the package for the updated path for elogind and I think they are correct. I am certainly no expert with runit, but as I contributed zcfan service dir at least I know something. Devuan uses the upstream packages for runit, runit-services, dash, bash so I expect that runit-services 0.7.2 will work just fine on Debian, too. It would unbreak running elogind for runit users that did not patch their systems manually already. I bet most of them did by now, as many desktop environments do not work well, if at all, without some systemd-logind replacement. And the timeouts with login into a TTY or SSH session without some systemd-logind replacement are quite annoying as well. Sure we are still talking about a (small) minority of Debian users here. Hope this helps regarding the review of the package and the sponsoring. In case any further changes need to be tested before upload, I am willing to do that. Best, -- Martin
