On Thu, 3 Mar 2011 14:42:33 +0100
Jan-Frode Myklebust <janfrode(a)tanso.net> wrote:
On Thu, Mar 03, 2011 at 08:13:29AM -0500, Jon Stanley wrote:
>
> Are you a Fedora package maintainer? If so, you need to just request
> branches through the normal SCM admin procedure.
I'm not.
> If not, then you need
> to be sponsored into the packager group, see
>
https://fedoraproject.org/wiki/Join_the_package_collection_maintainers
> for details.
Seeing as amavisd-new is available in F14:
http://download.fedora.redhat.com/pub/fedora/linux/releases/14/Everything...
and the missing dependencies for it is available from EPEL5:
http://download.fedora.redhat.com/pub/epel/5/SRPMS/perl-Convert-TNEF-0.17...
http://download.fedora.redhat.com/pub/epel/5/SRPMS/cabextract-1.3-1.el5.s...
http://download.fedora.redhat.com/pub/epel/5/SRPMS/altermime-0.3.7-2.el5....
and everything passes a trivial build and start test on RHEL6 -- so
should I take over maintainership of these all, and submit them
following the Join_the_package_collection_maintainers routine ?
Well, there's (at least) one additional monkey wrench in this:
recently we revamped clamav in EPEL.
We need to fix up amavisd-new to handle the new clamav.
So, if you could modify the package for the new clamav that would be
outstanding. ;)
Additionally, if we can get one of the amavisd-new maintainers to offer
to mentor you, we can sponsor you that way. See:
http://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_grou...
Hope that helps.
kevin