Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 684970

Summary: create avahi-libs sub-package
Product: Red Hat Enterprise Linux 5 Reporter: Guil Barros <gbarros>
Component: avahiAssignee: Lennart Poettering <lpoetter>
Status: CLOSED CURRENTRELEASE QA Contact: qe-baseos-daemons
Severity: medium Docs Contact:
Priority: low    
Version: 5.7CC: bnocera, cww, lpoetter, mclasen, twaugh, warthog9, yaneti
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 530087 Environment:
Last Closed: 2011-10-24 02:01:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 530087, 684971    
Bug Blocks: 668957, 719046    

Description Guil Barros 2011-03-14 21:29:19 UTC
+++ This bug was initially created as a clone of Bug #530087 +++

Description of problem:
In the same way that cups-libs is a sub-package of cups, with the server part being in the main 'cups' package and the libraries in 'cups-libs', I think avahi needs to package its libraries in a separate avahi-libs sub-package.

Version-Release number of selected component (if applicable):
avahi-0.6.25-5.fc12.x86_64

How reproducible:
100%

Steps to Reproduce:
1.rpm --test -e avahi --allmatches 2>&1| grep cups-1
  
Actual results:
	libavahi-client.so.3()(64bit) is needed by (installed) cups-1:1.4.1-10.fc12.x86_64
	libavahi-common.so.3()(64bit) is needed by (installed) cups-1:1.4.1-10.fc12.x86_64

Expected results:
No output.

Additional info:
The avahi package should be installed by comps, not by dependencies.  In a similar way, cups is installed by comps instead of being a dependency of e.g. gtk2 which uses libcups.

Original bug report: bug #513559

--- Additional comment from triage.org on 2009-11-16 08:57:43 EST ---


This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

--- Additional comment from mclasen on 2009-12-07 23:43:30 EST ---

Makes sense to me, but we probably want to target F13 for this now.

--- Additional comment from yaneti on 2009-12-08 01:54:05 EST ---

*** Bug 542775 has been marked as a duplicate of this bug. ***

--- Additional comment from triage.org on 2010-03-15 08:57:42 EDT ---


This bug appears to have been reported against 'rawhide' during the Fedora 13 development cycle.
Changing version to '13'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

--- Additional comment from svidal on 2010-04-12 14:42:44 EDT ---

pinging on this one again - subject came up on an irc discussion and I remembered this bug.

I realize it is too late for F13 at this point - but maybe rawhide?
thanks

--- Additional comment from warthog19 on 2010-04-12 14:49:30 EDT ---

I'd argue that this needs to happen in F13, heck I'd argue this needs to get back ported to F11 and F12 (depending on when support gets dropped for F11).  It's just the fact that avahi is going to get turned on for a lot of server installs that aren't expecting it (and arguably a lot of desktop / laptop installs that might not want it as well).

--- Additional comment from bnocera on 2010-04-14 05:01:57 EDT ---

I don't see the point given that it'll be blocked off by default, by the firewall, and that you'd need to explicitely unblock it from the firewall for it to do anything. At that point, you might as well be disabling it running altogether.

--- Additional comment from warthog19 on 2010-04-14 14:37:07 EDT ---

(In reply to comment #7)
> I don't see the point given that it'll be blocked off by default, by the
> firewall, and that you'd need to explicitely unblock it from the firewall for
> it to do anything. At that point, you might as well be disabling it running
> altogether.    

Your making the assumption that the firewall is either running at all, running in the default configuration or that an attack at the local system is impossible.  There are specific reasons why an end user, in particular servers, don't run firewalls, or run firewalls that are incredibly targeted and specific.  Depending on your firewall to protect you against this particular problem means you've already failed.

Here's the fundamental problem that started this whole debate, if I as a server administrator am not running avahi, have a machine on the public internet and such suddenly decide to install ImageMagick, a completely unrelated package that should *NOT* involve any new services I am suddenly bringing in avahi and it's starting by default.  It's the completely unexpected implication that anything I want that needs ghostscript will mean that I not only suddenly have bloat installed, but that I'm not by default running a service I wasn't expecting.

--- Additional comment from bnocera on 2010-04-19 12:24:07 EDT ---

Done in avahi-0.6.25-7.fc14.