* Detected file collision(s): * * /usr/bin/console * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * dev-ruby/ruby-termios-1.0.2:0::gentoo * /usr/bin/console * * Package 'app-admin/conserver-8.1.18-r1' NOT merged due to file ----------------------------------------------------------------- This is an unstable amd64 chroot image (named 13.0_20170224-122708) at a hardened host acting as a tinderbox. ----------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-5.4.0 * llvm-config: 3.9.1 Available Python interpreters, in order of preference: [1] python3.4 [2] python2.7 (fallback) [3] pypy3 (fallback) [4] pypy (fallback) Available Ruby profiles: [1] ruby21 (with Rubygems) * java-config: The following VMs are available for generation-2:
Created attachment 465916 [details] emerge-info.txt
Created attachment 465918 [details] app-admin:conserver-8.1.18-r1:20170304-034453.log
Created attachment 465920 [details] config.log.tbz2
Created attachment 465922 [details] emerge-history.txt
Created attachment 465924 [details] etc.portage.tbz2
This is an issue with many ruby packages - see bug # 571186, 593068, or 607806 - especially my explanation in last bug. This is going to keep happening until the ruby eclass gets fixed to filter out the affecting file(s).
Fixed in ruby-termios-1.0.2-r1.
(In reply to Daniel M. Weeks from comment #6) So shall I stop filing bugs related to file collisions with ruby packages ?
(In reply to Toralf Förster from comment #8) > (In reply to Daniel M. Weeks from comment #6) > So shall I stop filing bugs related to file collisions with ruby packages ? It might be better to just file them for the ruby team and not bother Daniel with them (if they are about /usr/bin/console and /usr/bin/setup).
