Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 439102 - dev-util/cucumber-1.1.4 fails during install without git
Summary: dev-util/cucumber-1.1.4 fails during install without git
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: AMD64 Linux
: Normal normal (vote)
Assignee: Hans de Graaff
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-20 20:30 UTC by Geoff Crew
Modified: 2013-01-06 13:17 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Geoff Crew 2012-10-20 20:30:52 UTC
Today I tried to install cucumber, but it failed in the install step with an error indicating it tried to use git I did not have installed. I installed git separately then tried again and it worked normally.

Here is an excerpt from the failure:

>>> Source prepared.
>>> Configuring source in /var/tmp/portage/dev-util/cucumber-1.1.4/work ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/dev-util/cucumber-1.1.4/work ...
 * Running compile phase for all ...
>>> Source compiled.
>>> Test phase [not enabled]: dev-util/cucumber-1.1.4

>>> Install cucumber-1.1.4 into /var/tmp/portage/dev-util/cucumber-1.1.4/image/ category dev-util
 * Running install phase for ruby18 ...
/usr/lib64/ruby/site_ruby/1.8/rubygems/specification.rb:821: 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):55:in `block in <main>'
	from /usr/lib64/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-util/cucumber-1.1.4 failed (install phase):
 *   Unable to generate gemspec file.
 * 
 * Call stack:
 *     ebuild.sh, line   85:  Called src_install
 *   environment, line 4453:  Called ruby-ng_src_install
 *   environment, line 4123:  Called _ruby_each_implementation 'each_ruby_install'
 *   environment, line  475:  Called _ruby_invoke_environment 'ruby19' 'each_ruby_install'
 *   environment, line  527:  Called each_ruby_install
 *   environment, line  813:  Called each_fakegem_install
 *   environment, line  786:  Called ruby_fakegem_install_gemspec
 *   environment, line 4304:  Called die
 * The specific snippet of code:
 *       fi ) || die "Unable to generate gemspec file.";
 * 
 * If you need support, post the output of `emerge --info '=dev-util/cucumber-1.1.4'`,
 * the complete build log and the output of `emerge -pqv '=dev-util/cucumber-1.1.4'`.
!!! When you file a bug report, please include the following information:
GENTOO_VM=  CLASSPATH="" JAVA_HOME="/etc/java-config-2/current-system-vm"
JAVACFLAGS="" COMPILER=""
and of course, the output of emerge --info
 * The complete build log is located at '/var/tmp/portage/dev-util/cucumber-1.1.4/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-util/cucumber-1.1.4/temp/environment'.
 * Working directory: '/var/tmp/portage/dev-util/cucumber-1.1.4/work/ruby19/cucumber-1.1.4'
 * S: '/var/tmp/portage/dev-util/cucumber-1.1.4/work/ruby19/cucumber-1.1.4'

>>> Failed to emerge dev-util/cucumber-1.1.4, Log file:

>>>  '/var/tmp/portage/dev-util/cucumber-1.1.4/temp/build.log'

 * Messages for package dev-util/cucumber-1.1.4:

 * ERROR: dev-util/cucumber-1.1.4 failed (install phase):
 *   Unable to generate gemspec file.
 * 
 * Call stack:
 *     ebuild.sh, line   85:  Called src_install
 *   environment, line 4453:  Called ruby-ng_src_install
 *   environment, line 4123:  Called _ruby_each_implementation 'each_ruby_install'
 *   environment, line  475:  Called _ruby_invoke_environment 'ruby19' 'each_ruby_install'
 *   environment, line  527:  Called each_ruby_install
 *   environment, line  813:  Called each_fakegem_install
 *   environment, line  786:  Called ruby_fakegem_install_gemspec
 *   environment, line 4304:  Called die
 * The specific snippet of code:
 *       fi ) || die "Unable to generate gemspec file.";
 * 
 * If you need support, post the output of `emerge --info '=dev-util/cucumber-1.1.4'`,
 * the complete build log and the output of `emerge -pqv '=dev-util/cucumber-1.1.4'`.
 * The complete build log is located at '/var/tmp/portage/dev-util/cucumber-1.1.4/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-util/cucumber-1.1.4/temp/environment'.
 * Working directory: '/var/tmp/portage/dev-util/cucumber-1.1.4/work/ruby19/cucumber-1.1.4'
 * S: '/var/tmp/portage/dev-util/cucumber-1.1.4/work/ruby19/cucumber-1.1.4'
Comment 1 Hans de Graaff gentoo-dev Security 2012-10-22 12:48:56 UTC
Yes, this happens because git is used to populate fields in the .gemspec file. I'll fix that when bumping cucumber to the latest version later this week.
Comment 2 Hans de Graaff gentoo-dev Security 2013-01-06 13:17:41 UTC
This should be fixed with cucumber 1.2.1 which got added some time ago.