Bug 673774

Summary:	dev-ruby/minitest-5.11.3 : file collision with dev-lang/ruby-2.6.0
Product:	Gentoo Linux	Reporter:	Toralf Förster <toralf>
Component:	Current packages	Assignee:	Gentoo Ruby Team <ruby>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	emerge-info.txt dev-ruby:minitest-5.11.3:20181226-201521.log emerge-history.txt etc.portage.tbz2 logs.tbz2

Description Toralf Förster gentoo-dev

2018-12-26 20:29:21 UTC

  -------------------------------------------------------------------

  This is an unstable amd64 chroot image at a tinderbox (==build bot)
  name: 17.0-hardened_libressl-test_20181218-071658

  -------------------------------------------------------------------

gcc-config -l:
 [1] x86_64-pc-linux-gnu-7.3.1
 [2] x86_64-pc-linux-gnu-8.2.0 *

Available Python interpreters, in order of preference:
  [1]   python3.6
  [2]   python2.7 (fallback)
  [3]   pypy (fallback)
Available Ruby profiles:
  [1]   ruby23 (with Rubygems)
  [2]   ruby24 (with Rubygems)
  [3]   ruby25 (with Rubygems)
  [4]   ruby26 (with Rubygems) *
Available Rust versions:
  [1]   rust-1.31.1 *
  [2]   rust-bin-1.31.1



emerge -qpvO dev-ruby/minitest
[ebuild   R   ] dev-ruby/minitest-5.11.3  USE="-doc -test" RUBY_TARGETS="ruby23 ruby24 ruby25 ruby26%*"

Comment 1 Toralf Förster gentoo-dev

2018-12-26 20:29:23 UTC

Created attachment 558514 [details]
emerge-info.txt

Comment 2 Toralf Förster gentoo-dev

2018-12-26 20:29:26 UTC

Created attachment 558516 [details]
dev-ruby:minitest-5.11.3:20181226-201521.log

Comment 3 Toralf Förster gentoo-dev

2018-12-26 20:29:29 UTC

Created attachment 558518 [details]
emerge-history.txt

Comment 4 Toralf Förster gentoo-dev

2018-12-26 20:29:32 UTC

Created attachment 558520 [details]
etc.portage.tbz2

Comment 5 Toralf Förster gentoo-dev

2018-12-26 20:29:34 UTC

Created attachment 558522 [details]
logs.tbz2

Comment 6 Hans de Graaff gentoo-dev

2018-12-27 06:31:51 UTC


*** This bug has been marked as a duplicate of bug 673760 ***