Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 212321 - dev-ruby/htmlentities ~amd64 keyword request
Summary: dev-ruby/htmlentities ~amd64 keyword request
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High enhancement (vote)
Assignee: AMD64 Project
URL:
Whiteboard:
Keywords: KEYWORDREQ
Depends on:
Blocks:
 
Reported: 2008-03-04 21:56 UTC by Adam James
Modified: 2008-03-05 19:03 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 Adam James 2008-03-04 21:56:32 UTC
$ ruby -e 'require "htmlentities"; p HTMLEntities.encode_entities("<>&")'
"&lt;&gt;&amp;"

$ emerge --info
Portage 2.1.4.4 (default-linux/amd64/2007.0, gcc-4.1.2, glibc-2.6.1-r0, 2.6.24-gentoo-r2 x86_64)
=================================================================
System uname: 2.6.24-gentoo-r2 x86_64 Intel(R) Xeon(R) CPU X3220 @ 2.40GHz
Timestamp of tree: Tue, 04 Mar 2008 05:16:01 +0000
app-shells/bash:     3.2_p17-r1
dev-lang/python:     2.4.4-r9
dev-python/pycrypto: 2.0.1-r6
sys-apps/baselayout: 1.12.11.1
sys-apps/sandbox:    1.2.18.1-r2
sys-devel/autoconf:  2.61-r1
sys-devel/automake:  1.6.3, 1.7.9-r1, 1.9.6-r2, 1.10
sys-devel/binutils:  2.18-r1
sys-devel/gcc-config: 1.4.0-r4
sys-devel/libtool:   1.5.26
virtual/os-headers:  2.6.23-r3
ACCEPT_KEYWORDS="amd64"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
Comment 1 Santiago M. Mola (RETIRED) gentoo-dev 2008-03-04 23:11:11 UTC
Fails on my stable chroot:

>>> Emerging (1 of 1) dev-ruby/htmlentities-4.0.0 to /
 * htmlentities-4.0.0.gem RMD160 SHA1 SHA256 size ;-) ...               [ ok ]
 * checking ebuild checksums ;-) ...                                    [ ok ]
 * checking auxfile checksums ;-) ...                                   [ ok ]
 * checking miscfile checksums ;-) ...                                  [ ok ]
 * checking htmlentities-4.0.0.gem ;-) ...                              [ ok ]
>>> Unpacking source...
>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/dev-ruby/htmlentities-4.0.0/work ...
>>> Source compiled.
>>> Test phase [none]: dev-ruby/htmlentities-4.0.0

>>> Install htmlentities-4.0.0 into /var/tmp/portage/dev-ruby/htmlentities-4.0.0/image/ category dev-ruby
/usr/lib64/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require': no such file to load -- sources (LoadError)
	from /usr/lib64/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `require'
	from /usr/lib64/ruby/site_ruby/1.8/rubygems/source_info_cache.rb:6
	from /usr/lib64/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require'
	from /usr/lib64/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `require'
	from /usr/lib64/ruby/site_ruby/1.8/rubygems/remote_installer.rb:12
	from /usr/lib64/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require'
	from /usr/lib64/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `require'
	from /usr/lib64/ruby/site_ruby/1.8/rubygems.rb:112:in `manage_gems'
	from /usr/bin/gem:10
 * 
 * ERROR: dev-ruby/htmlentities-4.0.0 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_install
 *             environment, line 2308:  Called gems_src_install
 *             environment, line 1324:  Called die
 * The specific snippet of code:
 *       gem install ${GEM_SRC} --version ${PV} ${myconf} --local --install-dir "${D}/${GEMSDIR}" || die "gem install failed";
 *  The die message:
 *   gem install failed

Can anyone reproduce this?

It works flawlessly on my main amd64 system.
Comment 2 Adam James 2008-03-05 11:06:39 UTC
I can't reproduce this using rubygems version 1.0.1. Presumably you're running 0.9.4 in the chroot?

From the code it looks like a paths issue in rubygems.
Comment 3 Hans de Graaff gentoo-dev Security 2008-03-05 19:03:13 UTC
Marked ~amd64. It works on my machine and we started using it today at work in a project on amd64. :-)

@Santiago: looks like a problem with your rubygems setup in the chroot.