* Press Ctrl-C to Stop * * net-im/element-desktop-bin-1.7.28:0::gentoo * /usr/lib/debug/.build-id/13/070cd6d4401903dee7a42e402d150de4362b18 * /usr/lib/debug/.build-id/13/070cd6d4401903dee7a42e402d150de4362b18.debug * /usr/lib/debug/.build-id/3e/d503d7be965ab698b328fe3a69162a4efb5351 ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_developer-j2-20210521-113651 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-11.1.0 * clang version 12.0.0 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/12/bin /usr/lib/llvm/12 12.0.0 Python 3.8.10 Available Ruby profiles: [1] ruby26 (with Rubygems) [2] ruby30 (with Rubygems) * Available Rust versions: [1] rust-bin-1.52.1 * The following VMs are available for generation-2: 1) IcedTea JDK 3.18.0 [icedtea-8] *) AdoptOpenJDK 8.292_p10 [openjdk-bin-8] Available Java Virtual Machines: [1] icedtea-8 [2] openjdk-bin-8 system-vm The Glorious Glasgow Haskell Compilation System, version 8.10.4 timestamp(s) of HEAD at this tinderbox image: /var/db/repos/gentoo Wed May 26 17:50:09 UTC 2021 emerge -qpvO net-im/signal-desktop-bin [ebuild N ] net-im/signal-desktop-bin-5.3.0 USE="sound"
Created attachment 711417 [details] emerge-info.txt
Created attachment 711420 [details] emerge-history.txt
Created attachment 711423 [details] etc.portage.tar.bz2
Created attachment 711426 [details] logs.tar.bz2
Created attachment 711429 [details] net-im:signal-desktop-bin-5.3.0:20210526-185632.log
I'm not quite sure if this is a duplicate of https://bugs.gentoo.org/549672 In this case, the collision probably exists because both packages contain Electron, so they share identical binaries which produce the same hash, which is the cause for the collision. A simple workaround could be adding COLLISION_IGNORE to the ebuilds.
https://bugs.gentoo.org/549672#c12 suggests to add RESTRICT=splitdebug. net-im/signal-desktop-bin already contains the restriction, so it needs to be added to net-im/element-desktop-bin
(In reply to Robert G. Siebeck from comment #6) > I'm not quite sure if this is a duplicate of https://bugs.gentoo.org/549672 > > In this case, the collision probably exists because both packages contain > Electron, so they share identical binaries which produce the same hash, > which is the cause for the collision. > > A simple workaround could be adding COLLISION_IGNORE to the ebuilds. Makes sense, thanks for working on it.
(In reply to Joonas Niilola from comment #8) > (In reply to Robert G. Siebeck from comment #6) > > I'm not quite sure if this is a duplicate of https://bugs.gentoo.org/549672 > > > > In this case, the collision probably exists because both packages contain > > Electron, so they share identical binaries which produce the same hash, > > which is the cause for the collision. > > > > A simple workaround could be adding COLLISION_IGNORE to the ebuilds. > > Makes sense, thanks for working on it. Or simply restrict strip.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ec4308f738ba4c5ac094f53c33d11dd913968582 commit ec4308f738ba4c5ac094f53c33d11dd913968582 Author: Robert Siebeck <gentoo.2019@r123.de> AuthorDate: 2021-06-01 16:39:19 +0000 Commit: Stefan Strogin <steils@gentoo.org> CommitDate: 2021-06-04 04:21:43 +0000 net-im/element-desktop-bin: RESTRICT splitdebug Avoids debug file collision with net-im/signal-desktop-bin Closes: https://bugs.gentoo.org/792309 Signed-off-by: Robert Siebeck <gentoo.2019@r123.de> https://github.com/gentoo/gentoo/pull/21076 Signed-off-by: Stefan Strogin <steils@gentoo.org> net-im/element-desktop-bin/element-desktop-bin-1.7.29.ebuild | 1 + 1 file changed, 1 insertion(+)
Thanks for the report and for the fix.
