Please stabilize this version, the gentoo website is running 0.6.4 right now, -r1 just does ruby19 removal.
amd64; all looks ok
addendum; testing; USE="-*" It doesn't invoke a failure, rather it also takes out the default RUBY_TARGETS="ruby18", causing it to exit. The ewarn is in place informing the need to add this to /etc/make.conf. This is a border line thing, the ebuild doing what as intended in this 'scenario'. I wonder if portage or emerge was intended to take out these additional variables with USE="-*"
it does not work for me: This is the output when I try to lauch gorg: /usr/lib64/rubyee/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require': no such file to load -- gorg/base (LoadError) from /usr/lib64/rubyee/site_ruby/1.8/rubygems/custom_require.rb:31:in `require' from /usr/bin/gorg:32 Works the actual stable
Ago; I copied /etc/gorg/gorg.conf.sample to /etc/gorg/gorg.conf , then launched. gentoo64-vm gorg # gorg Starting the Gorg web server on 127.0.0.1:8008 Hit Ctrl-C or type kill [pid number] to stop it Worked for me both as root and user. This bears no resemblance to yourlaunching flaw; appears need to re-emerge the ruby dependent packages. Why mine are fine have no idea
(In reply to comment #4) > Ago; > > I copied /etc/gorg/gorg.conf.sample to /etc/gorg/gorg.conf , then launched. > > gentoo64-vm gorg # gorg > > Starting the Gorg web server on 127.0.0.1:8008 > > Hit Ctrl-C or type kill [pid number] to stop it > > Worked for me both as root and user. > > This bears no resemblance to yourlaunching flaw; appears need to re-emerge the > ruby dependent packages. Why mine are fine have no idea Ian, I know it, I use it for italian translation and it is already configured. So, if actual stable works and ~arch no, I guess is not my bad. @Robbat2 the configuration's syntax of new gorg is different from the actual stable?
Builds and runs fine on x86. Please mark stable for x86.
(In reply to comment #5) > @Robbat2 > the configuration's syntax of new gorg is different from the actual stable? No, there are no config changes at all 0.6.4->0.6.4-r1. Between 0.6.3 and 0.6.4 there was one change, a new argument, "listen".
(In reply to comment #3) alex@neon gorg % grep USE_RUBY * gorg-0.6.3-r2.ebuild:USE_RUBY="ruby18" gorg-0.6.4.ebuild:USE_RUBY="ruby18" gorg-0.6.4-r1.ebuild:USE_RUBY="ruby18" No rubyee. Check your default ruby interpreter. Works here, nothing to do for ruby@ here.
(In reply to comment #8) > (In reply to comment #3) > > alex@neon gorg % grep USE_RUBY * > gorg-0.6.3-r2.ebuild:USE_RUBY="ruby18" > gorg-0.6.4.ebuild:USE_RUBY="ruby18" > gorg-0.6.4-r1.ebuild:USE_RUBY="ruby18" > > No rubyee. Check your default ruby interpreter. > Works here, nothing to do for ruby@ here. Alex, first ruby should be here because it is in metadata.xml. Second, if there are no changes between 0.6.3 and 0.6.4 (as interpreter) and the stable works for me, probably anything goes bad with 0.6.4-r1 anyway I have in make.conf: RUBY_TARGETS="ree18 ruby18 ruby19"
(In reply to comment #9) > (In reply to comment #8) > > (In reply to comment #3) > > > > alex@neon gorg % grep USE_RUBY * > > gorg-0.6.3-r2.ebuild:USE_RUBY="ruby18" > > gorg-0.6.4.ebuild:USE_RUBY="ruby18" > > gorg-0.6.4-r1.ebuild:USE_RUBY="ruby18" > > > > No rubyee. Check your default ruby interpreter. > > Works here, nothing to do for ruby@ here. > > Alex, first ruby should be here because it is in metadata.xml. Fair enough. > > anyway I have in make.conf: > > RUBY_TARGETS="ree18 ruby18 ruby19" That is not relevant.
@robbat2 we can try to solve this issue in bug 403563, and atm, for me is a blocker.
x86 stable
amd64 stable
ppc done; closing as last arch
