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 <x...@ubuntu.com>
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 <x...@ubuntu.com>  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.

Reply via email to