Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 202624 - dev-ruby/ruby-ferret-0.11.4 fails to install
Summary: dev-ruby/ruby-ferret-0.11.4 fails to install
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Christian Parpart (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-17 22:21 UTC by G. Gibson
Modified: 2008-01-09 09:31 UTC (History)
2 users (show)

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 G. Gibson 2007-12-17 22:21:57 UTC
>>> Install ruby-ferret-0.11.4 into /var/tmp/portage/dev-ruby/ruby-ferret-0.11.4/image/ category dev-ruby
ERROR:  Local gem file not found: /var/tmp/portage/dev-ruby/ruby-ferret-0.11.4/distdir/ruby-ferret-0.11.4*.gem
ERROR:  Could not install a local or remote copy of the gem: /var/tmp/portage/dev-ruby/ruby-ferret-0.11.4/distdir/ruby-ferret-0.11.4
 * 
 * ERROR: dev-ruby/ruby-ferret-0.11.4 failed.
 * Call stack:
 *     ebuild.sh, line 1684:  Called dyn_install
 *     ebuild.sh, line 1119:  Called qa_call 'src_install'
 *     ebuild.sh, line   44:  Called src_install
 *     ebuild.sh, line 1364:  Called gems_src_install
 *   gems.eclass, line   74:  Called die
 * The specific snippet of code:
 *      gem install ${GEM_SRC} -v ${PV} ${myconf} -l -i ${D}/${GEMSDIR} || die "gem install failed: gem-$(gem --version) install ${GEM_SRC} -v ${PV} ${myconf} -l -i ${D}/${GEMSDIR}"
 *  The die message:
 *   gem install failed: gem-0.9.4 install /var/tmp/portage/dev-ruby/ruby-ferret-0.11.4/distdir/ruby-ferret-0.11.4 -v 0.11.4 --no-ri --no-rdoc -l -i /var/tmp/portage/dev-ruby/ruby-ferret-0.11.4/image///usr/lib/ruby/gems/1.8
 * 
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/var/tmp/portage/dev-ruby/ruby-ferret-0.11.4/temp/build.log'.
 * 

 * Messages for package dev-ruby/ruby-ferret-0.11.4:

 * 
 * ERROR: dev-ruby/ruby-ferret-0.11.4 failed.
 * Call stack:
 *     ebuild.sh, line 1684:  Called dyn_install
 *     ebuild.sh, line 1119:  Called qa_call 'src_install'
 *     ebuild.sh, line   44:  Called src_install
 *     ebuild.sh, line 1364:  Called gems_src_install
 *   gems.eclass, line   74:  Called die
 * The specific snippet of code:
 *      gem install ${GEM_SRC} -v ${PV} ${myconf} -l -i ${D}/${GEMSDIR} || die "gem install failed: gem-$(gem --version) install ${GEM_SRC} -v ${PV} ${myconf} -l -i ${D}/${GEMSDIR}"
 *  The die message:
 *   gem install failed: gem-0.9.4 install /var/tmp/portage/dev-ruby/ruby-ferret-0.11.4/distdir/ruby-ferret-0.11.4 -v 0.11.4 --no-ri --no-rdoc -l -i /var/tmp/portage/dev-ruby/ruby-ferret-0.11.4/image///usr/lib/ruby/gems/1.8
 * 
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/var/tmp/portage/dev-ruby/ruby-ferret-0.11.4/temp/build.log'.
 * 


Reproducible: Always

Steps to Reproduce:
1.emerge ruby-ferret
2.
3.

Actual Results:  
>>> Install ruby-ferret-0.11.4 into /var/tmp/portage/dev-ruby/ruby-ferret-0.11.4/image/ category dev-ruby
ERROR:  Local gem file not found: /var/tmp/portage/dev-ruby/ruby-ferret-0.11.4/distdir/ruby-ferret-0.11.4*.gem
ERROR:  Could not install a local or remote copy of the gem: /var/tmp/portage/dev-ruby/ruby-ferret-0.11.4/distdir/ruby-ferret-0.11.4
 * 
 * ERROR: dev-ruby/ruby-ferret-0.11.4 failed.
 * Call stack:
 *     ebuild.sh, line 1684:  Called dyn_install
 *     ebuild.sh, line 1119:  Called qa_call 'src_install'
 *     ebuild.sh, line   44:  Called src_install
 *     ebuild.sh, line 1364:  Called gems_src_install
 *   gems.eclass, line   74:  Called die
 * The specific snippet of code:
 *      gem install ${GEM_SRC} -v ${PV} ${myconf} -l -i ${D}/${GEMSDIR} || die "gem install failed: gem-$(gem --version) install ${GEM_SRC} -v ${PV} ${myconf} -l -i ${D}/${GEMSDIR}"
 *  The die message:
 *   gem install failed: gem-0.9.4 install /var/tmp/portage/dev-ruby/ruby-ferret-0.11.4/distdir/ruby-ferret-0.11.4 -v 0.11.4 --no-ri --no-rdoc -l -i /var/tmp/portage/dev-ruby/ruby-ferret-0.11.4/image///usr/lib/ruby/gems/1.8
 * 
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/var/tmp/portage/dev-ruby/ruby-ferret-0.11.4/temp/build.log'.
 * 

 * Messages for package dev-ruby/ruby-ferret-0.11.4:

 * 
 * ERROR: dev-ruby/ruby-ferret-0.11.4 failed.
 * Call stack:
 *     ebuild.sh, line 1684:  Called dyn_install
 *     ebuild.sh, line 1119:  Called qa_call 'src_install'
 *     ebuild.sh, line   44:  Called src_install
 *     ebuild.sh, line 1364:  Called gems_src_install
 *   gems.eclass, line   74:  Called die
 * The specific snippet of code:
 *      gem install ${GEM_SRC} -v ${PV} ${myconf} -l -i ${D}/${GEMSDIR} || die "gem install failed: gem-$(gem --version) install ${GEM_SRC} -v ${PV} ${myconf} -l -i ${D}/${GEMSDIR}"
 *  The die message:
 *   gem install failed: gem-0.9.4 install /var/tmp/portage/dev-ruby/ruby-ferret-0.11.4/distdir/ruby-ferret-0.11.4 -v 0.11.4 --no-ri --no-rdoc -l -i /var/tmp/portage/dev-ruby/ruby-ferret-0.11.4/image///usr/lib/ruby/gems/1.8
 * 
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/var/tmp/portage/dev-ruby/ruby-ferret-0.11.4/temp/build.log'.
 * 


Expected Results:  
ruby-ferret merged
Comment 1 Richard Brown (RETIRED) gentoo-dev 2007-12-18 09:46:21 UTC
Trapni, you need to define MY_P if P is wrong, as gems.eclass uses P or MY_P if it exists, to know which gem to extract. Instead of your current SRC_URI you need 
MY_P="${P/ruby-/}"
SRC_URI="http://gems.rubyforge.org/gems/${MY_P}.gem"

I'm curious to know if this worked when you committed it, which is why I haven't fixed it yet.
Comment 2 Ingmar Vanhassel (RETIRED) gentoo-dev 2008-01-09 04:45:15 UTC
(In reply to comment #1)
> I'm curious to know if this worked when you committed it, which is why I
> haven't fixed it yet.

Admittedly, so am I, but can this get fixed meanwhile?
Comment 3 Richard Brown (RETIRED) gentoo-dev 2008-01-09 09:31:28 UTC
Fixed in CVS