#1788 Weird deps in mock build
Closed: Invalid None Opened 14 years ago by hadess.

This is the root.log from gstreamer-plugins-good in F12:

http://koji.fedoraproject.org/koji/getfile?taskID=1350206&name=root.log

As you can see, it mentions xfce4-notifyd, and notification-daemon, neither of those are being pulled in from BRs. Tomas saw the same problem on a gvfs build.


So, gvfs requires gnome-disk-utility-devel, which requires libnotify-devel.
libnotify requires desktop-notification-daemon.
desktop-notification-daemon is a virtual package provided by notification-daemon and
xfce4-notifyd.

xfce4-notifyd provides "Conflicts: notification-daemon", but notification-daemon doesn't provide "Conflicts: xfce4-notifyd" yet as it's a new package.

Now, when yum builds dependency tree, it searches for desktop-notification-daemon and pulls in both possibilities, resulting in a conflict. Adding explicit "BuildRequires: notification-daemon" to gvfs solves the issue and package builds correctly. And since it's just a BuildRequire, it doesn't hurt for the moment.

Question for yum masters: Does it make sense? Would adding "Conflicts: xfce4-notifyd" to notification-daemon solve the issue?

Replying to [comment:1 tbzatek]:

Question for yum masters: Does it make sense? Would adding "Conflicts: xfce4-notifyd" to notification-daemon solve the issue?

Not sure if it will fix the issue or if it's related to yum, but both packages need to conflict with each other since they both provide /usr/share/dbus-1/services/org.freedesktop.Notifications.service

Why does the library require the daemon?

I guess because the libnotify package contains /usr/bin/notify-send, which only works if there is a notification daemon present.

This is just packaging issues, not a releng issue, closing the ticket.

Login to comment on this ticket.

Metadata