On Mon, Mar 20, 2006 at 09:14:40PM +0100, Tomas Pospisek wrote: > On Mon, 20 Mar 2006, Justin Pryzby wrote: > > >>---------- Forwarded message ---------- > >>Date: Mon, 20 Mar 2006 19:43:58 +0100 > >>From: Tomas Pospisek <[EMAIL PROTECTED]> > >>To: Debian Bug Tracking System <[EMAIL PROTECTED]> > >>Subject: /etc/network/if-up.d/zeroconf doesn't check whether zeroconf been > >> removed > >> > >>Package: zeroconf > >>Version: 0.6.1-1 > >>Followup-For: Bug #347431 > >> > >>One of the causes I can see for the problem is that if you install, and > >>the *remove* zeroconf, instead of *purging* it, > >>/etc/network/if-up.d/zeroconf, beeing a configuration file remains > >>there, still trying to call /usr/sbin/zeroconf. > > > >Ah yes indeed. Policy 9.3.2 has this: > > > >| Therefore, you should include a test statement at the top of the > >| script, like this: > >| > >| test -f program-executed-later-in-script || exit 0 > >| http://www.us.debian.org/doc/debian-policy/ch-opersys.html#s-sysvinit > > Yes, but this will still uselessly execute the whole script except for the > last line :-/ Huh? No it wont. It will exit 0 since /u/s/zeroconf DNE.
> >>I don't have a really good suggestion how this could be fixed best - > >>clearly when zeroconf as a package is removed, it makes no sense to call > >>/etc/network/if-up.d/zeroconf at all. OTOH you shouldn't remove it > >>either since, being a configuration file (or is it?) the user might have > > > >Everything in /etc/ is a configuration file (though not all are > >automatically handled "conffiles"). > > > >>modified it. Maybe it'd be best to set a switch somewhere, such as in > >>/etc/defaults/zeroconf and check there whethere anything should be run > >>and, if removing zeroconf*deb setting that switch to off. > > > >Note that conffiles can't be touched at all by any maintainer scripts. > > Well I guess "ucf - Update Configuration File: preserves user changes to > config files" can be used for that? Kind of. That isn't the problem here though. Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
