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.
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
-- 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
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:
4 matches
Mail list logo