New version as of 12. July Reproducible: Always
Trying to bump this. Emerging in screen over ssh fails with: * Scanning for an open DISPLAY to start Xvfb ... /var/tmp/portage/media-sound/rubyripper-0.5.7/temp/environment: line 3027: 14560 Aborted ${XVFB} :${XDISPLAY} -fp built-ins -screen 0 800x600x24 >&/dev/null * Starting Xvfb on $DISPLAY=1 ... ./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 --prefix=/usr --enable-gtk2 --enable-cli Checking the NEEDED dependencies.... cdparanoia found... Checking the OPTIONAL dependencies... Testing support for the graphical frontend... /usr/lib64/ruby/site_ruby/1.8/gtk2.rb:13:in `init': Cannot open display: :1 (RuntimeError) from /usr/lib64/ruby/site_ruby/1.8/gtk2.rb:13 from /usr/lib64/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require' from /usr/lib64/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require' from ./configure:99:in `check_deps' from ./configure:182 * * ERROR: media-sound/rubyripper-0.5.7 failed. * Call stack: * ebuild.sh, line 49: Called src_configure * environment, line 2521: Called Xeconf '--prefix=/usr' '--enable-gtk2' '--enable-cli' * environment, line 129: Called virtualmake '--prefix=/usr --enable-gtk2 --enable-cli' * environment, line 3059: Called econf '--prefix=/usr' '--enable-gtk2' '--enable-cli' * ebuild.sh, line 536: Called die * The specific snippet of code: * die "econf failed" And I remember having similar failures with earlier versions.
Just so people know. I just copied the 0.5.5-r1 ebuild to my local overlay. Renamed it to 0.5.7 and copied over the files directory and emerged ... and the new version built fine. I am on x86.
Committed. Works when emerging from an xterm. I hate that, but I don't want to spend time on figuring out how to hack it so you can emerge it outside of X.
Yes, I can compile rubyripper-0.5.7 as is it now on portage outside X (and not inside kde4). But starting gives me these errors: rrip_cli /usr/lib64/ruby/site_ruby/1.8/rr_lib.rb:40: warning: Insecure world writable dir /w_LD2 in PATH, mode 040777 /usr/lib64/ruby/gems/1.8/gems/locale-2.0.5/lib/locale.rb:239:in `collect_candidates': undefined method `size' for nil:NilClass (NoMethodError) from /usr/lib64/ruby/gems/1.8/gems/locale-2.0.5/lib/locale.rb:222:in `candidates' from /usr/lib64/ruby/gems/1.8/gems/gettext-2.1.0/lib/gettext/runtime/textdomain_manager.rb:78:in `each_textdomains' from /usr/lib64/ruby/gems/1.8/gems/gettext-2.1.0/lib/gettext/runtime/textdomain_manager.rb:102:in `translate_singluar_message' from /usr/lib64/ruby/gems/1.8/gems/gettext-2.1.0/lib/gettext.rb:128:in `_' from /usr/bin/rrip_cli:62:in `parse_options' from /usr/lib64/ruby/1.8/optparse.rb:791:in `initialize' from /usr/bin/rrip_cli:61:in `new' from /usr/bin/rrip_cli:61:in `parse_options' from /usr/bin/rrip_cli:37:in `initialize' from /usr/bin/rrip_cli:502:in `new' from /usr/bin/rrip_cli:502 or /usr/lib64/ruby/site_ruby/1.8/rr_lib.rb:40: warning: Insecure world writable dir /w_LD2 in PATH, mode 040777 /usr/lib64/ruby/gems/1.8/gems/locale-2.0.5/lib/locale.rb:239:in `collect_candidates': undefined method `size' for nil:NilClass (NoMethodError) from /usr/lib64/ruby/gems/1.8/gems/locale-2.0.5/lib/locale.rb:222:in `candidates' from /usr/lib64/ruby/gems/1.8/gems/gettext-2.1.0/lib/gettext/runtime/textdomain_manager.rb:78:in `each_textdomains' from /usr/lib64/ruby/gems/1.8/gems/gettext-2.1.0/lib/gettext/runtime/textdomain_manager.rb:102:in `translate_singluar_message' from /usr/lib64/ruby/gems/1.8/gems/gettext-2.1.0/lib/gettext.rb:128:in `_' from /usr/bin/rrip_gui:65:in `create_buttonbox' from /usr/bin/rrip_gui:50:in `initialize' from /usr/bin/rrip_gui:1304:in `new' from /usr/bin/rrip_gui:1304 Nothing else seemed to happen. eselect ruby list: Available Ruby profiles: [1] ruby18 (with Rubygems) *
That's a different issue, and you should open a new bug for it, instead of attaching it to an already fixed one.
