Debian Bug report logs - #561627
sysvinit ALWAYS replaces upstart on dist-upgrade

version graph

Package: sysvinit; Maintainer for sysvinit is Debian sysvinit maintainers <pkg-sysvinit-devel@lists.alioth.debian.org>; Source for sysvinit is src:sysvinit.

Reported by: Matthew Grant <matthewgrant5@gmail.com>

Date: Fri, 18 Dec 2009 20:45:02 UTC

Severity: normal

Merged with 525141

Found in version sysvinit/2.87dsf-8

Reply or subscribe to this bug.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to debian-bugs-dist@lists.debian.org, matthewgrant5@gmail.com, Debian sysvinit maintainers <pkg-sysvinit-devel@lists.alioth.debian.org>:
Bug#561627; Package sysvinit. (Fri, 18 Dec 2009 20:45:05 GMT) Full text and rfc822 format available.

Acknowledgement sent to Matthew Grant <matthewgrant5@gmail.com>:
New Bug report received and forwarded. Copy sent to matthewgrant5@gmail.com, Debian sysvinit maintainers <pkg-sysvinit-devel@lists.alioth.debian.org>. (Fri, 18 Dec 2009 20:45:05 GMT) Full text and rfc822 format available.

Message #5 received at submit@bugs.debian.org (full text, mbox):

From: Matthew Grant <matthewgrant5@gmail.com>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: sysvinit ALWAYS replaces upstart on dist-upgrade
Date: Sat, 19 Dec 2009 09:42:02 +1300
Package: sysvinit
Version: 2.87dsf-8
Severity: normal

I should be able to install the system /sbin/init I want, not one that is
forced because it is 'essential'.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.31-1-686 (SMP w/1 CPU core)
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages sysvinit depends on:
ii  initscripts                   2.87dsf-8  scripts for initializing and shutt
ii  libc6                         2.10.2-2   GNU C Library: Shared libraries
ii  libselinux1                   2.0.89-4   SELinux runtime shared libraries
ii  libsepol1                     2.0.40-2   SELinux library for manipulating b
ii  sysv-rc                       2.87dsf-8  System-V-like runlevel change mech
ii  sysvinit-utils                2.87dsf-8  System-V-like utilities

sysvinit recommends no packages.

sysvinit suggests no packages.

-- no debconf information




Information forwarded to debian-bugs-dist@lists.debian.org, Debian sysvinit maintainers <pkg-sysvinit-devel@lists.alioth.debian.org>:
Bug#561627; Package sysvinit. (Sun, 27 Jun 2010 23:33:05 GMT) Full text and rfc822 format available.

Acknowledgement sent to Kenyon Ralph <kenyon@kenyonralph.com>:
Extra info received and forwarded to list. Copy sent to Debian sysvinit maintainers <pkg-sysvinit-devel@lists.alioth.debian.org>. (Sun, 27 Jun 2010 23:33:05 GMT) Full text and rfc822 format available.

Message #10 received at 561627@bugs.debian.org (full text, mbox):

From: Kenyon Ralph <kenyon@kenyonralph.com>
To: 561627@bugs.debian.org, 525141@bugs.debian.org
Subject: these two bugs are the same, but filed against different packages
Date: Sun, 27 Jun 2010 16:31:57 -0700
[Message part 1 (text/plain, inline)]
These two bugs are duplicates, but filed against different packages:

 * http://bugs.debian.org/525141 in upstart
 * http://bugs.debian.org/561627 in sysvinit

I'm not sure which package, or maybe both, should be modified to fix
this bug.

-- 
Kenyon Ralph
[signature.asc (application/pgp-signature, inline)]

Information forwarded to debian-bugs-dist@lists.debian.org, Debian sysvinit maintainers <pkg-sysvinit-devel@lists.alioth.debian.org>:
Bug#561627; Package sysvinit. (Tue, 13 Jul 2010 07:45:04 GMT) Full text and rfc822 format available.

Acknowledgement sent to Ira Rice <irarice@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian sysvinit maintainers <pkg-sysvinit-devel@lists.alioth.debian.org>. (Tue, 13 Jul 2010 07:45:04 GMT) Full text and rfc822 format available.

Message #15 received at 561627@bugs.debian.org (full text, mbox):

From: Ira Rice <irarice@gmail.com>
To: 561627@bugs.debian.org, 525141@bugs.debian.org
Subject: Virtual package
Date: Tue, 13 Jul 2010 01:43:48 -0600
[Message part 1 (text/plain, inline)]
I'm just a normal Debian user, not a developer, but couldn't this be solved
by creating a new virtual package, perhaps called init, which would then be
marked as essential, and make sysvinit or upstart a provider of the init
package, as well as any other init implementations which are compatible with
sysvinit style scripts. This way, you could still ensure that you have an
init implementation to be able to boot, but not have this current problem of
sysvinit clobbering upstart.

I'd also think that this could help with the migration to upstart, which has
already been suggested last year. While I do realize that the logic behind
how they operate is different, upstart does provide a sysvinit script
compatibility, so experimenting around with a virtual package for providing
init may be a good transition step. Later, for script migration, you could
then have another package, probably called upstart-initscripts, which could
gradually be built to optimize for upstart use, and eventually replace
initscripts as a requirement for upstart.

Any reason as to why this sort of a solution wouldn't work?
[Message part 2 (text/html, inline)]

Information forwarded to debian-bugs-dist@lists.debian.org, Debian sysvinit maintainers <pkg-sysvinit-devel@lists.alioth.debian.org>:
Bug#561627; Package sysvinit. (Wed, 28 Jul 2010 16:33:06 GMT) Full text and rfc822 format available.

Acknowledgement sent to Ira Rice <irarice@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian sysvinit maintainers <pkg-sysvinit-devel@lists.alioth.debian.org>. (Wed, 28 Jul 2010 16:33:06 GMT) Full text and rfc822 format available.

Message #20 received at 561627@bugs.debian.org (full text, mbox):

From: Ira Rice <irarice@gmail.com>
To: 561627@bugs.debian.org
Subject: Re: Virtual package
Date: Wed, 28 Jul 2010 10:29:38 -0600
I'll just mention a second naming possibility for a virtual package,
since this might come up later.

Having a virtual package for init scripts would be rather convenient
for the LSB as well, IMO, since the LSB requires that you use a System
V compatible initialization script, but doesn't exactly require you to
use sysvinit as far as I know. So, if no one likes the init package
name, then lsb-init might be an acceptable alternative. This is also
one of the reasons why upstart has a sysv compatible version (the
upstart-compat-sysv package in Ubuntu), since otherwise, it'd make it
impossible to use upstart and keep a LSB compatible configuration.

Now, it might not be perfect to just have the lsb-init package used
even in cases where the user doesn't care about containing LSB
compatibility, but it's something to take into consideration. I still
think that this would be the best sort of solution going forward to
solve this problem, and probably the most flexible as well.




Merged 525141 561627 Request was from Steve Langasek <steve.langasek@ubuntu.com> to control@bugs.debian.org. (Sat, 30 Nov 2013 06:12:10 GMT) Full text and rfc822 format available.

Send a report that this bug log contains spam.


Debian bug tracking system administrator <owner@bugs.debian.org>. Last modified: Sat Apr 19 18:46:56 2014; Machine Name: buxtehude.debian.org

Debian Bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.