------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_developer-20200813-172142 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.1 [2] x86_64-pc-linux-gnu-10.2.0 * clang version 10.0.1 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/10/bin /usr/lib/llvm/10 10.0.1 Available Python interpreters, in order of preference: [1] python3.7 [2] python3.9 (fallback) [3] python3.8 (fallback) [4] python3.6 (fallback) [5] python2.7 (fallback) [6] pypy3 (fallback) Available Ruby profiles: [1] ruby25 (with Rubygems) * Available Rust versions: [1] rust-bin-1.45.2 [2] rust-1.45.2 * The following VMs are available for generation-2: 1) IcedTea JDK 3.16.0 [icedtea-8] *) IcedTea JDK 3.16.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-8 [2] icedtea-bin-8 system-vm The Glorious Glasgow Haskell Compilation System, version 8.8.4 timestamp(s) of HEAD at this tinderbox image: /var/db/repos/gentoo Fri Aug 21 05:35:39 AM UTC 2020 emerge -qpvO dev-util/perf [ebuild N ] dev-util/perf-5.7-r1 USE="crypt demangle doc zlib -audit -clang -debug -gtk -java -lzma -numa -perl -python -slang -systemtap -unwind" PYTHON_TARGETS="python3_7 -python3_6 -python3_8"
Created attachment 655926 [details] emerge-info.txt
Created attachment 655928 [details] dev-util:perf-5.7-r1:20200821-065952.log
Created attachment 655930 [details] emerge-history.txt
Created attachment 655932 [details] etc.portage.tbz2
Created attachment 655934 [details] logs.tbz2
I ran into this too and I wonder what is going on in this one. What package bundles what and where is the problem.
To quickly answer this, doesn't happen with dev-util/trace-cmd-2.8.3::gentoo
Same issue here: --8<-- * Detected file collision(s): * * /usr/lib64/traceevent/plugins/plugin_futex.so * /usr/lib64/traceevent/plugins/plugin_tlb.so * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * dev-util/trace-cmd-2.9.1:0::gentoo * /usr/lib64/traceevent/plugins/plugin_futex.so * /usr/lib64/traceevent/plugins/plugin_tlb.so * * Package 'dev-util/perf-5.9.9' NOT merged due to file collisions. If * necessary, refer to your elog messages for the whole content of the * above message. --8<--
Both trace-cmd and perf are part of the Linux kernel tree, so it seems that the colliding files is shared code between them from the kernel repository. Not sure what is the best way to fix this. One way may be to add libraries for each of them under a subdirectory, and another way would be to make one package depend on the other and not install the plugins in one of them.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2d6af4f61aabf31b899bc7facb2e0f5b77ed0035 commit 2d6af4f61aabf31b899bc7facb2e0f5b77ed0035 Author: Guilherme Amadio <amadio@gentoo.org> AuthorDate: 2021-04-30 09:10:47 +0000 Commit: Guilherme Amadio <amadio@gentoo.org> CommitDate: 2021-04-30 09:10:47 +0000 dev-util/perf: fix file collision with trace-cmd, bug #738404 Closes: https://bugs.gentoo.org/738404 Package-Manager: Portage-3.0.18, Repoman-3.0.3 Signed-off-by: Guilherme Amadio <amadio@gentoo.org> dev-util/perf/perf-5.11.ebuild | 1 + dev-util/perf/perf-5.12.ebuild | 1 + dev-util/perf/perf-5.8.ebuild | 1 + 3 files changed, 3 insertions(+)
To avoid potential problems with compatibility between the plugins, I just changed perf's plugin directory to <libdir>/perf/plugins.
