Processed: this is an update-rc.d bug, really

2003-12-29 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 reassign 208569 sysv-rc
Bug#208569: apache2-mpm-prefork: starts before name server
Bug reassigned from package `apache2-mpm-prefork' to `sysv-rc'.

 retitle 208569  Can't change the startup time via update-rc.d
Bug#208569: apache2-mpm-prefork: starts before name server
Changed Bug title.

 thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)




Re: Processed: this is an update-rc.d bug, really

2003-12-29 Thread Miquel van Smoorenburg
reassign 208569 apache2-mpm-prefork
thanks

On 2003.12.29 16:03, Debian Bug Tracking System wrote:
 Processing commands for [EMAIL PROTECTED]:
 
  reassign 208569 sysv-rc
 Bug#208569: apache2-mpm-prefork: starts before name server
 Bug reassigned from package `apache2-mpm-prefork' to `sysv-rc'.
 
  retitle 208569  Can't change the startup time via update-rc.d
 Bug#208569: apache2-mpm-prefork: starts before name server
 Changed Bug title.
 
  thanks
 Stopping processing here.

It's not a bug, it's a feature. It works exactly as documented. If your
package installed the links with the wrong sequence number, it's the
responsibility of the package to detect and fix this in the postinst
of the new version.

This is admittedly not trivial. But it's how it works.

Mike.




Processed: Re: Processed: this is an update-rc.d bug, really

2003-12-29 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 reassign 208569 apache2-mpm-prefork
Bug#208569: Can't change the startup time via update-rc.d
Bug reassigned from package `sysv-rc' to `apache2-mpm-prefork'.

 thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)




Bug#208569: Processed: this is an update-rc.d bug, really

2003-12-29 Thread Thom May
* Miquel van Smoorenburg ([EMAIL PROTECTED]) wrote :
 It's not a bug, it's a feature. It works exactly as documented. If your
 package installed the links with the wrong sequence number, it's the
 responsibility of the package to detect and fix this in the postinst
 of the new version.
 
 This is admittedly not trivial. But it's how it works.
 
Um, eww. Oh well. It'd be nice if in the future you could tell update-rc.d
to do it for you - something like:
update-rc.d -u name new-seq old-seq and only have update-rc.d do it if
the old number matched?
Cheers,
-Thom




Bug#208569: Processed: this is an update-rc.d bug, really

2003-12-29 Thread Miquel van Smoorenburg
On Mon, 29 Dec 2003 17:24:11, Thom May wrote:
 * Miquel van Smoorenburg ([EMAIL PROTECTED]) wrote :
  It's not a bug, it's a feature. It works exactly as documented. If your
  package installed the links with the wrong sequence number, it's the
  responsibility of the package to detect and fix this in the postinst
  of the new version.
  
  This is admittedly not trivial. But it's how it works.
  
 Um, eww. Oh well. It'd be nice if in the future you could tell update-rc.d
 to do it for you - something like:
 update-rc.d -u name new-seq old-seq and only have update-rc.d do it if
 the old number matched?

I'm thinking of adding something like that to update-rc.d, for example
a -l flag (list) that shows the current settings for a script, e.g.
update-rc.d -l nis would output

nis start 19 2 3 4 5 . stop 19 0 1 6 .

(why that syntax? That's actually the command line syntax). With that
in place you can check for the wrong config and fix it.

There are already bugs open against sysvinit requesting something like that.
See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=179210

Mike.