* Detected file collision(s): * * /usr/bin/console * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * app-admin/conserver-8.1.18-r1:0::gentoo * /usr/bin/console * * Package 'dev-ruby/ruby-progressbar-1.8.3' NOT merged due to file ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 13.0-systemd_20170910-171402 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-6.4.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] python3.6 (fallback) [3] python2.7 (fallback) [4] pypy3 (fallback) [5] pypy (fallback) [6] jython2.7 (fallback) Available Ruby profiles: [1] ruby22 (with Rubygems) * java-config: The following VMs are available for generation-2: 1) IcedTea JDK 7.2.6.11 [icedtea-bin-7] *) IcedTea JDK 3.5.1 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-7 [2] icedtea-bin-8 system-vm emerge -qpv dev-ruby/ruby-progressbar [ebuild N ] dev-ruby/ruby-progressbar-1.8.3 USE="{-test}" RUBY_TARGETS="ruby22 -ruby23"
Created attachment 496564 [details] emerge-info.txt
Created attachment 496566 [details] dev-ruby:ruby-progressbar-1.8.3:20170926-081720.log
Created attachment 496568 [details] emerge-history.txt
Created attachment 496570 [details] etc.portage.tbz2
Now fixed in ruby-progressbar-1.8.3-r1. Some recent refactoring in my maintenance scripts made a check for this non-fatal and thus easy to overlook. Now fixed as well.
