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

Re: koji breakage for F12 builds



On Wed, 13 May 2009 01:54:56 +0200, Christoph wrote:

> Am Dienstag, den 12.05.2009, 23:04 +0100 schrieb Peter Robinson:
> > Just tried building a new package and it seems that it breaks because
> > xfce4-notifyd conflicts with notification-daemon.... wicked the new
> > rawhide is broken before the old rawhide is done and dusted :-)
> 
> See https://fedorahosted.org/rel-eng/ticket/1788
> 
> xfce4-notifyd conflicts with notification-daemon because both provide 
> /usr/share/dbus-1/services/org.freedesktop.Notifications.service
> 
> For compatibility they both provide a virtual
> desktop-notification-daemon, but ATM the "Conflicts: xfce4-notifyd" is
> missing from the notification-daemon package. Filed as
> https://bugzilla.redhat.com/show_bug.cgi?id=500513
> 
> > http://koji.fedoraproject.org/koji/getfile?taskID=1351516&name=root.log
> 
> The strange thing about this log: I don't see it installing
> notification-daemon. So where is the problem?
> 
> /me is confused
> Christoph

The output of the yum resolvedep step doesn't list xfce4-notifyd either.

I don't have my notes about koji's static repos here, so I cannot
find and repoquery the F-12 repodata to find out --whatrequires several
of these "Provides", but...

notification-daemon
http://koji.fedoraproject.org/koji/rpminfo?rpmID=1199322

  Provides  	
  config(notification-daemon) = 0.4.0-3.fc11
  desktop-notification-daemon
  libstandard.so()(64bit)
  notification-daemon = 0.4.0-3.fc11
  notification-daemon(x86-64) = 0.4.0-3.fc11
  notify-daemon

Can you rule out that anything in the dependency-chain pulls in
notification-daemon _and_ xfce4-notify due to competing Provides?
E.g. notify-daemon and desktop-notification-daemon and the package name
itself, notification-daemon. That's three things one can require to get
the same package. There's the risk that some dependencies are on virtual
Provides while others are on package names. How are dependencies resolved
in case explicit Conflicts are found? Does Yum replace equivalent packages
(which provide the same thing) automatically until a transaction set no
longer suffers from conflicts?


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