Bug 284760

Summary:	File collision when emerging net-libs/libsoup-gnome
Product:	Gentoo Linux	Reporter:	Kaleb Elwert (belak) <kelwert>
Component:	[OLD] GNOME	Assignee:	Gentoo Linux Gnome Desktop Team <gnome>
Status:	RESOLVED FIXED
Severity:	normal	CC:	bug-wranglers, kelwert, mark+gentoobugs, steffen
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	Includes emerge --info and the fail message

Description Kaleb Elwert (belak) 2009-09-13 13:40:59 UTC

I recently tried to update today...
libsoup-gnome failed to emerge because of package collisions.

I have tried unmerging libsoup and remerging all of it, but nothing changed.


Reproducible: Always

Steps to Reproduce:
1. emerge -uND world
2. Wait.
Actual Results:  
Package fails to merge.

Expected Results:  
Package should merge.

Comment 1 Kaleb Elwert (belak) 2009-09-13 13:42:22 UTC

Created attachment 203936 [details]
Includes emerge --info and the fail message

Comment 2 Kaleb Elwert (belak) 2009-09-13 13:44:53 UTC

And I don't know if bug-wranglers@gentoo.org should be added to this... forgive me... I'm not used to filing bugs, and don't really know how.

Comment 3 Kaleb Elwert (belak) 2009-09-13 13:50:11 UTC

Temporary fix: to emerge libsoup-gnome, run rm -R /usr/share/gtk-doc/html/libsoup-2.4/

This removes the conflicting files... they will be added back...

Thanks.

Comment 4 Romain Perier (RETIRED) gentoo-dev

2009-09-13 14:37:29 UTC

Fixed into the main tree without a bump, could you test it ?
feel free to reopen this bug in case of problem.
and please get back us.

Comment 5 Romain Perier (RETIRED) gentoo-dev

2009-09-13 14:46:52 UTC

*** Bug 284758 has been marked as a duplicate of this bug. ***

Comment 6 Steffen Schaumburg 2009-09-13 19:47:10 UTC

Had the same problem. Just resynced and it works now :)
Even better, your fix also fixed the problem that it failed emerging with USE+doc :)

Comment 7 Romain Perier (RETIRED) gentoo-dev

2009-09-13 20:28:32 UTC

(In reply to comment #6)
> Even better, your fix also fixed the problem that it failed emerging with
> USE+doc :)
> 

As specified in the appropriate bug yep :)