Bug#766187: The inittab interface - Re: Bug#766187: runit: Fails to install runit after fresh install of jessie beta2
On Tue, Dec 09, 2014 at 11:24:11AM +, Gerrit Pape wrote: On Mon, Nov 24, 2014 at 10:08:49PM +, Simon McVittie wrote: On 24/11/14 21:41, Gerrit Pape wrote: Better than (2) would be to make the existence of /etc/inittab still essential for jessie, by moving the corresponding code from sysvinit-core into the essential init package. What do you think? If you go this route, I think initscripts might be a better home for As I wrote above, I actually don't have the time to go any road at all. The packages worked just fine until I learnt that support for the inittab interface is dropped in jessie. I fixed the packages. Now I learnt that the existence of /etc/inittab is no longer essential, next thing breaking my packages - when switching jessie to sysvinit. Please advise whether I should reassign this release critically to the init and sysvinit packages, or upload the ugly workaround to copy sysvinit maintainer script code for generating /etc/inittab into the two affected packages. Hi init and sysvinit maintainers, it looks like I don't get reasonable advise on debian-devel. What is your stand on this? Regards, Gerrit. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766187: The inittab interface - Re: Bug#766187: runit: Fails to install runit after fresh install of jessie beta2
I noticed that my last mail about 766187 being related to 768657 didn't actually go to the bug report. (which was about this bug being related) Anyway, both of these bugs seem to be about providing /etc/inittab in one form or another. Please see KiBi's last entry about providing it via D-I which has gone unanswered. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768657 I'm only sharing this as it would appear there are two separate conversations happening about the same problem. (and i'm assuming that a solution should / would solve both) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766187: The inittab interface - Re: Bug#766187: runit: Fails to install runit after fresh install of jessie beta2
On Sat, Oct 25, 2014 at 09:34:50AM +, Gerrit Pape wrote: On Wed, Oct 22, 2014 at 09:20:46AM +, Gerrit Pape wrote: On Tue, Oct 21, 2014 at 08:29:54AM -0400, Nikolay Hristov wrote: Setting up runit (2.1.2-1) ... grep: /etc/inittab: No such file or directory grep: /etc/inittab: No such file or directory cp: cannot stat ‘/etc/inittab’: No such file or directory dpkg: error processing package runit (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: runit E: Sub-process /usr/bin/dpkg returned an error code (1) Since ages runit hooks into /etc/inittab to provide system wide service supervision. As long as sysvinit provided /etc/inittab and was essential this simply worked. Now on fresh jessie install, no /etc/inittab is created at all. While this alone wouldn't be a problem, because runit provides a simple systemd unit after I learned that there's no backward compatibility to the /etc/inittab interface, it is a problem when switching such an installation from systemd to sysvinit: When switching to sysvinit, the /etc/inittab file is created, but doesn't include the lines enabling the runit supervision. After reboot runit supervision will not be enabled, although the package is installed. This would be a grave bug as other packages depend on this assumption. Any idea on how to fix this? This is far from ideal, but the only easy fix I came up with until now is to copy debian/share/inittab* from the sysvinit source package, as well as the debian/rules logic to install a system-specific inittab template and the postinst logic to create /etc/inittab if it does not exist, into the runit package. A better fix certainly will need more thoughts, coordination, and testing, which I'm afraid I can't work on currently. Anyone? This is not yet resolved, unfortunately. It currently affects at least two packages and a minor number of dependencies: https://bugs.debian.org/766187 and https://bugs.debian.org/767933 Suggestions I got are (1) check whether /etc/inittab exists before adding the service, continue if it doesn't exist, and (2) https://bugs.debian.org/767933#46 (1) seems not to be the solution. When installing default jessie, then installing runit or daemontools-run, and afterwards sysvinit-core, the service supervision will be disabled. There may be a package in jessie that implements (1), I'm not sure what isdnutils does these days. Better than (2) would be to make the existence of /etc/inittab still essential for jessie, by moving the corresponding code from sysvinit-core into the essential init package. What do you think? Regards, Gerrit. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766187: The inittab interface - Re: Bug#766187: runit: Fails to install runit after fresh install of jessie beta2
On 24/11/14 21:41, Gerrit Pape wrote: Better than (2) would be to make the existence of /etc/inittab still essential for jessie, by moving the corresponding code from sysvinit-core into the essential init package. What do you think? If you go this route, I think initscripts might be a better home for inittab. It is depended on by all our supported pid 1 implementations - sysvinit-core, systemd-sysv (via systemd) and upstart - and comes from the same source package as sysvinit, which init does not. S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766187: The inittab interface - Re: Bug#766187: runit: Fails to install runit after fresh install of jessie beta2
On Wed, Oct 22, 2014 at 09:20:46AM +, Gerrit Pape wrote: On Tue, Oct 21, 2014 at 08:29:54AM -0400, Nikolay Hristov wrote: Setting up runit (2.1.2-1) ... grep: /etc/inittab: No such file or directory grep: /etc/inittab: No such file or directory cp: cannot stat ‘/etc/inittab’: No such file or directory dpkg: error processing package runit (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: runit E: Sub-process /usr/bin/dpkg returned an error code (1) Since ages runit hooks into /etc/inittab to provide system wide service supervision. As long as sysvinit provided /etc/inittab and was essential this simply worked. Now on fresh jessie install, no /etc/inittab is created at all. While this alone wouldn't be a problem, because runit provides a simple systemd unit after I learned that there's no backward compatibility to the /etc/inittab interface, it is a problem when switching such an installation from systemd to sysvinit: When switching to sysvinit, the /etc/inittab file is created, but doesn't include the lines enabling the runit supervision. After reboot runit supervision will not be enabled, although the package is installed. This would be a grave bug as other packages depend on this assumption. Any idea on how to fix this? This is far from ideal, but the only easy fix I came up with until now is to copy debian/share/inittab* from the sysvinit source package, as well as the debian/rules logic to install a system-specific inittab template and the postinst logic to create /etc/inittab if it does not exist, into the runit package. A better fix certainly will need more thoughts, coordination, and testing, which I'm afraid I can't work on currently. Anyone? Regards, Gerrit. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766187: The inittab interface - Re: Bug#766187: runit: Fails to install runit after fresh install of jessie beta2
severity 766187 grave quit On Tue, Oct 21, 2014 at 08:29:54AM -0400, Nikolay Hristov wrote: Fresh minimal install of Jessie Beta2 with only SSH server selected in tasksel. Tried to install runit with 'apt-get install runit' and apt-get exits with error message of missing /etc/inittab and leaves it unconfigured. root@tre:~# apt-get install runit [...] Setting up runit (2.1.2-1) ... grep: /etc/inittab: No such file or directory grep: /etc/inittab: No such file or directory cp: cannot stat ‘/etc/inittab’: No such file or directory dpkg: error processing package runit (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: runit E: Sub-process /usr/bin/dpkg returned an error code (1) root@tre:~# Hi, thanks for the report. I not yet have an idea how to fix this, hope you can help finding a solution. Since ages runit hooks into /etc/inittab to provide system wide service supervision. As long as sysvinit provided /etc/inittab and was essential this simply worked. Now on fresh jessie install, no /etc/inittab is created at all. While this alone wouldn't be a problem, because runit provides a simple systemd unit after I learned that there's no backward compatibility to the /etc/inittab interface, it is a problem when switching such an installation from systemd to sysvinit: When switching to sysvinit, the /etc/inittab file is created, but doesn't include the lines enabling the runit supervision. After reboot runit supervision will not be enabled, although the package is installed. This would be a grave bug as other packages depend on this assumption. Any idea on how to fix this? Thanks, Gerrit. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
