Bug#474515: Switching console-tolls to kbd breaks because of insserv

2009-04-15 Thread Petter Reinholdtsen
[Jan Hauke Rahm]
 Hi Petter,
 
 since you're pushing dependency based boot sequences as a release
 goal, is there any news on this issues? insserv in sid wouldn't
 allow me to be used because of the very same reason Philipp
 described: conflicting console-screen
 
 I habe console-tools removed and kbd installed.

I suspect the correct fix is for kdb and console-tools to not provide
the same facility.

Happy hacking,
-- 
Petter Reinholdtsen



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#474515: Switching console-tolls to kbd breaks because of insserv

2009-04-15 Thread Jan Hauke Rahm
On Wed, Apr 15, 2009 at 08:46:11AM +0200, Petter Reinholdtsen wrote:
 [Jan Hauke Rahm]
  Hi Petter,
  
  since you're pushing dependency based boot sequences as a release
  goal, is there any news on this issues? insserv in sid wouldn't
  allow me to be used because of the very same reason Philipp
  described: conflicting console-screen
  
  I habe console-tools removed and kbd installed.
 
 I suspect the correct fix is for kdb and console-tools to not provide
 the same facility.

Okay, then this is a serious bug in either one of the packages since it
was a release goal?

But how is insserv going to handle those situations anyways? I suppose
this kind of issues will come up every once in a while at least in sid.
So there has to be a solution from insserv or insserv isn't usable in
sid. Or am I missing something here?

Hauke


signature.asc
Description: Digital signature


Bug#474515: Switching console-tolls to kbd breaks because of insserv

2009-04-15 Thread Petter Reinholdtsen
[Jan Hauke Rahm]
 Okay, then this is a serious bug in either one of the packages since
 it was a release goal?

Nope, release goals do not increase the severity that much.  I suspect
at most severity important would be appropriate.

 But how is insserv going to handle those situations anyways? I
 suppose this kind of issues will come up every once in a while at
 least in sid.  So there has to be a solution from insserv or insserv
 isn't usable in sid. Or am I missing something here?

I believe you are missing the point, yes.  The scripts should not
provide other scripts facility.  Multiple scripts providing the same
service should be handled by virtual facilities, not by allowing
insserv to accept conflicting provides.

Happy hacking,
-- 
Petter Reinholdtsen



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#474515: Switching console-tolls to kbd breaks because of insserv

2009-04-14 Thread Jan Hauke Rahm
Hi Petter,

since you're pushing dependency based boot sequences as a release
goal, is there any news on this issues? insserv in sid wouldn't allow me
to be used because of the very same reason Philipp described:
conflicting console-screen

I habe console-tools removed and kbd installed.

Hauke

On Wed, Aug 06, 2008 at 11:46:13AM +0200, Philipp Matthias Hahn wrote:
 Package: insserv
 Followup-For: Bug #474515
 
 Today I switched from console-tools to kbd to test something, which
 failed because both /etc/init.d/console-screen.{kbd.,}sh provide
 console-screen:
 
   Richte kbd ein (1.14.1-4) ...
   insserv: script console-screen.kbd.sh: service console-screen already 
 provided!
   insserv: exiting now!
   dpkg: Fehler beim Bearbeiten von kbd (--configure):
Unterprozess post-installation script gab den Fehlerwert 1 zurück
   Fehler traten auf beim Bearbeiten von:
kbd
   E: Sub-process /usr/bin/dpkg returned an error code (1)
 
 This is because I only removed console-tools, but didn't purge it,
 because I don't know yet, if kbd solves my problem I currently have with
 console-tools.
 
 So it's more complicated for insserv, because there may exists old
 init.d scripts from removed packages, which aren't actually used
 because their test -x $DAEMON test just disables them during run-time.
 
 Probably insserv should only warn about multiple packages providing the
 same service, and only start services depending on any X after all X
 have been started.


signature.asc
Description: Digital signature


Bug#474515: Switching console-tolls to kbd breaks because of insserv

2008-08-06 Thread Philipp Matthias Hahn
Package: insserv
Followup-For: Bug #474515

Today I switched from console-tools to kbd to test something, which
failed because both /etc/init.d/console-screen.{kbd.,}sh provide
console-screen:

Richte kbd ein (1.14.1-4) ...
insserv: script console-screen.kbd.sh: service console-screen already 
provided!
insserv: exiting now!
dpkg: Fehler beim Bearbeiten von kbd (--configure):
 Unterprozess post-installation script gab den Fehlerwert 1 zurück
Fehler traten auf beim Bearbeiten von:
 kbd
E: Sub-process /usr/bin/dpkg returned an error code (1)

This is because I only removed console-tools, but didn't purge it,
because I don't know yet, if kbd solves my problem I currently have with
console-tools.

So it's more complicated for insserv, because there may exists old
init.d scripts from removed packages, which aren't actually used
because their test -x $DAEMON test just disables them during run-time.

Probably insserv should only warn about multiple packages providing the
same service, and only start services depending on any X after all X
have been started.

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

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

Versions of packages insserv depends on:
ii  debconf [debconf-2.0]1.5.23  Debian configuration management sy
ii  libc62.7-13  GNU C Library: Shared libraries
ii  sysv-rc  2.86.ds1-60 System-V-like runlevel change mech

insserv recommends no packages.

Versions of packages insserv suggests:
pn  bootchart none (no description available)

-- debconf information:
* insserv/enable: true



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]