[Pkg-sysvinit-devel] Bug#589561: init.d/Scripts are not considered conffiles

[Ralph Ulrich]

Am 18.07.2010 20:19, schrieb Petter Reinholdtsen:
> [Ralph Ulrich]
>> Although #grep '^/etc/init.d/' /var/lib/dpkg/info/*.conffiles shows
>> all packages do consider init.d/scripts as conffiles.  This might be
>> non-intuitive for Debian users! In fact it will provide, and has,
>> endless new bug reportings for packages not totally purged, if there
>> was installed an alternative conflicting resource.
>>
>> As of the existence of /etc/insserv/overrides there already is the
>> place to modify lsb-headers. Why not accepting the whole script from
>> there if user modification was needed ?  And remove all
>> /etc/init.d/Scipts when deinstalling !
>
> Can you provide more explanation?  I failed completely to understand
> what you mean.
>
> Note that a recent version of sysv-rc will only refuse to migrate to
> dependency based boot sequencing when obsolete init.d scripts are
> present if a problem is detected in the boot sequence.  Not sure if
> that is relevant for your report, but thought it best to mention it.
>
> Happy hacking,

I looked over the whole list of bugs:
- http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584082
would not occure...
- http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584086
updating a changed LSB-header!

I don't find all of the bugs today evening, but I have seen many of 
these the long afternoon I studied the list.

For a user removing a package but not purging, it is totally 
non-intuitive that remaining start scripts may cause some trouble in the 
future. These scripts are seen as NOT-editable und thus considered to be 
NO conffiles.

How do you handle a not removed init.d/SCRIPT, that is reused by the 
user for granted to implement something new he _wants_ ?