Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 691956

Summary: dev-ruby/power_assert-1.1.5 : * Unable to generate gemspec file.
Product: Gentoo Linux Reporter: Toralf Förster <toralf>
Component: Current packagesAssignee: 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:power_assert-1.1.5:20190811-181234.log
emerge-history.txt
environment
etc.portage.tbz2

Description Toralf Förster gentoo-dev 2019-08-11 18:56:31 UTC
 * ERROR: dev-ruby/power_assert-1.1.5::gentoo failed (install phase):
 *   Unable to generate gemspec file.
 * 

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

  This is an unstable amd64 chroot image at a tinderbox (==build bot)
  name: 17.1_developer-abi32+64-20190810-161025

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

gcc-config -l:
 [1] x86_64-pc-linux-gnu-9.1.0 *

Available Python interpreters, in order of preference:
  [1]   python3.6
  [2]   python2.7 (fallback)
Available Ruby profiles:
  [1]   ruby24 (with Rubygems) *




emerge -qpvO dev-ruby/power_assert
[ebuild  N    ] dev-ruby/power_assert-1.1.5  USE="-doc -test" RUBY_TARGETS="ruby24 -ruby25 -ruby26"
Comment 1 Toralf Förster gentoo-dev 2019-08-11 18:56:34 UTC
Created attachment 586584 [details]
emerge-info.txt
Comment 2 Toralf Förster gentoo-dev 2019-08-11 18:56:37 UTC
Created attachment 586586 [details]
dev-ruby:power_assert-1.1.5:20190811-181234.log
Comment 3 Toralf Förster gentoo-dev 2019-08-11 18:56:40 UTC
Created attachment 586588 [details]
emerge-history.txt
Comment 4 Toralf Förster gentoo-dev 2019-08-11 18:56:42 UTC
Created attachment 586590 [details]
environment
Comment 5 Toralf Förster gentoo-dev 2019-08-11 18:56:45 UTC
Created attachment 586592 [details]
etc.portage.tbz2
Comment 6 Hans de Graaff gentoo-dev Security 2019-08-12 04:50:12 UTC

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