Bug#861536: runit-init: Cannot reboot or shutdown after installing (or removing) the package.

On Fri 2017-06-02 02:53:47 +0200, Michael Biebl wrote: > Seems like you want a Breaks/Replaces: runit-init in runit to ensure the > package is properly upgraded for users who have already runit-init > installed. good call, thanks for the reminder. I'll do that in 2.1.2-9.2, which i'll upload

Bug#861536: runit-init: Cannot reboot or shutdown after installing (or removing) the package.

On Wed, 31 May 2017 13:26:36 -0400 Daniel Kahn Gillmor wrote: > I apologize for the oversight, and want to know if it'd be ok for me to > upload 2.1.2-9.2 using the attached debdiff. I've pushed a queue of > these changes into the "unstable" branch at >

Bug#861536: runit-init: Cannot reboot or shutdown after installing (or removing) the package.

Hi all-- On Tue 2017-05-30 13:07:01 -0400, Daniel Kahn Gillmor wrote: > I've now done this NMU, and filed #863732 to unblock the upload. > > I've pushed the changes in a git branch to > https://anonscm.debian.org/git/collab-maint/runit.git, which is forked > from of

Bug#861536: runit-init: Cannot reboot or shutdown after installing (or removing) the package.

On Sun 2017-05-28 15:14:24 -0400, Daniel Kahn Gillmor wrote: > On Sun 2017-05-28 19:54:33 +0200, Ivo De Decker wrote: >> If this bug can be fixed by removing runit-init, the removal of the other >> packages isn't necessary, but please note that this would need to happen very >> soon. > > fwiw, i'm

Bug#861536: runit-init: Cannot reboot or shutdown after installing (or removing) the package.

Hi, > runit-init: Cannot reboot or shutdown after installing (or removing) the > package. See also: https://bugs.debian.org/863539 https://bugs.debian.org/863541 https://bugs.debian.org/863542 https://bugs.debian.org/863543 Regards, -- ,''`. : :' : Chris Lamb

Bug#861536: runit-init: Cannot reboot or shutdown after installing (or removing) the package.

Hi there-- On Sun 2017-05-28 19:54:33 +0200, Ivo De Decker wrote: > On Sun, May 28, 2017 at 02:39:00PM +0200, Jan Niehusmann wrote: >> May I suggest only removing runit-init from the runit source package, if >> the bug can't be fixed in time for the stretch release? > > Sure. That just needs

Bug#861536: runit-init: Cannot reboot or shutdown after installing (or removing) the package.

Hi, On Sun, May 28, 2017 at 07:54:33PM +0200, Ivo De Decker wrote: > On Sun, May 28, 2017 at 02:39:00PM +0200, Jan Niehusmann wrote: > > May I suggest only removing runit-init from the runit source package, if > > the bug can't be fixed in time for the stretch release? > > Sure. That just needs

Bug#861536: runit-init: Cannot reboot or shutdown after installing (or removing) the package.

Hi, On Sun, May 28, 2017 at 02:39:00PM +0200, Jan Niehusmann wrote: > May I suggest only removing runit-init from the runit source package, if > the bug can't be fixed in time for the stretch release? Sure. That just needs someone to upload such an NMU very soon. I suggested this already at the

Bug#861536: runit-init: Cannot reboot or shutdown after installing (or removing) the package.

May I suggest only removing runit-init from the runit source package, if the bug can't be fixed in time for the stretch release? Because runit itself doesn't cause the issue discussed here, is useful on its own, and several packages depend on it. Thanks, Jan

Bug#861536: runit-init: Cannot reboot or shutdown after installing (or removing) the package.

BTW, I really think this doesn't need to be RC. (Or, at least, should be stretch-ignore, because removing all the reverse-dependencies would be worse than just shipping with runit-init.) I agree it's bad to leave a user with a broken system. But in this case, the user gets an appropriate

Bug#861536: runit-init: Cannot reboot or shutdown after installing (or removing) the package.

On 05/28/2017 12:30 PM, Matthew Hoare wrote: > Would it be appropriate to provide these commands for temporary use > after switching init? This would be hack and not a proper solution which would meet Debian standards. Really, the only solution here is simply not to replace the init system from

Bug#861536: runit-init: Cannot reboot or shutdown after installing (or removing) the package.

I can confirm that this issue also occurs with a fresh (debootstrap) installation of pure Debian stretch. I can also confirm that these four commands will reboot into the new init system without damaging the mounted filesystems: `echo 1 > /proc/sys/kernel/sysrq` `echo s > /proc/sysrq-trigger`

Bug#861536: runit-init: Cannot reboot or shutdown after installing (or removing) the package.

On 05/27/2017 11:37 PM, Ivo De Decker wrote: >> Well, there is also ulibc being shipped with Debian stable. Yet, when >> someone tries to use it and breaks their system, it's not supported >> either. So, I don't think this policy can be sweepingly applied to >> every package. > > There is no

Bug#861536: runit-init: Cannot reboot or shutdown after installing (or removing) the package.

Hi, On Fri, May 26, 2017 at 12:04:59PM +0200, John Paul Adrian Glaubitz wrote: > > > As the init system is a rather fundamental component of a Linux > > > distribution, it affects many other packages, directly or indirectly > > > and it's therefore too much of a burden to provide support for all

Bug#861536: runit-init: Cannot reboot or shutdown after installing (or removing) the package.

On Fri, 26 May 2017 11:28:48 +0200 Ivo De Decker wrote: > If the maintainer isn't interested in making sure that this package works as > expected, it isn't fit for a stable release... FYI. The maintainer cannot respond this for the time being [0]. [0]

Bug#861536: runit-init: Cannot reboot or shutdown after installing (or removing) the package.

Hi! On Fri, May 26, 2017 at 11:28:48AM +0200, Ivo De Decker wrote: > If a package leaves the system in a broken state, that is very much release > critical. So I'm upgrading the bug to serious. It should probably be > 'critical' (breaks the whole system), but as both are RC, that doesn't matter >

Bug#861536: runit-init: Cannot reboot or shutdown after installing (or removing) the package.

Control: severity -1 serious Hi, On Tue, May 23, 2017 at 09:27:14PM +0200, John Paul Adrian Glaubitz wrote: > > I can reproduce this issue in a fresh Debian stretch system if > > required but I was presuming that an upstream bug report was > > appropriate in this case, apologies if I was

Bug#861536: runit-init: Cannot reboot or shutdown after installing (or removing) the package.

Hi Matthew! On 05/23/2017 07:14 PM, Matthew Hoare wrote: > On 23/05/2017, John Paul Adrian Glaubitz wrote: >> I'm not sure why you are reporting this >> bug to Debian in the first place. >> > > I am one of the BunsenLabs developers, the distribution is a theming >

Bug#861536: runit-init: Cannot reboot or shutdown after installing (or removing) the package.

On 23/05/2017, John Paul Adrian Glaubitz wrote: > I'm not sure why you are reporting this > bug to Debian in the first place. > I am one of the BunsenLabs developers, the distribution is a theming and configuration set applied to a Debian base. The system from

Bug#861536: runit-init: Cannot reboot or shutdown after installing (or removing) the package.

Control: severity -1 normal On 05/04/2017 07:22 PM, John Paul Adrian Glaubitz wrote: > I'd be tempted to lower the severity to 'normal'. Downgrading this now because it is not relevant for the Stretch release. I also just noticed that you are actually not running Debian but a spin called

Bug#861536: runit-init: Cannot reboot or shutdown after installing (or removing) the package.

Hi Matthew! > I ran `apt install runit-init` and then attempted to reboot with > `/sbin/reboot`, `/sbin/poweroff`, `init 0` & `init 6`, all to no > effect; no error messages were returned and the exit status of all of > the commands was zero. This happens because the computer is still running

Bug#861536: runit-init: Cannot reboot or shutdown after installing (or removing) the package.

Package: runit-init Version: 2.1.2-9 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? I ran `apt install runit-init` and then attempted to reboot with `/sbin/reboot`, `/sbin/poweroff`, `init 0` & `init 6`, all to no effect; no