Spec URL: http://www.kanarip.com/custom/SPECS/rubygem-jeweler.spec SRPM URL: http://www.kanarip.com/custom/f12/SRPMS/rubygem-jeweler-1.4.0-1.fc12.src.rpm Description: \ Jeweler provides two things: * Rake tasks for managing gems and versioning of a GitHub project * A generator for creating kickstarting a new project * NOTE: %check has a lot of dependencies not yet in Fedora, so it's disabled for now
Hi Jeroen, There's a missing BuildRequires on rubygem-rcov. After disabling %check, the package builds fine, but please have a look at the rpmlint output, and your umask :-)
The rcov buildrequires is in there, it's just commented out as it's only need in %check which we can't execute now anyways, because of the buildrequires for %check that are not in Fedora yet.
Ah, I didn't see that. The %check section isn't disabled in the above spec. If you're going to use %check, don't forget to add a BR on rubygem(rake). %{geminstdir}/%{gemname}.gemspec can be removed, it's already in %{gemdir}/specifications/%{gemname}-%{version}.gemspec
What is the status of this bug?
jeweler.gemspec contains the following lines: s.add_runtime_dependency(%q<git>, [">= 1.2.5"]) s.add_runtime_dependency(%q<rubyforge>, [">= 2.0.0"]) s.add_runtime_dependency(%q<gemcutter>, [">= 0.1.0"]) AFAIK it means rubyforge and gemcutter gems should be added to the Require section in the spec file. Rubyforge gem also needs to be updated in Fedora, as jeweler complains about its version (when I add it to the Require section): irb(main):003:0> require 'rubygems' => true irb(main):004:0> require 'jeweler' Gem::LoadError: RubyGem version error: rubyforge(1.0.5 not >= 2.0.0)
Would someone update the status of this bug? By the way I submitted rubyforge 2.0.4 / hoe 2.5.0 / fixed gemcutter 0.3.0 updates for F-12 testing / F-13 stable (for F-13 updates request will go to stable in a day, perhaps). Currently I have no plan to update F-11 rubyforge 1.0.5 to 2.0.4. Karel and kanarip, do you need jeweler also for F-11?
Mamoru, thank you for the updates. I do not need jeweler in F-11.
Should this review be canceled? I would like to have jeweler in Fedora/EPEL and can package it up if this review is going nowhere.
Would someone update the status of this bug? Currently the review request for rubygem-construct blocks this review, however as far as I checked jeweler-1.4.0.gem, construct does not seem to be needed on runtime.
Someone ping again?
Jeweler is used in rubygem-robots.
In reply to comment #8: Sure, if you want to pick it up that would be great.