Re: koji breakage for F12 builds

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

 



Christoph Wickert wrote, at 05/13/2009 08:15 PM +9:00:
> Am Mittwoch, den 13.05.2009, 08:43 +0200 schrieb Michael Schwendt:
>> 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?
> 
> How would I check that?
> 
>> E.g. notify-daemon and desktop-notification-daemon and the package name
>> itself, notification-daemon. 
> 
> I think the problem is, that some packages  notification-deamon instead
> of (virtual) desktop-notification-deamon:
> 
> # repoquery --repoid rawhide --whatrequires notification-daemon
> gnome-bluetooth-0:2.27.5-1.fc11.i586
> notify-python-0:0.1.1-6.fc11.i586
> notification-daemon-engine-nodoka-0:0.1.0-6.fc11.i586
> system-config-printer-0:1.1.7-1.fc11.i586
> ibus-0:1.1.0.20090423-1.fc11.i586
> 
> I'm going to file bugs against these packages except
> notification-daemon-engine-nodoka, because it only works with
> notification-daemon.
> 
> Regards,
> Christoph

Well, this won't work for this issue, because:
- With yum shorter name will win depsolving game, so "Requires:
  desktop-notification-deamon" will always pull "xfce4-notify" in.

- On the other hand, with your idea yum resolver says libgnome
  will install notification-daemon with the following chain:
  libgnome -> fedora-gnome-theme -> notification-daemon-engine-nodoka
  -> notification-daemon

So when libnotify and libgnome are to be installed, for example,
conflicts can never be solved...

Regards,
Mamoru

-- 
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list

[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