EPEL Packages in need of building for EL-6
sixy at gmx.com
Thu Jul 8 08:58:29 UTC 2010
On 07/08/2010 09:36 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: sixy
mrepo I very recently took ownership of, and am actively working on
updating and fixing various bugs. I hope to have a fixed and updated
version in -testing in the next few days. There doesn't seem to me to
be much point in building the current version for EL-6, as I know it
will not work properly, and will be updated so soon.
netsniff-ng is awaiting an upstream release to fix various issues with
the current svn snapshot. I am closely following upstream mailing lists
- the 0.5.5.0 branch is getting very close to being stable now and I
expect to have a stable package of this long before RHEL 6 is released.
I can build this one for EL-6 before this if desired, however the coming
release will change command-line syntax and output formatting somewhat
so my original intention was to hold off until the new package was ready.
Please let me know of any comments on either!
P.S. I am not currently subscribed to epel-devel list, but hopefully
will have 5 mins today to sort that out. In any case, it's best to
contact me directly for the moment.
> 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 :
> 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 :
> 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
More information about the epel-devel-list