Your message dated Mon, 23 Feb 2026 19:06:56 +0000
with message-id <[email protected]>
and subject line Re: Bug#1128576: runit-run: upgrade caused trigger to start
administratively-down services
has caused the Debian Bug report #1128576,
regarding runit-run: upgrade caused trigger to start administratively-down
services
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1128576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1128576
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: runit-run
Version: 2.3.0-1
Severity: normal
Dear Maintainer,
I ran apt-get upgrade and the runit trigger caused two services to start which
had 'down' files in their service directory. A similar service was not started.
I would have expected them to stay down.
Note that these services predate the new 'runit user services' despite similar
style of names. No runit packages were upgraded in this step:
$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
...
Preparing to unpack …/189-luanti-server_5.14.0+dfsg-3_amd64.deb…
Unpacking luanti-server (5.14.0+dfsg-3) over (5.14.0+dfsg-2)…
...
Processing triggers for runit (2.3.0-1)…
Runit triggered upgrade: setup
Runit triggered upgrade: upgrade
ok: run: minetest-server@percyworld2: (pid 25619) 0s, normally down
ok: run: minetest-server@scaredlands: (pid 25638) 0s, normally down
...
$ sudo sv status /etc/service/*
run: /etc/service/minetest-server@percyworld2: (pid 25619) 906s, normally down;
run: log: (pid 3353) 1962s
run: /etc/service/minetest-server@scaredlands: (pid 25638) 906s, normally down;
run: log: (pid 3354) 1962s
down: /etc/service/minetest-server@thedeeps: 1962s; run: log: (pid 3356) 1962s
down: /etc/service/pdns-recursor: 1963s; run: log: (pid 3355) 1962s
$ tree /etc/service/
/etc/service/
├── minetest-server@percyworld2
│ ├── down
│ ├── finish
│ ├── log
│ │ ├── run
│ │ ├── run.dpkg-dist
│ │ └── supervise -> /run/runit/supervise/[email protected]
│ ├── run
│ └── supervise -> /run/runit/supervise/minetest-server@percyworld2
├── minetest-server@scaredlands
│ ├── down
│ ├── finish
│ ├── log
│ │ ├── run
│ │ ├── run.dpkg-dist
│ │ └── supervise -> /run/runit/supervise/[email protected]
│ ├── run
│ └── supervise -> /run/runit/supervise/minetest-server@scaredlands
├── minetest-server@thedeeps
│ ├── down
│ ├── finish
│ ├── log
│ │ ├── run
│ │ └── supervise -> /run/runit/supervise/[email protected]
│ ├── run
│ └── supervise -> /run/runit/supervise/minetest-server@thedeeps
└── pdns-recursor -> /etc/sv/pdns-recursor
...
$ tree /etc/sv
/etc/sv
...
│ └── supervise -> /run/runit/supervise/lxcfs
├── minetest-server@
│ ├── finish
│ ├── log
│ │ ├── run
│ │ └── run.dpkg-dist
│ └── run
├── pcscd
...
$ tree /usr/share/runit/
/usr/share/runit/
├── meta
│ ├── default-syslog
│ │ └── installed
│ ├── pcscd
│ │ └── installed
│ ├── ssh
│ │ └── installed
│ └── stubby
│ └── installed
├── sv
├── sv.current -> /usr/share/runit/sv.now
├── sv.now
└── sv.src -> /usr/share/runit/sv
-- System Information:
Debian Release: forky/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.18.9+deb14-amd64 (SMP w/24 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled
Versions of packages runit-run depends on:
ii runit 2.3.0-1
runit-run recommends no packages.
runit-run suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi Lorenzo,
On Sun, Feb 22, 2026 at 11:37:56PM +0100, lorenzo wrote:
> On Sat, 21 Feb 2026 12:25:06 +0000
> Andrew Bower <[email protected]> wrote:
> > I ran apt-get upgrade and the runit trigger caused two services to
> > start which had 'down' files in their service directory. A similar
> > service was not started. I would have expected them to stay down.
> >
> > Note that these services predate the new 'runit user services'
> > despite similar style of names. No runit packages were upgraded in
> > this step:
>
> it's the upgrade of luanti-server that triggers runit's trigger_sv;
> the 'setup' loop is only meant for runit-init, but the 'upgrade' loop
> works also for runit-run users (but in fact it didn't before 2.2.0-7 due
> to a bug)
Perhaps why I didn't notice this before.
> > $ sudo apt-get upgrade
> > Reading package lists... Done
> > Building dependency tree... Done
> > Reading state information... Done
> > Calculating upgrade... Done
> > ...
> > Preparing to unpack …/189-luanti-server_5.14.0+dfsg-3_amd64.deb…
> > Unpacking luanti-server (5.14.0+dfsg-3) over (5.14.0+dfsg-2)…
> > ...
> > Processing triggers for runit (2.3.0-1)…
> > Runit triggered upgrade: setup
> > Runit triggered upgrade: upgrade
> > ok: run: minetest-server@percyworld2: (pid 25619) 0s, normally down
> > ok: run: minetest-server@scaredlands: (pid 25638) 0s, normally down
>
> minetest-server@percyworld2 and minetest-server@scaredlands have a
> .meta/bin file inside their service directories (are they shipped with a
> deb package?) but there is no .meta/bin file in
> minetest-server@thedeeps: correct?
You are right!
Sorry, I should have run 'tree -a'. These files must have been left from
an early experiment in supporting template services at the package
level, before you added similar features for real - they aren't supposed
to be there now!
Thanks.
RESOLVED INVALID.
--- End Message ---
