This is a tracker bug for new package requests in Fedora Extras, when the
packager is not already sponsored.
SPONSORS: when you accept the responsibility of reviewing a package, please
take it off of this list.
People should not sit in NEED-SPONSOR status and just expect sponsorship. The
best way to get sponsorship is to continue doing other work, like reviewing
other packages, giving helpful advice, or submitting more packages for review.
Having approved packages is *NOT* the requirement for gaining cvsextras
sponsorship. Instead demonstrating that you understand the packaging guidelines
and Fedora process to sponsor members is what is necessary to gain sponsorship.
Reassigning to email@example.com at the request of Roozbeh. (See
The summary was wrong and FE-NEW is no longer used for new review requests
Adding Tracking keyword
Reporter changed to firstname.lastname@example.org per request of original reporter.
Once you sponsor someone, please remember to remove the FE-NEEDSPONSOR tag to avoid noise in the blocker bug.
Spec URL: https://fcon.fedorapeople.org/files/f22/rubygem-fpm.spec
SRPM URL: https://fcon.fedorapeople.org/files/f22/rubygem-fpm-1.3.3-1.fc22.src.rpm
Description: Convert directories, rpms, python eggs, rubygems, and more to rpms, debs, solaris packages and more.
Fedora Account System Username: fcon
fpm creates rpms from ruby gems, python eggs and installation sources easily.
COPR - https://copr.fedoraproject.org/coprs/fcon/fpm/
Cached list of open bugs with better formatting is available here:
List of sponsors can be found here:
This is a tracker bug and should not be closed.
Ah ok sorry for that.
csutherl's scratch build of fedora-tomcat-epel?#9661f8da0d7e82b63ef65ebe467e0eb103ae624f for el6-candidate and git://pkgs.fedoraproject.org/fedora-tomcat-epel?#9661f8da0d7e82b63ef65ebe467e0eb103ae624f failed http://koji.fedoraproject.org/koji/taskinfo?taskID=11823023
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.