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.
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
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.
*t
PS: I'm sending a Cc: to the other reporters to ask them whether they
did remove zeroconf instead of purging it...
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable'), (50, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.4.22
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages zeroconf depends on:
ii ifupdown 0.6.7 high level tools to configure netw
hi iproute 20051007-3 Professional tools to control the
ii libc6 2.3.5-13 GNU C Library: Shared libraries an
zeroconf recommends no packages.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
