]] Roger Leigh
> I'm not sure myself. Probably because it's potentially dangerous
> since it would want to replace it with a symlink, and that might
> result in dataloss. Do you have an example of the virtual
> facility problem?
Why would it want to replace it with a symlink? AIUI, insserv just
renames the files in /etc/rcN.d ?
For the latter, I seem to have:
: tfheen@qurzaw /etc/init.d > grep Provides bootlog*
bootlogd:# Provides: bootlogd
bootlogs:# Provides: bootlogs
bootlogs.sh:# Provides: bootlogs
which makes it complain about something already provided.
> Both of these are insserv bugs rather than sysv-rc bugs, BTW, so
> reassigning.
Sure.
> > What I'm complaining about is it's continued insistence on trying to
> > convert to another way of ordering the links when it's unable to do so,
> > especially when said complaining is in the form of a debconf error on
> > each and every upgrade of the package.
>
> Have you observed this on more than one system?
It complaining repeatedly on upgrade? That's clearly intentional from
looking at the sysv-rc postinst:
try_to_convert() {
PROBLEMATIC=""
if is_unsafe_to_activate ; then
# Make sure the note is seen every time
db_fset sysv-rc/unable-to-convert seen false
db_subst sysv-rc/unable-to-convert PROBLEMATIC "$PROBLEMATIC"
db_input critical sysv-rc/unable-to-convert || [ $? -eq 30 ]
db_go || true
return 1
[…]
> I've not seen either of these problems myself, and I've not seen any
> bugs filed recently about either issue.
There's an old bug filed about it complaining each time, at least. I
could of course file a new bug, but that'd just be a duplicate, so I
don't. :-)
> There was also a recent insserv update, BTW. Are both problems still
> reproducible with the current unstable insserv?
No, this is wheezy. Haven't tried with unstable.
--
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
