http://fedoraproject.org/wiki/EPEL/Reports/Week03 = Weekly EPEL Summary = Week 03/2008 == Most important happenings == * about 170 packages were moved from EPEL4 testing to EPEL4 proper in the last monthly move; for details see [https://www.redhat.com/archives/epel-devel-list/2008-January/msg00093.html announcement] and [https://www.redhat.com/archives/epel-devel-list/2008-January/msg00109.html Build report]; next move for EPEL5 planed for early February * reminder: Fedora contributers that want to build for EPEL but don't have a RHEL/CentOS box/VM for testing: feel free to ask on the [https://www.redhat.com/mailman/listinfo/epel-devel-list epel-devel-list] for help or contact someone from the [http://fedoraproject.org/wiki/EPEL/SIG EPEL SIG] * second reminder: if you want to build you package in EPEL but can't because a package your package depends on is not available in EPEL then just add it to the [http://fedoraproject.org/wiki/EPEL/WishList EPEL wishlist]; someone (normally [:ThorstenLeemhuis:knurd]) will send a mail to the package owner then asking branch the package in question for EPEL. You can of course send a mail to the owner of the package in question directly as well; see http://fedoraproject.org/wiki/EPEL/AskForFedoraPackageInEPEL for details Note that not all Fedora contributers participate in EPEL and those "please branch for EPEL" mails often get ignored7fall of the table. In those cases you are free to claim ownership of the package you need yourself (just CC the Fedora owner in the bugzilla branch request to make sure he's aware of the fact that the package is in EPEL). For details see "EPEL branching if Fedora maintainer does not react" on http://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies == Mailing list == === Noteworthy discussions === * [https://www.redhat.com/archives/epel-devel-list/2008-January/msg00094.html Zenoss Core for EPEL] == Meeting == === Next Meeting === Wednesday, 20080130 at 18:00 UTC in #fedora-meeting. === Last weeks meeting === Attendees: * [:RobMyers:_blah_] * [:Jonathan Steffan:daMaestro] * [:JesseKeating:f13] * [:JeffSheltren:Jeff_S] * [:ThorstenLeemhuis:knurd] * [:KevinFenzi:nirik] * [:KarstenWade:quaid] Summary: * next testing -> stable move | knurd | http://fedoraproject.org/wiki/EPEL/Tasks/NextTestingStableMove * being worked on (and realized already when this got published; see above) * knurd will write down how to actually prepare the move (happened in between as well; see http://fedoraproject.org/wiki/EPEL/Tasks/NextTestingStableMove) * EL-updates to the buildsys | mmcgrath | http://fedoraproject.org/wiki/EPEL/Tasks/Misc * skvidal made that happen * KojiAndBodhiForEpel | mmcgrath | http://fedoraproject.org/wiki/EPEL/Tasks/KojiAndBodhiForEpel * some progress; f13 reviewed an initial patch from _blah_; more work from _blah_ to come * permission to use spec files in other projects | http://fedoraproject.org/wiki/EPEL/Tasks/Misc * seems to be solved finally thx to spot; see http://fedoraproject.org/wiki/Licensing#LicenseOfFedoraSPECFiles * broken dep reports go to the list | http://fedoraproject.org/wiki/EPEL/Tasks/Misc * more discussion on the list * Free discussion around EPEL -- FUDCOn and EPEL? * there was no EPEL session on FUDCOn * f13> | I talked to the zenoss guy there, whom I've talked with before. He wasn't actually aware of EPEL and will be directing his folks to get ZenOSS packages ready for EPEL * Free discussion around EPEL -- get more contributers for EPEL * nirik> | I was thinking we should do a monthly or so email to the fedora-devel list asking people to consider branching for epel... I think many of the new maintainers aren't aware it exists... * knurd> | nirik, maybe we should mail the contributers directly that don't have a single EPEL package * some Fedora contributers might be willing to build for EPEL, but don't have a RHEL/CentOS box for testing; it was discussed if we need a group of people that can help in such situations; it was agreed that the EPEL SIG is that group * some more discussion around this; see 00:11:09 and later; * Free discussion around EPEL -- broken deps * nirk will try to file bugs for those broken deps that are around for more than just a few days * Free discussion around EPEL * nirik> | note that there are 26 open epel bugs... most of them are the broken deps stuff... a few others tho * clamav status: silug has agreed to maintain the fedora clamav in epel. == Stats == === General === Number of EPEL Contributors: 166 We welcome 1 new contributors: gospo === EPEL 5 === Number of source packages: 991 Number of binary packages: 1841 There are 13 new Packages: * ack | Grep-like text finder * bwm-ng | Bandwidth Monitor NG * jigdo | Ease distribution of large files over the Internet * libgdiplus | libgdiplus: An Open Source implementation of the GDI+ API * libstatgrab | Make system statistics * mono | a .NET runtime environment * perl-Devel-Leak | Utility for looking for perl objects that are not reclaimed * perl-File-Copy-Recursive | Extension for recursively copying files and directories * perl-File-Next | File::Next Perl module * perl-Module-Install | Standalone, extensible Perl module installer * postgresql-plruby | PostgreSQL Ruby Procedural Language * vnstat | Console-based network traffic monitor * wiggle | A tool for applying patches with conflicts === EPEL 4 === Number of source packages: 600 Number of binary packages: 1129 There are 15 new Packages: * ack | Grep-like text finder * bwm-ng | Bandwidth Monitor NG * jigdo | Ease distribution of large files over the Internet * libstatgrab | Make system statistics * perl-BSD-Resource | BSD process resource limit and priority functions * perl-Class-Inspector | Get information about a class and its structure * perl-Devel-Leak | Utility for looking for perl objects that are not reclaimed * perl-File-Copy-Recursive | Extension for recursively copying files and directories * perl-File-Next | File::Next Perl module * perl-Module-CoreList | Perl core modules indexed by perl versions * perl-Module-Install | Standalone, extensible Perl module installer * perl-Module-Pluggable | Automatically give your module the ability to have plugins * perl-Module-ScanDeps | Recursively scan Perl code for dependencies * pstoedit | Translates PostScript and PDF graphics into other vector formats * vnstat | Console-based network traffic monitor ---- ["CategoryEPELReports"] -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
