https://bugzilla.redhat.com/show_bug.cgi?id=1052524 --- Comment #4 from Henrik Hodne <henrik@xxxxxxxx> --- (In reply to Ken Dreyer from comment #3) > (In reply to Henrik Hodne from comment #2) > > I uploaded the new spec and SRPM in the same location as listed above. > > It's not strictly required, but it's a good idea to bump the release number > and upload a new SRPM. This feels a little bureaucratic, but it will show > potential sponsors that you understand the process of bugfixing and > releasing new versions in Fedora. (In Fedora's build system, Koji, every new > build requires a unique NEVR, Name-Epoch-Version-Release combination). Ah, I'll do that in the future then. I didn't do it this time since the package hadn't been released, but I have no problem bumping it in the future for bugfixes even if the previous ones haven't been released. > Another thing that will help with getting sponsored is submitting more than > one package, or in particular, doing unofficial reviews of others' packages. > Either approach will show sponsors that you understand the Fedora guidelines > and you're a reasonable person to work with :) I already have one other package submitted: the_silver_searcher (bug 1008063). I also have a few other RubyGems packages I want to submit (all dependencies of Rubinius, which I also have mostly working locally, but since it depends on some RubyGems I figured I'd start with those). I just started with this one to check if I was on the right track for packaging RubyGems. Thanks for the tips! -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review