Dear maintainer of openswan and Debian translators,
On Friday, March 21, 2008 I sent a notice to the maintainer of the openswan
Debian
package, mentioning the status of at least one old po-debconf translation
update in the BTS (bug #461841).
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 two
weeks, so I will proceed with the NMU.
The full planned schedule is available at the end of this mail.
The package is currently translated to: cs de es fi fr ja nl pt pt_BR sv vi
Among these, the following translations are incomplete: cs es nl pt pt_BR sv vi
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 openswan package so I can incorporate them in the build.
The deadline for receiving updates and new translations is Wednesday, April 16,
2008. 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):
Friday, March 21, 2008 : send the first intent to NMU notice to
the package maintainer.
Sunday, April 06, 2008 : send this notice
Wednesday, April 16, 2008 : deadline for receiving translation updates
Thursday, April 17, 2008 : build the package and upload it to
DELAYED/0-day
send the NMU patch to the BTS
Friday, April 18, 2008 : NMU uploaded to incoming
Thanks for your efforts and time.
--
--
# 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 PROTECTED], YEAR.
#
#, fuzzy
msgid
msgstr
Project-Id-Version: PACKAGE VERSION\n
Report-Msgid-Bugs-To: [EMAIL PROTECTED]
POT-Creation-Date: 2007-10-27 11:19+0200\n
PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n
Last-Translator: FULL NAME [EMAIL PROTECTED]\n
Language-Team: LANGUAGE [EMAIL PROTECTED]\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=CHARSET\n
Content-Transfer-Encoding: 8bit\n
#. Type: select
#. Choices
#: ../openswan.templates.master:1001
msgid earliest, \after NFS\, \after PCMCIA\
msgstr
#. Type: select
#. Description
#: ../openswan.templates.master:1002
msgid At which level do you wish to start Openswan?
msgstr
#. Type: select
#. Description
#: ../openswan.templates.master:1002
msgid
With the current Debian startup levels (nearly everything starting in level
20), it is impossible for Openswan to always start at the correct time.
There are three possibilities when Openswan can start: before or after the
NFS services and after the PCMCIA services. The correct answer depends on
your specific setup.
msgstr
#. Type: select
#. Description
#: ../openswan.templates.master:1002
msgid
If you do not have your /usr tree mounted via NFS (either you only mount
other, less vital trees via NFS or don't use NFS mounted trees at all) and
don't use a PCMCIA network card, then it's best to start Openswan at the
earliest possible time, thus allowing the NFS mounts to be secured by IPSec.
In this case (or if you don't understand or care about this issue), answer
\earliest\ to this question (the default).
msgstr
#. Type: select
#. Description
#: ../openswan.templates.master:1002
msgid
If you have your /usr tree mounted via NFS and don't use a PCMCIA network
card, then you will need to start Openswan after NFS so that all necessary
files are available. In this case, answer \after NFS\ to this question.
Please note that the NFS mount of /usr can not be secured by IPSec in this
case.
msgstr
#. Type: select
#. Description
#: ../openswan.templates.master:1002
msgid
If you use a PCMCIA network card for your IPSec connections, then you only
have to choose to start it after the PCMCIA services. Answer \after PCMCIA
\ in this case. This is also the correct answer if you want to fetch keys
from a locally running DNS server with DNSSec support.
msgstr
#. Type: boolean
#. Description
#: ../openswan.templates.master:2001
msgid Do you wish to restart Openswan?
msgstr
#. Type: boolean
#. Description
#: ../openswan.templates.master:2001
msgid
Restarting Openswan is a good idea, since if there is a security fix, it
will not be fixed until the daemon restarts. Most people expect the daemon
to restart, so this is generally a good idea. However this might take down
existing connections and then bring them back up.
msgstr
#. Type: boolean
#. Description
#: ../openswan.templates.master:3001
msgid Do you want to create a
