[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: EPEL Packages in need of building for EL-6



I would very much like build balsa for EL-6 but it requires libesmtp which has no EL-6 branch. I am libesmtp packager for fedora and I have unsuccessfully tried to create it. I have found

http://fedoraproject.org/wiki/EPEL/FAQ#How_do_I_request_a_EPEL_branch_for_an_existing_Fedora_package.3F

and created
https://bugzilla.redhat.com/show_bug.cgi?id=612334

I have not got a response yet, though.

I do not quite know what the next step should be...

Pawel

On 07/08/2010 10:37:15 AM, Mark Chappell 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: pawsa
balsa

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





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]