Forums before death by AOL, social media and spammers... "We can't have nice things"
|    linux.debian.bugs.dist    |    Ohh some weird Debian bug report thing    |    28,835 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 27,678 of 28,835    |
|    Lorenzo Puliti to All    |
|    Bug#1128003: trixie-pu: package runit-se    |
|    15 Feb 26 01:50:01    |
      XPost: linux.debian.devel.release       From: plorenzo@disroot.org              This is a multi-part MIME message sent by reportbug.                     Package: release.debian.org       Severity: normal       Tags: trixie       X-Debbugs-Cc: runit-services@packages.debian.org, plorenzo@disroot.org       Control: affects -1 + src:runit-services       User: release.debian.org@packages.debian.org       Usertags: pu              Dear Release Team,              I'm looking for pre-approval for a runit-services stable-update              [ Reason ]              Fix #1126699 and #1121099 for Trixie fresh install: for users       upgrading from 0.9.1 the fix will take effect after the first       system reboot.              [ Impact ]              1126699: duplicate instances of certain services are run during        the boot sequence: it's hard to predict how bad this is, it        depends on the service. For some services the duplicate        instance will just crush logging a misleading message on the        system logger; other services may just be able to run duplicate        instances without issues (except for wasting resources) or may        subtly misbehave.              1121099: slim forks in background but runit supervision expect        services to run in foreground: a second instance is started which        then blocks because the tty is aready used by the first instance.        the bug appear when a user logs out and try to restart slim which        does not respond to signals, except to sigkill. It's not straightforward        to understand why the slim service does not respond to sigterm        and that there are two instances running at the same time.              Also: the runit-services package is imported as is downstream at       Devuan where runit is a popular choice and slim is the default       login manager (in fact both bug reports came from downstream)              [ Tests ]       I tested on my system (unstable) that both bugs are fixed              [ Risks ]       Fix for 1121099 (slim) is a one line simple change; fix for       1126699 is a bit more complex but the code largely matches       another component of runit (/usr/lib/runit/run_sysv_scripts)       that is already in stable: I think the changes are low risk.              [ Checklist ]        [x] *all* changes are documented in the d/changelog        [x] I reviewed all changes and I approve them        [x] attach debdiff against the package in stable        [x] the issue is verified as fixed in unstable              [ Changes ]       * slim: run slim in foreground       * dbus.dep-fixer: correctly check for existing runit services definitions              Thanks,       Lorenzo              diff -Nru runit-services-0.9.1/debian/changelog runit-services-0       9.1+deb13u1/debian/changelog       --- runit-services-0.9.1/debian/changelog 2025-04-10 10:52:56.000000000 +0200       +++ runit-services-0.9.1+deb13u1/debian/changelog 2026-02-10 19:       8:57.000000000 +0100       @@ -1,3 +1,14 @@       +runit-services (0.9.1+deb13u1) trixie; urgency=medium       +       + * slim: start in foreground with -n.       + + thanks: Andrew Bower (Closes: #1121099)       + * dbus-dep.fixer:       + - correctly test for existing services definitions       + - only start dbus services, even with the sysv override.       + + thanks: S. Osipiuk (Closes: #1126699)       +       + -- Lorenzo Puliti |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca