Bug 529588 – media-gfx/imagemagick-6.8.9.9 - ?

• Status: RESOLVED INVALID
• Product: Gentoo Linux

[Description Thomas Capricelli 2014-11-17 00:35:28 UTC]

The compilation seems to went well, but it fails at install stage with this error i've never seen.

.....
 *      /usr/lib64/ImageMagick-6.8.9/modules-Q16/coders/sixel.la
 * Package 'media-gfx/imagemagick-6.8.9.9' merged despite file
 * collisions. If necessary, refer to your elog messages for the whole
 * content of the above message.
Traceback (most recent call last):
  File "/usr/lib64/python2.7/site-packages/portage/dbapi/_MergeProcess.py", line 234, in _spawn
    prev_mtimes=self.prev_mtimes, counter=counter)
  File "/usr/lib64/python2.7/site-packages/portage/dbapi/vartree.py", line 4888, in merge
    counter=counter)
  File "/usr/lib64/python2.7/site-packages/portage/dbapi/vartree.py", line 4163, in treewalk
    preserve_paths=preserve_paths)
  File "/usr/lib64/python2.7/site-packages/portage/dbapi/vartree.py", line 1934, in unmerge
    preserve_paths=preserve_paths)
  File "/usr/lib64/python2.7/site-packages/portage/dbapi/vartree.py", line 1774, in _prune_plib_registry
    unmerge_no_replacement)
  File "/usr/lib64/python2.7/site-packages/portage/dbapi/vartree.py", line 3098, in _find_unused_preserved_libs
    for c in self.vartree.dbapi._linkmap.findConsumers(f):
  File "/usr/lib64/python2.7/site-packages/portage/util/_dyn_libs/LinkageMapELF.py", line 742, in findConsumers
    raise KeyError("%s (%s) not in object list" % (obj_key, obj))
KeyError: u'<portage.util._dyn_libs.LinkageMapELF._ObjectKey object at 0x7f8f84075088> (/usr/lib64/libMagick++-6.Q16.so.3.0.0) not in object list'


Reproducible: Always

[Comment 1 Thomas Capricelli 2014-11-17 00:39:24 UTC]

Created attachment 389552 [details]
build.log

I removed some lines so that it fits the 1mb limit. I put \n...\n where i've cut, should not prevent any understanding imho.

[Comment 2 Jeroen Roovers (RETIRED) 2014-11-17 13:14:04 UTC]

Comment on attachment 389552 [details]
build.log

(In reply to Thomas Capricelli from comment #1)
> Created attachment 389552 [details]
> build.log
> 
> I removed some lines so that it fits the 1mb limit. I put \n...\n where i've
> cut, should not prevent any understanding imho.

This is why files can be compressed.

Please attach the entire build log to this bug report. And please don't put it in an archive before you compress it.

[Comment 3 Thomas Capricelli 2014-11-17 15:30:30 UTC]

come on, i know how rigid you are wrt to administrativia, but the lines i've removed are absolutely useless. Just successful compilation units lines among other similar ones.

[Comment 4 Thomas Capricelli 2014-11-17 15:32:11 UTC]

i've turn around the problem by 
* unmerging imagemagick
* removing /usr/lib64/libMagic*
* re-emerging

But imho, there's still a bug somewhere, this is only a turn around.

[Comment 5 Jeroen Roovers (RETIRED) 2014-11-18 16:39:03 UTC]

Since we have no idea how those files got installed in the first place, and since we will probably never know now, I don't see a bug here.