Package: zeroconf Followup-For: Bug #347431 I ran into this too after doing aptitude remove zeroconf.
I'm not sure if the suggestion that the file is a holdover from an old version is still live, but I'll note this was on a system created in the last month or two. I believe that previous analyses have identified the problem as being that /etc/netnwork/if-up.d/zeroconf is a configuration file, and so remains after a remove. If it is not possible/safe/policy-compliant to delete the file, my understanding is that the usual way to deal with this is have some kind of text for the existence of the file or package before its invocation. I think doing this would eliminate the problem--or at least the one I'm seeing. Maybe the problem on boot up is separate. I'll just delete the file. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (990, 'stable'), (50, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.4.27advncdfs Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
