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

Tue Nov 13 05:45:47 UTC 2007

Quoting Russ Allbery (rra at debian.org):

> 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.
   ^^^^^^^^^^^^^^^^^

Branding...:-)

I suggest "OpenLDAP packages" to be more neutral about the
distribution that uses the templates.

>  .
>  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.

Otherwise, fine by me.

> 
> > 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.

OK, then. "Final" templates attached (with Debian branding removed).
Shall we go for these ones?

(poor translators...including /me.....:-))

-------------- next part --------------
# These templates have been reviewed by the debian-l10n-english
# team
#
# If modifications/additions/rewording are needed, please ask
# debian-l10n-english at lists.debian.org for advice.
#
# Even minor modifications require translation updates and such
# changes should be coordinated with translators and reviewers.

Template: slapd/no_configuration
Type: boolean
Default: false
_Description: Omit OpenLDAP server configuration?
 If you enable this option, no initial configuration or database will be
 created.

Template: slapd/dump_database
Type: select
__Choices: always, when needed, never
Default: when needed
_Description: Dump databases to file on upgrade:
 Before the upgrade to a new version of the OpenLDAP server, the LDAP
 directories can be dumped into plain text LDIF files (in the
 standardized LDAP Data Interchange Format).
 .
 Selecting "always" will cause the databases to be dumped
 unconditionally before an upgrade. Selecting "when needed" will only
 dump the database if the new version is incompatible with the old
 database format and it needs to be reimported. Selecting "never" will
 cause no dump to occur.

Template: slapd/dump_database_destdir
Type: string
Default: /var/backups/slapd-VERSION
_Description: Directory for dumped databases:
 Please specify the directory where the LDAP databases will be exported.
 In this directory, several LDIF files will be created which correspond
 to the search bases located on the server. Make sure you have enough
 free space on the partition where it's located. The first
 occurrence of the string "VERSION" is replaced with the server version
 you are upgrading from.

Template: slapd/move_old_database
Type: boolean
Default: true
_Description: Move old database?
 There are still files in /var/lib/ldap which will probably break
 the configuration process. If you enable this option, the maintainer
 scripts will move the old database files out of the way before
 creating a new database.

Template: slapd/invalid_config
Type: boolean
Default: true
_Description: Retry configuration?
 The configuration you entered is invalid. Make sure that the DNS domain name
 is valid, the organization is not left empty and that the admin
 passwords match. If you decide not to retry the configuration the LDAP server
 will not be set up. Run 'dpkg-reconfigure slapd' if you want to retry later.

Template: slapd/domain
Type: string
_Description: DNS domain name:
 The DNS domain name is used to construct the base DN of the LDAP directory.
 For example, 'foo.example.org' will create the directory with
 'dc=foo, dc=example, dc=org' as base DN.

Template: shared/organization
Type: string
_Description: Organization:
 Please enter the name of the organization to use in
 the base DN of the LDAP directory.

Template: slapd/password1
Type: password
_Description: Administrator password:
 Please enter the password for the administrator entry in the LDAP directory.

Template: slapd/password2
Type: password
_Description: Confirm password:

Template: slapd/password_mismatch
Type: note
_Description: Password mismatch
 The administrator password and its confirmation must match. Please
 note that differences such as uppercase/lowercase and added
 whitespace matter.

Template: slapd/purge_database
Type: boolean
Default: false
_Description: Do you want the LDAP database to be removed when purging the package?

Template: slapd/internal/adminpw
Type: password
_Description: Encrypted administrator password:

Template: slapd/allow_ldap_v2
Type: boolean
Default: false
_Description: Allow LDAPv2 protocol?
 The obsolete LDAPv2 protocol is disabled by default in slapd.
 Programs and users should upgrade to LDAPv3.
 If some old programs can't use LDAPv3, you should
 select this option and 'allow bind_v2' will be added to the
 slapd.conf file.

Template: slapd/suffix_change
Type: boolean
Default: false
_Description: Back up current database and create a new one?
 The directory suffix (domain) you specified doesn't match the
 one currently in /etc/ldap/slapd.conf. Changing the directory suffix
 requires moving aside the current LDAP database and creating a new
 one. Please confirm whether you want to back up and abandon the current
 database.

Template: slapd/upgrade_slapcat_failure
Type: error
#flag:translate!:5
#flag:comment:4
# This paragraph is followed by a (non translatable) paragraph
# containing a command line
#flag:comment:6
# Translators: keep "$location" unchanged. This is a variable that
# will be replaced by a directory name at execution
_Description: slapcat failure during upgrade
 An error occurred during the attempt to upgrade the LDAP directory.
 .
 The 'slapcat' program, which attempts to
 extract the LDAP directory, failed. This may be caused by an
 incorrect configuration file (for example, missing 'moduleload'
 lines to support the backend database).
 .
 This failure will cause 'slapadd' to later fail. The old database files
 will be moved to /var/backups. If you want to retry the upgrade, you
 should move the old database files back into place, fix whatever
 caused slapcat to fail, and run:
 .
  slapcat | /usr/share/slapd/fix_ldif -w -o "$organization" > $location
 .
 Then move the database files back to a backup area and then try running
 slapadd from $location.

Template: slapd/upgrade_slapadd_failure
Type: note
_Description: slapadd failed during upgrade
 An error occurred during the attempt to upgrade the LDAP directory.
 .
 The 'slapadd' program, which attempts to
 populate an empty new LDAP directory using the information from the
 original LDAP directory, failed. This may be caused by an
 incorrect configuration file (for example, missing 'moduleload'
 lines to support the backend database).

 Original LDAP directory files are saved in
 /var/backups. The result of the attempted upgrade is the LDIF file
 in /var/backups. The failure may be due to a configuration problem
 (in which case slapcat would have failed too) or due to a problem in the
 LDIF file. In such case, you should fix it and run slapadd
 again.

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 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: 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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-openldap-devel/attachments/20071113/e5b68a79/attachment-0001.pgp 