Hide Forgot
+++ This bug was initially created as a clone of Bug #913168 +++ The dependency added in this commit does not seem right: commit 661b35b0ba7b3752e02261c0ddf601a826102d7e Author: Matthias Clasen <mclasen@redhat.com> Date: Fri Feb 1 15:26:42 2013 -0500 tighten inter-subpackage symlinks ... @@ -247,6 +249,7 @@ Mono programs that use avahi-ui. %package libs Summary: Libraries for avahi run-time use +Requires: %{name} = %{version}-%{release} The main package already has a versioned dependency on the avahi-libs subpackage, which is alright. But the dependency in the opposite direction is wrong. [...] This problem has been corrected on Fedora 20+, but the correction needs to be backported to RHEL-7.
Minor specfile only change. Proposing for RHEL-7.2 fastrack. Unfortunately it is too late for RHEL-7.1.
http://pkgs.devel.redhat.com/cgit/rpms/avahi/commit/?h=rhel-7.1&id=6b6b15c555685770464af89f4c5e3febac341750 -> MODIFIED
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-0603.html
I don't know how this bug was fixed, but avahi is completely un-upgradeable from 0.6.31-13.el7 to 0.6.31-14.el7, with yum. Error: avahi-libs conflicts with avahi-0.6.31-14.el7.x86_64
By that I mean that apparently one has to force-remove avahi, before upgrading the libraries (and then optionally reinstalling avahi): # rpm --erase --nodeps avahi
Can you please provide a list of avahi packages on your system and yum error output when you try to upgrade avahi?
I'm sorry, I can't reproduce those errors any longer. I worked it around as described in comment 20. The update I tried to exec was from 0.6.31-13.el7 to 0.6.31-14.el7. That said, I've seen this kind of error with other (independent) packages at other times. If there is an incorrect circular dependency between packages, and that cycle is broken in a later spec update, I guess it might not be possible to perform update at all, without manually breaking the cycle first in the installed rpmdb. BTW: while I was googling for a prior report, I found bug 1199462. That report seems to capture a very similar (if not exactly same) update error, except it seems to attribute the error to gnome-shell-browser-plugin. In my case, gnome-shell-browser-plugin was nowhere around, I just got the avahi conflicts that are listed in bug 1199462 comment 0,
Sorry, that should have been a period (.). I don't have anything else to add.