Your message dated Fri, 31 Jan 2025 12:20:36 +0100
with message-id <895aee4b-ae1c-4f32-8b78-561279dd7...@debian.org>
and subject line Re: RFS: runit/2.1.2-61 [RC] -- system-wide service supervision
has caused the Debian Bug report #1094231,
regarding RFS: runit/2.1.2-61 [RC] -- system-wide service supervision
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 ow...@bugs.debian.org
immediately.)


-- 
1094231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1094231
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for my package "runit":

Note: this version B-D on dh-sysuser >= 1.6 so #1093846 needs to go
first.

 * Package name     : runit
   Version          : 2.1.2-61
   Upstream contact : Gerrit Pape <p...@smarden.org>
 * URL              : http://smarden.org/runit/
 * License          : CC0-1.0, GPL-3+, BSD-3-clause, GPL-2+
 * 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)
  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-61.dsc

git repo:
  https://salsa.debian.org/debian/runit/-/tree/next?ref_type=heads

Changes since the last upload:

 runit (2.1.2-61) unstable; urgency=medium
 .
   [ Lorenzo Puliti ]
   * NEWS for runit, runit-init users
   * export PATH in stage 1,2,3. (Closes: #1068922)
     + Thanks to Martin Steigerwald <mar...@lichtvoll.de>
   * stage1, shutdown.c: write boot and shutdown
      wtmpdb entry (Closes: #992648)
 .
   [ Andrew Bower ]
   * shutdown.c : accept but ignore -H, -P and message
      arguments (Closes: #1087001)
 .
   [ Lorenzo Puliti ]
   * service, invoke-rc.d:
     - import from i-s-h 1.67, add runit patches
     - runit-init: divert helpers and manpages
     - adjust d/clean, d/rules clean target
     - update copyright for init-helpers
   * sysv override:
      - change sysv script override mechanism (Closes: #1071395)
      - add /etc/runit/override-sysv.d/README
      - finish-exec: remove *.pkgrunit override files
      - run_sysv_script: adjust (this partially reverts the fix
        for #1022837, other workarounds are provided)
   * invoke-run:
      - print a message about starting runscript when in
        verbose mode
      - update wtime file at service startup
      - update manpage
   * trigger_vs:
      - skip upgrade iteration if binary not installed
      - test for runsvdir before SIGALRM
   * move policy-rc.d layer from invoke-run to trigger_sv
   * sync available services in stage2, before runsvdir
   * cpsv: fix make_svlinks for log's run
 .
   [ наб ]
   * Drop B-D on dh-buildinfo (Closes: #1090770)
 .
   [ Lorenzo Puliti ]
   * adjust autopkgtest/upstream-testsuite
   * fix d/runit.install
   * update lintian overrides
   * d/patches (quilt):
      -  drop move-comunication-files patch, not really needed
      -  drop patch to disable sv test, issue fixed on Hurd
         side (see #1009712). (Closes: #1003891)
         + Thanks to João Pedro Malhado, Samuel Thibault
   * dh-sysuser: use a sysusers.d control file, drop
      our legacy control file (Closes: #981799)

Regards,
Lorenzo

--- End Message ---
--- Begin Message ---
Thanks for the update!

--- End Message ---

Reply via email to