[Pkg-openldap-devel] Bug#447224: Bug#447224: openldap2.3: [debconf_rewrite] Debconf templates and debian/control review

[Russ Allbery]

Christian Perrier <bubulle at debian.org> writes:

> Attached is my current version of the debconf templates. Let's triple
> confirm that it is OK to you and I'll start the translation update
> round.

Two more changes:

> Template: slapd/migrate_ldbm_to_bdb
> Type: boolean
> Default: true
> _Description: Change backend type from LDBM to BDB?
>  The LDBM backend type has been deprecated in OpenLDAP 2.2.
>  BDB is the recommended choice.
>  .
>  When the BDB backend is used, it must be configured properly. For
>  more information, see /usr/share/doc/slapd/README.DB_CONFIG.gz.
>  .
>  If you enable this option, an attempt will be made to update the
>  configuration to use BDB instead of LDBM and convert the databases.

This should be more severe now, since we no longer support LDBM at all.
How about:

Template: slapd/migrate_ldbm_to_bdb
Type: boolean
Default: true
_Description: Change backend type from LDBM to BDB?
 The LDBM backend type has serious stability problems and has been
 deprecated by OpenLDAP as of 2.2. It is no longer supported by the
 OpenLDAP Debian packages. BDB is the recommended database backend.
 .
 When the BDB backend is used, it must be configured properly. For
 more information, see /usr/share/doc/slapd/README.DB_CONFIG.gz.
 .
 If you enable this option, an attempt will be made to update the
 configuration to use BDB instead of LDBM and convert the databases.
 If you do not enable this option, the upgrade will be aborted.

> Template: slapd/backend
> Type: select
> Choices: BDB, HDB
> Default: BDB
> _Description: Database backend to use:
>  The BDB backend is recommended.
>  When using it, the database must be configured accordingly.
>  Please check /usr/share/doc/slapd/README.DB_CONFIG.gz for more details.
>  .
>  HDB uses a similar storage format to BDB but adds support for subtree
>  renames. It is otherwise identical to BDB and supports the same
>  configuration options.

Quanah says that HDB is now recommended over BDB.  So let's instead say:

Template: slapd/backend
Type: select
Choices: HDB, BDB
Default: HDB
_Description: Database backend to use:
 The HDB backend is recommended. HDB and BDB use similar storage formats,
 but HDB adds support for subtree renames. Both support the same
 configuration options.
 .
 In either case, you should review the resulting database configuration
 for your needs. See /usr/share/doc/slapd/README.DB_CONFIG.gz for more
 details.

Everything else looks good to me.

-- 
Russ Allbery (rra at debian.org)               <http://www.eyrie.org/~eagle/>