https://bugzilla.redhat.com/show_bug.cgi?id=768846

Jan Pazdziora <jpazdzi...@redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |CLOSED
         Resolution|---                         |NEXTRELEASE
        Last Closed|2012-08-07 14:39:13         |2013-07-04 03:33:31

--- Comment #15 from Jan Pazdziora <jpazdzi...@redhat.com> ---
(In reply to Joe Orton from comment #12)
> Paul's comment 9 is a good point, downgrading perl-BerkeleyDB to db 4.8 as
> an f17 update will undoubtedly break existing users of the module.  So I
> think  we're screwed here, we can't fix it until f18.   We could ship an
> alternative, conflicting version of perl-BerkeleyDB linked against lidb-4.8
> if somebody was screaming for that.  But it's probably best to
> CLOSED->SORRY->NEXTRELEASE this.

Yes, I confirm that with Fedora 19 and the packages listed below, the problem
is gone.

# rpm -q httpd mod_perl perl-BerkeleyDB
httpd-2.4.4-6.fc19.x86_64
mod_perl-2.0.7-12.20130221svn1448242.fc19.x86_64
perl-BerkeleyDB-0.51-4.fc19.x86_64

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug 
https://bugzilla.redhat.com/token.cgi?t=KaSkLQT1Bi&a=cc_unsubscribe
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Reply via email to