Bug#756023: init: Please drop Essential:yes from init metapackage
Am 25.07.2014 16:48, schrieb Dimitri John Ledkov: > In that case, apart from a new name and new source-package, why do we > need two identical "metapackages"? > This seems utterly redundant and more complicated then simply using > sysvinit package for the transition. Ok, whatever. Well, read the transition plan I referenced in my other reply. The point is, that we want different behaviour depending on whether you upgrade or do a fresh installation. The sysvinit package in jessie won't be Essential: yes / Priority: required anymore (upload for that is pending). It will become an (optional) transitional package with the only purpose being to ensure a smooth upgrade and providing a safety net. Hope that clears things up. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#756023: init: Please drop Essential:yes from init metapackage
On 25 July 2014 15:28, Ansgar Burchardt wrote: > Control: severity -1 wishlist > > On 07/25/2014 16:19, Dimitri John Ledkov wrote: >> "init" metapackage is marked essential, even though none of the inits >> are currently essential. There are environments in which no init is >> needed, e.g. chroots and minimal/exec-only containers (like >> docker). Also one shouldn't be making 3 inits transitively essential, >> when they currently are not. > > They are already transitively essential: > >Package: sysvinit >Version: 2.88dsf-53.2 >Essential: yes >[...] >Pre-Depends: sysvinit-core | upstart | systemd-sysv > > init is intended to replace the sysvinit package; it doesn't change > anything about init systems being essential or not. > In that case, apart from a new name and new source-package, why do we need two identical "metapackages"? This seems utterly redundant and more complicated then simply using sysvinit package for the transition. Ok, whatever. -- Regards, Dimitri. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756023: init: Please drop Essential:yes from init metapackage
severity 756023 wishlist thanks Hi, Am 25.07.2014 16:19, schrieb Dimitri John Ledkov: > Package: init > Version: 1.20 > Severity: serious > Tags: patch > > Dear Maintainer, > > "init" metapackage is marked essential, even though none of the inits > are currently essential. There are environments in which no init is > needed, e.g. chroots and minimal/exec-only containers (like > docker). Also one shouldn't be making 3 inits transitively essential, > when they currently are not. Well, see the transition plan as outlined and discussed on debian-devel [1]. The new "init" metapackage takes over the role of the sysvinit package, which (currently) is Essential: yes and Priority: required. The point here is to ensure that an init system is installed at all times. Dropping the Essential flag would counter that. The question if "init" needs to be Essential came up as well. The current sysvinit package in wheezy is Essential so packages do rely on tools like /sbin/runlevel to be existing and working. Dropping the Essential flag would break that assumption and as Tollef said would require an archive wide cleanup before we could drop this flag. I'm marking this as a whishlist bug as I see no justitification for it being serious. Regards, Michael [1] https://lists.debian.org/debian-devel/2014/07/msg00611.html [2] https://lists.debian.org/debian-devel/2014/07/msg00631.html -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#756023: init: Please drop Essential:yes from init metapackage
Control: severity -1 wishlist On 07/25/2014 16:19, Dimitri John Ledkov wrote: > "init" metapackage is marked essential, even though none of the inits > are currently essential. There are environments in which no init is > needed, e.g. chroots and minimal/exec-only containers (like > docker). Also one shouldn't be making 3 inits transitively essential, > when they currently are not. They are already transitively essential: Package: sysvinit Version: 2.88dsf-53.2 Essential: yes [...] Pre-Depends: sysvinit-core | upstart | systemd-sysv init is intended to replace the sysvinit package; it doesn't change anything about init systems being essential or not. Ansgar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756023: init: Please drop Essential:yes from init metapackage
Package: init Version: 1.20 Severity: serious Tags: patch Dear Maintainer, "init" metapackage is marked essential, even though none of the inits are currently essential. There are environments in which no init is needed, e.g. chroots and minimal/exec-only containers (like docker). Also one shouldn't be making 3 inits transitively essential, when they currently are not. Patch attached. >From 99cde7b65ed839df2250f9278847ca20c64e6fd6 Mon Sep 17 00:00:00 2001 From: Dimitri John Ledkov Date: Fri, 25 Jul 2014 15:15:33 +0100 Subject: [PATCH] Drop "Essential: yes" from "init" metapackage. None of the init's are currently essential, and there is no use for init in many environments, e.g. chroots / exec-only containers (docker). --- debian/changelog | 8 debian/control | 1 - 2 files changed, 8 insertions(+), 1 deletion(-) diff --git a/debian/changelog b/debian/changelog index e01de73..8d68f82 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +init-system-helpers (1.21) UNRELEASED; urgency=medium + + * Drop "Essential: yes" from "init" metapackage. None of the init's are +currently essential, and there is no use for init in many +environments, e.g. chroots / exec-only containers (docker). + + -- Dimitri John Ledkov Fri, 25 Jul 2014 15:14:34 +0100 + init-system-helpers (1.20) unstable; urgency=medium [ Michael Stapelberg ] diff --git a/debian/control b/debian/control index c9fe0df..ef8beec 100644 --- a/debian/control +++ b/debian/control @@ -41,7 +41,6 @@ Description: debhelper add-on to handle systemd unit files Package: init Section: metapackages Architecture: any -Essential: yes Priority: required Pre-Depends: sysvinit-core | systemd-sysv [linux-any] | upstart [linux-any] Description: System-V-like init utilities - metapackage -- 2.0.1 Regards, Dimitri.
