* Detected file collision(s): * * /usr/bin/singularity * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * sys-cluster/singularity-2.2.1:0::gentoo * /usr/bin/singularity * * Package 'games-simulation/singularity-0.30c-r2' NOT merged due to file ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: gnome_20170512-200701 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-6.3.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] python2.7 (fallback) Available Ruby profiles: [1] ruby21 (with Rubygems) [2] ruby22 (with Rubygems) * java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.3.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm
Created attachment 472966 [details] emerge-info.txt
Created attachment 472968 [details] emerge-history.txt
Created attachment 472970 [details] etc.portage.tbz2
Created attachment 472972 [details] games-simulation:singularity-0.30c-r2:20170517-024110.log
This is still the case for the freshly packaged =singularity-1.0_alpha1 version.
Still very much the case for latest versions of both packages.
I'll go for a blocker for now.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=dc21c8edefa2fea132be161c43f2562c2426d356 commit dc21c8edefa2fea132be161c43f2562c2426d356 Author: Sam James <sam@gentoo.org> AuthorDate: 2021-03-25 15:16:09 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2021-03-25 15:21:58 +0000 games-simulation/singularity: add blocker with sys-cluster/singularity Closes: https://bugs.gentoo.org/618770 Signed-off-by: Sam James <sam@gentoo.org> games-simulation/singularity/singularity-1.0_alpha1-r1.ebuild | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-)
