On 06.03.2013 00:20, Steve Langasek wrote: > FWIW, I agree with Andrew that this isn't an interface change; this is a > latent bug in the avahi hook which has merely been exposed by this behavior > change in ifupdown. ifupdown supports more address families than ipv4 and > ipv6 (specifically, it supports ipx); if a user had configured a system with > only ipx interfaces statically configured (as unlikely as that would be in > the 21st century), it appears that avahi would have misbehaved in the same > way.
A quick grep over all unpacked packages shipping ifupdown hooks show 60 hook scripts which don't have ADDRFAM set. I haven't checked them individually, though. > I don't know why these --all calls are a useful thing for ifupdown to do, > but I do think it's the responsibility of the avahi package to sensibly > ignore values of $ADDRFAM that it doesn't understand. What I'm not happy about is, that such a change was made without notifiying the affected package maintainers *in advance* with clear instructions how to address this. Ideally via the BTS. Such documentation and instructions are still missing. Andrew, care to explain what a package maintainer is supposed to consider when shipping such a hook? The existing documentation is rather scarce on this topic. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
