Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 439556 - x11-libs/motif: file collision issues after package move from openmotif
Summary: x11-libs/motif: file collision issues after package move from openmotif
Status: RESOLVED OBSOLETE
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Ulrich Müller
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-24 20:36 UTC by Toralf Förster
Modified: 2012-10-26 15:42 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
build log (x11-libs:motif-2.3.3-r1:20121024-200951.log.gz,61.54 KB, text/plain)
2012-10-24 20:36 UTC, Toralf Förster 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Toralf Förster gentoo-dev 2012-10-24 20:36:53 UTC 
Created attachment 327334 [details]
build log

Today suddenly net-misc/icaclient-12.1.0 required new package : 

These are the packages that would be merged, in reverse order:

Calculating dependencies  ...... .... done!
[nomerge       ] net-misc/icaclient-12.1.0 
[ebuild  N     ]  x11-libs/motif-2.3.3-r1  USE="jpeg png unicode -doc -examples -static-libs -xft" 

The emerge failed due to file collisions b/c I do already have installed openmotif (required by x11-misc/xlockmore-5.38) - so shouldn't icaclient respect this ?
Comment 1 Manuel Rüger (RETIRED) gentoo-dev 2012-10-25 00:51:13 UTC 
  24 Oct 2012; Ulrich Müller <ulm@gentoo.org> xlockmore-5.38.ebuild,
  xlockmore-5.39.ebuild, xlockmore-5.40.ebuild:
  Update dependency after package move from x11-libs/openmotif to
  x11-libs/motif.



Just resync.
Comment 2 Ulrich Müller gentoo-dev 2012-10-25 05:00:40 UTC 
Package move, and updating it's many reverse dependencies wasn't atomic. (That's one of the things that will become better when we move the tree to git.)

(In reply to comment #1)
> Just resync.

Right, this should fix it.