Maven 3.5.4 and 3.60 contain both the same shared library for jansi and the installation process strips the debug info into /usr/lib/debug where the collision happens: =============== %< ================= >>> Install maven-bin-3.6.0 into /var/tmp/portage/portage/dev-java/maven-bin-3.6.0/image/ category dev-java >>> Completed installing maven-bin-3.6.0 into /var/tmp/portage/portage/dev-java/maven-bin-3.6.0/image/ * Final size of build directory: 10612 KiB (10.3 MiB) * Final size of installed tree: 10632 KiB (10.3 MiB) strip: x86_64-pc-linux-gnu-strip --strip-unneeded -R .comment -R .GCC.command.line -R .note.gnu.gold-version usr/share/maven-bin-3.6/lib/jansi-native/freebsd32/libjansi.so usr/share/maven-bin-3.6/lib/jansi-native/freebsd64/libjansi.so usr/share/maven-bin-3.6/lib/jansi-native/linux32/libjansi.so usr/share/maven-bin-3.6/lib/jansi-native/linux64/libjansi.so >>> Installing (1 of 1) dev-java/maven-bin-3.6.0::gentoo * 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/lib/debug/.build-id/5f/b40ad650b711da4eb18584bccb731d0211e2af * /usr/lib/debug/.build-id/5f/b40ad650b711da4eb18584bccb731d0211e2af.debug * /usr/lib/debug/.build-id/e9/631fef334d8b32619da859129c3d315e0475ac * /usr/lib/debug/.build-id/e9/631fef334d8b32619da859129c3d315e0475ac.debug * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * dev-java/maven-bin-3.5.4:3.5::gentoo * /usr/lib/debug/.build-id/5f/b40ad650b711da4eb18584bccb731d0211e2af * /usr/lib/debug/.build-id/5f/b40ad650b711da4eb18584bccb731d0211e2af.debug * /usr/lib/debug/.build-id/e9/631fef334d8b32619da859129c3d315e0475ac * /usr/lib/debug/.build-id/e9/631fef334d8b32619da859129c3d315e0475ac.debug * * Package 'dev-java/maven-bin-3.6.0' NOT merged due to file collisions. * If necessary, refer to your elog messages for the whole content of the * above message. =============== %< ================= From emerge --info: =============== %< ================= CONFIG_PROTECT="/etc /usr/lib64/libreoffice/program/sofficerc /usr/share/config /usr/share/gnupg/qualified.txt /usr/share/maven-bin-2.0/conf /usr/share/maven-bin-2.2/conf /usr/share/maven-bin-3.2/conf /usr/share/maven-bin-3.3/conf /usr/share/maven-bin-3.5/conf /usr/share/themes/oxygen-gtk/gtk-2.0 /usr/share/themes/oxygen-gtk/gtk-3.0" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo" FEATURES="assume-digests binpkg-logs config-protect-if-modified distlocks ebuild-locks fixlafiles merge-sync multilib-strict news parallel-fetch preserve-libs protect-owned sandbox sfperms splitdebug strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync xattr" =============== %< =================
i will drop the version 3.5.x completely to avoid this. according to following page there is no bold version of 3.5.x so i suppose that version 3.6.0 replaces versions 3.5.x. https://maven.apache.org/docs/history.html
so versions 3.5.x are gone from the main tree...
