[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Announce of the upcoming NMU for the strongswan package



Dear maintainer of strongswan and Debian translators,

Some days ago, I sent a notice to the maintainer of the strongswan 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.

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

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

Among these, the following translations are incomplete: de ja 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 strongswan package so I can incorporate them in the build.

The deadline for receiving updates and new translations is Sunday, January 24, 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):

 Saturday, January 16, 2010   : send the first intent to NMU notice to
                 the package maintainer.
 Monday, January 18, 2010       : send this notice
 Sunday, January 24, 2010       : (midnight) deadline for receiving translation updates
 Monday, January 25, 2010       : build the package and upload it to DELAYED/7-day
                 send the NMU patch to the BTS
 Monday, February 01, 2010       : 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@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: strongswan@packages.debian.org\n"
"POT-Creation-Date: 2009-05-25 14:44+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=CHARSET\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: select
#. Choices
#: ../strongswan-starter.templates:2001
msgid "earliest"
msgstr ""

#. Type: select
#. Choices
#: ../strongswan-starter.templates:2001
msgid "after NFS"
msgstr ""

#. Type: select
#. Choices
#: ../strongswan-starter.templates:2001
msgid "after PCMCIA"
msgstr ""

#. Type: select
#. Description
#: ../strongswan-starter.templates:2002
msgid "When to start strongSwan:"
msgstr ""

#. Type: select
#. Description
#: ../strongswan-starter.templates:2002
msgid ""
"StrongSwan starts during system startup so that it can protect filesystems "
"that are automatically mounted."
msgstr ""

#. Type: select
#. Description
#: ../strongswan-starter.templates:2002
msgid ""
" * earliest: if /usr is not mounted through NFS and you don't use a\n"
"   PCMCIA network card, it is best to start strongSwan as soon as\n"
"   possible, so that NFS mounts can be secured by IPSec;\n"
" * after NFS: recommended when /usr is mounted through NFS and no\n"
"   PCMCIA network card is used;\n"
" * after PCMCIA: recommended if the IPSec connection uses a PCMCIA\n"
"   network card or if it needs keys to be fetched from a locally running "
"DNS\n"
"   server with DNSSec support."
msgstr ""

#. Type: boolean
#. Description
#: ../strongswan-starter.templates:3001
msgid "Restart strongSwan now?"
msgstr ""

#. Type: boolean
#. Description
#: ../strongswan-starter.templates:3001
msgid ""
"Restarting strongSwan is recommended, because if there is a security fix, it "
"will not be applied until the daemon restarts. However, this might close "
"existing connections and then bring them back up."
msgstr ""

#. Type: boolean
#. Description
#: ../strongswan-starter.templates:3001
msgid ""
"If you don't restart strongSwan now, you should do so manually at the first "
"opportunity."
msgstr ""

#. Type: boolean
#. Description
#: ../strongswan-starter.templates:4001
msgid "Start strongSwan's IKEv1 daemon?"
msgstr ""

#. Type: boolean
#. Description
#: ../strongswan-starter.templates:4001
msgid ""
"The pluto daemon must be running to support version 1 of the Internet Key "
"Exchange protocol."
msgstr ""

#. Type: boolean
#. Description
#: ../strongswan-starter.templates:5001
msgid "Start strongSwan's IKEv2 daemon?"
msgstr ""

#. Type: boolean
#. Description
#: ../strongswan-starter.templates:5001
msgid ""
"The charon daemon must be running to support version 2 of the Internet Key "
"Exchange protocol."
msgstr ""

#. Type: boolean
#. Description
#: ../strongswan-starter.templates:6001
msgid "Create an RSA public/private keypair for this host?"
msgstr ""

#. Type: boolean
#. Description
#: ../strongswan-starter.templates:6001
msgid ""
"StrongSwan can use a Pre-Shared Key (PSK) or an RSA keypair to authenticate "
"IPSec connections to other hosts. RSA authentication is generally considered "
"more secure and is easier to administer. You can use PSK and RSA "
"authentication simultaneously."
msgstr ""

#. Type: boolean
#. Description
#: ../strongswan-starter.templates:6001
msgid ""
"If you do not want to create a new public/private keypair, you can choose to "
"use an existing one in the next step."
msgstr ""

#. Type: boolean
#. Description
#: ../strongswan-starter.templates:7001
msgid "Use an existing X.509 certificate for strongSwan?"
msgstr ""

#. Type: boolean
#. Description
#: ../strongswan-starter.templates:7001
msgid ""
"The required information can automatically be extracted from an existing "
"X.509 certificate with a matching RSA private key. Both parts can be in one "
"file, if it is in PEM format. You should choose this option if you have such "
"an existing certificate and key file and want to use it for authenticating "
"IPSec connections."
msgstr ""

#. Type: string
#. Description
#: ../strongswan-starter.templates:8001
msgid "File name of your X.509 certificate in PEM format:"
msgstr ""

#. Type: string
#. Description
#: ../strongswan-starter.templates:8001
msgid ""
"Please enter the full location of the file containing your X.509 certificate "
"in PEM format."
msgstr ""

#. Type: string
#. Description
#: ../strongswan-starter.templates:9001
msgid "File name of your existing X.509 private key in PEM format:"
msgstr ""

#. Type: string
#. Description
#: ../strongswan-starter.templates:9001
msgid ""
"Please enter the full location of the file containing the private RSA key "
"matching your X.509 certificate in PEM format. This can be the same file as "
"the X.509 certificate."
msgstr ""

#. Type: string
#. Description
#: ../strongswan-starter.templates:10001
msgid "RSA key length:"
msgstr ""

#. Type: string
#. Description
#: ../strongswan-starter.templates:10001
msgid ""
"Please enter the length of RSA key you wish to generate. A value of less "
"than 1024 bits is not considered secure. A value of more than 2048 bits will "
"probably affect performance."
msgstr ""

#. Type: boolean
#. Description
#: ../strongswan-starter.templates:11001
msgid "Create a self-signed X.509 certificate?"
msgstr ""

#. Type: boolean
#. Description
#: ../strongswan-starter.templates:11001
msgid ""
"Only self-signed X.509 certificates can be created automatically, because "
"otherwise a certificate authority is needed to sign the certificate request."
msgstr ""

#. Type: boolean
#. Description
#: ../strongswan-starter.templates:11001
msgid ""
"If you accept this option, the certificate created can be used immediately "
"to connect to other IPSec hosts that support authentication via an X.509 "
"certificate. However, using strongSwan's PKI features requires a trust path "
"to be created by having all X.509 certificates signed by a single authority."
msgstr ""

#. Type: boolean
#. Description
#: ../strongswan-starter.templates:11001
msgid ""
"If you do not accept this option, only the RSA private key will be created, "
"along with a certificate request which you will need to have signed by a "
"certificate authority."
msgstr ""

#. Type: string
#. Description
#: ../strongswan-starter.templates:12001
msgid "Country code for the X.509 certificate request:"
msgstr ""

#. Type: string
#. Description
#: ../strongswan-starter.templates:12001
msgid ""
"Please enter the two-letter ISO3166 country code that should be used in the "
"certificate request."
msgstr ""

#. Type: string
#. Description
#: ../strongswan-starter.templates:12001
msgid "This field is mandatory; otherwise a certificate cannot be generated."
msgstr ""

#. Type: string
#. Description
#: ../strongswan-starter.templates:13001
msgid "State or province name for the X.509 certificate request:"
msgstr ""

#. Type: string
#. Description
#: ../strongswan-starter.templates:13001
msgid ""
"Please enter the full name of the state or province to include in the "
"certificate request."
msgstr ""

#. Type: string
#. Description
#: ../strongswan-starter.templates:14001
msgid "Locality name for the X.509 certificate request:"
msgstr ""

#. Type: string
#. Description
#: ../strongswan-starter.templates:14001
msgid ""
"Please enter the locality name (often a city) that should be used in the "
"certificate request."
msgstr ""

#. Type: string
#. Description
#: ../strongswan-starter.templates:15001
msgid "Organization name for the X.509 certificate request:"
msgstr ""

#. Type: string
#. Description
#: ../strongswan-starter.templates:15001
msgid ""
"Please enter the organization name (often a company) that should be used in "
"the certificate request."
msgstr ""

#. Type: string
#. Description
#: ../strongswan-starter.templates:16001
msgid "Organizational unit for the X.509 certificate request:"
msgstr ""

#. Type: string
#. Description
#: ../strongswan-starter.templates:16001
msgid ""
"Please enter the organizational unit name (often a department) that should "
"be used in the certificate request."
msgstr ""

#. Type: string
#. Description
#: ../strongswan-starter.templates:17001
msgid "Common name for the X.509 certificate request:"
msgstr ""

#. Type: string
#. Description
#: ../strongswan-starter.templates:17001
msgid ""
"Please enter the common name (such as the host name of this machine) that "
"should be used in the certificate request."
msgstr ""

#. Type: string
#. Description
#: ../strongswan-starter.templates:18001
msgid "Email address for the X.509 certificate request:"
msgstr ""

#. Type: string
#. Description
#: ../strongswan-starter.templates:18001
msgid ""
"Please enter the email address (for the individual or organization "
"responsible) that should be used in the certificate request."
msgstr ""

#. Type: boolean
#. Description
#: ../strongswan-starter.templates:19001
msgid "Enable opportunistic encryption?"
msgstr ""

#. Type: boolean
#. Description
#: ../strongswan-starter.templates:19001
msgid ""
"This version of strongSwan supports opportunistic encryption (OE), which "
"stores IPSec authentication information in DNS records. Until this is widely "
"deployed, activating it will cause a significant delay for every new "
"outgoing connection."
msgstr ""

#. Type: boolean
#. Description
#: ../strongswan-starter.templates:19001
msgid ""
"You should only enable opportunistic encryption if you are sure you want it. "
"It may break the Internet connection (default route) as the pluto daemon "
"starts."
msgstr ""

Attachment: signature.asc
Description: Digital signature


Reply to: