Activity log for bug #192258

Date Who What changed Old value New value Message
2008-02-15 22:43:47 Loye Young bug added bug
2008-02-15 22:48:49 Loye Young title avahi should be downgraded to Recommend dependency avahi should be downgraded to Suggests dependency
2008-02-15 22:51:00 Loye Young bug assigned to kubuntu-meta (Ubuntu)
2008-02-15 22:51:19 Loye Young bug assigned to xubuntu-meta (Ubuntu)
2008-02-15 22:52:17 Loye Young bug assigned to edubuntu-meta (Ubuntu)
2008-02-15 22:53:02 Loye Young bug assigned to gnome-vfs (Ubuntu)
2008-02-15 23:03:33 Loye Young description Binary package hint: ubuntu-desktop All avahi programs and libraries (and its multicast cousin libnss-mdns) should be downgraded to a Suggests dependency (or at most Recommends). The Debian Policy Manual describes the appropriate uses of the various dependencies: [quote] Depends This declares an absolute dependency. A package will not be configured unless all of the packages listed in its Depends field have been correctly configured. The Depends field should be used if the depended-on package is required for the depending package to provide a significant amount of functionality. Recommends This declares a strong, but not absolute, dependency. The Recommends field should list packages that would be found together with this one in all but unusual installations. Suggests This is used to declare that one package may be more useful with one or more others. Using this field tells the packaging system and the user that the listed packages are related to this one and can perhaps enhance its usefulness, but that installing this one without them is perfectly reasonable [/quote] Avahi does not provide any functionality under most circumstances (because the rest of the local network has to be configured for it), and even in circumstances when it does provide some functionality, it's not an essential function. Certainly, reasonable minds can differ on whether it should be installed at all. Many of us in the community (myself included) believe that [avahi / zeroconf / rendezvous / bonjour] is fundamentally a bad idea and should not be implemented at all, but other reasonable minds like avahi. This is exactly the situation for which Suggests is best suited for. Some in the community are of the opinion that the best solution is to install it, but not enable it by default. From the outset, such an argument essentially agrees that avahi is not an essential or even a strong dependency, which would dictate a Suggests dependency level. Further, avahi-daemon, avahi-autoipd, libavahi-*, and libnss-mdns run processes and scripts that interfere with other programs and make setting up a secure, centrally managed network in a business setting extremely troublesome. It has cost me personally several occasions of spending all night reconfiguring the network of an entire organization, usually when upgrades overwrite configurations. It's not simply a bug in avahi; it is the fundamental nature of avahi to interfere with the networking protocols. This creates havoc with networks configured for stability and security rather than for ease of use. Uninstalling the desktop metapackage is not a reasonable work-around because the metapackage ensures clean and automatic upgrades. While I sympathize with those who want to make the home computer of Mom and Pop "just work" without configuring anything, surely the advocates of avahi can sympathize with those of us who are trying to bring Ubuntu to businesses and organizations. Happy Trails, Loye Young Isaac & Young Computer Company Laredo, Texas http://www.iycc.biz Binary package hint: ubuntu-desktop All avahi programs and libraries (and its multicast cousin libnss-mdns) should be downgraded to a Suggests dependency (or at most Recommends). This is of great importance because business organizations are not installing (*)ubuntu because of the presence of avahi and the difficulty involved in removing it from the installation. The Debian Policy Manual describes the appropriate uses of the various dependencies: [quote] Depends This declares an absolute dependency. A package will not be configured unless all of the packages listed in its Depends field have been correctly configured. The Depends field should be used if the depended-on package is required for the depending package to provide a significant amount of functionality. Recommends This declares a strong, but not absolute, dependency. The Recommends field should list packages that would be found together with this one in all but unusual installations. Suggests This is used to declare that one package may be more useful with one or more others. Using this field tells the packaging system and the user that the listed packages are related to this one and can perhaps enhance its usefulness, but that installing this one without them is perfectly reasonable [/quote] Avahi does not provide any functionality under most circumstances (because the rest of the local network has to be configured for it), and even in circumstances when it does provide some functionality, it's not an essential function. Certainly, reasonable minds can differ on whether it should be installed at all. Many of us in the community (myself included) believe that [avahi / zeroconf / rendezvous / bonjour] is fundamentally a bad idea and should not be implemented at all, but other reasonable minds like avahi. This is exactly the situation for which Suggests is best suited for. Some in the community are of the opinion that the best solution is to install it, but not enable it by default. From the outset, such an argument essentially agrees that avahi is not an essential or even a strong dependency, which would dictate a Suggests dependency level. Further, avahi-daemon, avahi-autoipd, libavahi-*, and libnss-mdns run processes and scripts that interfere with other programs and make setting up a secure, centrally managed network in a business setting extremely troublesome. It has cost me personally several occasions of spending all night reconfiguring the network of an entire organization, usually when upgrades overwrite configurations. It's not simply a bug in avahi; it is the fundamental nature of avahi to interfere with the networking protocols. This creates havoc with networks configured for stability and security rather than for ease of use. Uninstalling the desktop metapackage is not a reasonable work-around because the metapackage ensures clean and automatic upgrades. While I sympathize with those who want to make the home computer of Mom and Pop "just work" without configuring anything, surely the advocates of avahi can sympathize with those of us who are trying to bring Ubuntu to businesses and organizations. Happy Trails, Loye Young Isaac & Young Computer Company Laredo, Texas http://www.iycc.biz
2008-04-17 00:22:18 Oliver Grawert edubuntu-meta: status New Invalid
2008-06-18 13:06:19 Martin Pitt title avahi should be downgraded to Suggests dependency avahi should be downgraded to Recommends:
2008-06-18 13:06:47 Martin Pitt ubuntu-meta: status New In Progress
2008-06-18 13:06:47 Martin Pitt ubuntu-meta: assignee pitti
2008-06-18 13:06:47 Martin Pitt ubuntu-meta: importance Undecided Wishlist
2008-06-18 16:14:11 Martin Pitt ubuntu-meta: status In Progress Fix Committed
2008-06-18 16:14:29 Martin Pitt gnome-vfs: status New Invalid
2008-06-18 16:14:38 Martin Pitt kubuntu-meta: status New Fix Committed
2008-06-18 16:14:55 Martin Pitt xubuntu-meta: status New Fix Committed
2008-06-18 16:48:15 Loye Young bug added attachment 'unnamed' (unnamed)
2008-07-12 11:49:52 Cody A.W. Somerville xubuntu-meta: status Fix Committed Fix Released
2008-07-12 23:02:13 Jonathan Thomas kubuntu-meta: status Fix Committed Fix Released
2008-07-12 23:04:23 Jonathan Thomas ubuntu-meta: status Fix Committed Fix Released