Bug#1070167: openrc: postinst fails with not executable script in /etc/init.d/
Package: openrc Version: 0.45.2-2 Severity: normal X-Debbugs-Cc: plore...@disroot.org Hi, it appears that, at least under certain conditions, openrc postinstall script fails if a sysvinit script in /etc/init.d/ is not executable. Note that recently debhelper started to chmod -x initscripts when a package is removed but not purged, so openrc should deal whit non executebles files under /etc/init.d/ Not sure if the bug is in openrc tools or in update-rc.d/invoke-rc.d's openrc bits See https://dev1galaxy.org/viewtopic.php?id=6549 for some output of the problem Best, Lorenzo -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: runit (via /run/runit.stopit) LSM: AppArmor: enabled Versions of packages openrc depends on: ii insserv 1.24.0-2 ii libaudit11:3.1.2-2.1 ii libc62.37-18 ii libcap2 1:2.66-5 pn libeinfo1 ii libpam0g 1.5.3-7 pn librc1t64 ii libselinux1 3.5-2+b2 openrc recommends no packages. Versions of packages openrc suggests: pn policycoreutils pn sysvinit-core
Bug#1070032: elogind: add NEWS for 255.4.1, suspend now default to s2idle instead of s2ram
Package: elogind Version: 255.4.1-1debian2 Severity: normal X-Debbugs-Cc: plore...@disroot.org Hi, Elogind 255 changed the implicit default for suspend; it was 'deep' until 252, now it's 's2idle'. This is documented nowhere, except if one reads Yamakuzure reply in https://github.com/elogind/elogind/issues/280 and it took me a while [1] to understand that the state where the screen goes black but power led is still on and fans keep spinning is not a bug in elogind. I think this change is worth a NEWS entry, with an example that explains how to revert to the previous default. I suggest something like This version of elogind changes the default Mode for suspend, before elogind 255 it was suspend2ram, now it's suspend2idle. To revert to the previous default you can add a line with SuspendMode=deep in elogind's sleep.conf; for example cat /etc/elogind/sleep.conf.d/20-suspend.conf [Sleep] SuspendMode=deep Best, Lorenzo [1] https://docs.kernel.org/admin-guide/pm/sleep-states.html -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: runit (via /run/runit.stopit) LSM: AppArmor: enabled Versions of packages elogind depends on: ii dbus 1.14.10-4+b1 ii debconf 1.5.86 ii init-system-helpers 1.66 ii libacl1 2.3.2-1 ii libc62.37-18 ii libcap2 1:2.66-5 ii libmount12.40-6 ii libpam0g 1.5.3-7 ii libselinux1 3.5-2+b2 ii libsystemd0 255.5-1 ii libudev1 255.5-1 Versions of packages elogind recommends: ii libpam-elogind 255.4.1-1debian2 ii polkitd 124-2 elogind suggests no packages. -- no debconf information
Bug#1069595: mplayer: FTBFS with ffmpeg 7
Source: mplayer Version: 2:1.5+svn38446-2 Severity: important Tags: upstream ftbfs X-Debbugs-Cc: plore...@disroot.org Mplayer fails to build from source with ffmpeg7 (currently in experimental); there are patches upstream but it looks that there are still open issues, at least with jack. https://trac.mplayerhq.hu/ticket/2419 https://lists.mplayerhq.hu/pipermail/mplayer-dev-eng/2024-April/074132.html filing with severity important for now, until ffmpeg 7 is uploaded to unstable. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0van (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_CPU_OUT_OF_SPEC, TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: runit (via /run/runit.stopit)
Bug#1069592: runit: trigger_sv logic broken: enable and disable a service in the same loop
Package: runit Version: 2.1.2-59 Severity: normal X-Debbugs-Cc: plore...@disroot.org in order to temporary counter #1069075 I've created a local copy of elogind in /etc/sv/ ; then the elogind path is updated both in the run script and in the .meta/bin metafile so that ~# cat /etc/sv/elogind/.meta/bin /usr/libexec/elogind ~# cat /etc/sv/elogind/run | grep elogind exec /usr/libexec/elogind also (to see more messages from the trigger) touch /etc/runit/verbose then I call the trigger as it would be activated in almost any apt invocation and a not so "funny" thing happens ~# /lib/runit/trigger_sv setup Runit triggered upgrade: setup elogind enabled elogind disabled elogind service is enabled and disabled in the same loop. basically the shadowing logic works for "enable" action but not for "disable", resulting in bin metafiles being processed for both the copy in /etc/sv/ and /usr/share/runit with the latter that prevails due to be processed later. this need to be addressed -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0van (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_CPU_OUT_OF_SPEC, TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: runit (via /run/runit.stopit) Versions of packages runit depends on: ii libc6 2.37-17 ii runit-helper2.16.2 ii sysuser-helper 1.3.9+really1.4.3 Versions of packages runit recommends: ii runit-init 2.1.2-59 Versions of packages runit suggests: ii runit-services 0.7.1 ii socklog 2.1.0+repack-5 ii ucspi-unix 1.0-3 pn zsh -- Configuration Files: /etc/default/runit changed: VERBOSE=1 DEBUG=1 /etc/runit/runsvdir/single/sulogin/run [Errno 2] No such file or directory: '/etc/runit/runsvdir/single/sulogin/run' -- no debconf information
Bug#1069075: elogind: service broken by elogind path change in 255.4.1
Package: runit-services Version: 0.7.1 Severity: important X-Debbugs-Cc: plore...@disroot.org Version 255.4.1 of elogind changes elogind's path from /lib/elogind/elogind to /usr/libexec/elogind; this breaks quite a lot in a desktop setup. the runscript and the bin metafiles need to be updated -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: runit (via /run/runit.stopit) LSM: AppArmor: enabled Versions of packages runit-services depends on: ii runit 2.1.2-58 ii runit-helper 2.16.2 Versions of packages runit-services recommends: ii runit-init 2.1.2-58 Versions of packages runit-services suggests: ii socklog 2.1.0+repack-5 -- no debconf information
Bug#1063819: dh-sysuser: uses deprecated given/when
Package: dh-sysuser
Version: 1.3.10+really1.4.4
Severity: normal
Tags: patch
X-Debbugs-Cc: Niko Tyni , plore...@disroot.org
Building runit package I have
create-stamp debian/debhelper-build-stamp
dh_testroot -O--sourcedirectory=runit-2.1.2/src
dh_prep -O--sourcedirectory=runit-2.1.2/src
dh_installdirs -O--sourcedirectory=runit-2.1.2/src
dh_auto_install -O--sourcedirectory=runit-2.1.2/src
dh_sysuser -O--sourcedirectory=runit-2.1.2/src
given is deprecated at /usr/bin/dh_sysuser line 37.
when is deprecated at /usr/bin/dh_sysuser line 38.
when is deprecated at /usr/bin/dh_sysuser line 39.
when is deprecated at /usr/bin/dh_sysuser line 46.
dh_install -O--sourcedirectory=runit-2.1.2/src
dh_installdocs -O--sourcedirectory=runit-2.1.2/src
dh_buildinfo -O--sourcedirectory=runit-2.1.2/src
so I guess it needs an update like in dh-runit's #1060709
What I'm not sure is if this need to be fixed in unstable as
possible or it can wait longer. The autopkgtest covers only
sysuser-helper, so the package does not fail to build.
Patch at the bottom.
Dear Niko, please bump the severity if this is urgent.
Regards,
Lorenzo
diff --git a/dh_sysuser b/dh_sysuser
index 74195f9..fbe9c30 100755
--- a/dh_sysuser
+++ b/dh_sysuser
@@ -34,17 +34,17 @@ init();
sub parse_options($conf, $options, $user) {
foreach my $opt (split(/,/, $options)) {
-given ($opt) {
-when (/^home=(.*)$/) { $conf->{home} = $1; }
-when (/^home$/) {
+for ($opt) {
+if (/^home=(.*)$/) { $conf->{home} = $1; }
+elsif (/^home$/) {
my $normal = $user;
$normal =~ s/^_+//; # strip leading
$normal =~ s/_+$//; # and trailing underscore
$normal =~ s/^[Dd]ebian-//; # and discouraged debian- prefix
$conf->{home} = "/var/lib/$normal";
}
-when (/^defaults$/) { "do nothing"; }
-default { error("unknown option `$opt'"); }
+elsif (/^defaults$/) { "do nothing"; }
+else { error("unknown option `$opt'"); }
}
}
}
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0van (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CPU_OUT_OF_SPEC, TAINT_FIRMWARE_WORKAROUND,
TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: runit (via /run/runit.stopit)
Versions of packages dh-sysuser depends on:
ii perl 5.38.2-3
dh-sysuser recommends no packages.
dh-sysuser suggests no packages.
-- no debconf information
Bug#1062682: runit-services: fails to remove (prerm) (piuparts)
Package: runit-services Version: 0.7.0 Severity: important Tags: patch X-Debbugs-Cc: plore...@disroot.org when one wants to remove this package dpkg fails with [1] (Reading database ... 5625 files and directories currently installed.) Removing runit-services (0.7.0) ... cat: /usr/share/runit/sv/acpi-fakekey/.meta/onupgrade: No such file or directory dpkg: error processing package runit-services (--remove): installed runit-services package pre-removal script subprocess returned error exit status 1 dpkg: too many errors, stopping Errors were encountered while processing: runit-services Processing was halted because there were too many errors. E: Sub-process /usr/bin/dpkg returned an error code (1) this affects version of the package that are build with dh_runit>=2.16 (currently in unstable); 0.5.5 is not affected right now but it could be if a no-change rebuild is triggered in unstable for some reason. patch: https://salsa.debian.org/Lorenzo.ru.g-guest/runit-services/-/commit/407919bcf17fd2560f86194badaeced2f528b1af [1] https://piuparts.debian.org/experimental/fail/runit-services_0.7.0.log -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0van (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_CPU_OUT_OF_SPEC, TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: runit (via /run/runit.stopit) Versions of packages runit-services depends on: ii runit 2.1.2-57 ii runit-helper 2.16.2 Versions of packages runit-services recommends: ii runit-init 2.1.2-57 Versions of packages runit-services suggests: ii socklog 2.1.0+repack-5 -- no debconf information
Bug#1059930: runit-init: needs conflict with molly-guard before moving shutdown links
Package: runit-init
Version: 2.1.2-56
Severity: important
Tags: patch
X-Debbugs-Cc: Helmut Grohne , plore...@disroot.org
Hello,
If I undestrand correctly (there was a PM from Helmut explaining this
to me, but it was before [1]) runit init needs a conflicts with
molly-guard when it moves halt, poweroff, etc.. links from /sbin
to /usr/sbin. Now, following patches already applied to systemd
and reading [2], I'm attempting a patchset for runit-init.
[I know it's holiday time and I'm not in a rush for this]
Helmut, could you have a look (patches attached)?
* Is molly-guard enough or do I need to consider other packages?
I'm excluding progress-linux-container and bfh-container since
they depends on systemd-sysv
* the conflicts is in patch 003, restore the links is in 004
* note that for consistency I'm also moving runit's shutdown
from /lib/runit/ to /usr/lib/runit. For that I have to bump
the Depends to the latest runit (patch 001), I hope that it
doesn't create issues to the apt resolver
Many thanks,
Lorenzo
[1] https://lists.debian.org/debian-devel/2023/12/msg00020.html
[2] https://lists.debian.org/debian-devel/2024/01/msg00025.html
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
merged-usr: no
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0van (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CPU_OUT_OF_SPEC, TAINT_FIRMWARE_WORKAROUND,
TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: runit (via /run/runit.stopit)
Versions of packages runit-init depends on:
ii getty-run2.1.2-56
ii initscripts 3.08-1
ii insserv 1.24.0-1
ii mount2.39.2-1
ii runit2.1.2-56
Versions of packages runit-init recommends:
ii runit-services 0.7.0
runit-init suggests no packages.
-- no debconf information
>From 798a86a24e582a20295741ef808121fe06abcba3 Mon Sep 17 00:00:00 2001
From: Lorenzo Puliti
Date: Wed, 3 Jan 2024 15:01:17 +0100
Subject: [PATCH 1/4] runit: move shutdown to /usr/lib/runit
runit: move shutdown under /usr
runit-init: adjust symlink (halt,poweroff,shutdown,reboot) targets
to point to /usr/lib/runit/shutdown; Depends on runit >= 2.1.2-57
---
debian/control | 2 +-
debian/runit-init.links | 8
debian/runit.install| 2 +-
3 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/debian/control b/debian/control
index 3e254a2..1fea2ed 100644
--- a/debian/control
+++ b/debian/control
@@ -71,7 +71,7 @@ Description: runscripts to supervise getty processes
Package: runit-init
Architecture: any
-Depends: runit (>= 2.1.2-43~), ${misc:Depends},
+Depends: runit (>= 2.1.2-57~), ${misc:Depends},
${shlibs:Depends}, getty-run, insserv, initscripts, mount [linux-any]
Breaks: ${runit:Breaks}
Replaces: systemd-sysv, sysvinit-core
diff --git a/debian/runit-init.links b/debian/runit-init.links
index 84d5822..ef10f73 100644
--- a/debian/runit-init.links
+++ b/debian/runit-init.links
@@ -4,9 +4,9 @@
/usr/share/man/man8/runit-shutdown.8.gz /usr/share/man/man8/shutdown.8.gz
/usr/share/man/man8/runit-init.8.gz /usr/share/man/man8/init.8.gz
/usr/share/man/man8/runit-runlevel.8.gz /usr/share/man/man8/runlevel.8.gz
-/lib/runit/shutdown /sbin/halt
-/lib/runit/shutdown /sbin/reboot
-/lib/runit/shutdown /sbin/poweroff
-/lib/runit/shutdown /sbin/shutdown
+/usr/lib/runit/shutdown /sbin/halt
+/usr/lib/runit/shutdown /sbin/reboot
+/usr/lib/runit/shutdown /sbin/poweroff
+/usr/lib/runit/shutdown /sbin/shutdown
/lib/runit/runlevel /sbin/runlevel
/lib/runit/runit-init /sbin/init
diff --git a/debian/runit.install b/debian/runit.install
index 04c1954..4fc9bf9 100644
--- a/debian/runit.install
+++ b/debian/runit.install
@@ -27,7 +27,7 @@ debian/contrib/lib/trigger_sv /lib/runit
runit-2.1.2/src/runit-init /lib/runit
runit-2.1.2/src/runit /sbin
-debian/contrib/shutdown /lib/runit
+debian/contrib/shutdown /usr/lib/runit
debian/contrib/runlevel /lib/runit
debian/sv/sulogin/run /etc/runit/runsvdir/single/sulogin
debian/sv/svlogd/ /etc/sv/
--
2.40.1
>From 656e677e9a08eabcb27b2c13404b7acfd3cea83e Mon Sep 17 00:00:00 2001
From: Lorenzo Puliti
Date: Wed, 3 Jan 2024 15:37:16 +0100
Subject: [PATCH 2/4] runit-init: move shutdown links to /usr/sbin/
* Move halt, poweroff, reboot, shutdown symlinks to /usr/sbin/
* update runit-shutdown(8) manpage in runit package
---
debian/contrib/shutdown.8 | 8
debian/runit-init.links | 8
2 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/debian/contrib/shutdown.8 b/debian/contrib/shutdown.8
index 15590e5..cf6956d 100644
--- a/debian/contrib/shutdown.8
+++ b/debian/contrib/shutdown.8
@@ -2,13 +2,13 @@
.SH NAME
shutdown, reboot, poweroff \- poweroff or reboot the system
.SH SYNOPSIS
-.B
Bug#1057095: runit trigger_sv missing services restart
Package: runit Version: 2.1.2-56 Severity: normal X-Debbugs-Cc: plore...@disroot.org Control: affects -1 runit-services the /lib/runit/trigger_sv code sometime fails to restart a service on the services package upgrade - this is a regression compared to 2.1.2-55, and it depends on where is the service in the filesystem. Sometimes I think it also misses enable/disable of services. This is because of recent changes in trigger_sv code. Note that this is a separate and unrelated issue to #1043419; the trigger here is activated but it does not work as expected. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 6.1.0van (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_CPU_OUT_OF_SPEC, TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit) Versions of packages runit depends on: ii libc6 2.37-10 ii runit-helper2.16.1 ii sysuser-helper 1.3.9+really1.4.3 Versions of packages runit recommends: ii runit-init 2.1.2-56 Versions of packages runit suggests: ii runit-services 0.7.0 ii socklog 2.1.0+repack-5 ii ucspi-unix 1.0-2 pn zsh -- Configuration Files: /etc/default/runit changed [not included] /etc/runit/runsvdir/single/sulogin/run [Errno 2] No such file or directory: '/etc/runit/runsvdir/single/sulogin/run' -- no debconf information -- debsums errors found: debsums: changed file /lib/lsb/init-functions.d/40-runit (from runit package) debsums: changed file /lib/runit/trigger_sv (from runit package)
Bug#1057094: runit: lsb 40-runit does not forward sysv nonstandard actions
Package: runit Version: 2.1.2-56 Severity: normal X-Debbugs-Cc: plore...@disroot.org Control: affects -1 runit-services This was reported downstream but it affects Debian as well; runit uses /lib/lsb/init-functions.d/40-runit code to intercept calls to sysvinit scripts, when on the system an equivalent native runit services exists. This is to avoid conflicts and duplicate instances. However sysv scripts can define non standard actions (such as log rotation) that are not defined in runit's sv(8) control program. So it could be useful to forward such actions to the sysv script even when there is a runit services active. An example where this is useful is rsyslogd and many httpd servers. It should be considered that this strategy is not guaranteed to work, but it This strategy works for services that I've considered so far but it may not work for others: the sysv script uses the PID file (likely in /run/) while runit (actually runsv) maintain the PID process in it's own file inside the service directory, so a mismatch will break this. the alternative would be to define runit timers or oneshots companion services for each non standard actions but it's too expensive for now -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 6.1.0van (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_CPU_OUT_OF_SPEC, TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit) Versions of packages runit depends on: ii libc6 2.37-10 ii runit-helper2.16.1 ii sysuser-helper 1.3.9+really1.4.3 Versions of packages runit recommends: ii runit-init 2.1.2-56 Versions of packages runit suggests: ii runit-services 0.7.0 ii socklog 2.1.0+repack-5 ii ucspi-unix 1.0-2 pn zsh -- Configuration Files: /etc/default/runit changed [not included] /etc/runit/runsvdir/single/sulogin/run [Errno 2] No such file or directory: '/etc/runit/runsvdir/single/sulogin/run' -- no debconf information -- debsums errors found: debsums: changed file /lib/lsb/init-functions.d/40-runit (from runit package) debsums: changed file /lib/runit/trigger_sv (from runit package)
Bug#1050722: bookworm-pu: package runit-services/0.5.5~deb12u1
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: runit-servi...@packages.debian.org, plore...@disroot.org Control: affects -1 + src:runit-services [ Reason ] The version in stable (0.5.4) is currently affected by #1033542, where in most cases the dhclient service fails to start and syslog is flooded with failure messages at a very high rate, hiding other potentially relevant logs. The flood is a consequence of runit supervision design: when a service wanted status is 'up' and the service crashes, it's automatically restarted after a 1 second grace time. Bug #1033542 was filed with severity 'normal' during the freeze and at the time I thought that it was not worth an unblock request; now, given several complains I've received about this, I'm reconsidering. Dhclient is enabled and started by default for runit-init users; it may take time to notice the flood on syslog and even then, for a user that is not expert in runit, it's not easy to understand what is causing it. The attached debdiff is for a no change rebuild of the same version that is currently in unstable/testing [ Tests ] I tested the fix personally and it solves the issue [ Risks ] Low [ 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 ] * stop hardcoding eth1 in dhclient run file * adapt the check file for empty $INTERFACE Regards, Lorenzo
Bug#1035837: dhclient: memory limit too low on kFreeBSD
Package: runit-services Version: 0.6.0 Severity: normal dhclient service fails to start on kFreeBSD port, the current memory limit is too low and need to be doubled (12 --> 24) compared to linux kernel -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') merged-usr: no Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 10.3-0-amd64 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit) Versions of packages runit-services depends on: ii runit 2.1.2-54 ii runit-helper 2.15.2 Versions of packages runit-services recommends: ii runit-init 2.1.2-54 Versions of packages runit-services suggests: pn socklog -- no debconf information
Bug#1032947: dh-sysuser: typo in postrm snippet turn purge into noop
Package: dh-sysuser Version: 1.3.9+really1.4.3 Severity: important X-Debbugs-Cc: plore...@disroot.org I just discovered a typo that happened when #1000478 was fixed: the 'postrm-sysuser' snippet that calls sysuser-helper with 'prerm' instead of 'postrm'. Because of this the purge action becomes a noop. This need to be fixed in dh-sysuser and than all package that use it will have to be rebuilded. -- System Information: Debian Release: 12.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 6.1.0van (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_CPU_OUT_OF_SPEC, TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit) Versions of packages dh-sysuser depends on: ii perl 5.36.0-7 dh-sysuser recommends no packages. dh-sysuser suggests no packages. -- no debconf information
Bug#1032943: runit-init: halt called with unsupported options during poweroff
Package: runit-init Version: 2.1.2-54 Severity: minor X-Debbugs-Cc: Olaf Meeuwissen , Mark Hindley , plore...@disroot.org >From Devuan bug #749 [1] > > Every time I `poweroff` my machine, I see error message flash by that > complain about `halt` being called with unsupported options. I think > I have tracked this down to /etc/init.d/halt making blind assumptions > about the options supported by the `halt` command. When runit is init, calling halt or reboot at the end of stage3 is unecessary, so an easy solution to silent those warnings is to skip halt and reboot scripts during the shutdown loop, so that reboot or poweroff is carry on by runit code as stage 3 returns. There will be still one warning left for the -w flag but that is already tracked in #992648 [2]. I prefer not to silence the warning in shutdown.c: * It nice for the user to be warned that a used flag is noop * (more important) halt/reboot are called by other scripts or programs in the system, and I don't have a complete picture of that, so I'm using the warning to make debug easier in such situations. Olaf, let me know if you would be unsatisfyied with the above solution; Mark, I think the Devuan bug can be closed or marked as reassigned to this one (I don't know how to manipulate the Devuan BTS). Best, Lorenzo [1] https://bugs.devuan.org/cgi/bugreport.cgi?bug=749 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992648 -- System Information: Debian Release: 12.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 6.1.0van (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_CPU_OUT_OF_SPEC, TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit) Versions of packages runit-init depends on: ii getty-run2.1.2-54 ii initscripts 3.06-2 ii insserv 1.24.0-1 ii mount2.38.1-5 ii runit2.1.2-54 Versions of packages runit-init recommends: ii runit-services 0.5.4 runit-init suggests no packages. -- no debconf information
Bug#1031658: plasma-desktop: Depends on plasma-workspace-wayland looks wrong
Package: plasma-desktop Version: 4:5.27.0-1 Severity: normal X-Debbugs-Cc: plore...@disroot.org Dear maintainer, Latest update (4:5.27.0-1) of this package adds a dependency on plasma-workspace-wayland (it already dependes on plasma-workspace); however it looks like this is not accurate since plasmadesktop works just fine with plasma-workspace/kwin-x11, as I'm doing right now. Please consider to add an OR dependency like plasma-workspace-wayland | plasma-workspace so that users can choose to install only packages that they need, like only X11 or only wayland. Thanks, Lorenzo -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 6.1.0van (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_CPU_OUT_OF_SPEC, TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit) Versions of packages plasma-desktop depends on: ii accountsservice 22.08.8-6 ii breeze 4:5.27.0-1 ii kactivitymanagerd5.27.0-1 ii kde-cli-tools4:5.27.0-1 ii kded55.103.0-1 ii kio 5.103.0-1 ii kpackagetool55.103.0-1 ii layer-shell-qt 5.27.0-1 ii libaccounts-qt5-11.16-2 ii libc62.36-8 ii libglib2.0-0 2.74.5-1 ii libibus-1.0-51.5.27-5 ii libkaccounts24:22.12.1-1 ii libkf5activities55.103.0-1 ii libkf5activitiesstats1 5.103.0-1 ii libkf5authcore5 5.103.0-1 ii libkf5baloo5 5.103.0-1 ii libkf5bookmarks5 5.103.0-1 ii libkf5codecs55.103.0-1 ii libkf5completion55.103.0-1 ii libkf5configcore55.103.0-1 ii libkf5configgui5 5.103.0-1 ii libkf5configwidgets5 5.103.0-1 ii libkf5coreaddons55.103.0-1 ii libkf5crash5 5.103.0-1 ii libkf5dbusaddons55.103.0-1 ii libkf5globalaccel-bin5.103.0-1 ii libkf5globalaccel5 5.103.0-1 ii libkf5guiaddons5 5.103.0-1 ii libkf5i18n5 5.103.0-1 ii libkf5iconthemes55.103.0-1 ii libkf5itemviews5 5.103.0-1 ii libkf5jobwidgets55.103.0-1 ii libkf5kcmutils5 5.103.0-1 ii libkf5kcmutilscore5 5.103.0-1 ii libkf5kdelibs4support5 5.103.0-1 ii libkf5kiocore5 5.103.0-1 ii libkf5kiofilewidgets55.103.0-1 ii libkf5kiogui55.103.0-1 ii libkf5kiowidgets55.103.0-1 ii libkf5newstuffcore5 5.103.0-1 ii libkf5notifications5 5.103.0-1 ii libkf5notifyconfig5 5.103.0-1 ii libkf5package5 5.103.0-1 ii libkf5plasma55.103.0-1 ii libkf5plasmaquick5 5.103.0-1 ii libkf5quickaddons5 5.103.0-1 ii libkf5runner55.103.0-1 ii libkf5service-bin5.103.0-1 ii libkf5service5 5.103.0-1 ii libkf5solid5 5.103.0-1 ii libkf5sonnetcore55.103.0-1 ii libkf5sonnetui5 5.103.0-1 ii libkf5widgetsaddons5 5.103.0-1 ii libkf5windowsystem5 5.103.0-1 ii libkf5xmlgui55.103.0-1 ii libkworkspace5-5 4:5.27.0-1 ii libnotificationmanager1 4:5.27.0-1 ii libpackagekitqt5-1 1.1.0-1 ii libphonon4qt5-4 4:4.11.1-4 ii libprocesscore9 4:5.27.0-1 ii libqt5concurrent55.15.8+dfsg-2 ii libqt5core5a 5.15.8+dfsg-2 ii libqt5dbus5 5.15.8+dfsg-2 ii libqt5gui5 5.15.8+dfsg-2 ii libqt5network5 5.15.8+dfsg-2 ii libqt5qml5 5.15.8+dfsg-2 ii libqt5quick5 5.15.8+dfsg-2 ii libqt5quickwidgets5 5.15.8+dfsg-2 ii libqt5sql5 5.15.8+dfsg-2 ii
Bug#1031244: mariadb-server.postinst: line 236: [: too many arguments
Package: mariadb-server Version: 1:10.11.1-4 Severity: normal X-Debbugs-Cc: plore...@disroot.org Hello, During the last upgrade of mariadb in Sid, when the unversioned package replaced the versioned one, I run into the following output: [...] Processing triggers for mailcap (3.70+nmu1) ... Processing triggers for desktop-file-utils (0.26-1) ... Processing triggers for hicolor-icon-theme (0.17-2) ... Setting up mariadb-server (1:10.11.1-4) ... Installing new version of config file /etc/init.d/mariadb ... Installing new version of config file /etc/logrotate.d/mariadb ... Installing new version of config file /etc/mysql/mariadb.conf.d/50-server.cnf ... /var/lib/dpkg/info/mariadb-server.postinst: line 236: [: too many arguments insserv: warning: current start runlevel(s) (empty) of script `mariadb' overrides LSB defaults (2 3 4 5). [...] I suspect this is another instance of #1029136. I use apt-get to upgrade and it doesn't automatically purge removed packages; for this reason I'm not affected by #1029136 but also I have several old postrm files in the system ls /var/lib/dpkg/info/* | grep mariadb-server- /var/lib/dpkg/info/mariadb-server-10.0.list /var/lib/dpkg/info/mariadb-server-10.0.postrm /var/lib/dpkg/info/mariadb-server-10.1.list /var/lib/dpkg/info/mariadb-server-10.1.postrm /var/lib/dpkg/info/mariadb-server-10.3.list /var/lib/dpkg/info/mariadb-server-10.3.postrm /var/lib/dpkg/info/mariadb-server-10.5.list /var/lib/dpkg/info/mariadb-server-10.5.postrm /var/lib/dpkg/info/mariadb-server-10.6.list /var/lib/dpkg/info/mariadb-server-10.6.postrm So the test in postinstall line 236 fails and dh snippets in postrm files are not removed. Regards, Lorenzo -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 6.1.0van (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_CPU_OUT_OF_SPEC, TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit) Versions of packages mariadb-server depends on: ii adduser 3.131 ii debconf [debconf-2.0] 1.5.82 ii galera-426.4.13-1 ii gawk1:5.1.0-1 ii iproute26.1.0-1 ii libc6 2.36-8 ii libdbi-perl 1.643-4 ii libpam0g1.5.2-6 ii libssl3 3.0.8-1 ii libstdc++6 12.2.0-14 ii lsof4.95.0-1 ii mariadb-client 1:10.11.1-4 ii mariadb-common 1:10.11.1-4 ii mariadb-plugin-provider-bzip2 1:10.11.1-4 ii mariadb-plugin-provider-lz4 1:10.11.1-4 ii mariadb-plugin-provider-lzma1:10.11.1-4 ii mariadb-plugin-provider-lzo 1:10.11.1-4 ii mariadb-plugin-provider-snappy 1:10.11.1-4 ii mariadb-server-core 1:10.11.1-4 ii passwd 1:4.13+dfsg1-1 ii perl5.36.0-7 ii procps 2:4.0.2-3 ii psmisc 23.6-1 ii rsync 3.2.7-1 ii socat 1.7.4.4-2 ii zlib1g 1:1.2.13.dfsg-1 Versions of packages mariadb-server recommends: ii libhtml-template-perl 2.97-2 ii pv 1.6.20-1 Versions of packages mariadb-server suggests: ii bsd-mailx [mailx] 8.1.2-0.20220412cvs-1 ii mailutils [mailx] 1:3.15-3+b2 pn mariadb-test pn netcat-openbsd -- debconf information: mariadb-server/old_data_directory_saved: mariadb-server/postrm_remove_databases: false mariadb-server/nis_warning:
Bug#1031111: orphan-sysvinit-scripts: please add a script for Avahi daemon
Package: orphan-sysvinit-scripts
Version: 0.12
Severity: wishlist
Tags: patch
X-Debbugs-Cc: plore...@disroot.org
Hi,
Michael just dropped [1] another init script (actually two), this time is avahi.
I think it would be nice to add the scripts to this package for bookworm,
if possible. I'm attaching the last version of the init script from avahi 0.8-7;
mapping is:
avahi-daemon.service avahi-daemon
avahi-dnsconfd.service avahi-dnsconfd
License is GNU Lesser General Public License, version 2 or any later version
Not sure if the scripts are from upstream or Debian:
Utopia Maintenance Team
or
Upstream Avahi developers
Best Regards,
Lorenzo
[1]
https://tracker.debian.org/news/1417862/accepted-avahi-08-8-source-into-unstable/
and also
https://salsa.debian.org/utopia-team/avahi/-/commit/41a296309334853ed3164544bd39d872a8fc70a4
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
merged-usr: no
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0van (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CPU_OUT_OF_SPEC, TAINT_FIRMWARE_WORKAROUND,
TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: runit (via /run/runit.stopit)
Versions of packages orphan-sysvinit-scripts depends on:
ii ucf 3.0043+nmu1
orphan-sysvinit-scripts recommends no packages.
orphan-sysvinit-scripts suggests no packages.
#!/bin/sh
### BEGIN INIT INFO
# Provides: avahi avahi-daemon
# Required-Start:$remote_fs dbus
# Required-Stop: $remote_fs dbus
# Should-Start: $syslog
# Should-Stop: $syslog
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Avahi mDNS/DNS-SD Daemon
# Description: Zeroconf daemon for configuring your network
#automatically
### END INIT INFO
PATH=/sbin:/bin:/usr/sbin:/usr/bin
DESC="Avahi mDNS/DNS-SD Daemon"
NAME="avahi-daemon"
DAEMON="/usr/sbin/$NAME"
SCRIPTNAME=/etc/init.d/$NAME
# Gracefully exit if the package has been removed.
test -x $DAEMON || exit 0
. /lib/lsb/init-functions
# Include avahi-daemon defaults if available.
test -f /etc/default/avahi-daemon && . /etc/default/avahi-daemon
DISABLE_TAG="/var/run/avahi-daemon/disabled-for-unicast-local"
#
# Function that starts the daemon/service.
#
d_start() {
$DAEMON -c && return 0
if [ -e $DISABLE_TAG -a "$AVAHI_DAEMON_DETECT_LOCAL" != "0" ]; then
# Disabled because of the existance of an unicast .local domain
log_warning_msg "avahi-daemon disabled because there is a unicast
.local domain"
exit 0;
fi;
$DAEMON -D
}
#
# Function that stops the daemon/service.
#
d_stop() {
if $DAEMON -c ; then
$DAEMON -k
fi
}
#
# Function that reload the config file for the daemon/service.
#
d_reload() {
$DAEMON -c && $DAEMON -r
}
#
# Function that check the status of the daemon/service.
#
d_status() {
$DAEMON -c && { echo "$DESC is running"; exit 0; } || { echo "$DESC is not
running"; exit 3; }
}
case "$1" in
start)
log_daemon_msg "Starting $DESC" "$NAME"
d_start
log_end_msg $?
;;
stop)
log_daemon_msg "Stopping $DESC" "$NAME"
d_stop
log_end_msg $?
;;
reload|force-reload)
log_daemon_msg "Reloading services for $DESC" "$NAME"
d_reload
log_end_msg $?
;;
restart)
log_daemon_msg "Restarting $DESC" "$NAME"
d_stop
if [ "$?" -eq 0 ]; then
d_start
log_end_msg $?
else
log_end_msg 1
fi
;;
status)
d_status
;;
*)
echo "Usage: $SCRIPTNAME
{start|stop|restart|force-reload|reload|status}" >&2
exit 3
;;
esac
exit 0
#!/bin/sh
### BEGIN INIT INFO
# Provides: avahi-dnsconfd
# Required-Start:$remote_fs avahi-daemon
# Required-Stop: $remote_fs avahi-daemon
# Should-Start: $syslog
# Should-Stop: $syslog
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Avahi Unicast DNS Configuration Daemon
# Description: A DNS configuration daemon using mDNS in a
#DHCP-like fashion
### END INIT INFO
PATH=/sbin:/bin:/usr/sbin:/usr/bin
DESC="Avahi Unicast DNS Configuration Daemon"
NAME="avahi-dnsconfd"
DAEMON="/usr/sbin/$NAME"
SCRIPTNAME=/etc/init.d/$NAME
# Gracefully exit if the package has been removed.
test -x $DAEMON || exit 0
. /lib/lsb/init-functions
#
# Function that starts the daemon/service.
#
d_start() {
$DAEMON -c && return 0
if [ -s /etc/localtime ]; then
if [ ! -d /etc/avahi/etc ]; then
mkdir -p /etc/avahi/etc >/dev/null 2>&1
fi
cp -fp /etc/localtime /etc/avahi/etc >/dev/null 2>&1
fi;
$DAEMON -D
}
#
# Function that stops the daemon/service.
#
d_stop() {
Bug#1028270: getty-run: enable a serial getty to increase testability of runit-init
Package: getty-run Version: 2.1.2-52 Severity: important X-Debbugs-Cc: Helmut Grohne , plore...@disroot.org Hi Helmut, >From #1028181 > | Activating swapfile swap, if any...done. > | Cleaning up temporary files > | Cleaning up temporary files > | - runit: leave stage: /etc/runit/1 > | - runit: enter stage: /etc/runit/2 > | runsvchdir: default: current. > > In particular, the user has no way to log into the system as no getty > is being spawned. I see that the autopkgtest has to do this manually > via "ln -s /etc/sv/getty-ttyS0 /etc/service/". Note that the "user has no way to log into the system" is true if the only mean to login is a serial port; by default the user has 6 getty on tty[1-6] enabled. Said that I agree that it's nice to provide a setup that works out of the box; the quick fix that hopefully can improve the situation is that getty-run ship that service as enabled (it's disabled by default right now) so that the manual creation of the link is no longer needed. However I'm afraid that, since /dev/ttyS0 is hardcoded in the service, it won't work in environments where the serial device has a different name (let's say ttyS1)... > Do you think there > could be a better way to achieve this such that at least the console= > kernel command line parameter is automatically issued a getty? (just to be sure that I'm not misunderstanding the above) are you suggesting that runit grep /proc/cmdline for `console=' and if there is a match extract the device name and start a getty on that device? Or there is another more obvious way that I'm not considering? Lorenzo > > Helmut Note to myself: * the command= parameter can take several forms and there are comma separated options [1] * see also what systemd does with the getty-generator [2] [1] https://www.kernel.org/doc/html/latest/admin-guide/kernel-parameters.html [2] https://manpages.debian.org/testing/systemd/systemd-getty-generator.8.en.html
Bug#1028267: initscripts: runs fsck unconditionally but does not depends on e2fsprogs
Package: initscripts Version: 3.06-2 Severity: normal X-Debbugs-Cc: plore...@disroot.org Hi all, there are 2 scripts that run fsck without testing if the command is available in the system: checkroot.sh and checkfs.sh This package "only" recommands e2fsprogs, so I think it should just print a warning and go ahead if fsck is not available. The current behaviour can fail to boot in some cases https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028181 Lorenzo -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 6.1.0van (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_CPU_OUT_OF_SPEC, TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit) Versions of packages initscripts depends on: ii sysv-rc 3.06-2 ii sysvinit-utils 3.06-2 Versions of packages initscripts recommends: ii e2fsprogs 1.46.6~rc1-1+b1 ii psmisc 23.6-1 initscripts suggests no packages. -- Configuration Files: /etc/init.d/mountall.sh changed [not included] -- no debconf information
Bug#1028115: init: Document requirements for being an alternative pre-dependency of init
Package: init Version: 1.65.2 Severity: normal X-Debbugs-Cc: plore...@disroot.org Dear i-s-h maintainers, I intend to ask for the inclusion of runit-init into the pre-dep list of this package right after the bookworm release. For now I'm following the list of suggestions provided by Simon McVittie [1] in #923450 msg#15; please document your requirements. Regards, Lorenzo [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923450
Bug#1026836: RFS: runit-services/0.5.2 -- UNIX init scheme with service supervision (services)
Package: sponsorship-requests Severity: normal X-Debbugs-Cc: plore...@disroot.org Dear mentors, I am looking for a sponsor for my package "runit-services": * Package name : runit-services Version : 0.5.2 Upstream contact : [fill in name and email of upstream] * URL : [fill in URL of upstream's web site] * License : BSD-3-Clause, CC0-1.0 * Vcs : https://salsa.debian.org/Lorenzo.ru.g-guest/runit-services Section : admin The source builds the following binary packages: runit-services - UNIX init scheme with service supervision (services) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/runit-services/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/r/runit-services/runit-services_0.5.2.dsc Git repo: https://salsa.debian.org/Lorenzo.ru.g-guest/runit-services/-/tree/next Changes since the last upload: runit-services (0.5.2) experimental; urgency=medium . * Improve purge documentation (Closes: #1024962) * Fix wrong boot order for sysv dbus-services (Closes: #1024969) * Automate d/copyright update for runscripts: - add a simple copyright header to each runfile - add d/copyright.in - add a script that automatically update d/copyright based on copyright.in and runscripts headers * update copyright and copyright.in * d/prerm: fix wrong path for meta files * All runscripts cleanup: - do not set -e, relevant commands are tested - do not use redundant 'sv check' for checking service dependencies, 'sv start' is enough Regards, -- Lorenzo Puliti
Bug#1025721: RFS: dh-runit/2.15.1 -- debhelper add-on to handle runit runscripts
Package: sponsorship-requests Severity: normal X-Debbugs-Cc: plore...@disroot.org Dear mentors, I am looking for a sponsor for my package "dh-runit": * Package name : dh-runit Version : 2.15.1 Upstream contact : Lorenzo Puliti * URL : https://salsa.debian.org/debian/dh-runit * License : GPL-3+ * Vcs : https://salsa.debian.org/debian/dh-runit Section : admin The source builds the following binary packages: dh-runit - debhelper add-on to handle runit runscripts runit-helper - dh-runit implementation detail To access further information about this package, please visit the following URL: https://mentors.debian.net/package/dh-runit/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/d/dh-runit/dh-runit_2.15.1.dsc Git repo: https://salsa.debian.org/debian/dh-runit/-/tree/next Changes since the last upload: dh-runit (2.15.1) experimental; urgency=medium . * Remove duplicate metafiles * update tests for metafiles Regards, -- Lorenzo Puliti
Bug#1025718: RFS: runit/2.1.2-51 -- system-wide service supervision
Package: sponsorship-requests Severity: normal X-Debbugs-Cc: plore...@disroot.org Dear mentors, I am looking for a sponsor for my package "runit": * Package name : runit Version : 2.1.2-51 Upstream contact : Gerrit Pape * URL : http://smarden.org/runit/ * License : CC0-1.0, BSD-3-clause, GPL-3+ * Vcs : https://salsa.debian.org/debian/runit Section : admin The source builds the following binary packages: runit - system-wide service supervision runit-run - service supervision (systemd and sysv integration) runit-systemd - transitional package for runit-systemd users getty-run - runscripts to supervise getty processes runit-init - system-wide service supervision (as init system) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/runit/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/r/runit/runit_2.1.2-51.dsc Git repo: https://salsa.debian.org/debian/runit/-/tree/next Changes since the last upload: runit (2.1.2-51) experimental; urgency=medium . * Improve readability of stage 1 (Closes: #1022814) + thanks to András Korn * Don't skip rcS boot scripts in stage 1 (Closes: #1023358) * Improve check for default-syslog (Closes: #1023476) + thanks to András Korn * runit: suggests ucspi-unix * invoke-run: use env instead of conf for chpst envdir * cpsv: - merge make_svlinks functionality into cpsv - temporary keep make_svlinks for backward compatibility - simplify syntax check - fallback on bin file for sync - configurable stock directory with CPSV_SOURCE - use CPSV_DEST instead of CPSV_DIR - more accurate diff - more accurate list output - use less ambiguous syntax - update manpage * Add source directory for cpsv * runit NEWS, changes in cpsv and invoke-run * runit-systemd NEWS, recommend removal * d/tests: update tests dependency (Closes: #1025641) Regards, -- Lorenzo Puliti
Bug#1025505: RFS: runit-services/0.5.1 -- UNIX init scheme with service supervision (services)
Package: sponsorship-requests Severity: normal X-Debbugs-Cc: plore...@disroot.org Dear mentors, I am looking for a sponsor for my package "runit-services": * Package name : runit-services Version : 0.5.1 Upstream contact : [fill in name and email of upstream] * URL : [fill in URL of upstream's web site] * License : BSD-3-Clause, CC0-1.0 * Vcs : https://salsa.debian.org/Lorenzo.ru.g-guest/runit-services Section : admin The source builds the following binary packages: runit-services - UNIX init scheme with service supervision (services) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/runit-services/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/r/runit-services/runit-services_0.5.1.dsc Git repo: https://salsa.debian.org/Lorenzo.ru.g-guest/runit-services/-/tree/next Changes since the last upload: runit-services (0.5.1) experimental; urgency=medium . * dhclient: - raise memory limit - remove -e option - fix wrong keyword in check - move interfaces file in a conf subdirectory * update README * update copyright Regards, -- Lorenzo Puliti
Bug#1024969: runit-services: several Dbus services fail to start at boot when this package is installed
Package: runit-services Version: 0.5.0 Severity: important X-Debbugs-Cc: plore...@disroot.org Not sure about the severity, it technically fits in "makes unrelated software on the system break" which would be grave >From early testing of this package Martin Steigerwald wrote: > 1) Major issue: Once I install runit-services Network Manager is not > started on boot automatically anymore. I tried it on two laptops. On > one I removed runit-services again. Then Network Manager started > again on next reboot. As I use Devuan network-manager package still > has the init script /etc/init.d/network-manager. In /var/log/boot I > have only: > > Tue Nov 22 10:22:22 2022: Starting network connection manager: > NetworkManager. > > No error message or so. Starting it manually after boot works okay. > > I have no idea why cause your package does not provide a service dir > for it that could fail. Expect maybe that is the reason: Maybe an > ordering issue? As so DBUS not yet up before Network Manager is > starting? Probably would be best to also make a runit service dir for > Network Manager and implement proper dependency handling there. > > Another thing I just discovered. The bluetooth related services are > not started when your package runit-services is installed. > > I now removed the package. > To summarize: for a runit-init user: * with this package installed, each service that connects to (depends on) dbus for which there is a sysv service but not a runscript will fail to start at boot, because it's started as sysv script when dbus is still not available. Such services can be started manually later. * without this package the sysv-emulation (/lib/runit/run_sysv_scripts) run sysv scripts at boot in the correct (Sysv) order, so everything works as expected So installing this package will make dbus-services that are not included in runit-services, like netwok-manager, bluetoothd and others, fail to start at boot. Lorenzo
Bug#1024965: runit-services: use Debconf to upgrade services
Package: runit-services Version: 0.5.0 Severity: normal X-Debbugs-Cc: plore...@disroot.org >From early testing of the package > > > > What do you think about the way the upgrade of services is (not) > > handled? > > Perhaps this is not obvious right now because this is the first > > version of the package, but at each upgrade cpsv will just print a > > warning if a new version of a service is available and it won't > > automatically replace the the old version in /etc/sv/ . > > If the user decides to upgrade the service an extra invocation of > > cpsv is needed. > > For a few services I think this would be okay. Of course it would be > more comfortable to be asked whether to upgrade a service. It could > even be in a dialog like needrestart presents. It asks which of the > services to restart after updates in a nice dialog window where you > can select those to be restarted. So it would ask once and the user > selects the services to upgrade. > > > Do you prefer some kind of automation, similar to what dpkg or ucf > > provide? > > Hmmm, I think dpkg diffing and ucf would not work that well for > service directories. Those mechanisms work on single files. > > But might be an option to present some kind of diff. Then of course > update handling would be one by one. > > However, I think offering some automation has not really the highest > priority. It is nice to have. Not essential. > I've to look if this is doable with debconf: cpsv is already able to show a diff and to overwrite a service, so maybe debconf on top of cpsv... Lorenzo
Bug#1024962: runit-services: Purge in a system with Dbus is problematic
Package: runit-services Version: 0.5.0 Severity: normal X-Debbugs-Cc: plore...@disroot.org >From early testing of this package Martin Steigerwald wrote: > 2) Purging the package on a system with DBUS and SDDM is problematic. > It fails the purge cause it does not like to remove DBUS and SDDM > service directories while DBUS and SDDM are running. Thus the purge > operation fails. It asks to manually stop those services. For SDDM > this is easy. However DBUS just was started again. But maybe if I > would have stopped the Plasma desktop session before and stopped DBUS > on a TTY it would have worked. I bet this could use some explanation > for users who for whatever reason like to remove runit-services > again. What I did was just removing those service directories from > /etc/service myself using rm -r. By the way: Runit did not stop those > sddm then, or well at least the Plasma desktop session was still > running. A small number of services is marked "not safe to restart" because a restart can crash the graphic session on which the upgrade/removal/purge is performed. Example: dbus, lightdm, sddm, slim, xdm. So postrm of this package will not stop the above services on removal, and will fail to purge if one of the above services is still running as runit service. Not sure how to improve the situation here: stopping any display manager from within a graphic session would break purge in any case .. I'll see if it's acceptable to ignore dbus/elogind and/or to improve the message printed. >From some test it looks that my desktop (lxqt+openbox+slim) survives if only dbus is restarted, but some programs crash and other misbehave, I'll do more tests on other desktop environments. Probably this deserve its own section in the README. Lorenzo
Bug#1023476: runit: Improve default-syslog check
Package: runit Version: 2.1.2-50 Severity: normal X-Debbugs-Cc: plore...@disroot.org >From #1022837 > 2. a default-syslog service is created by something, and all it does on my > systems is sleep indefinitely (I use socklog as my syslogd, but have > my own service directory for that as well, and its name is just > "socklog", so the magic "check" script won't pick it up -- and > neither will it pick up a syslogd that is not managed by runit. Maybe > just try to see if something is listening on /dev/log in "check"?). the check could be just something like lsof /dev/log >/dev/null || exit 1 -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit) LSM: AppArmor: enabled Versions of packages runit depends on: ii libc6 2.36-4 ii runit-helper2.15.0 ii sysuser-helper 1.3.7+really1.4.1 Versions of packages runit recommends: ii runit-init 2.1.2-50 Versions of packages runit suggests: ii socklog 2.1.0+repack-4+b1 pn zsh -- Configuration Files: /etc/default/runit changed [not included] /etc/runit/ctrlaltdel changed [not included] /etc/runit/runsvdir/single/sulogin/run [Errno 2] No such file or directory: '/etc/runit/runsvdir/single/sulogin/run' -- no debconf information
Bug#1023358: runit: Stage 1: boot script in rcS should never be skipped
Package: runit Version: 2.1.2-50 Severity: important Partially related to #1022837. run_sysv_scripts is invoked in stage 1 to run boot scripts (initscripts); however it skip the sysv script when a runit service with the same name exists. This is wrong for early boot tasks and it can break the boot sequence. For example one can have a /etc/sv/udev longrun that will replace the sysv instance in stage 2, but still need to run /etc/init.d/udev during eraly boot. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit) LSM: AppArmor: enabled Versions of packages runit depends on: ii libc6 2.36-3 ii runit-helper2.15.0 ii sysuser-helper 1.3.7+really1.4.1 Versions of packages runit recommends: ii runit-init 2.1.2-50 Versions of packages runit suggests: ii socklog 2.1.0+repack-4+b1 pn zsh -- Configuration Files: /etc/default/runit changed [not included] /etc/runit/ctrlaltdel changed [not included] /etc/runit/runsvdir/single/sulogin/run [Errno 2] No such file or directory: '/etc/runit/runsvdir/single/sulogin/run' -- no debconf information
Bug#1022139: RFS: dh-runit/2.15.0 -- debhelper add-on to handle runit runscripts
Package: sponsorship-requests Severity: normal X-Debbugs-Cc: plore...@disroot.org Dear mentors, I am looking for a sponsor for my package "dh-runit": * Package name : dh-runit Version : 2.15.0 Upstream contact : Lorenzo Puliti * URL : https://salsa.debian.org/debian/dh-runit * License : GPL-3+ * Vcs : https://salsa.debian.org/debian/dh-runit Section : admin The source builds the following binary packages: dh-runit - debhelper add-on to handle runit runscripts runit-helper - dh-runit implementation detail To access further information about this package, please visit the following URL: https://mentors.debian.net/package/dh-runit/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/d/dh-runit/dh-runit_2.15.0.dsc Git repo: https://salsa.debian.org/debian/dh-runit/-/tree/next Changes since the last upload: dh-runit (2.15.0) unstable; urgency=medium . * metafiles: write packagename inside a pkg file * Add a bin option, useful for triggered upgrade * update dh-runit manpage * Revert "Temporary disable ghc testsuite" * Update testsuite Regards, -- Lorenzo Puliti
Bug#1022138: RFS: runit/2.1.2-50 -- system-wide service supervision
Package: sponsorship-requests Severity: normal X-Debbugs-Cc: plore...@disroot.org Dear mentors, I am looking for a sponsor for my package "runit": * Package name : runit Version : 2.1.2-50 Upstream contact : Gerrit Pape * URL : http://smarden.org/runit/ * License : GPL-3+, CC0-1.0, BSD-3-clause * Vcs : https://salsa.debian.org/debian/runit Section : admin The source builds the following binary packages: runit - system-wide service supervision runit-run - service supervision (systemd and sysv integration) runit-systemd - transitional package for runit-systemd users getty-run - runscripts to supervise getty processes runit-init - system-wide service supervision (as init system) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/runit/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/r/runit/runit_2.1.2-50.dsc Git repo: https://salsa.debian.org/debian/runit/-/tree/next Changes since the last upload: runit (2.1.2-50) unstable; urgency=medium . * Upload to unstable * runit.postinst: run the trigger also at configure * cpsv diff: exclude wtime file * lsb-40-runit: fix 'force-sysv' unset variable * sv_wtime: small adjustment * invoke-run: - stop service when the binary is not installed - avoid loop with start-stop-daemon.runit * trigger_sv: - enable the service by default - don't fail the upgrade when sv fails to restart * Document flag files with a readme * NEWS file for runit users * lintian: fix mismatched overrides Regards, -- Lorenzo Puliti
Bug#1021484: RFS: runit/2.1.2-49 -- system-wide service supervision
Package: sponsorship-requests Severity: normal X-Debbugs-Cc: plore...@disroot.org Dear mentors, I am looking for a sponsor for my package "runit": * Package name : runit Version : 2.1.2-49 Upstream contact : Gerrit Pape * URL : http://smarden.org/runit/ * License : GPL-3+, CC0-1.0, BSD-3-clause * Vcs : https://salsa.debian.org/debian/runit Section : admin The source builds the following binary packages: runit - system-wide service supervision runit-run - service supervision (systemd and sysv integration) runit-systemd - transitional package for runit-systemd users getty-run - runscripts to supervise getty processes runit-init - system-wide service supervision (as init system) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/runit/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/r/runit/runit_2.1.2-49.dsc Git repo: https://salsa.debian.org/debian/runit/-/tree/next Changes since the last upload: runit (2.1.2-49) experimental; urgency=medium . * make_svlink: create links also when CPSV_DIR is not /etc/sv * make the default directory for runsvdir configurable * stage 1: setup to experiment with a runtime service layout * /lib/lsb/init-functions.d/40-runit: mask sysv services and forward signals to runscripts; this can be tuned with flag files if start-stop-daemon wrapper is preferred. (Closes: #1021465) * add an sv_wtime utility needed for triggered upgrade of services * support triggered upgrade for runit services; this mode requires metafiles that are usually produced by dh-runit (Closes: #1021474) * invoke-run: - check for new metafile path inside the service directory - remove hardcoded path when 'chpst -e' is used - avoid loop when signals for sysv script are forwarded * cpsv: - improve readability of -d with colored diff - improve heuristic on sysvinit scripts * update-service: - add policy compliant commands - update manpage * run_sysv_scripts: small optimizations * svlogd: copy pkg metafile inside the log directory * Add a purge fallback for runit package, to fix piuparts sporadic failure Regards, -- Lorenzo Puliti
Bug#1021474: runit: forward signals from systemd-only services
Package: runit Version: 2.1.2-48 Severity: wishlist X-Debbugs-Cc: plore...@disroot.org Solutions listed in #1021465 provide access only to sysv service but there are other issues left: 1. can't forward signals from systemd path, socket, timers; even an override of deb-systemd-invoke from i-s-h won't work as calls to deb-systemd-invoke in maintscript are run only when systemd is init. 2. same problem as above for packages that ship a systemd service without a sysvscript counterpart, either because it never existed or because it's been removed 3. the standard upgrade sequence that happens at postinstall, or at prerem and postrm is unfitted for runit design: - in runit, when a service is enabled is also automatically started, and when is disabled is also stopped, no way around it. So doing enable+ start at postinstall and stop + disable at pre|postrm is not just pointless, but can be racy like in #919296 Also, combo like 'enable but don't start' that are possible with debhelper are not feasible in runit. - the standard postinstall ( enable + rescan + start/restart ) sequence is not efficient when more services are involved in the same upgrade, for example if 10 packages with services are upgraded the results is 10*(enable+rescan+start/restart), while a more conveninent sequence could be 10*(enable) + 1*(rescan) + X*(restart), skipping the start of newly enabled service ( to avoid te race) and doing one rescan for the entire upgrade. 4. the one-to-one equivalence between runit and systemd or sysv services is not always feasible and sometimes is undesiderable: - runit does not have a service manager, supervised services are started in parallel and dependencies are automatically sorted out with polling; with this design splitting services into several pieces like systemd does is not a great idea as it makes relation between services more complex to solve - sometimes the opposite is true and one sysv or systemd service has to be expressed with more than one runit services ( for example the ExecStartPost systemd directive) Overall, 1, 2 and 4 can be resolved by merging native runscript into packages but there are other two problems: * during the boot runit first runs all enabled sysv services in rc2.d (skipping when a native one exists), then starts all native services in parallel; so services that are involved in a dependency relationship should be merged in reverse order (otherwise the boot sequence will be broken). For example, before merging dbus runscript, all services that depends on dbus should be merged. This should be done without NMU as support for non default init is a whishlist bug. This is simply not feasible. * there is a social issue with non default init in Debian; a certain group of maintainer will refuse to merge support for other init system. So there is a need for a catch all 'runit-services' package at least for the above two case. As a runit-services package ships only services definition while binaries are in separate packages from other multiple sources, there is no established way to perform the standard maintscripts sequence[1]. This is not just an issue of reduced support for an alternative init: silently omitting to restart a runit service when a new version of the package that ships the binary fixes an outstanding CVE is a bad, probably RC security bug. An optimal solution is one that: * provide enable/disable and restart when the service definition is in a separate package from the one the ships the binary (without cooperation from the latter) * works when there a one-to-one relation with sysv or systemd services is not possible (basically decoupling runit services from other inits) * provide an efficient sequence where services are first enabled/disabled, then runsvdir is told to rescan and finally only services that are upgraded are restarted (decoupled from dpkg configure order) * bonus point if the mechanism can be used by local admin to handle their collection of services without the need to do a deb package Probably it can be done by writing data that is usually in maintscirpt inside some file that is parsed at runtime by a dpkg noawait trigger. This is kind of reinventing the wheel, except that if it works, it's a technical solution to workaround a social problem. Anyway I think this is within the scope of the "experimenting with alternative init" of the last init GR. [1] something like enable/disable the runit service when the package that ships the correspondent binary is installed/removed and restart the service on upgrade -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Bug#1021465: runit: Mask sysv services and forward signal to native runscripts
Package: runit Version: 2.1.2-48 Severity: normal X-Debbugs-Cc: plore...@disroot.org Maintscript run unconditionally sysv script during packages install/remove/upgrade: this is ok when a correspondant runscript does not exist (runit uses sysv script as fallback in that case) but it creates several issues when a native runscripts exists. * one can end up with tho instances of the same services, and one is unsupervised * the sysv instance may clash with the runit one, runit usually wins but in the meanwhile the package upgrade may fail to configure (for example mariadb) and the running instance may crash * the two instances may also interact in unspected ways without crashing Several solution exists but it's not obvious to me what's the right one: A. divert or override in some way update-rc.d and invoke-rc.d form i-s-h package B. abuse the policy-rc.d hack to run the action instead of denying it C. divert /etc/init.d/foo and replace it with a symlink to /usr/bin/sv D. hijack lsb init functions like /lib/lsb/init-functions.d/40-systemd E. use a start-stop-daemon wrapper All the above have the problem that are limited to sysv script, so it's not possible to access to a systemd socket/path/timer service, but that's probably a separate problem. All of the above interact badly with invoke-run, when it call '/etc/init.d/foo stop' the runit service enters a loop where it down itself.. Other disadvantages: A.1. no hope to merge into i-s-h package, discussion with patches is stuck since 2019, see #924132 and discussion on salsa MR. So I'll have to maintain a runit version of the two helpers forever 2. overrride or divert of essential bin, which can break package install, see #986644 B.1. old and somehow obscure interface, it probably should be handled with alternatives.. 2. running the action is outside the scope of the interface, as it should just allow or deny an action by return an appropriate code, but is not supposed to run the replacement directly C.1 insserv complains with four line of warning for each diverted scripts during upgrades 2. insserv ignores the diverted scripts which has the LSB header, so it no longer consider the script when it sets the start order of scripts D.1. doesn't work on initscripts that do not include lsb init functions, not sure how many are there 2. one need to be carefull to not pollute sysvscript namespace when a runscript does not exists 3. if a sysv script is written in some wierd/unexpected way, not sure who knows what happens.. E.1. uses zsh 2. overrride or divert of essential bin 3. are there sysv scripts that do not use start-stop-daemon (except 'oneshots')? 4. what if start-stop-daemon changes the interface (very very unlikely) Overall E and D seem far better than A, B and C, in term of risk and maintainance burden required; D may be slightly better than E (mainly because of E1 and E2) but I'm unsure of consequence of D2 and D3. It is probably worth to experiment with both, I think I'm going to enable D and provide a way to disable it so that E is still usable. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit) LSM: AppArmor: enabled Versions of packages runit depends on: ii libc6 2.34-8 ii runit-helper2.14.2 ii sysuser-helper 1.3.7+really1.4.1 Versions of packages runit recommends: ii runit-init 2.1.2-48 Versions of packages runit suggests: ii socklog 2.1.0+repack-4+b1 pn zsh -- Configuration Files: /etc/default/runit changed [not included] /etc/runit/ctrlaltdel changed [not included] /etc/runit/runsvdir/single/sulogin/run [Errno 2] No such file or directory: '/etc/runit/runsvdir/single/sulogin/run' -- no debconf information -- debsums errors found: debsums: changed file /lib/lsb/init-functions.d/40-runit (from runit package) debsums: changed file /lib/runit/trigger_sv (from runit package)
Bug#1020284: git-daemon-run: fails to purge: deluser -f: Unknown option: f
Package: git-daemon-run Version: 1:2.36.1-1 Severity: important Tags: patch X-Debbugs-Cc: plore...@disroot.org Hi, git-daemon-run fails to purge because in postrm it does ! deluser --version >/dev/null 2>&1 || exec deluser -f gitlog but '-f' does not appear to be a valid option in Debian deluser since a while. Gitlog user is created with '--home /nonexistent' and '--no-create-home' options, so I think just removing the -f option will fix this the right way. Regards, Lorenzo -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit) LSM: AppArmor: enabled Versions of packages git-daemon-run depends on: ii adduser 3.129 ii git 1:2.36.1-1 ii runit2.1.2-48 git-daemon-run recommends no packages. git-daemon-run suggests no packages. -- no debconf information
Bug#994683: RFS: opensysusers/0.6-3 [QA] [RC] -- processes sysusers.d directory to create system users
Package: sponsorship-requests Severity: normal X-Debbugs-Cc: plore...@disroot.org Dear mentors, I am looking for a sponsor for my package "opensysusers": * Package name: opensysusers Version : 0.6-3 Upstream Author : Chris Cromer * URL : https://github.com/artix-linux/opensysusers * License : LGPL-2.1+, BSD-2-clause * Vcs : https://salsa.debian.org/debian/opensysusers Section : admin It builds those binary packages: opensysusers - processes sysusers.d directory to create system users To access further information about this package, please visit the following URL: https://mentors.debian.net/package/opensysusers/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/o/opensysusers/opensysusers_0.6-3.dsc Git repo: https://salsa.debian.org/Lorenzo.ru.g-guest/opensysusers/-/commits/next Changes since the last upload: opensysusers (0.6-3) unstable; urgency=medium . * QA upload. * Update copyright years * Bump Standards-Version to 4.6.0, no changes required * Change section to admin * Update gitignore files * quilt patches: - Stop using eval (Closes: #992058, CVE-2021-40084) - Create group with m action (Closes: #986015) - Fix wrong nologin path Regards, -- Lorenzo Puliti
Bug#993953: RFS: runit/2.1.2-43 -- system-wide service supervision
Package: sponsorship-requests
Severity: normal
X-Debbugs-Cc: plore...@disroot.org
Dear mentors,
I am looking for a sponsor for my package "runit":
* Package name: runit
Version : 2.1.2-43
Upstream Author : Gerrit Pape
* URL : http://smarden.org/runit/
* License : GPL-3+, BSD-3-clause
* Vcs : https://salsa.debian.org/debian/runit
Section : admin
It builds those binary packages:
runit-init - system-wide service supervision (as init system)
getty-run - runscripts to supervise getty processes
runit-systemd - transitional package for runit-systemd users
runit-run - service supervision (systemd and sysv integration)
runit - system-wide service supervision
To access further information about this package, please visit the following
URL:
https://mentors.debian.net/package/runit/
Alternatively, one can download the package with dget using this command:
dget -x https://mentors.debian.net/debian/pool/main/r/runit/runit_2.1.2-43.dsc
Git repo:
https://salsa.debian.org/debian/runit/-/tree/next
Changes since the last upload:
runit (2.1.2-43) unstable; urgency=medium
.
* default-syslog: add a comment in the run file to
clarify the intended usage.
* Move the nosync file back to /etc/runit/:
it was moved to /run by mistake (Closes: #993602)
+ thanks to András Korn
* Stop using sysv-rc in stage 3: 'run_sysv_scripts' can
be easily used for shutdown tasks
* Adjust runit-init Depends:
- drop sysv-rc: it's still impossible to remove it because
of initscripts
- add insserv, it's needed to get the right boot sequence
for initscripts and sysvinit scripts
- bump the minimal required runit version to 2.1.2-43,
because of changes in 'run_sysv_scripts' and stage 3
* Update runit-init and runit-systemd description
* source only changes:
- move all contrib services under debian/sv
- stop patching upstream stage{1,2}, we already
maintain our version of stage{1,2,3} in d/contrib
- rename quilt patches to match the order in which
they are applied
Regards,
--
Lorenzo Puliti
Bug#993265: RFS: runit/2.1.2-42 -- system-wide service supervision
Package: sponsorship-requests Severity: normal X-Debbugs-Cc: plore...@disroot.org Dear mentors, I am looking for a sponsor for my package "runit": * Package name: runit Version : 2.1.2-42 Upstream Author : Gerrit Pape * URL : http://smarden.org/runit/ * License : BSD-3-clause, GPL-3+ * Vcs : https://salsa.debian.org/debian/runit Section : admin It builds those binary packages: runit-init - system-wide service supervision (as init system) getty-run - runscripts to supervise getty processes runit-systemd - transitional package for runit-systemd users runit-run - service supervision (systemd and sysv integration) runit - system-wide service supervision To access further information about this package, please visit the following URL: https://mentors.debian.net/package/runit/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/r/runit/runit_2.1.2-42.dsc git repo: https://salsa.debian.org/debian/runit/-/tree/next Changes since the last upload: runit (2.1.2-42) unstable; urgency=medium . * Release to unstable * getty-run: add hvc0 service, disabled by default: this is usually needed by Xen hypervisor * Add a default-syslog virtual service: to increase portability, services that log to syslog can depend on this rather than on a specific syslog daemon * shutdown.c: - try to fix FTBFS on Hurd (Closes: #992629) - distinguish between halt and shutdown flags: The -r flag ( as reboot) now only works with shutdown; Add a -f flag to shutdown (skip fsck next boot); Add -F flag to shutdown (force fsck next boot); The -f (as force a shutdown) and -w/--wtmp-only flags now only work with halt. (Closes: #992631) - Add a -n flag to halt, to skip sync() before reboot/poweroff; also, always check for runit.nosync flag file before invoking sync() (Closes: #992641) - make halt '-f' flag a noop when runit is init. This way runit can use its own code to reboot/poweroff the system; users can still use the long '--force' option to force a shutdown without signaling the init (Closes: #899246) * Update shutdown(8) manpage * Bump Standards Version to 4.6.0, no change required * Update lintian overrides for 'alternative init but not init.d script' Regards, -- Lorenzo Puliti
Bug#992648: runit: write wtmp entry at boot and shutdown
Package: runit Version: 2.1.2-41 Severity: normal X-Debbugs-Cc: plore...@disroot.org Other inits write a wtmp entry during boot and also when shutdown or reboot actions are requested. Runit currently has no such feature. Void Linux has code in its halt implementation that can write a wtmp entry see https://github.com/void-linux/void-runit/commit/8045334f08798ea91e25875539efb3b430ed3e99 maybe Void code can be imported in our shutdown implementation with minimal effort. Another option would be to use some variation of the Void code to extend the runit's utmpset utility. I prefer the latter but it requires more work on my side plus in the long term I'll have to carry on another quilt patch likely forever.. -- System Information: Debian Release: 11.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit) Versions of packages runit depends on: ii libc6 2.31-13 ii sysuser-helper 1.3.5.1 Versions of packages runit recommends: ii runit-init 2.1.2-41 Versions of packages runit suggests: ii socklog 2.1.0+repack-4+b1 -- no debconf information
Bug#992641: shutdown.c: does not check for /run/runit.nosync
Package: runit Version: 2.1.2-41 Severity: normal X-Debbugs-Cc: plore...@disroot.org When called as reboot/halt/poweroff -f shutdown code does a sync(), regardless of existence of /run/runit.nosync, then poweroff/reboot the system without contacting the init. However according to runit(8) 'If /run/runit.nosync exists, runit doesn't invoke sync().' -- System Information: Debian Release: 11.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit) Versions of packages runit depends on: ii libc6 2.31-13 ii sysuser-helper 1.3.5.1 Versions of packages runit recommends: ii runit-init 2.1.2-41 Versions of packages runit suggests: ii socklog 2.1.0+repack-4+b1 -- no debconf information
Bug#992631: runit: shutdown.c does not handle shutdown/halt overlapped flags
Package: runit Version: 2.1.2-41 Severity: normal X-Debbugs-Cc: plore...@disroot.org Shutdown that comes with runit can be called both as 'shutdown' or 'halt/reboot/poweroff'. Following the SysVinit implementation, -h, -n, -f are overlapped and have a different effect with halt or shutdown. Runit's shutdown.c does not support -n nor -h and -f forces a reboot/poweroff even if called with shutdown. Also is possible to reboot the system with a combo like 'poweroff -r' All this should be fixed. -- System Information: Debian Release: 11.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit) Versions of packages runit depends on: ii libc6 2.31-13 ii sysuser-helper 1.3.5.1 Versions of packages runit recommends: ii runit-init 2.1.2-41 Versions of packages runit suggests: ii socklog 2.1.0+repack-4+b1 -- no debconf information
Bug#992629: shutdown.c: FTBFS on Hurd
Source: runit Version: 2.1.2-41exp Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: plore...@disroot.org According to buildd logs, the shutdown.c source fails to build on Hurd > debian/contrib/shutdown.c:108:10: error: ‘RB_POWER_OFF’ undeclared (first use > in this function) this goes on since the shutdown.c source was introduced in runit (2.1.2-10). Note that the build un Hurd was failing even before that because of sv test failure, see https://buildd.debian.org/status/fetch.php?pkg=runit=hurd-i386=2.1.2-9=1476227134=0 the sv test failure can be dealt with after this one is fixed. -- System Information: Debian Release: 11.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit) -- no debconf information
Bug#991536: RFS: runit/2.1.2-41 [RC] -- system-wide service supervision
Package: sponsorship-requests Severity: normal X-Debbugs-Cc: plore...@disroot.org Dear mentors, I am looking for a sponsor for my package "runit": this upload has already been approved by the release team, see bug #991491 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991491 * Package name: runit Version : 2.1.2-41 Upstream Author : Gerrit Pape * URL : http://smarden.org/runit/ * License : BSD-3-clause * Vcs : https://salsa.debian.org/debian/runit Section : admin It builds those binary packages: runit - system-wide service supervision runit-run - service supervision (systemd and sysv integration) runit-systemd - transitional package for runit-systemd users getty-run - runscripts to supervise getty processes runit-init - system-wide service supervision (as init system) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/runit/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/r/runit/runit_2.1.2-41.dsc Git repo: https://salsa.debian.org/Lorenzo.ru.g-guest/runit/-/tree/bullseye-support Changes since the last upload: runit (2.1.2-41) unstable; urgency=medium . * Cherry-pick shutdown.c fixes from experimental for incoming stable release: - fix broken switch from SysVinit due to wrong command line parsing logic (Closes: #991227) - reboot the system with -r flag instead of poweroff (Closes: #990774) - Update shutdown(8) manpage Regards, -- Lorenzo Puliti
Bug#991491: unblock: runit/2.1.2-41 (pre-approval)
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: plore...@disroot.org Dear release team, this is a pre-approval request for a runit upload. [ Reason ] The switch for SysVinit users is broken, the current code works only if a user types 'reboot', then login into the emergency shell and types 'reboot' again (see #991227). With the attached patch: * the -f and -r flags work as expected * the shutdown interface is documented in the manpage. [ Impact ] Without this patch SysVinit users will likely need to press the reset button (see #991227), which is a regression compared to the runit's version in Buster - the bug was introduced in runit 2.1.2-27 (#919699). Poweroff instead of reboot when the -r flag is passed (#990774) can be bad if one does 'shutdown -r now' on a remote machine expecting to be able to login again.. [ Tests ] I've manually run the qemu autopkgtest to ensure that there is no regression for the systemd-->runit-init switch. I've tested in Virtualbox that the patch fixes the SysVinit-->runit-init switch, which is currently broken in unstable/testing. I'm using the runit package from experimental that include the proposed fix and shutdown or reboot works as expected. [ Risks ] This change affects runit-init users (popcon ~ 20) and users of other init systems but only when they perform the switch to runit. [ 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 testing unblock runit/2.1.2-41 Lorenzo diff -Nru ./runit/debian/changelog ./runit-bullseye/debian/changelog --- ./runit/debian/changelog2021-07-25 15:48:55.494007628 +0200 +++ ./runit-bullseye/debian/changelog 2021-07-25 17:03:59.122707529 +0200 @@ -1,3 +1,14 @@ +runit (2.1.2-41) unstable; urgency=medium + + * Cherry-pick shutdown.c fixes from experimental +for incoming stable release: +- fix broken switch from SysVinit due to wrong + command line parsing logic +- reboot the system with -r flag instead of poweroff +- Update shutdown(8) manpage + + -- Lorenzo Puliti Sun, 25 Jul 2021 16:35:08 +0200 + runit (2.1.2-40) unstable; urgency=medium * Ack previous NMU, thanks Boyuan Yang for the upload diff -Nru ./runit/debian/contrib/shutdown.8 ./runit-bullseye/debian/contrib/shutdown.8 --- ./runit/debian/contrib/shutdown.8 2021-07-25 15:48:55.494007628 +0200 +++ ./runit-bullseye/debian/contrib/shutdown.8 2021-07-25 16:23:23.731732301 +0200 @@ -1,15 +1,66 @@ -.TH SHUTDOWN 8 "Oct 10, 2016" "" "GNU/Linux System Adminstrator's manual" +.TH SHUTDOWN 8 "July 16, 2021" "" "GNU/Linux System Adminstrator's manual" .SH NAME -shutdown, reboot, poweroff \- stop the system +shutdown, reboot, poweroff \- poweroff or reboot the system .SH SYNOPSIS -.B /sbin/shutdown +.B /sbin/shutdown [-w] [-f] [-r] .br -.B /sbin/reboot +.B /sbin/reboot [-w] [-f] [-r] .br -.B /sbin/halt +.B /sbin/halt [-w] [-f] [-r] +.br +.B /sbin/poweroff [-w] [-f] [-r] .SH DESCRIPTION -SysV-init compatibility scripts, that just invokes -.BR /sbin/init , -which are expected by graphical desktop environments. +.BR Shutdown +is a program to poweroff or reboot the system that maintains some compatibility with +original SysV-init halt, poweroff, reboot and shutdown programs. +These programs are expected by some initscripts, graphical desktop environments and tools like acpi. +.RE +When called as shutdown, halt or poweroff without options, +.BR runit(8) +is told to shutdown the system and poweroff. +.RE +When called as reboot +.BR runit(8) +is told to reboot the system. +.RE +When +.BR runit(8) +is not the current init system this program sends data in the appropriate format to perform the requested action to the initctl pipe, if it exists. +.SH OPTIONS + +.TP +.B \-f, \-\-force +Force unsafe reboot or poweroff immediately without signaling the init system. +This will likely result in an unclean shutdown an can cause data loss or corruption. + +.TP +.B \-w, \-\-wtmp\-only +No-Op, maintained for compatibility with initscripts. See #919699 + +.TP +.B \-r +Reboot the system regardless of how the command is called. +.SH SWITCHING FORM OTHER INIT SYSTEMS +This program maintains a compatibility layer with SysV-init's initctl pipe according to the spec described in SysV-init's initctl(5). This allow one to reboot the system when switching from another init to runit-init. +.RE +Currently only switching from systemd and SysV-init is tested but any other init system that maintains an initctl pipe compatible with SysV's one should work. + +.SH BUGS +Non existent or unsupported options are silently ignored. +.RE +Combining flags, like +.B halt -wf +is not supported, all merged short options will be ignored. +.RE +The +.B -r +flag will always reboot the system, even if called as poweroff or halt; this is
Bug#991282: RFS: runit/2.1.2-41exp1 -- system-wide service supervision
Package: sponsorship-requests Severity: normal X-Debbugs-Cc: plore...@disroot.org Dear mentors, I am looking for a sponsor for my package "runit": * Package name: runit Version : 2.1.2-41exp1 Upstream Author : Gerrit Pape * URL : http://smarden.org/runit/ * License : GPL-3+, BSD-3-clause * Vcs : https://salsa.debian.org/debian/runit Section : admin It builds those binary packages: runit-init - system-wide service supervision (as init system) getty-run - runscripts to supervise getty processes runit-systemd - transitional package for runit-systemd users runit-run - service supervision (systemd and sysv integration) runit - system-wide service supervision To access further information about this package, please visit the following URL: https://mentors.debian.net/package/runit/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/r/runit/runit_2.1.2-41exp1.dsc Git repo: https://salsa.debian.org/Lorenzo.ru.g-guest/runit/-/tree/2.1.2-41exp Changes since the last upload: runit (2.1.2-41exp1) experimental; urgency=medium . * Set rules-requires-root to no * Runit-run: drop dependency on runit-systemd | sysvinit-core * Runit: get rid of ancient transition code in prerm * Add upstream metadata * Add support for policy-rc.d hack in invoke-run * Update invoke-run manpage for policy-rc.d * Update News files * Shutdown.c: - fix wrong command line parsing logic that always caused a No-Op when any option was given, breaking, among other things, the init switch from Sysvinit (Closes: #991227) - reboot the system with -r flag (Closes: #990774) * Update shutdown(8) manpage * Update license and copyright years Regards, -- Lorenzo Puliti
Bug#991266: postinst: Can't exec systemctl: No such file or directory
Package: proftpd-core Version: 1.3.7b+dfsg-1 Severity: normal Tags: patch X-Debbugs-Cc: plore...@disroot.org Dear Maintainer, during the last upgrade of proftpd i got [...] Setting up proftpd-core (1.3.7b+dfsg-1) ... usermod: no changes Can't exec "systemctl": No such file or directory at /usr/bin/deb-systemd-invoke line 110. sh: 1: systemctl: not found Can't exec "systemctl": No such file or directory at /usr/bin/deb-systemd-invoke line 94. proftpd.service is a disabled or a static unit not running, not starting it. insserv: warning: current start runlevel(s) (empty) of script `proftpd' overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `proftpd' overrides LSB defaults (0 1 6). insserv: Script `lvm2' has overlapping Default-Start and Default-Stop runlevels (S) and (S). This should be fixed. Stopping ftp server: proftpd. Starting ftp server: proftpd. [...] Not a tragic issue since it looks that postinst script proceeds anyway with the rest of the configuration, but if you look at snippets from debhelper deb-systemd-invoke is always called only if systemd is PID1. The patch at the bottom should fix the issue. Regards, Lorenzo $ diff -u ./proftpd-core.postinst proftpd-core.postinst-new --- ./proftpd-core.postinst 2021-07-15 23:33:15.0 +0200 +++ proftpd-core.postinst-new 2021-07-19 10:02:48.080741451 +0200 @@ -207,8 +207,10 @@ # enable and start proftpd daemon via systemctl if egrep -qi "^[[:space:]]*ServerType.*standalone" /etc/proftpd/proftpd.conf then - deb-systemd-invoke enable proftpd.service - deb-systemd-invoke restart proftpd.service + if [ -d /run/systemd/system ]; then + deb-systemd-invoke enable proftpd.service + deb-systemd-invoke restart proftpd.service + fi fi fi -- System Information: Debian Release: 11.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit) Versions of packages proftpd-core depends on: ii adduser 3.118 ii debianutils 4.11.2 ii init-system-helpers 1.60 ii libacl1 2.2.53-10 ii libc62.31-13 ii libcap2 1:2.44-1 ii libcrypt11:4.4.18-4 ii libhiredis0.14 0.14.1-1 ii libmemcached11 1.0.18-4.2 ii libmemcachedutil21.0.18-4.2 ii libncursesw6 6.2+20201114-2 ii libpam-runtime 1.4.0-9 ii libpam0g 1.4.0-9 ii libpcre3 2:8.39-13 ii libssl1.11.1.1k-1 ii libtinfo66.2+20201114-2 ii lsb-base 11.1.0 ii netbase 6.3 ii sed 4.7-1 ii ucf 3.0043 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages proftpd-core recommends: ii proftpd-doc 1.3.7b+dfsg-1 Versions of packages proftpd-core suggests: pn openbsd-inetd | inet-superserver ii openssl 1.1.1k-1 ii proftpd-mod-crypto1.3.7b+dfsg-1 pn proftpd-mod-geoip pn proftpd-mod-ldap pn proftpd-mod-mysql pn proftpd-mod-odbc pn proftpd-mod-pgsql pn proftpd-mod-snmp pn proftpd-mod-sqlite ii proftpd-mod-wrap 1.3.7b+dfsg-1 -- no debconf information
Bug#991227: runit: Broken switch from SysVinit - needs hardreset
Package: runit
Version: 2.1.2-40
Severity: important
Tags: patch
X-Debbugs-Cc: plore...@disroot.org
The fix for #919699 introduced a regression described in #990774: when shutdown,
halt or reboot is called with parameters it does nothing. This includes the -f
flag.
A consequence is that the switch Sysvinit --> runit-init can be broken.
When plain shutdown or reboot are called (for instance by a graphical desktop
env),
SysVinit is told to enter runlevel 0 or 6, but then it expects halt -f or
reboot -f
to finish the job (but they are noop, so the system is left in a wierd state).
When reboot is called the system initate the shutdown process, then stops and
the user can login into emergency shell: from there, only if the user call
again reboot,
the system will complete the shutdown process (after about 15 seconds of
waiting).
If shutdown is called the system initate the shutdown process but then stops:
all
tty's are down, no way to login, and init does not complete the shutdown. From
there
one can only press the reset button.
Runit-init users are not affected only because, when stage3 returns (because
halt -f is a noop)
runit uses it's own internal code to poweroff or reboot.
The switch from systemd is not affected because systemd uses it's own internal
code
to perform the shutdown.
I've already tested that the patch for #990774, attached below,
fix this issue too
patch: (the last two lines with the -r flag are not strictly needed here )
--- ./shutdown.c2020-01-13 01:07:09.185373016 +0100
+++ ./shutdown-new.c2021-07-15 14:51:04.482088733 +0200
@@ -134,14 +134,16 @@
}
for (i = 1; i != argc; ++i) {
- if (strcmp(argv[i], "-f"))
+ if (strcmp(argv[i], "-f") == 0)
cfg->force = true;
- if (strcmp(argv[i], "--force"))
+ if (strcmp(argv[i], "--force") == 0)
cfg->force = true;
- if (strcmp(argv[i], "-w"))
+ if (strcmp(argv[i], "-w") == 0)
cfg->wtmp_only = true;
- if (strcmp(argv[i], "--wtmp-only"))
+ if (strcmp(argv[i], "--wtmp-only") == 0)
cfg->wtmp_only = true;
+ if (strcmp(argv[i], "-r") == 0)
+ cfg->action = ACTION_REBOOT;
}
}
-- System Information:
Debian Release: 11.0
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: runit (via /run/runit.stopit)
Versions of packages runit depends on:
ii libc6 2.31-12
ii sysuser-helper 1.3.5.1
Versions of packages runit recommends:
ii runit-init 2.1.2-41exp1
Versions of packages runit suggests:
ii socklog 2.1.0+repack-4+b1
-- Configuration Files:
/etc/default/runit changed [not included]
/etc/runit/ctrlaltdel changed [not included]
/etc/runit/runsvdir/single/sulogin/run [Errno 2] No such file or directory:
'/etc/runit/runsvdir/single/sulogin/run'
-- no debconf information
Bug#988903: RFS: dh-runit/2.11.0 -- debhelper add-on to handle runit runscripts
Package: sponsorship-requests Severity: normal X-Debbugs-Cc: plore...@disroot.org Dear mentors, I am looking for a sponsor for my package "dh-runit": * Package name: dh-runit Version : 2.11.0 Upstream Author : Lorenzo Puliti * URL : https://salsa.debian.org/debian/dh-runit * License : GPL-3+ * Vcs : https://salsa.debian.org/debian/dh-runit Section : admin It builds those binary packages: dh-runit - debhelper add-on to handle runit runscripts runit-helper - dh-runit implementation detail To access further information about this package, please visit the following URL: https://mentors.debian.net/package/dh-runit/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/d/dh-runit/dh-runit_2.11.0.dsc Git repo: https://salsa.debian.org/Lorenzo.ru.g-guest/dh-runit/-/tree/exp-2.11.0 Changes since the last upload: dh-runit (2.11.0) experimental; urgency=medium . * Expose enable and onupgrade as metafiles * Add a noscripts option * Add a usr option * Add a test for the usr option * Add a test for the enable metafile * Install a finish file by default * Add a nofinish option * Update tests for finish and nofinish Regards, -- Lorenzo Puliti
Bug#986978: RFS: opentmpfiles/0.3.1-2 [QA] -- standalone utility to process tmpfiles.d files
Package: sponsorship-requests Severity: normal X-Debbugs-Cc: plore...@disroot.org Dear mentors, I am looking for a sponsor for my package "opentmpfiles": * Package name: opentmpfiles Version : 0.3.1-2 Upstream Author : William Hubbs * URL : https://github.com/OpenRC/opentmpfiles * License : LGPL-2.1+, BSD-2-clause * Vcs : https://salsa.debian.org/debian/opentmpfiles Section : net It builds those binary packages: opentmpfiles - standalone utility written to process systemd-style tmpfiles.d files To access further information about this package, please visit the following URL: https://mentors.debian.net/package/opentmpfiles/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/o/opentmpfiles/opentmpfiles_0.3.1-2.dsc Git repo: https://salsa.debian.org/Lorenzo.ru.g-guest/opentmpfiles/-/tree/qa-0.3.1-2 Changes since the last upload: opentmpfiles (0.3.1-2) unstable; urgency=medium . * QA upload. * Conflicts with systemd (see #986886) * Remove the systemd-tmpfiles diversion Regards, -- Lorenzo Puliti
Bug#986656: ITP: runit-services -- a collection of services for runit
Package: wnpp Severity: wishlist Owner: Lorenzo Puliti X-Debbugs-Cc: debian-de...@lists.debian.org, plore...@disroot.org * Package name: runit-services Version : 0.5.0 Upstream Author : Gerrit Pape (2005-2008), Lorenzo Puliti (2021) * URL : https://salsa.debian.org/runit-team/runit-services * License : (BSD-3-Clause) Programming Lang: (shell) Description : a collection of services for runit supervision suite runit is a replacement for SysV-init and other init schemes. It runs on Debian GNU/Linux, *BSD, MacOSX, and Solaris, and may be easily adapted to other Unix operating systems. runit implements a simple three-stage concept. Stage 1 performs the system's one-time initialization tasks. Stage 2 starts the system's uptime services (via the runsvdir program). Stage 3 handles the tasks necessary to shutdown and halt or reboot. . See http://smarden.org/runit/ for more information. . This package contains services directories for a collection of services available in Debian, to have them run under runit service supervision instead of sysvinit or through init.d scripts. Amongst other services, it includes service directories for apache, cron, dhclient, exim, gdm, postfix, squid, ssh. This is a Debian native package that already existed in the archive in the past and was removed I believe around 2010. I intend to use this as a way to made a collection of most popular and requested services quickly available as native runscripts for runit users. This is a subpar solution compared to dh-runit, which remains the preferred option for runscripts, but it could be a good chance to let people experiment with runit. I'm looking for a sponsor for this package. Regards, Lorenzo
Bug#986644: dpkg-divert: document how to use with --no-rename
Package: dpkg Version: 1.20.7.1 Severity: important X-Debbugs-Cc: plore...@disroot.org Dear maintainer, I want one of my packages to divert files from an essential package: I used code from examples (with --rename option) online [1] that works fine, but lintian complains. Moving essential files can be dangerous, use the --no-rename. Ok. So I assumend that the same code would work fine, just replacing '--rename' with 'no-rename', silly me.. instead it broke my system. It is true that the manpage states under [ --add/remove] "The file is currently not renamed, see --rename" However reading the --rename/--no-rename description I was under the impression that the --no-rename was a safer option - overwrite during unpack instead of moving aside before the unpack, and that it's safer also when the diversion is removed. This is not the case, or maybe there is an easy way that i'm not considering but it's not documented anywere and also serching the code base for examples [2] provides no clue. Somehow i found a way but it requires some additional code in preinst and giving that lintian screams in all the four cardinal direction I suspect it's not the right way [ example appended at the end ] I'm having the following problems with --no-rename: * At preinst, it doesn't create a copy of the original file "file.real" * at postrm, the file disappear and it's not replaced by anything; also, if there is a copy "file.real" is left there (i guess piuparts would complain) Even if one use the --rename option in postrm, the "file.real" is not granted to exists untill the package that ship the original file is upgraded or reinstalled. Finally, while during the unpack the file is overwritten, during the removal there is still a moment where the file disappear (am I wrong?) so overall it does look more complex to handle but not that safer than a standard --rename. Regards, Lorenzo [1] https://www.debian.org/doc/debian-policy/ap-pkg-diversions.html [2] https://codesearch.debian.net/search?q=dpkg-divert+--no-rename=1 Example $ cat runit-init.preinst #!/bin/sh set -e # make sure that the *.real diverted file exists when postrm is called # as with --no-rename the diverted file is not created: if this package # is removed before init-system-helpers is upgraded the system will be # left without helpers!! see postrm if [ upgrade != "$1" ] || dpkg --compare-versions "$2" lt 2.1.2-41; then for file in /usr/sbin/invoke-rc.d /usr/sbin/service /usr/sbin/update-rc.d ; do if [ ! -e "$file".real ] ; then cp "$file" "$file".real fi done fi # install helpers with runit support if [ upgrade != "$1" ] || dpkg --compare-versions "$2" lt 2.1.2-41; then dpkg-divert --package runit-init --add --no-rename \ --divert /usr/sbin/invoke-rc.d.real /usr/sbin/invoke-rc.d dpkg-divert --package runit-init --add --no-rename \ --divert /usr/sbin/service.real /usr/sbin/service dpkg-divert --package runit-init --add --no-rename \ --divert /usr/sbin/update-rc.d.real /usr/sbin/update-rc.d fi #DEBHELPER# exit 0 --- $ cat runit-init.postrm #!/bin/sh set -e # need to use --rename here, with --no-rename the *.real diverted file will # not be back and the system is left without helpers! # *.real is granted to be there because of preinst if [ "$1" = "remove" ] || [ "$1" = "abort-install" ] || [ "$1" = "disappear" ] ; then dpkg-divert --package runit-init --remove --rename \ --divert /usr/sbin/invoke-rc.d.real /usr/sbin/invoke-rc.d dpkg-divert --package runit-init --remove --rename \ --divert /usr/sbin/service.real /usr/sbin/service dpkg-divert --package runit-init --remove --rename \ --divert /usr/sbin/update-rc.d.real /usr/sbin/update-rc.d fi #the following can be removed as runit 2.1.2-41 is out of oldoldstable if [ "abort-upgrade" = "$1" ] && dpkg --compare-versions "$2" lt 2.1.2-41; then dpkg-divert --package runit-init --remove --rename \ --divert /usr/sbin/invoke-rc.d.real /usr/sbin/invoke-rc.d dpkg-divert --package runit-init --remove --rename \ --divert /usr/sbin/service.real /usr/sbin/service dpkg-divert --package runit-init --remove --rename \ --divert /usr/sbin/update-rc.d.real /usr/sbin/update-rc.d fi #DEBHELPER# exit 0 $ cat runit-init.install debian/contrib/helpers/invoke-rc.d/usr/sbin debian/contrib/helpers/service/usr/sbin debian/contrib/helpers/update-rc.d/usr/sbin - $ lintian -Ev --pedantic runit_2.1.2-41_amd64.changes N: Using profile debian/main. N: Starting on group runit/2.1.2-41 N: Finished processing group runit/2.1.2-41 E: runit-init: diversion-for-unknown-file --no-rename/usr/sbin/invoke-rc.d preinst:19 E: runit-init: diversion-for-unknown-file --no-rename/usr/sbin/service preinst:21 E: runit-init: diversion-for-unknown-file
Bug#982954: RFS: runit/2.1.2-40 -- system-wide service supervision
Package: sponsorship-requests Severity: normal X-Debbugs-Cc: plore...@disroot.org Dear mentors, I am looking for a sponsor for my package "runit": * Package name: runit Version : 2.1.2-40 Upstream Author : Gerrit Pape * URL : http://smarden.org/runit/ * License : BSD-3-clause * Vcs : https://salsa.debian.org/debian/runit Section : admin It builds those binary packages: runit-init - system-wide service supervision (as init system) getty-run - runscripts to supervise getty processes runit-systemd - transitional package for runit-systemd users runit-run - service supervision (systemd and sysv integration) runit - system-wide service supervision To access further information about this package, please visit the following URL: https://mentors.debian.net/package/runit/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/r/runit/runit_2.1.2-40.dsc Git repo: https://salsa.debian.org/Lorenzo.ru.g-guest/runit/-/tree/2.1.2-40-release Changes since the last upload: runit (2.1.2-40) unstable; urgency=medium . * Ack previous NMU, thanks Boyuan Yang for the upload * Getty-run: default to agetty, only suggests fgetty (Closes: #981248) * invoke-run: don't stop sysv script if is a symlink + many thanks to Devuan testers Regards, -- Lorenzo Puliti
Bug#981948: RFS: dh-sysuser/1.3.5.1 -- debhelper addon to handle creation of system users
Package: sponsorship-requests Severity: normal X-Debbugs-Cc: plore...@disroot.org Dear mentors, I am looking for a sponsor for my package "dh-sysuser": * Package name: dh-sysuser Version : 1.3.5.1 Upstream Author : [fill in name and email of upstream] * URL : https://salsa.debian.org/debian/dh-sysuser * License : GPL-3+ * Vcs : https://salsa.debian.org/debian/dh-sysuser Section : admin It builds those binary packages: sysuser-helper - dh-sysuser implementation detail dh-sysuser - debhelper addon to handle creation of system users To access further information about this package, please visit the following URL: https://mentors.debian.net/package/dh-sysuser/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/d/dh-sysuser/dh-sysuser_1.3.5.1.dsc Git repo: https://salsa.debian.org/Lorenzo.ru.g-guest/dh-sysuser/-/tree/1.3.5.1-release Changes since the last upload: dh-sysuser (1.3.5.1) unstable; urgency=medium . * Bump Stadards-Version to 4.5.1 * Mark dh-sysuser and sysuser-helper Multi-Arch: foreign (Closes: #981683) + Many thanks to Helmut Grohne Regards, -- Lorenzo Puliti
Bug#981941: sysuser-helper: Merged-usr transition
Package: sysuser-helper Version: 1.3.5 Severity: important X-Debbugs-Cc: plore...@disroot.org Note for myself: after recent TC decision Debian is going to support merged-usr only, starting from Bookworm. Sysuser-helper ships files under /lib/sysuser-helper/ so need a transition plan. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit) -- no debconf information
Bug#981937: dh-sysuser: Reduce negative impact and assess overall utility
Package: dh-sysuser Version: 1.3.5 Severity: wishlist X-Debbugs-Cc: plore...@disroot.org Note: CC Helmut Grohne as he started the discussion, CC Niels Thykier as he might want to say something here Helmut Grohne , from #981683: > Further development seems like a good idea. The package uses useradd > instead of the policy-recommended adduser. Is there a good reason for > doing so? The approach taken here entirely sidesteps the established and > declarative sysusers.d format. Is there a reason for not cooperating > with it? Niels Thykier is working a lot on removing maintainer scripts > and turning them into declarative alternatives such as triggers. > dh-sysusers works towards the opposite. Why? As far as I can tell, > project consensus is that system users should not be removed on purge, > but dh-sysuser does so. From my subjectively skewed perception, > dh-sysuser has only created problems, not solved any. I acknowledge that > this is not the whole picture. Short answer: Given that this is an alternative implementation for creating system users related to an alternitive init system, and given the last GR results, it make sense to drive the development of this package in a way that shift the burden from Debian infrastructure and contributors to this package maintainance, whenever this is possible. If dh-sysuser creates problem, then people affected need to report bugs about that. There is nothing i can and i will do if i'm not even aware of the existence of an issue [ this package had 0 bug reported until the beginning of 2021]. I've already opened bugs for the 'adduser'and the 'remove on purge' issues, but that's not the kind of bugs we are talking about. Long answer: Following the last GR, the overall state of 'creating system users' in Debian is getting messy, currently we have * systemd-sysusers [systemd package]: this is destructive on systems with an alternative init system, as installing systemd package will likely remove your Desktop Environment (due to conflict with elogind). This was one of the reason for the existence of dh-sysuser at least at the beginning * opensysusers: in Debian only since 2020; i'm doing some QA maintainance on it to allow it's inclusion in Bullseye. Supposed to work fine with alternative init systems, possibly also with systemd although this setup is not tested (and not sure someone is interested in this) * dh-sysuser: alternative declarative interface to handle creation and removal of users; known to work both with systemd and alternative init systems. It's part of the runit infrastructure. * systemd-standalone-sysusers [ future package ] currently does not exists, not sure when it will, but has been discussed in TC list and some other bug too. Will work fine for alternative init systems. Not sure if it will work on BSD port, wich is relevant for runit As of my personal efforts: I plan to stop doing QA on opensysusers if the standalone package from systemd proves to works fine on all cases that I care (including BDS port). At that point someone else steps in for opensysusers or the package will end up removed (or limited to BDS port). I don't plan to drop dh-sysuser soon as I may need it for runit future development. More about dh-sysuser: > doing so? The approach taken here entirely sidesteps the established and > declarative sysusers.d format. Is there a reason for not cooperating > with it? Niels Thykier is working a lot on removing maintainer scripts > and turning them into declarative alternatives such as triggers. > dh-sysusers works towards the opposite. I don't see it that way, maybe I'm missing something? It's declarative and it parses a file in the source. It allows me to fix things uploading a new version of sysuser-helper, without the need to rebuild the affected package from source. It's probably able to handle many kind of transition without requiring coordination form others maintainers (I guess I will find out soon if it works as expected with the Merged-usr transition). Also (looking at the patch from #981799) I don't see a clear advantage of systemd-sysusers in simlpifying syntax of rules or other files in the /debian directory. One notable difference is that dh-sysuser parses on buildtime while systemd-sysusers parses on runtime, but for Debian I'm not sure what can be the advantage of one approach versus the other. I plan to keep this bug open for the next release cycle so there is time for people to highlight bug or other problems with this package. Regards, Lorenzo -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash
Bug#981918: dh-sysuser: Removes user on purge (against project consensus)
Package: dh-sysuser Version: 1.3.5 Severity: normal X-Debbugs-Cc: plore...@disroot.org Helmut Grohne in #981683 > Further development seems like a good idea. [...] > As far as I can tell,project consensus is that system users > should not be removed on purge, but dh-sysuser does so. Reminder for myself: Check users removal on purge (maybe makes sense to remove if home is set to nonexistent?) This will be dealt with after Bullseye release -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit) Versions of packages dh-sysuser depends on: ii perl 5.32.0-6 dh-sysuser recommends no packages. dh-sysuser suggests no packages. -- no debconf information
Bug#981917: dh-sysuser: Uses useradd instead of the policy-recommended adduser
Package: dh-sysuser Version: 1.3.5 Severity: normal X-Debbugs-Cc: plore...@disroot.org Helmut Grohne, from #981683 > Further development seems like a good idea. The package uses useradd > instead of the policy-recommended adduser. Is there a good reason for > doing so? Reminder for myself: Check why sysuser-helper uses useradd insted of adduser (might be because of syntax or some other reason, the choice was done by the former maintainer) This will be dealt with after Bullseye release -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit) Versions of packages dh-sysuser depends on: ii perl 5.32.0-6 dh-sysuser recommends no packages. dh-sysuser suggests no packages. -- no debconf information
Bug#981527: RFS: opentmpfiles/0.3.1-1 [QA] -- standalone utility written to process tmpfiles.d files
Package: sponsorship-requests Severity: normal X-Debbugs-Cc: plore...@disroot.org Dear mentors, I am looking for a sponsor for my package "opentmpfiles": * Package name: opentmpfiles Version : 0.3.1-1 Upstream Author : William Hubbs * URL : https://github.com/OpenRC/opentmpfiles * License : LGPL-2.1+, BSD-2-clause * Vcs : https://salsa.debian.org/debian/opentmpfiles Section : net It builds those binary packages: opentmpfiles - standalone utility written to process systemd-style tmpfiles.d files To access further information about this package, please visit the following URL: https://mentors.debian.net/package/opentmpfiles/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/o/opentmpfiles/opentmpfiles_0.3.1-1.dsc Git repo: https://salsa.debian.org/Lorenzo.ru.g-guest/opentmpfiles/-/tree/opentmpfiles-0.3.1-release Changes since the last upload: opentmpfiles (0.3.1-1) unstable; urgency=medium . * QA upload. * New upstream version 0.3.1 * Import and rename manpages from systemd-247 * Update copyright for systemd manpages Regards, -- Lorenzo Puliti
Bug#981143: RFS: opensysusers/0.6-2 [QA] -- processes sysusers.d directory to create system users
Package: sponsorship-requests Severity: normal X-Debbugs-Cc: plore...@disroot.org Dear mentors, I am looking for a sponsor for my package "opensysusers": * Package name: opensysusers Version : 0.6-2 Upstream Author : Chris Cromer * URL : https://github.com/artix-linux/opensysusers * License : LGPL-2.1+, BSD-2-clause * Vcs : https://salsa.debian.org/debian/opensysusers Section : net It builds those binary packages: opensysusers - processes sysusers.d directory to create system users To access further information about this package, please visit the following URL: https://mentors.debian.net/package/opensysusers/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/o/opensysusers/opensysusers_0.6-2.dsc Git repo: https://salsa.debian.org/Lorenzo.ru.g-guest/opensysusers/-/tree/release-0.6-2 Changes since the last upload: opensysusers (0.6-2) unstable; urgency=medium . * QA upload. * Rename and ship opensysusers manpages: changing name is necessary to avoid a conflict with systemd manpages Regards, -- Lorenzo Puliti
Bug#978638: RFS: dh-runit/2.10.3 -- debhelper add-on to handle runit runscripts
Package: sponsorship-requests Severity: normal X-Debbugs-Cc: plore...@disroot.org Dear mentors, I am looking for a sponsor for my package "dh-runit": * Package name: dh-runit Version : 2.10.3 Upstream Author : [fill in name and email of upstream] * URL : https://salsa.debian.org/debian/dh-runit * License : GPL-3+ * Vcs : https://salsa.debian.org/debian/dh-runit Section : admin It builds those binary packages: runit-helper - dh-runit implementation detail dh-runit - debhelper add-on to handle runit runscripts To access further information about this package, please visit the following URL: https://mentors.debian.net/package/dh-runit/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/d/dh-runit/dh-runit_2.10.3.dsc Git repo: https://salsa.debian.org/Lorenzo.ru.g-guest/dh-runit/-/tree/2.10.3-release Changes since the last upload: dh-runit (2.10.3) unstable; urgency=medium . * Always create supervise link for log service (Closes: #977925) * Add 2 testcase for supervise links * Bump out version to 2.10.3 * Bump Stadards-Version to 4.5.1 Regards, -- Lorenzo Puliti
Bug#977948: RFS: opensysusers/0.6-1 [QA] -- processes sysusers.d directory to create system users
Package: sponsorship-requests Severity: normal X-Debbugs-Cc: plore...@disroot.org Dear mentors, I am looking for a sponsor for my package "opensysusers": * Package name: opensysusers Version : 0.6-1 Upstream Author : Chris Cromer * URL : https://github.com/artix-linux/opensysusers * License : LGPL-2.1+, BSD-2-clause * Vcs : https://salsa.debian.org/debian/opensysusers Section : net It builds those binary packages: opensysusers - processes sysusers.d directory to create system users To access further information about this package, please visit the following URL: https://mentors.debian.net/package/opensysusers/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/o/opensysusers/opensysusers_0.6-1.dsc Git repo: https://salsa.debian.org/Lorenzo.ru.g-guest/opensysusers/-/tree/release-0.6-1 Changes since the last upload: opensysusers (0.6-1) unstable; urgency=medium . * QA upload. * Add a sysvinit script * Add a lintian override for missing systemd unit * New upstream version 0.6 * Set maintainer to QA Group (see #975378) * Bump debhelper-compat to 13 * Bump Standards-Version to 4.5.1 * d/clean: remove autogenereted manpages * Provide systemd-sysusers * Set Rules-requires-root to no * Enable the standard Salsa CI pipeline Regards, -- Lorenzo Puliti
Bug#977775: RFS: runit/2.1.2-39 -- system-wide service supervision
Package: sponsorship-requests Severity: normal X-Debbugs-Cc: plore...@disroot.org Dear mentors, I am looking for a sponsor for my package "runit": this version reintroduces an empty transitional runit-systemd package, as I haven't found a better solution for #976187 * Package name: runit Version : 2.1.2-39 Upstream Author : Gerrit Pape * URL : http://smarden.org/runit/ * License : BSD-3-clause * Vcs : https://salsa.debian.org/debian/runit Section : admin It builds those binary packages: runit-init - system-wide service supervision (as init system) getty-run - runscripts to supervise getty processes runit-systemd - transitional package for runit-systemd users runit-run - service supervision (systemd and sysv integration) runit - system-wide service supervision To access further information about this package, please visit the following URL: https://mentors.debian.net/package/runit/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/r/runit/runit_2.1.2-39.dsc Git repo: https://salsa.debian.org/Lorenzo.ru.g-guest/runit/-/tree/2.1.2-39-release Changes since the last upload: runit (2.1.2-39) unstable; urgency=medium . * Enable shutdown on ctrl-alt-del keyboard request * Bump Standards Version to 4.5.1 * Reintroduce transitional runit-systemd package (Closes: #976187) * Add a news file for runit-init Regards, -- Lorenzo Puliti
Bug#977242: RFS: fgetty/0.7-7 [QA] [RC] -- very small, efficient, console-only getty and login
Package: sponsorship-requests Severity: important X-Debbugs-Cc: plore...@disroot.org Dear mentors, I am looking for a sponsor for my package "fgetty": * Package name: fgetty Version : 0.7-7 Upstream Author : Felix von Leitner * URL : https://www.fefe.de/fgetty * License : GPL-2+ * Vcs : https://salsa.debian.org/debian/fgetty Section : admin It builds those binary packages: fgetty - very small, efficient, console-only getty and login To access further information about this package, please visit the following URL: https://mentors.debian.net/package/fgetty/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/f/fgetty/fgetty_0.7-7.dsc Updated git repo: https://salsa.debian.org/Lorenzo.ru.g-guest/fgetty/-/tree/qa-0.7-7 Changes since the last upload: fgetty (0.7-7) unstable; urgency=medium . * QA upload. . [ Francisco M Neto ] * Add minimal metadata file * Add two superficial autopkgtests * Bump DH version to 13 * Set Rules-Requires-Root to no * Fix spelling error in patch-link-checkpassword * Set maintainer to QA Group (see #947640) . [ Lorenzo Puliti ] * Bump SV to 4.5.1, no changes required * d/control: Add shlibs:Depends (Closes: #969063) + Thanks to Aurelien Jarno * Cleanup unused lintian overrides Regards, -- Lorenzo Puliti
Bug#976076: RFS: opentmpfiles/0.2+2019.05.21.git.44a55796ba-3 [QA] -- standalone systemd-tmpfiles utility
Package: sponsorship-requests Severity: normal X-Debbugs-Cc: plore...@disroot.org Dear mentors, I am looking for a sponsor for my package "opentmpfiles": * Package name: opentmpfiles Version : 0.2+2019.05.21.git.44a55796ba-3 Upstream Author : William Hubbs * URL : https://github.com/OpenRC/opentmpfiles * License : BSD-2-clause * Vcs : https://salsa.debian.org/debian/opentmpfiles Section : net It builds those binary packages: opentmpfiles - standalone utility written to process systemd-style tmpfiles.d files To access further information about this package, please visit the following URL: https://mentors.debian.net/package/opentmpfiles/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/o/opentmpfiles/opentmpfiles_0.2+2019.05.21.git.44a55796ba-3.dsc Git repo: https://salsa.debian.org/Lorenzo.ru.g-guest/opentmpfiles/-/tree/qa-next Changes since the last upload: opentmpfiles (0.2+2019.05.21.git.44a55796ba-3) unstable; urgency=medium . * QA upload. * Provide systemd-tmpfiles (Closes: #952897) * Bump Debhelper Compat to 13 - Disable openstack-pkg-tools ( see #976038) * Bump S-V to 4.5.1 * Set Maintainer to QA Group (see #975377) * Set Rules-requires-root to no Regards, -- Lorenzo Puliti
Bug#976038: openstack-pkg-tools: pkgos-make causes FTBFS when used in Dh-Compat 13 (due to dh_systemd_enable)
Package: openstack-pkg-tools Version: 116 Severity: important Tags: patch X-Debbugs-Cc: plore...@disroot.org Dear Maintainers, bumping the Dh_compat level to 13 of opentmpfiles causes FTBFS with the following $ dpkg-buildpackage -us -uc dpkg-buildpackage: info: source package opentmpfiles dpkg-buildpackage: info: source version 0.2+2019.05.21.git.44a55796ba-3 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Lorenzo Puliti dpkg-buildpackage: info: host architecture amd64 dpkg-source --before-build . fakeroot debian/rules clean pyversions: missing X(S)-Python-Version in control file, fall back to debian/pyversions pyversions: missing debian/pyversions file, fall back to supported versions py3versions: no X-Python3-Version in control file, using supported versions debian/rules:16: warning: overriding recipe for target 'override_dh_installinit' /usr/share/openstack-pkg-tools/pkgos.make:43: warning: ignoring old recipe for target 'override_dh_installinit' dh clean dh: warning: The target override_dh_systemd_enable references a now obsolete command and will not be run! dh: error: Aborting due to left over override/hook targets for now removed commands. make: *** [debian/rules:7: clean] Error 255 dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit status 2 dh_systemd_enable is discouraged and in dh compat 13 causes an error, this is documented in Debhelper manpage (section describing Compat level 13) "- The dh command will now error if an override or hook target for an obsolete command are present in debian/rules (e.g. override_dh_systemd_enable:)." The attached patch fix the issue for me but be aware that i'm building on a non standard system, I have a poor knowledge about systemd and its dh tools, and I have not serched for other occurrencies of dh_systemd_enable in this package, so it could be wise to seek help from the systemd team before applying the patch Best Regards, Lorenzo -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit) Versions of packages openstack-pkg-tools depends on: ii gettext 0.19.8.1-10 ii jq 1.6-1 ii po-debconf 1.0.21 ii python3-pip 20.1.1-2 Versions of packages openstack-pkg-tools recommends: ii autopkgtest 5.15 ii madison-lite 0.26 ii pristine-tar 1.49 openstack-pkg-tools suggests no packages. -- no debconf information -- debsums errors found: debsums: changed file /usr/share/openstack-pkg-tools/pkgos.make (from openstack-pkg-tools package) --- pkgos.make.now 2020-11-15 22:59:21.0 +0100 +++ pkgos.make.patched 2020-11-28 16:23:29.562425427 +0100 @@ -36,8 +36,8 @@ fi \ done -override_dh_systemd_enable: gen-init-configurations - dh_systemd_enable +override_dh_installsystemd: gen-init-configurations + dh_installsystemd override_dh_installinit: gen-init-configurations dh_installinit --error-handler=true
Bug#972671: RFS: runit/2.1.2-38 [RC] -- system-wide service supervision
Package: sponsorship-requests Followup-For: Bug #972671 X-Debbugs-Cc: plore...@disroot.org Just re-uploaded the package with the following changes * drop commit that bumped B-D on dh-sysuser, was really unnecessary * add commit to not restart the gettys: a restart can break an ongoing upgrade ( this is needed since dh-runit 2.10.2 has landed in unstable/testing) * suggests socklog below the updated template Dear mentors, I am looking for a sponsor for my package "runit": * Package name: runit Version : 2.1.2-38 Upstream Author : Gerrit Pape * URL : http://smarden.org/runit/ * License : BSD-3-clause * Vcs : https://salsa.debian.org/debian/runit Section : admin It builds those binary packages: runit-init - system-wide service supervision (as init system) getty-run - runscripts to supervise getty processes runit-run - service supervision (systemd and sysv integration) runit - system-wide service supervision To access further information about this package, please visit the following URL: https://mentors.debian.net/package/runit/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/r/runit/runit_2.1.2-38.dsc updated git repo: https://salsa.debian.org/Lorenzo.ru.g-guest/runit/-/tree/2.1.2-38-release Changes since the last upload: runit (2.1.2-38) unstable; urgency=medium . * Clean up at the end of the forced-rescan-test * Fix some minor lintian tag * Bump dh compat level to 13 * d/rules: fix broken autopkgtest phony target * d/runit.NEWS: document recent changes * Do not restart the gettys on upgrade * Suggests socklog with runit * Release to unstable Regards, -- Lorenzo Puliti
Bug#974887: RFS: dh-runit/2.10.2 -- debhelper add-on to handle runit runscripts
Package: sponsorship-requests Severity: normal X-Debbugs-Cc: plore...@disroot.org Dear mentors, I am looking for a sponsor for my package "dh-runit": * Package name: dh-runit Version : 2.10.2 Upstream Author : [fill in name and email of upstream] * URL : https://salsa.debian.org/debian/dh-runit * License : GPL-3+ * Vcs : https://salsa.debian.org/debian/dh-runit Section : admin It builds those binary packages: runit-helper - dh-runit implementation detail dh-runit - debhelper add-on to handle runit runscripts To access further information about this package, please visit the following URL: https://mentors.debian.net/package/dh-runit/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/d/dh-runit/dh-runit_2.10.2.dsc Git repo: https://salsa.debian.org/Lorenzo.ru.g-guest/dh-runit/-/tree/2.10.2-release Changes since the last upload: dh-runit (2.10.2) unstable; urgency=medium . * Don't run shake autopkgtest on armhf and armel (Closes: #973337) * Allow outptut to stderr for update-rc.d test Regards, -- Lorenzo Puliti
Bug#973337: dh-runit: autopkgtest-virt-lxc failure on armhf and armel
Source: dh-runit Followup-For: Bug #973337 X-Debbugs-Cc: plore...@disroot.org Control: found -1 2.10.0 Hello, sorry for the late response. There are outstanding issues with ghc and arm architectures, see #954190 for example. For now, the only thing that i can do form dh-runit side is to properly declare the autopkgtest non compatible with armel and armhf, so that it will be auto skipped :/ Regards, Lorenzo
Bug#972685: needrestart: Please add support for runit
Package: needrestart
Version: 3.5-1
Followup-For: Bug #972685
On 10/22/20 8:16 PM, Thomas Liske wrote:
> Hi,
>
> thanks for the patch. Would it possible that you provide a updated patch
> compatible with upstream's git HEAD?
>
Hi,
You should be able to git am the patch attached to this message.
Note that i've used 'service' instead of invoke-run, to be consistent
with upstream code, so this will need further work on Debian side,
updating and refreshing the quilt '01-use-invoke-rc.d.diff' patch.
Regards,
Lorenzo
>From 6a7ae3df50ab24c833db3c1ba2d771688347097e Mon Sep 17 00:00:00 2001
From: Lorenzo Puliti
Date: Fri, 23 Oct 2020 10:46:55 +0200
Subject: [PATCH] Add support for runit
When runit is used as init system, a native runscript exists
and is enabled, use 'sv' instead of 'service'.
If no native runscript exists (or is disabled) we fallback on 'service'
---
needrestart | 9 +
1 file changed, 9 insertions(+)
diff --git a/needrestart b/needrestart
index d5c94fd..7d70633 100755
--- a/needrestart
+++ b/needrestart
@@ -46,6 +46,7 @@ $Getopt::Std::STANDARD_HELP_VERSION++;
my $LOGPREF = '[main]';
my $is_systemd = -d q(/run/systemd/system);
+my $is_runit = -e q(/run/runit.stopit);
my $is_tty = (-t *STDERR || -t *STDOUT || -t *STDIN);
my $is_vm;
my $is_container;
@@ -386,6 +387,14 @@ sub restart_cmd($) {
(qw(systemctl restart), qq($rc.service));
}
}
+ elsif($is_runit && -d qq(/etc/sv/$rc)) {
+ if(-e qq(/etc/service/$rc)) {
+ (qw(sv restart), $rc);
+ }
+ else {
+ (q(service), $rc, q(restart));
+ }
+ }
else {
(q(service), $rc, q(restart));
}
--
2.28.0
Bug#972685: needrestart: Please add support for runit
Package: needrestart
Version: 3.5-1
Severity: normal
Tags: patch
Dear maintainer,
Please consider the attached patch that adds support for runit to needrestart.
Runit is a very lightweight init scheme with service supervision capability;
for more details see http://smarden.org/runit/
Regards,
Lorenzo Puliti
-- Package-specific info:
needrestart output:
Your outdated processes:
kactivitymanage[23935], kdeconnectd[22453], kded5[6680], kdeinit5[6696],
kglobalaccel5[23942], klauncher[6697], konqueror[6620], kuiserver[22496],
lxqt-notificati[5553], lxqt-panel[5557], lxqt-policykit-[5558],
lxqt-powermanag[8009], lxqt-runner[5559], lxqt-session[5460], openbox[5530],
qjackctl[8006], qterminal[8833, 5222], QtWebEngineProc[9293, 6647],
superkaramba[8014]
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: runit (via /run/runit.stopit)
Versions of packages needrestart depends on:
ii binutils 2.35.1-2
ii dpkg 1.20.5
ii gettext-base 0.19.8.1-10
ii libintl-perl 1.26-2
ii libmodule-find-perl0.15-1
ii libmodule-scandeps-perl1.29-1
ii libproc-processtable-perl 0.59-2
ii libsort-naturally-perl 1.03-2
ii libterm-readkey-perl 2.38-1+b1
ii perl 5.30.3-4
ii xz-utils 5.2.4-1+b1
Versions of packages needrestart recommends:
ii libpam-elogind-compat [libpam-systemd] 1.2
Versions of packages needrestart suggests:
ii iucode-tool 2.3.1-1
pn needrestart-session | libnotify-bin
-- no debconf information
-- debsums errors found:
debsums: changed file /usr/sbin/needrestart (from needrestart package)
Description: Add support for runit init system
When runit is used as init system, a native runit service exists and is
enabled,
use sv instead of invoke-rc.d. If no native service exists (or is disabled)
fallback
on invoke-rc.d
Author: Lorenzo Puliti
Last-Update: 2020-10-22
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/needrestart
+++ b/needrestart
@@ -46,6 +46,7 @@
my $LOGPREF = '[main]';
my $is_systemd = -d q(/run/systemd/system);
+my $is_runit = -e q(/run/runit.stopit);
my $is_tty = (-t *STDERR || -t *STDOUT || -t *STDIN);
my $is_vm;
my $is_container;
@@ -386,6 +387,14 @@
(qw(systemctl restart), qq($rc.service));
}
}
+ elsif($is_runit && -d qq(/etc/sv/$rc)) {
+ if(-e qq(/etc/service/$rc)) {
+ (qw(sv restart), $rc);
+ }
+ else {
+ (q(invoke-rc.d), $rc, q(restart));
+ }
+ }
else {
(q(invoke-rc.d), $rc, q(restart));
}
Bug#972671: RFS: runit/2.1.2-38 [RC] -- system-wide service supervision
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "runit": [RC]: i need this upload to deal with #953875 in unstable/testing * Package name: runit Version : 2.1.2-38 Upstream Author : Gerrit Pape * URL : http://smarden.org/runit/ * License : BSD-3-clause * Vcs : https://salsa.debian.org/debian/runit Section : admin It builds those binary packages: runit-init - system-wide service supervision (as init system) getty-run - runscripts to supervise getty processes runit-run - service supervision (systemd and sysv integration) runit - system-wide service supervision To access further information about this package, please visit the following URL: https://mentors.debian.net/package/runit/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/r/runit/runit_2.1.2-38.dsc Updated git repo: https://salsa.debian.org/Lorenzo.ru.g-guest/runit/-/tree/2.1.2-38-release Changes since the last upload: runit (2.1.2-38) unstable; urgency=medium . * Clean up at the end of the forced-rescan-test * Fix some minor lintian tag * Bump build-dep on dh-sysuser (>= 1.3.5) * Bump dh compat level to 13 * d/rules: fix broken autopkgtest phony target * d/runit.NEWS: document recent changes * Release to unstable Regards, -- Lorenzo Puliti
Bug#972407: RFS: mini-httpd/1.30-3 [QA] -- Small HTTP server
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "mini-httpd": * Package name: mini-httpd Version : 1.30-3 Upstream Author : [fill in name and email of upstream] * URL : https://www.acme.com/software/mini_httpd * License : BSD-2-clause * Vcs : https://salsa.debian.org/debian/mini-httpd Section : web It builds those binary packages: mini-httpd - Small HTTP server To access further information about this package, please visit the following URL: https://mentors.debian.net/package/mini-httpd/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/m/mini-httpd/mini-httpd_1.30-3.dsc Updated git repo: https://salsa.debian.org/Lorenzo.ru.g-guest/mini-httpd/-/tree/qa-1.30-3 Changes since the last upload: mini-httpd (1.30-3) unstable; urgency=medium . [ Lorenzo Puliti ] * QA upload. * Fix lintian error 'init-d script not starting the service': the service is now shipped as disabled with Sysv * Warn users of changes in /etc/default/mini-httpd with a NEWS file * Set rules-requires-root to 'binary-targets' * Add an experimental systemd native service: - do not start the service after install - run in foreground - use the conf file in /etc/ for other options - Same start sequence of other httpds (Apache2, Nginx..) * Bump Standards-Version to 4.5, no chages required * Bump dh-compat version to 13 * Merge the runscript from 'mini-httpd-run' package: - Add a Build-Dep on dh-runit>=2.9.0 - ship the runit service as disabled - Breaks and Replaces with 'mini-httpd-run' - ship a presubj file to easy work of QA * Update runit runscript: - use the 'invoke-run' interpreter - ship a default finish file - use the conf file in /etc instead of command line options (note that this way the server no longer run inside a chroot) * Sysv: add the syslog facility to LSB header: this is needed because the Sysv script logs to syslog by default . [ Jean ] * Update init.d script LSB Header with $network: otherwise mini-httpd starts too early during the boot sequence Regards, -- Lorenzo Puliti
Bug#971847: RFS: dh-runit/2.10.1 -- debhelper add-on to handle runit runscripts
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "dh-runit": * Package name: dh-runit Version : 2.10.1 Upstream Author : [fill in name and email of upstream] * URL : https://salsa.debian.org/debian/dh-runit * License : GPL-3+ * Vcs : https://salsa.debian.org/debian/dh-runit Section : admin It builds those binary packages: runit-helper - dh-runit implementation detail dh-runit - debhelper add-on to handle runit runscripts To access further information about this package, please visit the following URL: https://mentors.debian.net/package/dh-runit/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/d/dh-runit/dh-runit_2.10.1.dsc Git repository https://salsa.debian.org/Lorenzo.ru.g-guest/dh-runit/-/tree/2.10.1-release Changes since the last upload: dh-runit (2.10.1) unstable; urgency=medium . * Add autopkgtest for runit-helper (update-rc.d) (Closes: #969512) * Update dh-runit package description * Bump our version to 2.10.1 * Error on wrong or unknown onupgrade string * Bump debhelper compat to 13 * Use d/clean instead of override in d/rules * Runit-helper: use explicit 0 exit status for return * Release to unstable Regards, -- Lorenzo Puliti
Bug#971337: RFS: dh-sysuser/1.3.5 [ITA] -- debhelper addon to handle creation of system users
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "dh-sysuser": * Package name: dh-sysuser Version : 1.3.5 Upstream Author : [fill in name and email of upstream] * URL : https://salsa.debian.org/debian/dh-sysuser * License : GPL-3+ * Vcs : https://salsa.debian.org/debian/dh-sysuser Section : admin It builds those binary packages: sysuser-helper - dh-sysuser implementation detail dh-sysuser - debhelper addon to handle creation of system users To access further information about this package, please visit the following URL: https://mentors.debian.net/package/dh-sysuser/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/d/dh-sysuser/dh-sysuser_1.3.5.dsc updated git: https://salsa.debian.org/Lorenzo.ru.g-guest/dh-sysuser/-/commits/1.3.5-release/ Changes since the last upload: dh-sysuser (1.3.5) unstable; urgency=medium . [ Lorenzo Puliti ] * Do not pollute namespace in maintscript * Do not impose unneeded dependency on sysuser-helper * Bump Standards-Versions to 4.5.0: - Add Rules-Requires-Root: no * Update copyright file * Adopt the package * Release to unstable . [ Chris Lamb ] * Tidy the grammar (etc.) of the dh_sysuser(1) manpage. Regards, -- Lorenzo Puliti
Bug#969562: "QA upload; overall maintenance of the packaging, and fixing
Package: fgetty Version: 0.7-6+b1 Followup-For: Bug #969562 X-Debbugs-Cc: fmn...@gmail.com Hi Francisco, > Tags: patch if you add this tag you need to provide a patch.. are you building from [1]? > This is a non-maintainer upload. > > I did some housekeeping in the packaging, updated the Maintainer to Debian QA > Group (package has been orphaned) and fixed Bug #969063. This package is marked for autoremoval and will be removed in a week from now: please file a proper RFS bug on debian-mentors list. Best Regards, Lorenzo [1] https://salsa.debian.org/fmneto-guest/fgetty/-/tree/debian/master/debian -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit) -- no debconf information
Bug#960940: RFS: runit/2.1.2-37 [RC] -- system-wide service supervision
Package: sponsorship-requests Followup-For: Bug #960940 Dear mentors, I'm still looking for a sponsor and I've uploaded again with the following changes: * autopkgtest on #953875 (unwanted init switch) marked as superficial * Change the name of the special rundirectory to run selected service in container: renamend from 'isolation' to 'solo' (to avoid confusion with docker isolation feature) * New runit-run package: do not restart the systemd service on upgrade. Restarting the whole supervision tree can be dangerous if certain services that do not support runtime restart are supervised (think dbus or any display manager) (this issue is unreported on BTS for now and affects runit-systemd package) * New runit-run package: use 'telinit q' to start the supervision tree after install and to stop it after removal, when running under sysvinit. The current (somehow buggy) behaviour with runit-sysv package is that changes in /etc/inittab are effective only after a system reboot. Full datail below * Package name: runit Version : 2.1.2-37 Upstream Author : Gerrit Pape * URL : http://smarden.org/runit/ * License : BSD-3-clause * Vcs : https://salsa.debian.org/debian/runit Section : admin It builds those binary packages: runit - system-wide service supervision runit-run - service supervision (systemd and sysv integration) getty-run - runscripts to supervise getty processes runit-init - system-wide service supervision (as init system) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/runit/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/r/runit/runit_2.1.2-37.dsc updated git repo: https://salsa.debian.org/Lorenzo.ru.g-guest/runit/-/tree/release-2.1.2-37 Changes since the last upload: runit (2.1.2-37) experimental; urgency=medium . * Bring back the test about forced-rescan * Fix forced rescan test failure on sbuild (Closes: #941322) * Clean the 'current' symlink on purge * Invoke-run: add a DEBUG option to finish-default * Finish-default: print invoke-run instead of runsv * Get non default rundirectory from kernel command line * Add a 'solo' rundirectory for containers (Closes: #950851) * Merge runit-sysv and runit-systemd into runit-run (Closes: #953875) * Add lintian overrides for manpage without executable * Update copyright for debian files * Add an autopkgtest to catch regression on #953875 * runit-run: don't stop the service on upgrade (systemd) * runit-run: rescan inittab on install/remove (sysvinit) Regards, -- Lorenzo Puliti
Bug#970262: virtualbox-source: fail to install modules ( unsigned kernel )
Package: virtualbox-source Version: 6.1.14-dfsg-3 Severity: normal Tags: patch Hello, after successfully building with m-a, the modules package fails to install because i'm running on 'linux-image-5.7.0-1-amd64-unsigned' but the dependency only takes into account signed kernels. # m-a install virtualbox-source Selecting previously unselected package virtualbox-modules-5.7.0-1-amd64. (Reading database ... 617609 files and directories currently installed.) Preparing to unpack .../virtualbox-modules-5.7.0-1-amd64_6.1.12-dfsg-9+5.7.6-1_amd64.deb ... Unpacking virtualbox-modules-5.7.0-1-amd64 (6.1.12-dfsg-9+5.7.6-1) ... dpkg: dependency problems prevent configuration of virtualbox-modules-5.7.0-1-amd64: virtualbox-modules-5.7.0-1-amd64 depends on linux-modules-5.7.0-1-amd64 | linux-image-5.7.0-1-amd64; however: Package linux-modules-5.7.0-1-amd64 is not installed. Package linux-image-5.7.0-1-amd64 is not installed. dpkg: error processing package virtualbox-modules-5.7.0-1-amd64 (--install): dependency problems - leaving unconfigured Errors were encountered while processing: virtualbox-modules-5.7.0-1-amd64 I: Direct installation failed, trying to post-install the dependencies Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following package was automatically installed and is no longer required: libpoppler95 Use 'apt autoremove' to remove it. The following packages will be REMOVED: virtualbox-modules-5.7.0-1-amd64 0 upgraded, 0 newly installed, 1 to remove and 18 not upgraded. 1 not fully installed or removed. After this operation, 17.6 MB disk space will be freed. Do you want to continue? [Y/n] y changing the line in /modules/virtualbox/debian/control.modules.in from Depends: linux-modules-_KVERS_ | linux-image-_KVERS_ to Depends: linux-modules-_KVERS_ | linux-image-_KVERS_ | linux-image-_KVERS_-unsigned works for me. Thanks, Lorenzo -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit) Versions of packages virtualbox-source depends on: ii build-essential 12.8 ii bzip2 1.0.8-4 ii debhelper [debhelper-compat] 13.2.1 ii kbuild1:0.1.9998svn3301+dfsg-1 ii module-assistant 0.11.10 Versions of packages virtualbox-source recommends: ii virtualbox 6.1.14-dfsg-3 virtualbox-source suggests no packages. -- no debconf information -- debsums errors found: debsums: changed file /usr/src/virtualbox.tar.bz2 (from virtualbox-source package)
Bug#969924: RFS: dh-runit/2.10.0 -- debhelper add-on to handle runit runscripts
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "dh-runit": This version adds support for invoke-rc.d actions, especially whether or not to restart a service during upgrade. It may also help with #924132 * Package name: dh-runit Version : 2.10.0 Upstream Author : Lorenzo Puliti * URL : https://salsa.debian.org/debian/dh-runit * License : GPL-3+ * Vcs : https://salsa.debian.org/debian/dh-runit Section : admin It builds those binary packages: runit-helper - dh-runit implementation detail dh-runit - debhelper add-on to handle runit runscripts To access further information about this package, please visit the following URL: https://mentors.debian.net/package/dh-runit/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/d/dh-runit/dh-runit_2.10.0.dsc Updated git repo: https://salsa.debian.org/Lorenzo.ru.g-guest/dh-runit/-/tree/2.10.0-release Changes since the last upload: dh-runit (2.10.0) experimental; urgency=medium . * Add invoke-rc.d actions support into dh-runit (Closes: #969511) * Deprecate the noreplace option, coupled with onupgrade=nostop * Add onupgrade=reload * Bump our version to 2.10.0 * Don't call sv if is runit is not installed (Closes: #968114) Regards, -- Lorenzo Puliti
Bug#968114: /lib/runit-helper/runit-helper: 74: sv: not found
Package: runit-helper Version: 2.9.0 Followup-For: Bug #968114 Control: tag -1 confirmed Control: tag -1 patch Christoph, thank you for reporting this > | /lib/runit-helper/runit-helper: 74: sv: not found > ... > It looks the sv program is shipped in the runit package which is not > installed here, hence the above error message. Also, since the Yes, while focused on fixing a transition with runit i forgot to think about this super obvious case. > /lib/runit-helper/runit-helper program lacks the "set -e" setting - The program is already 'set -e' but there are a couple of lines that ends with '|| true' and i'm afraid i still need to do that for now. patch available on salsa, see https://salsa.debian.org/Lorenzo.ru.g-guest/dh-runit/-/commit/a141af7e6bbd3068ad4e239f049c332620fbce30 Regards, Lorenzo -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit) -- no debconf information -- debsums errors found: debsums: changed file /lib/runit-helper/runit-helper (from runit-helper package)
Bug#969514: runit-helper: Remove transition code after Bullseye
Package: runit-helper Version: 2.9.0 Severity: minor Several blocks of runit-helper's code are just transition code that sooner or later can be removed. to be on the super-safe side we can wait up to Bookworm release, but Bullseye should be safe too. Reminder: * Loguser transition * Moving supervise from /var/* to /run/* -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit) -- no debconf information -- debsums errors found: debsums: changed file /lib/runit-helper/runit-helper (from runit-helper package)
Bug#969513: src:dh-runit: Reenable the testsuite on armhf
Package: src:dh-runit Version: 2.9.0 Severity: normal The testsuite is disabled on armhf, see #954190 Do not forget to test if the problem is fixed and reenable the testsuite on armhf -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit)
Bug#969512: src:dh-runit: Add autopkgtest for runit-helper
Package: src:dh-runit Version: 2.9.0 Severity: wishlist The package has already an autopkgtest that checks dh-runit when it is used to build a package, but it miss a test for runit-helper. Runit-helper is called during packages install/remove/upgrade and an issue there can cause a break on systems even when runit is not installed. See #968114 for an example of a mild issue caused by runit-helper. It would be nice to have a test that prevents at least catastrophic breakages. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit)
Bug#969511: dh-runit: Add invoke-rc.d actions support
Package: dh-runit Version: 2.9.0 Severity: normal After a long discussion [1][2] with init-system-helper's maintainers it looks like it's a good idea to decouple runit support from invoke-rc.d and update-rc.d. Dh-runit already has support for enabling and disabling services, but it lacks support for sending signals (start stop restart and so on) to supervised services. In runit, when a service is enabled is also started (and is stopped when disabled), so the missing part is 'what to do during the upgrade' of a service. Options supported by dh_installinit and dh_systemd are: 1. restart during postinstall (the default) 2. stop during prerm and start in postinst (the old default) 3. do not restart the service at all (useful for dbus sddm and the like) [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924132 [2] https://salsa.debian.org/debian/init-system-helpers/-/merge_requests/10 -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit) Versions of packages dh-runit depends on: ii debhelper13.2 ii libfile-copy-recursive-perl 0.45-1 ii libfile-slurp-perl .32-1 ii libtext-hogan-perl 2.03-1 dh-runit recommends no packages. dh-runit suggests no packages. -- no debconf information
Bug#964928: RFS: dh-runit/2.9.0 [RC] -- debhelper add-on to handle runit runscripts
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "dh-runit" * Package name: dh-runit Version : 2.9.0 Upstream Author : Dmitry Bogatov, Lorenzo Puliti * URL : https://salsa.debian.org/debian/dh-runit * License : GPL-3+ * Vcs : https://salsa.debian.org/debian/dh-runit Section : admin It builds those binary packages: dh-runit - debhelper add-on to handle runit runscripts runit-helper - dh-runit implementation detail To access further information about this package, please visit the following URL: https://mentors.debian.net/package/dh-runit Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/d/dh-runit/dh-runit_2.9.0.dsc Updated git repository: https://salsa.debian.org/Lorenzo.ru.g-guest/dh-runit/-/tree/release-2.9.0 Changes since the last upload: * Add a comment on Conflicts and Breaks runit 2.1.2-36 * Deprecate the 'since' option, bump depends on runit-helper * d/rules: clean testsuite artifacts * Disable the testsuite on armhf to workaroud FTBFS (Closes: #954190) * Acknowledge Helmut Grohne for fixing #939631 * d/control: set Rules-Requires-Root: no * d/copyright: update copyright * Fix logservice failure due to loguser transition (Closes: #964175) * Avoid infinte loop of symlinks (Closes: #964174) * Print version in maintscript snippets * Do not overwrite the presubj file (Closes: #964178) Some explanation that maybe can help people reviewing this package: This is mainly a bugfix release: [3f619215e51c8 ..] The minor version bump is because the 'since' option is deprecated, I should have done that in the 2.8.15 upload but I failed to realize that the patch for #942323 makes the since option useless. With this commit when the option is used dh-runit does nothing but prints a warning. [ed9cf32f1b9e ..] the testsuite fails but only on armhf architecture. I think this is an issue in libghc-shake so i'm disabling the tests on armhf for now. I'm using the DEB_HOST_ARCH=armhf for this, i'm not sure if it's better to use the DEB_BUILD_ARCH instead [6dedbf79ab4b86 ..] runit uses the '_runit-log' user for logging a service stdout: previously was the 'runit-log' user. This change in runit (2.1.2-36) breaks the appendant log service. Currently openssh-server and tor are already affected by this, a few other services will suffer the same issue as they will be rebuild with dh-runit in Sid. this commit provides some transition code in 'runit-helper'; the code make sure to change the ownership of 'lock' and 'current' files in the log directory [cf9322698bc46f ..] dh-runit has an option to ship a presubj file. It looks like if the package ships it's own presubj, this option overwrites the presubj file from the package with dh-runit presubj. This commit turn the presubj option into a noop if there's already a presubj file and prints a warning. It's possible to change this commit and make dh-runit append its presubj file content to the package presubj, but i'm not sure about the result (merging two presubj with potentially unrelated content, and the layout is of some concern too) Regards, -- Lorenzo Puliti -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit)
Bug#952897: opentmpfiles: Please make opentmpfiles to be drop-in replacement to systemd-tmpfiles
Package: opentmpfiles Followup-For: Bug #952897 Control: tag -1 patch Hi, the following MR on Salsa might fix this bug https://salsa.debian.org/debian/opentmpfiles/-/merge_requests/2 Best Regards, Lorenzo
Bug#953875: runit - default installation can force init switch
Package: runit Version: 2.1.2-36 Followup-For: Bug #953875 Control: tag -1 patch There is an open RFS bug (#960940) on mentors that fixes this bug. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960940 Lorenzo -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit) Versions of packages runit depends on: ii libc6 2.30-8 ii sysuser-helper 1.3.3 Versions of packages runit recommends: ii runit-init 2.1.2-36 runit suggests no packages. -- Configuration Files: /etc/default/runit changed [not included] -- no debconf information
Bug#964178: dh-runit: overwrites presubj file from package when the presubj option is used
Package: dh-runit
Version: 2.8.15
Severity: normal
Tags: patch
It looks that when the 'presubj' option is set and the package ships it's own
presubj file (using package.bug-presubj), dh-runit completely overwrites the
presubj
file from the package.
Thanks to Colin Watson for spotting this.
A quick fix can be to turn the presubj option into a noop if a presubj file is
detected,
see the patch
---
dh_runit | 11 ---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/dh_runit b/dh_runit
index 6d778ca..dfc0ecf 100755
--- a/dh_runit
+++ b/dh_runit
@@ -155,9 +155,14 @@ PKG: foreach my $pkg (@{$dh{DOPACKAGES}}) {
}
if ($conf->{presubj}) {
-template_from_data_directory('presubj',
"$tmp/usr/share/bug/$pkg/presubj",
- { pkg => $pkg }, 0644);
-}
+if ( -e "debian/$pkg.bug-presubj") {
+ warning("presubj for $pkg already exists and takes precedence,
runit presubj file not installed")
+}
+ else {
+ template_from_data_directory('presubj',
"$tmp/usr/share/bug/$pkg/presubj",
+ { pkg => $pkg }, 0644);
+ }
+ }
}
# runit=2.1.2-20 introduced 'runit-log' user
# runit=2.1.2-23 introduced /lib/runit/invoke-run
--
2.27.0
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: runit (via /run/runit.stopit)
Versions of packages dh-runit depends on:
ii debhelper13.1
ii libfile-copy-recursive-perl 0.45-1
ii libfile-slurp-perl .30-1
ii libtext-hogan-perl 2.01-1
dh-runit recommends no packages.
dh-runit suggests no packages.
-- no debconf information
Bug#964174: runit-helper: Create an infinite loop of symlink when enable a service
Package: runit-helper
Version: 2.8.15
Severity: normal
Tags: patch
The following code
if [ "${ENABLE}" = yes ] && \
[ ! -h "/etc/runit/runsvdir/default/.$NAME" ] ; then
ln -sf "/etc/sv/$NAME"
"/etc/runit/runsvdir/default/$NAME"
creates a loop of symlinks if the symlink already exists.
The runit service remains functional but the loop prevents the removal of
the service directory (not empty) on purge.
Affects each package that uses dh-runit.
diff --git a/runit-helper b/runit-helper
index 70596ce..7b92efe 100755
--- a/runit-helper
+++ b/runit-helper
@@ -40,7 +40,10 @@ postinst () {
# decision (see #899242 and 942323 ).
if [ "${ENABLE}" = yes ] && \
[ ! -h "/etc/runit/runsvdir/default/.$NAME" ] ; then
- ln -sf "/etc/sv/$NAME" "/etc/runit/runsvdir/default/$NAME"
+ # avoid infinte loop of symlinks
+ if [ ! -h "/etc/runit/runsvdir/default/$NAME" ]; then
+ ln -sf "/etc/sv/$NAME"
"/etc/runit/runsvdir/default/$NAME"
+ fi
fi
# ENABLE=no is always a no-op
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: runit (via /run/runit.stopit)
-- no debconf information
Bug#964175: dh-runit: Change in runit loguser need transition code
Package: dh-runit
Version: 2.8.15
Severity: important
Tags: patch
Runit recently changed the loguser from runit-log to _runit-log; dh-runit
now ships a logservice that uses the new loguser, but the appendant log
service will fail to start if the 'current' and 'lock' files inside the
logservice
directory are owned by the old 'runit-log' user.
the following patch should fix the issue
---
dh_runit | 3 ++-
runit-helper | 22 ++
2 files changed, 24 insertions(+), 1 deletion(-)
diff --git a/dh_runit b/dh_runit
index b41ad37..1c49ec6 100755
--- a/dh_runit
+++ b/dh_runit
@@ -161,9 +161,10 @@ PKG: foreach my $pkg (@{$dh{DOPACKAGES}}) {
# runit=2.1.2-23 introduced /lib/runit/invoke-run
# runit=2.1.2-36 introduced '_runit-log' user
# runit-helper 2.8.15 use dotlinks to mark a service as disabled, 'since'
option is deprecated
+# runit-helper 2.9.0 has code for loguser transition
addsubstvar($pkg, 'runit:Conflicts', 'runit', '<< 2.1.2-36~');
addsubstvar($pkg, 'runit:Breaks', 'runit', '<< 2.1.2-36~');
-addsubstvar($pkg, 'misc:Depends', 'runit-helper', '>= 2.8.15~');
+addsubstvar($pkg, 'misc:Depends', 'runit-helper', '>= 2.9.0~');
}
# PROMISE: DH NOOP WITHOUT runit
diff --git a/runit-helper b/runit-helper
index 1a5a1f2..70596ce 100755
--- a/runit-helper
+++ b/runit-helper
@@ -21,6 +21,21 @@ set -e
postinst () {
local action="${1}" previous="${2:-}"
+ # loguser transition: to be removed when the transition is done
+ # we do ths before enable to avoid races
+ # old loguser is 'runit-log', new is '_runit-log'
+ # 'current' and 'lock' files in the run directory must be owned by
+ # the new loguser
+ if [ "${ENABLE}" = yes ] && \
+ [ -f "/var/log/runit/$NAME/current" ] ; then
+ loguser="$(stat --format '%U' /var/log/runit/$NAME/current)"
+ if [ "${loguser}" = "runit-log" ]; then
+ sv d "/etc/sv/$NAME/log" >/dev/null || true
+ chown _runit-log:adm /var/log/runit/$NAME/current
+ chown _runit-log:adm /var/log/runit/$NAME/lock
+ fi
+ fi
+
# It is important to not override local admin
# decision (see #899242 and 942323 ).
if [ "${ENABLE}" = yes ] && \
@@ -48,6 +63,13 @@ postinst () {
if [ -d "${old}" ] ; then
ln -sf "${old}" "${new}"
fi
+
+ # loguser transition: to be removed when the transition is done
+ # we do this after enable to reduce chance of races
+ if [ "${ENABLE}" = yes ] && \
+ [ -f "/etc/sv/$NAME/log/run" ] ; then
+ sv u "/etc/sv/$NAME/log" >/dev/null || true
+ fi
}
postrm () {
--
2.27.0
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: runit (via /run/runit.stopit)
Versions of packages dh-runit depends on:
ii debhelper13.1
ii libfile-copy-recursive-perl 0.45-1
ii libfile-slurp-perl .30-1
ii libtext-hogan-perl 2.01-1
dh-runit recommends no packages.
dh-runit suggests no packages.
-- no debconf information
Bug#954190: dh-runit: FTBFS on armhf due to shake testsuite failure
Package: src:dh-runit Followup-For: Bug #954190 This is probably a bug in libghc-shake-dev, for example the changelog of haskell-shake that says ' * Disable testsuite on armhf, fails on Ubuntu builders, probably due to a misalignment bug due to 64bit kernel. ' -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit)
Bug#960940: RFS: runit/2.1.2-37 [RC] -- system-wide service supervision
Package: sponsorship-requests Followup-For: Bug #960940 On 5/19/20 12:12 AM, David Kalnischkies wrote: > Hi, > > Disclaimer: Not sponsoring as I am oblivious to init systems of all > kinds, so I don't feel confident reviewing changes in that area. > > (I am not stalking you – I promise! – I just couldn't let that > opportunity pass by after pushing another set of apt resolver changes > triggered by your packages :P) Thanks you for your review and also for the quick response to bug reports that I have made on apt :) After your review, I've made the following changes; * versioned Breaks+Replaces * upload to experimental instead of unstable * runit-run.postinst: add a newline before inserting the text avoid code duplication * runit-run.postrm: remove newline at the end of the inittab file, but only if more than one is detected > Also, but that is bike shed material: "-run" ? > I don't have a good suggestion, but I think for the uninitiated > -run and -init will be indistinguishable (also: run-it-run, init!). I haven't addressed this: the "-run" suffix is common for runit related packages (and also runit users) and it's used to mark a tiny config package that ships a runit service, for example - getty-run --> runit service for getty - git-daemon-run --> runit service for git daemon - mini-httpd-run --> runit service for mini-httpd So runit-run is for "run runit as a service under another init system" as opposite to runit-init which is for "use runit as full init replacement". I think the uninitiated user can get an idea by reading the package description of runit, runit-init and runit-run. Anyway I'm open to suggestions if someone thinks that the package description is not helping or there is an idea for a better name then "runit-run". I've re-uploaded the package: Info: https://mentors.debian.net/package/runit Download: dget -x https://mentors.debian.net/debian/pool/main/r/runit/runit_2.1.2-37.dsc updated git repo: https://salsa.debian.org/Lorenzo.ru.g-guest/runit/-/tree/release-2.1.2-37 Best Regards, Lorenzo -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.5.9-van (SMP w/4 CPU cores; PREEMPT) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit)
Bug#960940: RFS: runit/2.1.2-37 [RC] -- system-wide service supervision
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "runit" * Package name: runit Version : 2.1.2-37 Upstream Author : Gerrit Pape * URL : http://smarden.org/runit/ * License : BSD-3-clause * Vcs : https://salsa.debian.org/debian/runit Section : admin It builds those binary packages: runit - system-wide service supervision runit-run - service supervision (systemd and sysv integration) getty-run - runscripts to supervise getty processes runit-init - system-wide service supervision (as init system) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/runit Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/r/runit/runit_2.1.2-37.dsc Updated git repo: https://salsa.debian.org/Lorenzo.ru.g-guest/runit/-/tree/release-2.1.2-37 Changes since the last upload: * Bring back the test about forced-rescan * Fix forced rescan test failure on sbuild (Closes: #941322) * Clean the current symlink on purge * Invoke-run: add a DEBUG option to finish-default * Finish-default: print invoke-run instead of runsv * Get non default rundirectory from kernel command line * Add an isolation rundirectory for containers (Closes: #950851) * Merge runit-sysv and runit-systemd into runit-run (Closes: #953875) * Add lintian overrides for manpage without executable * Update copyright for debian files * Add an autopkgtest to catch regression on 953875 Regards, -- Lorenzo Puliti -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.5.9-van (SMP w/4 CPU cores; PREEMPT) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit)
Bug#950851: runit: Obey policy-rc.d aka use invoke-rc.d to run statup/shutdown scripts
Package: src:runit Followup-For: Bug #950851 Control: severity -1 normal Hi, I'm downgrading the severity of this because there is consensus on Debian-devel that the policy-rc.d mechanism is not the right tool to achieve what you're asking for. See [1] for details About your request, with the next runit Debian release (2.1.2-37), you will be able to skip all sysvinit scripts in /etc/rc2.d/ and have runit manage only selected services by setting the 'runitdir' environment variable to 'isolation'. This will be documented in the runit(8) manpage. I've tested in docker and using the 'env runitdir=isolation' option works as expected. Of course, in your Dockerfile, you need to symlink your runit service into /etc/runit/runsvdir/isolation/ otherwise runsvdir will have nothing to supervise. Hope this will solve your problem, feedback is welcome. Regards, Lorenzo [1] https://lists.debian.org/debian-devel/2020/04/msg00231.html -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.5.9-van (SMP w/4 CPU cores; PREEMPT) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit)
Bug#960705: apt: --allow-remove-essential doesn't work as expected (regression)
Package: apt Version: 2.1.2 Severity: normal Hi, recent changes in apt makes harder than it was to install runit-init: with the current (2.1.2) apt: # apt-get install --allow-remove-essential runit-init Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: runit-init : Conflicts: sysvinit-core but 2.96-3 is to be installed E: Unable to correct problems, you have held broken packages. I can only perform the install in two step # apt-get remove --allow-remove-essential init Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: initscripts insserv startpar sysv-rc Use 'apt autoremove' to remove them. The following packages will be REMOVED: init WARNING: The following essential packages will be removed. This should NOT be done unless you know exactly what you are doing! init 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 21.5 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 12861 files and directories currently installed.) Removing init (1.57) ... root@8208a6e6a7c8:/var/cache/apt/archives# apt-get install runit-init Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: fgetty getty-run The following packages will be REMOVED: libnss-systemd libpam-systemd systemd-sysv The following NEW packages will be installed: fgetty getty-run runit-init 0 upgraded, 3 newly installed, 3 to remove and 0 not upgraded. Need to get 71.1 kB of archives. After this operation, 863 kB disk space will be freed. Do you want to continue? [Y/n] This is a regression, and it breaks runit autopkgtest about init-switch, which used to work; downgrading apt, apt-utils and libapt-pkg6 to 2.0.2 # dpkg -l | grep apt ii apt 2.0.2 amd64commandline package manager ii apt-utils 2.0.2 amd64package management related utility programs ii libapt-pkg6.0:amd64 2.0.2 amd64package management runtime library # apt-get install --allow-remove-essential runit-init Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: fgetty getty-run The following packages will be REMOVED: init libnss-systemd libpam-systemd systemd-sysv The following NEW packages will be installed: fgetty getty-run runit-init WARNING: The following essential packages will be removed. This should NOT be done unless you know exactly what you are doing! init systemd-sysv (due to init) 0 upgraded, 3 newly installed, 4 to remove and 3 not upgraded. Need to get 71.1 kB of archives. After this operation, 885 kB disk space will be freed. Do you want to continue? [Y/n] I guess this is karma striking back to me from trying to dump #953875 on you.. Regards, Lorenzo -- Package-specific info: -- apt-config dump -- APT ""; APT::Architecture "amd64"; APT::Build-Essential ""; APT::Build-Essential:: "build-essential"; APT::Install-Recommends "1"; APT::Install-Suggests "0"; APT::Sandbox ""; APT::Sandbox::User "_apt"; APT::Authentication ""; APT::Authentication::TrustCDROM "true"; APT::NeverAutoRemove ""; APT::NeverAutoRemove:: "^firmware-linux.*"; APT::NeverAutoRemove:: "^linux-firmware$"; APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*$"; APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*-[a-z0-9]*$"; APT::NeverAutoRemove:: "^linux-.*-3\.18\.5-bfs1$"; APT::NeverAutoRemove:: "^linux-.*-4\.0\.1-van$"; APT::NeverAutoRemove:: "^linux-.*-4\.1\.3-van$"; APT::NeverAutoRemove:: "^linux-.*-4\.14\.11-van$"; APT::NeverAutoRemove:: "^linux-.*-4\.14\.2-van$"; APT::NeverAutoRemove:: "^linux-.*-4\.15\.12-van$"; APT::NeverAutoRemove:: "^linux-.*-4\.17\.3-van$"; APT::NeverAutoRemove:: "^linux-.*-4\.19\.0-5-amd64-unsigned$"; APT::NeverAutoRemove:: "^linux-.*-4\.6\.4-van$"; APT::NeverAutoRemove:: "^linux-.*-5\.3\.0-2-amd64$"; APT::NeverAutoRemove:: "^linux-.*-5\.3\.0-2-amd64-unsigned$"; APT::NeverAutoRemove:: "^linux-.*-5\.5\.9-van$"; APT::NeverAutoRemove:: "^kfreebsd-.*-3\.18\.5-bfs1$"; APT::NeverAutoRemove:: "^kfreebsd-.*-4\.0\.1-van$"; APT::NeverAutoRemove:: "^kfreebsd-.*-4\.1\.3-van$"; APT::NeverAutoRemove:: "^kfreebsd-.*-4\.14\.11-van$"; APT::NeverAutoRemove:: "^kfreebsd-.*-4\.14\.2-van$"; APT::NeverAutoRemove:: "^kfreebsd-.*-4\.15\.12-van$"; APT::NeverAutoRemove:: "^kfreebsd-.*-4\.17\.3-van$";
Bug#953875: runit - default installation can force init switch
Followup-For: Bug #953875 Control: reassign -1 apt 2.0.2 Dear apt maintainers, runit package has a recommends that is in the form Recommends: runit-sysv | runit-init | runit-systemd Runit-sysv needs sysvinit as init, and runit-systemd needs systemd as init. The problem is that, when installing runit, apt chooses to install 'runit-sysv'(forcing an init switch), regardless of the fact that there is another alternative listed (runit-systemd) that does not cause an init switch and also it's very unlikely to cause the removal of any installed package. Please implement a logic where apt parse the alternative recommends in order and pick up the first that does not require a removal of any installed package in the system. If none of the listed recommends can be installed without removing any packages, then I think it's ok to pick the first listed. Note that this bug is not easy to fix on runit side: * changing the order of the recommends will cause the same issue for sysvinit users * the trick suggested by Adam Borowski in #10 does not work * bundle the sysv and the systemd implementation in runit package, like a common service, is not easy since the sysv implementation is respawned with a line in /etc/inittab which is a conffile of sysvinit-core. And even if I ship and maintain my own version of inittab, I would still have to deal with 'runit-init'. Regards, Lorenzo -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.5.9-van (SMP w/4 CPU cores; PREEMPT) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit)
Bug#956659: autopkgtest-build-qemu fails to create an image for qemu
Package: autopkgtest
Version: 5.12.1
Severity: important
Hello,
I'm no longer able to create an image for autopkgtest with
# autopkgtest-build-qemu unstable ./autopkgtest.img
Load spec file /tmp/tmp.r8ug3ZCECh
ERROR: No runner implements step with keys device, set
It seems to be because of this part of autopkgtest-build-qemu script,
that was added with commit adc0aa94 [1]
- set: flag
device: "{{ image }}"
The above error disappear if I remove that part from the script,
and the process goes ahead. Not sure if it's a bug in autopkgtest
or in vmbd2.
However, even with the autopkgtest-build-qemu script modified,
the creation of the image fails with another error
autopkgtest-build-qemu unstable ../autopkgtest.img
Load spec file /tmp/tmp.GYgpSOLAo0
Exec: ['qemu-img', 'create', '-f', 'raw', '../autopkgtest.img.raw', '25G']
Exec: ['parted', '-s', '../autopkgtest.img.raw', 'mklabel', 'gpt']
Exec: ['parted', '-m', '../autopkgtest.img.raw', 'print']
Exec: ['parted', '-s', '../autopkgtest.img.raw', 'mkpart', 'primary', 'ext2',
'0%', '5%']
Exec: ['parted', '-m', '../autopkgtest.img.raw', 'print']
Exec: ['parted', '-s', '../autopkgtest.img.raw', 'mkpart', 'primary', 'ext2',
'5%', '100%']
Exec: ['kpartx', '-asv', '../autopkgtest.img.raw']
remembering /dev/mapper/loop1p1 as boot
remembering /dev/mapper/loop1p2 as root
Exec: ['/sbin/mkfs', '-t', 'ext4', '/dev/mapper/loop1p2']
Exec: ['mount', '/dev/mapper/loop1p2', '/tmp/tmpmgw2bhok']
Exec: ['debootstrap', '--variant', '-', 'unstable', '/tmp/tmpmgw2bhok',
'http://deb.debian.org/debian']
mounting proc: ['chroot', '/tmp/tmpmgw2bhok', 'mount', '-t', 'proc', 'proc',
'/proc']
Exec: ['chroot', '/tmp/tmpmgw2bhok', 'apt-get', 'update']
unmounting proc: ['chroot', '/tmp/tmpmgw2bhok', 'umount', '/proc']
mounting proc: ['chroot', '/tmp/tmpmgw2bhok', 'mount', '-t', 'proc', 'proc',
'/proc']
Exec: ['chroot', '/tmp/tmpmgw2bhok', 'apt-get', 'update']
unmounting proc: ['chroot', '/tmp/tmpmgw2bhok', 'umount', '/proc']
mounting proc: ['chroot', '/tmp/tmpmgw2bhok', 'mount', '-t', 'proc', 'proc',
'/proc']
Exec: ['chroot', '/tmp/tmpmgw2bhok', 'apt-get', '-y', '--no-show-progress',
'install', 'eatmydata']
unmounting proc: ['chroot', '/tmp/tmpmgw2bhok', 'umount', '/proc']
mounting proc: ['chroot', '/tmp/tmpmgw2bhok', 'mount', '-t', 'proc', 'proc',
'/proc']
Exec: ['chroot', '/tmp/tmpmgw2bhok', 'eatmydata', 'apt-get', 'update']
unmounting proc: ['chroot', '/tmp/tmpmgw2bhok', 'umount', '/proc']
mounting proc: ['chroot', '/tmp/tmpmgw2bhok', 'mount', '-t', 'proc', 'proc',
'/proc']
Exec: ['chroot', '/tmp/tmpmgw2bhok', 'eatmydata', 'apt-get', '-y',
'--no-show-progress', 'install', 'linux-image-amd64', 'ifupdown']
unmounting proc: ['chroot', '/tmp/tmpmgw2bhok', 'umount', '/proc']
mounting proc: ['chroot', '/tmp/tmpmgw2bhok', 'mount', '-t', 'proc', 'proc',
'/proc']
Exec: ['chroot', '/tmp/tmpmgw2bhok', 'apt-get', 'clean']
unmounting proc: ['chroot', '/tmp/tmpmgw2bhok', 'umount', '/proc']
Installing GRUB for BIOS
Exec: ['mount', '--bind', '/dev', '/tmp/tmpmgw2bhok/dev']
Exec: ['mount', '--bind', '/sys', '/tmp/tmpmgw2bhok/sys']
mounting proc: ['chroot', '/tmp/tmpmgw2bhok', 'mount', '-t', 'proc', 'proc',
'/proc']
Exec: ['chroot', '/tmp/tmpmgw2bhok', 'apt-get', '-y', '--no-show-progress',
'install', 'grub-pc']
unmounting proc: ['chroot', '/tmp/tmpmgw2bhok', 'umount', '/proc']
mounting proc: ['chroot', '/tmp/tmpmgw2bhok', 'mount', '-t', 'proc', 'proc',
'/proc']
Exec: ['chroot', '/tmp/tmpmgw2bhok', 'grub-mkconfig', '-o',
'/boot/grub/grub.cfg']
unmounting proc: ['chroot', '/tmp/tmpmgw2bhok', 'umount', '/proc']
mounting proc: ['chroot', '/tmp/tmpmgw2bhok', 'mount', '-t', 'proc', 'proc',
'/proc']
Exec: ['chroot', '/tmp/tmpmgw2bhok', 'grub-install', '--target=i386-pc',
'--no-nvram', '--force-extra-removable', '--no-floppy', '--modules=part_msdos
part_gpt', '--grub-mkdevicemap=/boot/grub/device.map', '/dev/loop1']
unmounting proc: ['chroot', '/tmp/tmpmgw2bhok', 'umount', '/proc']
unmounting proc: ['chroot', '/tmp/tmpmgw2bhok', 'umount', '/proc']
umount: /proc: not mounted.
ERROR: Command '['chroot', '/tmp/tmpmgw2bhok', 'umount', '/proc']' returned
non-zero exit status 32.
ERROR: CalledProcessError(32, ['chroot', '/tmp/tmpmgw2bhok', 'umount', '/proc'])
Something went wrong, cleaning up!
Exec: ['umount', '/tmp/tmpmgw2bhok/dev']
Exec: ['umount', '/tmp/tmpmgw2bhok/sys']
Exec: ['umount', '/tmp/tmpmgw2bhok']
Exec: ['kpartx', '-dsv', '../autopkgtest.img.raw']
and I'm not able to work around this; any ideas?
Regards,
Lorenzo
[1]
https://salsa.debian.org/ci-team/autopkgtest/-/commit/adc0aa941cd31c7ccb90f4ca030d6c15973af9f5
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.3.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked
Bug#954190: dh-runit: FTBFS on armhf due to shake testsuite failure
Package: dh-runit
Version: 2.8.15
Severity: serious
Tags: ftbfs
Justification: fails to build from source
According to build logs dh-runit FTBFS, but only on armhf. This is because
the testsuite exits nonzero. I can reproduce the error in the log [1]
inside an armhf chroot (created with debootstrap), but not on other
architectures (amd64).
To reproduce there is no need to build the package, just download dh-runit
source inside
the chroot, make sure build-dep are installed, then do
root@lorenz:/home/extra/dh-runit-2.8.15# ghc testrunner.hs
[1 of 1] Compiling Main ( testrunner.hs, testrunner.o )
Linking testrunner ...
root@lorenz:/home/extra/dh-runit-2.8.15# ./testrunner
Error when reading Shake database .shake/.shake.database
Witness type has disappeared, StepKey {4f23698ed1fc9a1a}
CallStack (from HasCallStack):
error, called at src/Development/Shake/Internal/Core/Storage.hs:191:40 in
shake-0.16.4-1RhwnB79ZHh8eiw92e7jMZ:Development.Shake.Internal.Core.Storage
All files will be rebuilt
# tar (for t/out/935997.tar)
# mv (for t/out/935997.tar)
# rm (for t/out/935997.log)
# mkdir (for t/out/935997.log)
[ and the test continue till the end]
Dear libghc-shake-dev maintainer,
I'm not knowledgeble of shake: is this likely a bug in shake or a bug that
need a fix on dh-runit side?
Thanks,
Lorenzo
[1]
https://tests.reproducible-builds.org/debian/rb-pkg/bullseye/armhf/dh-runit.html
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.5.9-van (SMP w/4 CPU cores; PREEMPT)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: runit (via /run/runit.stopit)
Versions of packages dh-runit depends on:
ii debhelper12.9
ii libfile-copy-recursive-perl 0.45-1
ii libfile-slurp-perl .29-1
ii libtext-hogan-perl 2.01-1
dh-runit recommends no packages.
dh-runit suggests no packages.
-- no debconf information
Bug#922653: irqbalance: restart loop when running under runit and with a single CPU
Package: irqbalance Version: 1.6.0-3 Followup-For: Bug #922653 Hi, > Thanks for clarifying. Can you confirm that the patch from Mathieu > Mirmont will correctly fix this bug? The patch looks reasonable to me, > but I can't test it on a runit based system at the moment. Yes, the patch correctly fix this issue Lorenzo -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.5.9-van (SMP w/4 CPU cores; PREEMPT) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit) Versions of packages irqbalance depends on: ii init-system-helpers1.57runit1 ii libc6 2.30-2 ii libcap-ng0 0.7.9-2.1+b2 ii libelogind0 [libsystemd0] 241.3-1+debian3 ii libglib2.0-0 2.64.1-1 ii libncursesw6 6.2-1 ii libnuma1 2.0.12-1+b1 ii libtinfo6 6.2-1 ii lsb-base 11.1.0 ii runit-helper 2.8.15 irqbalance recommends no packages. irqbalance suggests no packages. -- Configuration Files: /etc/sv/irqbalance/run changed [not included] -- debconf information excluded
Bug#924132: runit: Add support for runit in init-system-helpers
Package: init-system-helpers Version: 1.57runit1 Followup-For: Bug #924132 Control: affects -1 + runit-init Hi, I'm now maintaining runit: is there any update on the progress of this bug? If you don't have time to spend on this, would be ok if I ask another DD for an NMU? Thanks Lorenzo -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.5.9-van (SMP w/4 CPU cores; PREEMPT) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit) Versions of packages init-system-helpers depends on: ii perl-base 5.30.0-9 init-system-helpers recommends no packages. init-system-helpers suggests no packages. Versions of packages init-system-helpers is related to: ii insserv 1.21.0-1 -- no debconf information -- debsums errors found: debsums: changed file /usr/sbin/invoke-rc.d (from init-system-helpers package) debsums: changed file /usr/sbin/update-rc.d (from init-system-helpers package)
Bug#929884: dnsmasq: please provide runscript file
Package: src:dnsmasq Followup-For: Bug #929884 -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.5.9-van (SMP w/4 CPU cores; PREEMPT) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit) > [ I no longer using Debian, added new runit maintainer into CC. ] Hi, > Runscript is using #!/lib/runit/invoke-run as interpreter, which sources > /etc/default/dnsmasq automatically. exactly About the patch, I suggest a change in the following part > +++ b/debian/dnsmasq.runit > @@ -0,0 +1 @@ > +debian/dnsmasq.runscript name=dnsmasq,logscript,since=2.80-1+runit > diff --git a/debian/dnsmasq.runscript/finish b/debian/dnsmasq.runscript/finish > new file mode 100755 > index 000..cf35240 > --- /dev/null > If you use dh-runit >= 2.8.15 to build, the 'since' option is obsoleted (no longer needed); I've forgot to mention that in the manpage, I will add a note in the next upload. You probably want to add the 'presubj' option instead, that suggest the reporter to add the runit maintainer in CC when reporting a bug, if he is using runit the line would look like this +debian/dnsmasq.runscript name=dnsmasq,logscript,presubj In any case, if you decide to merge this and some runit-specific bug should arise, feel free to add me in CC, I will provide assistance. Best Regards, Lorenzo
