Bug#931186: marked as done (unblock: init-system-helpers/1.57)
Your message dated Fri, 28 Jun 2019 11:07:07 +0200
with message-id <20190628090705.tqwk4bril5kf4hts@debian.org>
and subject line Re: unblock: init-system-helpers/1.57
has caused the Debian Bug report #931186,
regarding unblock: init-system-helpers/1.57
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 owner@bugs.debian.org
immediately.)
--
931186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931186
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock
Hi,
I know this is unblock request is rather late, apologies for that.
The current version of init-system-helpers in buster has a change which
was not acked by its maintainers.
The bug submitter ignored that feedback and NMUed the package anyway.
Not adding runit-init as alternative means, that when installing
runit-init, dpkg/apt will prompt you, if you really want to do that
change. Given the experience I and Martin Pitt had, when evaluating
runit, this is probably not a bad thing.
After all, the init meta package is merely a safety net to prevent users
from shooting themselves in the foot. The init meta-package doesn't
provide any functionality and serves no other purpose otherwise.
I've seen that [1] was just filed, I hope this doesn't block testing
migration
Regards,
Michael
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931181
unblock init-system-helpers/1.57
-- System Information:
Debian Release: 10.0
APT prefers unstable
APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Hi,
On Thu, Jun 27, 2019 at 08:53:12PM +0200, Michael Biebl wrote:
> I know this is unblock request is rather late, apologies for that.
>
> The current version of init-system-helpers in buster has a change which
> was not acked by its maintainers.
> The bug submitter ignored that feedback and NMUed the package anyway.
>
> Not adding runit-init as alternative means, that when installing
> runit-init, dpkg/apt will prompt you, if you really want to do that
> change. Given the experience I and Martin Pitt had, when evaluating
> runit, this is probably not a bad thing.
> After all, the init meta package is merely a safety net to prevent users
> from shooting themselves in the foot. The init meta-package doesn't
> provide any functionality and serves no other purpose otherwise.
Sorry, it's too late for this.
The hostile NMU was done 6 months before you uploaded the revert. That was
plenty of time to do so.
Some additional remarks:
It would have been a lot clearer to explicitly state that you are reverting
the NMU in the changelog.
If you think runit-init is not suitable as an init system, you should file an
RC bug against it.
Thanks,
Ivo
--- End Message ---
Reply to: