Your message dated Mon, 09 Feb 2026 22:18:15 +0000
with message-id <[email protected]>
and subject line Bug#1101895: fixed in runit 2.3.0-1
has caused the Debian Bug report #1101895,
regarding runit-init: Fully support running as init on Hurd port
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.)


-- 
1101895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101895
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: runit-init
Version: 2.2.0-2
Severity: normal
X-Debbugs-Cc: João Pedro Malhado <[email protected]>, [email protected]

I received a private mail with a report about runit as init on Hurd,
and it looks there are missing pieces
[writing this bug as a reminder for myself]

João, feel free to follow-up here if/when you have further infos.

So it looks like Hurd kernel first runs /etc/hurd/runsystem script which is
handled via alternatives; at the end the script exec /sbin/init.
When sysvinit-core is installed, /etc/hurd/runsystem.sysv is used;

on runit-init side, at least the following is needed:

* install a /etc/hurd/runsystem.runit and update the alternatives
  (/etc/hurd/runsystem.sysv invokes init with parameters that are not ok for 
runit-init)

* mount proc at boot: proc is not mounted automatically (as it is in linux);
  in sysvinit the mount is done inside the /etc/init.d/rc script, not used by 
runit-init

* runit-init for now conflicts with sysvinit-core so either remove the conflic 
for Hurd
  or at least make sure that when runit-init is installed the alternative of 
sysvinit-core
  is removed; this may require cooperation of Hurd porters and/or sysvinit 
maintainers

on getty-run side:

* getty tty[n] uses the 'linux' parameter which is wrong for Hurd (no parameter 
at
  all seems ok)

and maybe few other things

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.8.12-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, 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)

Versions of packages runit-init depends on:
ii  getty-run    2.2.0-2
ii  initscripts  3.14-4
ii  insserv      1.26.0-1
ii  mount        2.40.4-5
ii  runit        2.2.0-2

Versions of packages runit-init recommends:
ii  runit-services  0.9.0

runit-init suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: runit
Source-Version: 2.3.0-1
Done: Lorenzo Puliti <[email protected]>

We believe that the bug you reported is fixed in the latest version of
runit, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Lorenzo Puliti <[email protected]> (supplier of updated runit package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sun, 08 Feb 2026 13:11:14 +0100
Source: runit
Architecture: source
Version: 2.3.0-1
Distribution: unstable
Urgency: medium
Maintainer: Lorenzo Puliti <[email protected]>
Changed-By: Lorenzo Puliti <[email protected]>
Closes: 1101895
Changes:
 runit (2.3.0-1) unstable; urgency=medium
 .
   * New upstream version 2.3.0
        (LP: #399634)
   * d/patches:
       - drop patches accepted or rejected upstream
       - refresh remaining quilt patches
   * getty-run:
      - add support for Hurd
      - use --noclear on tty1
   * runit-init: add experimental support for Hurd (Closes: #1101895)
      - install /etc/hurd/runsystem.runit
      - remove runsystem.runit at purge on Hurd
   * testsuite: trigger-sv : add test for user services
   * trigger_sv: fix user services (enable and restart)
   * svlogd/run: fix user services use case
   * cpsv: add i command
Checksums-Sha1:
 ad7838fb150798812f542a2ad8d6816c13e924f2 2212 runit_2.3.0-1.dsc
 3f84890ea45633a939344fa169e022f2407d08c3 108059 runit_2.3.0.orig.tar.gz
 c87fb7b3b7b7c74fe87f246f9e768dd3a586e6d4 83892 runit_2.3.0-1.debian.tar.xz
 906a16b84df631becb748d417c69666f13a47eb5 6990 runit_2.3.0-1_amd64.buildinfo
Checksums-Sha256:
 8857a37d666df3b012707771d0f26c6567ef07457d4ca3ec7cf172346a31a78d 2212 
runit_2.3.0-1.dsc
 190e11c1f8072b543bb6bd53850555c458d6e306d53df3fc1232d300c3e21b51 108059 
runit_2.3.0.orig.tar.gz
 614b35ec5232ff80b6e9b650ed36834de147407f3af521e73c34843e9636ede3 83892 
runit_2.3.0-1.debian.tar.xz
 59975fc7cd7b68d836374151ab9aee83bf538b23b03db7fd0a5a60178b974bcc 6990 
runit_2.3.0-1_amd64.buildinfo
Files:
 f7b27de95f786c246c33b90970037d4d 2212 admin optional runit_2.3.0-1.dsc
 0a6b0dbfd892fb432db0a6a5affa0c3d 108059 admin optional runit_2.3.0.orig.tar.gz
 c21baae4f6b316dc521b50c9467bb25d 83892 admin optional 
runit_2.3.0-1.debian.tar.xz
 6809dd2d459f9cea55f58eb3b1a72288 6990 admin optional 
runit_2.3.0-1_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE2ji91PGnrxOd1bVNxxYb07RU7gMFAmmKUxwACgkQxxYb07RU
7gOAag/8CbCuCvJnK84+IY5BwYG/uCEt1GCoyemNvFK3W8QpohuMwOw3qHiqr6pQ
Cj7tACiB9f0tXW5Fg69Jg44hT9J9cTeh1RJb/anWTv5I/p09z/hpBbDQhaMBvtge
IEHStFy4+8CI3XIexXkDG5AA5HTVxfk0MvY0buLsVscK0SWMhznfqddfsL5zO7qr
2UT2AYnarHlcKJ1kKVP1nc8Wynf1iW5zkyuQdl9GY4Q3uiNWTJo3gQZHj4kl41z4
D5viHEtr7oDLBccYmX/WL1MK8IyxmJ1pIEz3iNqWFYstNPWKyeCDvywh8Znndzgk
VjbSXUSFvJG40zQGTCIMfpAi5q1Obeg4bcML66aD5rPq2eLHtQDfCCUeHJytS+Cr
tLDPtzbsJXDXMpDTsIky56BPGI4kc4+rkoU50iHrLEy4ktlcYESxVlNNcFQd246U
FGeFcB4g7yTpRNqTI4vK5gACUlkKk5vSTOTVjH3mX5fss9yUg4JbEJnS5gn0n+bE
zYif38PzPK/BCujelL5WNxnBFQGcWWvUFSdy5hImOF+3YNduVHDMM0ieIj6yJnBA
V3D1nFSJb20W/ak07n8loJZfU+BPFHqOc3v5E/yd26AtfqusyqiDce5JCTKXFg2y
qJkIOEfIuYuOrM0951sQeHIko1nn4VqNBP0vGAEeUt7CrmX8W+M=
=toao
-----END PGP SIGNATURE-----

Attachment: pgpfZ2gaGnk9P.pgp
Description: PGP signature


--- End Message ---

Reply via email to