EPEL Packages in need of building for EL-6

[Colin Coe]

Apologies for this reply to an automated email...

I've tried to rebuild for EL-6 but am getting cvs.fedoraproject.org
connection refused messages.  I do want to continue maintaining these
packages.  I started requesting help on #EPEL last night and will
continue again tonight.

Thanks

CC

On Thu, Jul 8, 2010 at 4:37 PM, Mark Chappell <tremble at fedoraproject.org> wrote:
>
> Dear Package owner,
>
> On Monday June 28th at the EPEL meeting on IRC we agreed to an initial
> target date of August 15th for having all packages built for EL-6.
>
> Below is a summary of EPEL packages for Enterprise Linux 6 that you own
> which have not yet been built.
>
> Owner: coec
> editarea
> perl-Net-Whois
> perl-Net-Whois-IP
> RackTables
> vmpsd
>
> As with Rawhide Bodhi is not currently in use for EPEL for EL-6, a switch
> will be made closer to RHEL-6 General Availability.
>
> We are aware that there are some packages which got branched which
> either you may not be interested in maintaining for EL-6 or which we
> have not caught as having made it into EL-6.
>
> If you do not wish to maintain your package for EL-6 please follow the
> usual process for orphaning a package for a branch :
> https://fedoraproject.org/wiki/Orphaned_package_that_need_new_maintainers#Orphaning_Procedure
>
> If you do not currently have the time to work on packages for EL-6, but
> would like to continue maintaining you packages it would be appreciated if
> you could either ask on the EPEL-devel mailing list or over on #epel on
> freenode and we will find some extra help to help you get your packages
> built for EL-6.
>
> If we have not caught the fact that the package has now made it`s way
> into EL-6 please follow the usual process for orphaning a package for a
> branch :
> https://fedoraproject.org/wiki/Orphaned_package_that_need_new_maintainers#Orphaning_Procedure
> additionally please make sure to note that its moved to rhel when
> requesting that it be blocked.
>
> Any questions or concerns, please ask over on #epel on freenode or
> the epel-devel mailing list
>



-- 
RHCE#805007969328369