ruby-cvs, as you can see by trying to use it is dead. The mirror was taken down in favor or SVN. I've made a rudimentary SVN ebuild. Also, ruby-svn works on my ~amd64 box. Problems: the 'threads' IUSE _must_ be enabled or it won't build. You need a previous version of Ruby installed because it tries to execute a ruby before it is done compiling/installed. (Feel free to update the ebuild and force these). Reproducible: Always Steps to Reproduce: emerge ruby-cvs Actual Results: localhost kyle # emerge ruby-cvs Calculating dependencies... done! >>> Verifying ebuild Manifests... >>> Emerging (1 of 1) dev-lang/ruby-cvs-1.9.0-r2 to / * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] >>> Unpacking source... * Fetching CVS module ruby into /distfiles/cvs-src ... * Running cvs -q -f -z1 -d ":pserver:anonymous:anonymous@cvs.ruby-lang.org:/src" login Logging in to :pserver:anonymous@cvs.ruby-lang.org:2401/src cvs [login aborted]: connect to cvs.ruby-lang.org(221.186.184.68):2401 failed: Connection refused !!! ERROR: dev-lang/ruby-cvs-1.9.0-r2 failed. Call stack: ebuild.sh, line 1614: Called dyn_unpack ebuild.sh, line 751: Called qa_call 'src_unpack' ebuild.sh, line 44: Called src_unpack ebuild.sh, line 1304: Called cvs_src_unpack cvs.eclass, line 504: Called cvs_fetch cvs.eclass, line 332: Called die !!! cvs login command failed !!! 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-lang/ruby-cvs-1.9.0-r2/temp/build.log'. Expected Results: should have emerged ruby-cvs
Created attachment 115765 [details] ruby-svn-1.9.0.ebuild Needs work -- see "Problems" in original.
I have put dev-lang/ruby-cvs in package.mask: it doesn't make sense to keep it around if it's broken.
dev-ruby/ruby-cvs is no longer in the tree. I also don't expect that we will add a ruby-svn ebuild any time soon, especially since there are now regular ruby 1.9.x releases that we currently track in the ruby overlay. I'm closing this bug as WONTFIX for this reason. Perhaps we will add something like this in the future when we get a lot more manpower in the ruby herd.
