Re: Yum dependency resolving & remove_leaf_only

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 15. 10. 2013 at 04:33:08, P J P wrote:
> > On Monday, 14 October 2013 8:05 PM, Eric H. Christensen
> > <sparks@xxxxxxxxxxxxxxxxx> wrote: I believe he is assuming that xchat has
> > a direct relationship with bluez which, I'm guessing here as I haven't
> > checked, probably isn't the case. Because bluez affects something that
> > xchat depends on xchat is getting thrown into the pile of things that
> > will break without bluez.  Dependencies aren't always 1:1...
> 
>    Yes, I understand that Xchat is not directly dependent on bluez; It is
> being a victim of associative dependency, something like
> 
> bluez <= gnome-bluetooth(libgnome-bluetooth-applet.so.0) <= gnome-shell <=
> libnotify.so.4 <= xchat
> 
> 
> My original question was if this is due to a packaging error  or  if yum's
> dependency resolving algorithm is at fault. Because with
> remove_leaf_only=1, if you try to remove individual packages,
> 
>     # yum remove bluez,
>     # yum remove gnome-bluetooth
>     # yum remove pulseaudio-module-bluetooth
> 
> None of  them work. But if you try to remove all 3 together
> 
>     # yum remove gnome-bluetooh bluez pulseaudio-module-bluetooth
> 
> Yum prompts you to remove bluez  ->
> https://lists.fedoraproject.org/pipermail/devel/2013-October/190101.html

Yum's behavior is absolutely correct, it even reports you reasons why it 
doesn't uninstall individual packages (in general none of them is a leaf 
package).

In this particular case the problem is also the circular dependency between 
bluez and gnome-bluetooth [1]. At this point I'm not sure about pulseaudio-
module-bluetooth but I suspect something similar going on there.

Even though yum might handle the resolution a little better (and dnf probably 
will do that, feel free to check it), the ultimate culprit here is a very poor 
packaging and both dnf and yum have only a limited set of options what to do 
in such cases. Usually both do the right thing, as yum did in this case.

Thanks
Jan


[1]
$ repoquery --whatrequires gnome-bluetooth | grep bluez | tail -n 1
bluez-0:4.101-9.fc19.x86_64
$ repoquery --whatrequires bluez | grep gnome-bluetooth | tail -n 1
gnome-bluetooth-1:3.8.2.1-1.fc19.x86_64




-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct





[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux