Spec URL: http://tejas.fedorapeople.org/ruby-build/ruby-build.spec
SRPM URL: <srpm info here>
Description: ruby-build provides a simple way to compile and install different versions of Ruby on UNIX-like systems.
I'm currenly asking the maintainer of ruby-build to tag releases of ruby-build. Currently, the version number was set by me. I wanted a bit of feedback on the steps in the %install, specifically, if this line is allowed:
(as this calls install.sh in the tarball).
SRPM URL: http://tejas.fedorapeople.org/ruby-build/ruby-build-20110906.1-2.fc15.src.rpm
I checked with mether about the style of using install.sh, and he felt it was acceptable.
I am triaging old review tickets. I apologize that it has been so long since
anyone looked at this ticket, but there are more packages submitted now than
the pool of reviewers can handle, and some tickets fall through the cracks.
In order to keep the queue manageable, we need to occasionally find tickets
which are not reviewable so as to not waste what reviewer time is available.
Accordingly, I'm pinging this ticket and setting NEEDINFO. If you are still
interested in having your package reviewed, please do the following:
* Make sure your package still reflects the current status of its upstream.
* Check that your package still builds on current Fedora releases.
* Audit your package versus the current status of the packaging guidelines,
current rpmlint and current fedora-review tools.
And, finally, reply, making sure that the NEEDINFO flag gets cleared so that
this ticket reappears in the review queue. I can't promise a review if you
reply, but by closing out the stale tickets we can devote extra attention to
the ones which aren't stale.
jgrulich's scratch build of kdevelop?#c8e2b9bc57f11e41f3dc6612cdbcc591078d9062 for f22-candidate and git://pkgs.fedoraproject.org/kdevelop?#c8e2b9bc57f11e41f3dc6612cdbcc591078d9062 completed http://koji.fedoraproject.org/koji/taskinfo?taskID=11212117
There had been no response from the requester to a needs info flag in over a year.
Closing this bug as per policy