Bug 476820

Summary:	dev-ruby/rspec-1.3.2 needs dev-vcs/git as DEPEND
Product:	Gentoo Linux	Reporter:	Agostino Sarubbo <ago>
Component:	New packages	Assignee:	Gentoo Ruby Team <ruby>
Status:	RESOLVED FIXED
Severity:	normal
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Agostino Sarubbo gentoo-dev

2013-07-14 12:14:01 UTC

* Package:    dev-ruby/rspec-1.3.2
 * Repository: gentoo
 * Maintainer: ruby@gentoo.org
 * USE:        alpha elibc_glibc kernel_linux ruby_targets_ruby18 ruby_targets_ruby19 userland_GNU
 * FEATURES:   sandbox userpriv usersandbox
 * Running unpack phase for all ...
 * Unpacking .gem file... ...
 [ ok ]
 * Uncompressing metadata ...
 [ ok ]
 * Unpacking data.tar.gz ...
 [ ok ]
 * Running prepare phase for all ...
 * Running source copy phase for ruby18 ...
 * Running source copy phase for ruby19 ...
 * Running compile phase for all ...
 * Running install phase for ruby18 ...
(eval):5: command not found: git ls-files
sh: git: command not found
sh: git: command not found
 * Running install phase for ruby19 ...
-e:1:in `eval': No such file or directory - git ls-files (Errno::ENOENT)
        from (eval):17:in `block in <main>'
        from /usr/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:1368:in `initialize'
        from (eval):5:in `new'
        from (eval):5:in `<main>'
        from -e:1:in `eval'
        from -e:1:in `<main>'
 * ERROR: dev-ruby/rspec-1.3.2 failed (install phase):
 *   Unable to generate gemspec file.

Comment 1 Hans de Graaff gentoo-dev

2013-07-16 06:37:59 UTC

Fixed in 1.3.2 by removing the git calls from the gemspec file. Even with git installed this won't provide meaningful information anyway.