[gentoo-user] File collisions while syncing/updateing

[gentoo-user] File collisions while syncing/updateing

[tuxic]

Hi,

I've got this this morning:
strip: x86_64-pc-linux-gnu-strip --strip-unneeded -R .comment -R .GCC.command.line -R .note.gnu.gold-version
   /usr/lib64/libmxml.so.1.6
 * checking 9 files for package collisions
 * This package will overwrite one or more files that may belong to other
 * packages (see list below). You can use a command such as `portageq
 * owners / <filename>` to identify the installed package that owns a
 * file. If portageq reports that only one package owns a file then do
 * NOT file a bug report. A bug report is only useful if it identifies at
 * least two or more packages that are known to install the same file(s).
 * If a collision occurs and you can not explain where the file came from
 * then you should simply ignore the collision since there is not enough
 * information to determine if a real problem exists. Please do NOT file
 * a bug report at https://bugs.gentoo.org/ unless you report exactly
 * which two packages install the same file(s). See
 * https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how
 * to solve the problem. And once again, please do NOT file a bug report
 * unless you have completely understood the above message.
 * 
 * Detected file collision(s):
 * 
 * 	/usr/share/man/man3/mxml.3.bz2
 * 	/usr/include/mxml.h
 * 	/usr/lib64/libmxml.so.1.6
 * 	/usr/lib64/pkgconfig/mxml.pc
 * 	/usr/lib64/libmxml.so.1
 * 	/usr/lib64/libmxml.so
 * 
 * Searching all installed packages for file collisions...
 * 
 * Press Ctrl-C to Stop
 * 
 * dev-libs/mxml-2.12:0::gentoo
 * 	/usr/include/mxml.h
 * 	/usr/lib64/libmxml.so
 * 	/usr/lib64/libmxml.so.1
 * 	/usr/lib64/libmxml.so.1.6
 * 	/usr/lib64/pkgconfig/mxml.pc
 * 	/usr/share/man/man3/mxml.3.bz2
 * 
 * Package 'dev-libs/mxml-3.0' NOT merged due to file collisions. If
 * necessary, refer to your elog messages for the whole content of the
 * above message.
 * 
 * The following package has failed to build, install, or execute postinst:
 * 
 *  (dev-libs/mxml-3.0:1/6::gentoo, ebuild scheduled for merge), Log file:
 *   '/var/tmp/portage/dev-libs/mxml-3.0/temp/build.log'


Is it ok tp rm 
    /usr/share/man/man3/mxml.3.bz2
   	/usr/include/mxml.h
   	/usr/lib64/libmxml.so.1.6
   	/usr/lib64/pkgconfig/mxml.pc
   	/usr/lib64/libmxml.so.1
   	/usr/lib64/libmxml.so
   
manually prior to reemergeing?

Cheers!
Meino

Re: [gentoo-user] File collisions while syncing/updateing

[Jack]

On 2019.03.10 22:50, tuxic@posteo.de wrote:
> Hi,
> 
> I've got this this morning:
> strip: x86_64-pc-linux-gnu-strip --strip-unneeded -R .comment -R  
> .GCC.command.line -R .note.gnu.gold-version
>    /usr/lib64/libmxml.so.1.6
>  * checking 9 files for package collisions
>  * This package will overwrite one or more files that may belong to  
> other
>  * packages (see list below). You can use a command such as `portageq
>  * owners / <filename>` to identify the installed package that owns a
>  * file. If portageq reports that only one package owns a file then do
>  * NOT file a bug report. A bug report is only useful if it  
> identifies at
>  * least two or more packages that are known to install the same  
> file(s).
>  * If a collision occurs and you can not explain where the file came  
> from
>  * then you should simply ignore the collision since there is not  
> enough
>  * information to determine if a real problem exists. Please do NOT  
> file
>  * a bug report at https://bugs.gentoo.org/ unless you report exactly
>  * which two packages install the same file(s). See
>  * https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on  
> how
>  * to solve the problem. And once again, please do NOT file a bug  
> report
>  * unless you have completely understood the above message.
>  *
>  * Detected file collision(s):
>  *
>  * 	/usr/share/man/man3/mxml.3.bz2
>  * 	/usr/include/mxml.h
>  * 	/usr/lib64/libmxml.so.1.6
>  * 	/usr/lib64/pkgconfig/mxml.pc
>  * 	/usr/lib64/libmxml.so.1
>  * 	/usr/lib64/libmxml.so
>  *
>  * Searching all installed packages for file collisions...
>  *
>  * Press Ctrl-C to Stop
>  *
>  * dev-libs/mxml-2.12:0::gentoo
>  * 	/usr/include/mxml.h
>  * 	/usr/lib64/libmxml.so
>  * 	/usr/lib64/libmxml.so.1
>  * 	/usr/lib64/libmxml.so.1.6
>  * 	/usr/lib64/pkgconfig/mxml.pc
>  * 	/usr/share/man/man3/mxml.3.bz2
>  *
>  * Package 'dev-libs/mxml-3.0' NOT merged due to file collisions. If
>  * necessary, refer to your elog messages for the whole content of the
>  * above message.
>  *
>  * The following package has failed to build, install, or execute  
> postinst:
>  *
>  *  (dev-libs/mxml-3.0:1/6::gentoo, ebuild scheduled for merge), Log  
> file:
>  *   '/var/tmp/portage/dev-libs/mxml-3.0/temp/build.log'
> 
> 
> Is it ok tp rm
>     /usr/share/man/man3/mxml.3.bz2
>    	/usr/include/mxml.h
>    	/usr/lib64/libmxml.so.1.6
>    	/usr/lib64/pkgconfig/mxml.pc
>    	/usr/lib64/libmxml.so.1
>    	/usr/lib64/libmxml.so
> 
> manually prior to reemergeing?
Hello  Meino,

I'd file a bug, as it looks like 2.12 in slot 0 and 3.0 in slot 1 both  
install some of the same files.  It looks like version 3.0 was just  
added to the tree, so either it doesn't need to be in a separate slot,  
or else those files need renaming.

Deleting and re-emerging would probably work, but if you later remove  
one of the versions, those files will also be removed, and the  
remaining version will probably fail due to the missing .so file(s).

Jack