RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 684971 - create avahi-libs sub-package
Summary: create avahi-libs sub-package
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: avahi
Version: 6.2
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Lennart Poettering
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On: 530087
Blocks: 684970
TreeView+ depends on / blocked
 
Reported: 2011-03-14 21:31 UTC by Guil Barros
Modified: 2018-11-14 14:05 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 530087
Environment:
Last Closed: 2011-03-14 21:36:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Guil Barros 2011-03-14 21:31:27 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.

Comment 3 Guil Barros 2011-03-14 21:36:11 UTC
My bad, this is already done.


Note You need to log in before you can comment on or make changes to this bug.