Description of problem: Please rebuild perl-MLDBM for EPEL 4 and 5 Version-Release number of selected component (if applicable): perl-MLDBM-2.01-5 Actual results: No perl-MLDBM in EPEL 4 and 5 Expected results: Package perl-MLDBM in EPEL 4 and 5, because it's a perl-BerkeleyDB dependency. Additional info: Please let me know, when you're not interested in maintaining the package there.
Rebuilding in mock at EPEL 5 succeeded and looks fine: Wrote: /builddir/build/RPMS/perl-MLDBM-2.01-5.el5.noarch.rpm
Ping?
*** Bug 305721 has been marked as a duplicate of this bug. ***
I think for new branch is review needed: http://fedoraproject.org/wiki/PackageMaintainers/CVSAdminProcedure and I didn't find any review of this package.
CVS request is missing, so here it is: Package Change Request ====================== Package Name: perl-MLDBM New Branches: EL-4 EL-5
Well, I'm still waiting for Jose. If he doesn't care about the package at all, I would take it - or just the EPEL branches. If he cares about the package, I will be just quiet. Thus I put no branch request into.
I am pretty sure Jose is no longer interested in fedora. Robert: Let me know if you would like to wait a bit more, or would like me to just go ahead and make those branches for you now.
jpo has been marked as AWOL. Please see: https://www.redhat.com/archives/fedora-devel-list/2007-November/msg02343.html for more info.
So someone has already built this, and we can close the ticket, correct?
I see perl-MLDBM-2.01-5.el5 in the epel-5 testing repo, built on Nov 17th. I don't see any build yet for epel-4.
(In reply to comment #10) > I see perl-MLDBM-2.01-5.el5 in the epel-5 testing repo, built on Nov 17th. > > I don't see any build yet for epel-4. Weird. I don't know what I thought I saw. I've updated the spec to match the devel branch and fired off EL-4 and EL-5 builds.
OK, it is definitely in testing now.
Clearing the cvs flag here as no cvsadmin attention seems needed.