>Number: 5382 >Category: mod_auth-any >Synopsis: mod_auth_db doesn't support Berkeley DB/3.x >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: open >Class: change-request >Submitter-Id: apache >Arrival-Date: Sat Nov 27 11:40:00 PST 1999 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.3.9 >Environment: Linux blighty.com 2.0.36 #2 Wed Dec 2 20:01:51 PST 1998 i686 unknown
Berkeley DB 3.0.55 >Description: mod_auth_db supports BerkeleyDB 1.x and 2.x APIs transparently, but not 3.x. >How-To-Repeat: Build with DB 3.x >Fix: http://blighty.com/apache-auth-db3.patch has a simple context diff to add 3.x support. Lightly tested - it seems to work fine here. >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, you need] [to include <[EMAIL PROTECTED]> in the Cc line and make sure the] [subject line starts with the report component and number, with ] [or without any 'Re:' prefixes (such as "general/1098:" or ] ["Re: general/1098:"). If the subject doesn't match this ] [pattern, your message will be misfiled and ignored. The ] ["apbugs" address is not added to the Cc line of messages from ] [the database automatically because of the potential for mail ] [loops. If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request from a ] [developer. Reply only with text; DO NOT SEND ATTACHMENTS! ]
