[Pkg-openldap-devel] Bug#598575: Announce of the upcoming NMU for the openldap package

Christian PERRIER bubulle at debian.org
Sun Nov 14 08:30:12 UTC 2010


Dear maintainer of openldap and Debian translators,

Some days ago, I sent a notice to the maintainer of the openldap Debian
package, mentioning the status of at least one old po-debconf translation update in the BTS.

I announced the intent to build and possibly upload a non-maintainer upload
for this package in order to fix this long-time pending localization
bug as well as all other pending translations.

The package maintainer agreed for the NMU or did not respond in four
days, so I will proceed with the NMU.

(I'm somehow a little bit surprised as I was expecting an answer about
upcoming upload, eventually with help by me...it's still not too late
if you prefer avoiding an NMU)

The full planned schedule is available at the end of this mail.

The package is currently translated to: 
cs da de es eu fi fr gl it ja nl pt pt_BR ru sv vi

Among these, the following translations are incomplete: fi nl pt_BR

If you did any of the, currently incomplete, translations you will get
ANOTHER mail with the translation to update.

Other translators also have the opportunity to create new translations
for this package. Once completed, please send them as a bug report
against the openldap package so I can incorporate them in the build.

The deadline for receiving updates and new translations is Thursday, November 18, 2010. If you
are not in time you can always send your translation to the BTS.

The POT file is attached to this mail.

If the maintainer objects to this process I will immediately abort my NMU
and send him/her all updates I receive.

Otherwise the following will happen (or already has):

 Thursday, November 11, 2010   : send the first intent to NMU notice to
                 the package maintainer.
 Sunday, November 14, 2010       : send this notice
 Thursday, November 18, 2010       : (midnight) deadline for receiving translation updates
 Friday, November 19, 2010       : build the package and upload it to DELAYED/2-day
                 send the NMU patch to the BTS
 Sunday, November 21, 2010       : NMU uploaded to incoming

Thanks for your efforts and time.

-- 


-- 


-------------- next part --------------
# SOME DESCRIPTIVE TITLE.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: openldap at packages.debian.org\n"
"POT-Creation-Date: 2010-07-15 22:05+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <LL at li.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=CHARSET\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: boolean
#. Description
#: ../slapd.templates:1001
msgid "Omit OpenLDAP server configuration?"
msgstr ""

#. Type: boolean
#. Description
#: ../slapd.templates:1001
msgid ""
"If you enable this option, no initial configuration or database will be "
"created for you."
msgstr ""

#. Type: select
#. Choices
#: ../slapd.templates:2001
msgid "always"
msgstr ""

#. Type: select
#. Choices
#: ../slapd.templates:2001
msgid "when needed"
msgstr ""

#. Type: select
#. Choices
#: ../slapd.templates:2001
msgid "never"
msgstr ""

#. Type: select
#. Description
#: ../slapd.templates:2002
msgid "Dump databases to file on upgrade:"
msgstr ""

#. Type: select
#. Description
#: ../slapd.templates:2002
msgid ""
"Before upgrading to a new version of the OpenLDAP server, the data from your "
"LDAP directories can be dumped into plain text files in the standard LDAP "
"Data Interchange Format."
msgstr ""

#. Type: select
#. Description
#: ../slapd.templates:2002
msgid ""
"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. If you select \"never\", no dump will be done."
msgstr ""

#. Type: string
#. Description
#: ../slapd.templates:3001
msgid "Directory to use for dumped databases:"
msgstr ""

#. Type: string
#. Description
#: ../slapd.templates:3001
msgid ""
"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 the directory is located. The first occurrence of the "
"string \"VERSION\" is replaced with the server version you are upgrading "
"from."
msgstr ""

#. Type: boolean
#. Description
#: ../slapd.templates:4001
msgid "Move old database?"
msgstr ""

#. Type: boolean
#. Description
#: ../slapd.templates:4001
msgid ""
"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."
msgstr ""

#. Type: boolean
#. Description
#: ../slapd.templates:5001
msgid "Retry configuration?"
msgstr ""

#. Type: boolean
#. Description
#: ../slapd.templates:5001
msgid ""
"The configuration you entered is invalid. Make sure that the DNS domain name "
"is syntactically valid, the field for the organization is not left empty and "
"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."
msgstr ""

#. Type: string
#. Description
#: ../slapd.templates:6001
msgid "DNS domain name:"
msgstr ""

#. Type: string
#. Description
#: ../slapd.templates:6001
msgid ""
"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."
msgstr ""

#. Type: string
#. Description
#: ../slapd.templates:7001
msgid "Organization name:"
msgstr ""

#. Type: string
#. Description
#: ../slapd.templates:7001
msgid ""
"Please enter the name of the organization to use in the base DN of your LDAP "
"directory."
msgstr ""

#. Type: password
#. Description
#: ../slapd.templates:8001
msgid "Administrator password:"
msgstr ""

#. Type: password
#. Description
#: ../slapd.templates:8001
msgid "Please enter the password for the admin entry in your LDAP directory."
msgstr ""

#. Type: password
#. Description
#: ../slapd.templates:9001
msgid "Confirm password:"
msgstr ""

#. Type: password
#. Description
#: ../slapd.templates:9001
msgid ""
"Please enter the admin password for your LDAP directory again to verify that "
"you have typed it correctly."
msgstr ""

#. Type: note
#. Description
#: ../slapd.templates:10001
msgid "Password mismatch"
msgstr ""

#. Type: note
#. Description
#: ../slapd.templates:10001
msgid "The two passwords you entered were not the same. Please try again."
msgstr ""

#. Type: boolean
#. Description
#: ../slapd.templates:11001
msgid "Do you want the database to be removed when slapd is purged?"
msgstr ""

#. Type: boolean
#. Description
#: ../slapd.templates:14001
msgid "Allow LDAPv2 protocol?"
msgstr ""

#. Type: boolean
#. Description
#: ../slapd.templates:14001
msgid ""
"The obsolete LDAPv2 protocol is disabled by default in slapd. Programs and "
"users should upgrade to LDAPv3.  If you have old programs which can't use "
"LDAPv3, you should select this option and 'allow bind_v2' will be added to "
"your slapd.conf file."
msgstr ""

#. Type: error
#. Description
#: ../slapd.templates:15001
msgid "slapcat failure during upgrade"
msgstr ""

#. Type: error
#. Description
#: ../slapd.templates:15001
msgid "An error occurred while upgrading the LDAP directory."
msgstr ""

#. Type: error
#. Description
#: ../slapd.templates:15001
msgid ""
"The 'slapcat' program failed while extracting the LDAP directory. This may "
"be caused by an incorrect configuration file (for example, missing "
"'moduleload' lines to support the backend database)."
msgstr ""

#. Type: error
#. Description
#. This paragraph is followed by a (non translatable) paragraph
#. containing a command line
#: ../slapd.templates:15001
msgid ""
"This failure will cause 'slapadd' to fail later as well. The old database "
"files will be moved to /var/backups. If you want to try this upgrade again, "
"you should move the old database files back into place, fix whatever caused "
"slapcat to fail, and run:"
msgstr ""

#. Type: error
#. Description
#. Translators: keep "${location}" unchanged. This is a variable that
#. will be replaced by a directory name at execution
#: ../slapd.templates:15001
msgid ""
"Then move the database files back to a backup area and then try running "
"slapadd from ${location}."
msgstr ""

#. Type: select
#. Description
#: ../slapd.templates:16001
msgid "Database backend to use:"
msgstr ""

#. Type: select
#. Description
#: ../slapd.templates:16001
msgid ""
"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."
msgstr ""

#. Type: select
#. Description
#: ../slapd.templates:16001
msgid ""
"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."
msgstr ""
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-openldap-devel/attachments/20101114/238d7a4b/attachment.pgp>


More information about the Pkg-openldap-devel mailing list