zeroconf (0.8-3) unstable; urgency=low
* Each netlink RTM_NEWLINK was causing zeroconf to re-probe for a new
address. Only do that if the NEWLINK message is for our interface
zeroconf (0.8-2) unstable; urgency=low
* Only run a single instance per device
zeroconf (0.8-1) unstable; urgency=low
* New upstream release
* Correctly detach from controlling terminals and don't go into loops
causing intialisation to be (significantly) delayed.
(Closes: #349340, #353113)
* If the package has been removed (not purged) don't run the daemon.
(Closes: #359195, #347431)
* Remove detrious left over from previous versions
(Closes: #347431)
* Upstream notes rewritten ARP logic will fix these
(Closes: #340186, #334027)
* Upstream notes broadcast address is correctly set
(Closes: #360607)
* If being removed or purged, terminate any currently running daemons
(Closes: #347301)
-- J?r?mie Corbier <email address hidden> Tue, 25 Apr 2006 13:22:30 +0100