Your message dated Wed, 24 Jun 2009 09:20:53 +0000
with message-id <[email protected]>
and subject line Bug#525234: fixed in strongswan 4.3.2-1
has caused the Debian Bug report #525234,
regarding [INTL:ja] Update po-debconf template translation (ja.po)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
525234: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=525234
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: strongswan
Version: 4.2.14-1
Severity: wishlist
Tags: patch l10n
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Dear strongswan maintainer,
Here's updated Japanese po-debconf template (ja.po) file.
Could you apply it, please?
- --
Regards,
Hideki Yamane henrich @ debian.or.jp
http://wiki.debian.org/HidekiYamane
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAknwBO8ACgkQIu0hy8THJktu3QCbB6OTLQImRpn0+/wVuBOifMJS
yxQAn0XzlhwLkXfJcLv1JNafgpU7xDqU
=3zAR
-----END PGP SIGNATURE-----
#
# Translators, if you are not familiar with the PO format, gettext
# documentation is worth reading, especially sections dedicated to
# this format, e.g. by running:
# info -n '(gettext)PO Files'
# info -n '(gettext)Header Entry'
#
# Some information specific to po-debconf are available at
# /usr/share/doc/po-debconf/README-trans
# or http://www.debian.org/intl/l10n/po-debconf/README-trans
#
# Developers do not need to manually edit POT or PO files.
#
#
msgid ""
msgstr ""
"Project-Id-Version: strongswan 4.2.14-1\n"
"Report-Msgid-Bugs-To: [email protected]\n"
"POT-Creation-Date: 2009-03-27 07:38+0100\n"
"PO-Revision-Date: 2009-04-23 06:52+0900\n"
"Last-Translator: Hideki Yamane (Debian-JP) <[email protected]>\n"
"Language-Team: Japanese <[email protected]>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Type: select
#. Choices
#: ../strongswan-starter.templates:1001
msgid "earliest, \"after NFS\", \"after PCMCIA\""
msgstr "可能な限り早く, \"NFS 起動後\", \"PCMCIA 起動後\""
#. Type: select
#. Description
#: ../strongswan-starter.templates:1002
msgid "When to start strongSwan:"
msgstr "strongSwan の起動タイミング:"
#. Type: select
#. Description
#: ../strongswan-starter.templates:1002
msgid ""
"There are three possibilities when strongSwan can start: before or after the "
"NFS services and after the PCMCIA services. The correct answer depends on "
"your specific setup."
msgstr ""
"strongSwan を起動させるタイミングの選択肢としては3つが考えられます: NFS サー"
"ビスの開始前・開始後・PCMCIA サービスの開始後、です。正解はあなたの設定次第で"
"す。"
#. Type: select
#. Description
#: ../strongswan-starter.templates: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 strongSwan 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 ""
"NFS 経由で /usr をマウントせず (他のパーティションやあまり重要ではないパー"
"ティションを NFS 経由でマウントするか、または NFS マウントを全く使わない)、加"
"えて PCMCIA ネットワークカードを利用していない場合、可能な限り早いタイミング"
"で strongSwan を起動するのがベストです。この設定によって、NFS でのマウントは "
"IPSec で保護されます。この場合 (またはこの問題を理解していないか特に気にしな"
"い場合) 、\"可能な限り早く\"と質問に答えてください (標準設定です) 。"
#. Type: select
#. Description
#: ../strongswan-starter.templates: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 strongSwan 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 ""
"NFS 経由で /usr をマウントしていて PCMCIA ネットワークカードを使用していない"
"場合は、必要なファイルを利用可能にするために strongSwan を NFS の後で起動しな"
"ければなりません。この場合、\"NFS 起動後\" と答えてください。この時に NFS 経"
"由でマウントされる /usr は、IPSec によるセキュアな状態にはならないということ"
"に注意してください。"
#. Type: select
#. Description
#: ../strongswan-starter.templates: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 ""
"IPSec 接続に PCMCIA ネットワークカードを利用していた場合、PCMCIA サービスの起"
"動後に strongSwan を起動する以外に選択はありません。この場合、\"PCMCIA 起動後"
"\" と答えてください。ローカルで動作している DNSSec 機能を使用している DNS "
"サーバから鍵を取得したい場合でも、この答えをしてください。"
#. Type: boolean
#. Description
#: ../strongswan-starter.templates:2001
msgid "Do you wish to restart strongSwan?"
msgstr "strongSwan を再起動しますか?"
#. Type: boolean
#. Description
#: ../strongswan-starter.templates:2001
msgid ""
"Restarting strongSwan 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 ""
"セキュリティ修正があった場合にはデーモンが再起動されるまで修正が反映されませ"
"ん。ですので、strongSwan を再起動するのは良い考えです。ほとんどの人はデーモン"
"を再起動しようとしますが、これは大抵問題ありません。しかし、この作業で現在の"
"接続は切断され、再度繋ぎなおすことになります。"
#. Type: boolean
#. Description
#: ../strongswan-starter.templates:3001
msgid "Do you wish to support IKEv1?"
msgstr "IKEv1 をサポートしますか?"
#. Type: boolean
#. Description
#: ../strongswan-starter.templates:3001
msgid ""
"strongSwan supports both versions of the Internet Key Exchange protocol, "
"IKEv1 and IKEv2. Do you want to start the \"pluto\" daemon for IKEv1 support "
"when strongSwan is started?"
msgstr ""
"strongSwan は IKEv1 と IKEv2 の両方のインターネット鍵交換プロトコルをサポート"
"しています。strongSwan が起動する際、IKEv1 サポートのため \"pluto\" デーモン"
"を起動しますか?"
#. Type: boolean
#. Description
#: ../strongswan-starter.templates:4001
msgid "Do you wish to support IKEv2?"
msgstr "IKEv2 をサポートしますか?"
#. Type: boolean
#. Description
#: ../strongswan-starter.templates:4001
msgid ""
"strongSwan supports both versions of the Internet Key Exchange protocol, "
"IKEv1 and IKEv2. Do you want to start the \"charon\" daemon for IKEv2 "
"support when strongSwan is started?"
msgstr ""
"strongSwan は IKEv1 と IKEv2 の両方のインターネット鍵交換プロトコルをサポート"
"しています。strongSwan が起動する際、IKEv2 サポートのため \"pluto\" デーモン"
"を起動しますか?"
#. Type: boolean
#. Description
#: ../strongswan-starter.templates:5001
msgid "Do you want to create a RSA public/private keypair for this host?"
msgstr "このホストの RSA 公開鍵・秘密鍵のキーペアを生成しますか?"
#. Type: boolean
#. Description
#: ../strongswan-starter.templates:5001
msgid ""
"This installer can automatically create a RSA public/private keypair with an "
"X.509 certificate for this host. This can be used to authenticate IPSec "
"connections to other hosts and is the preferred way for building up secure "
"IPSec connections. The other possibility would be to use pre-shared secrets "
"(PSKs, passwords that are the same on both sides of the tunnel) for "
"authenticating an connection, but for a larger number of connections RSA "
"authentication is easier to administer and more secure. Note that having a "
"keypair allows to use both X.509 and PSK authentication for IPsec tunnels."
msgstr ""
"このインストーラはこのホストの X.509 認証用の RSA 公開鍵・秘密鍵のキーペアを"
"自動的に生成できます。このキーペアは他のホストとの IPSec 通信での認証に利用"
"可能で、セキュアな IPSec 通信を確立する方法として好まれています。他に利用可能"
"な方法としては事前に設定してある共通鍵 (PSK、トンネルの双方で同じパスワードを"
"を利用する) を通信の認証に利用するというのがありますが、多数の接続に対しては、"
"RSA 認証のほうが管理がより簡単でよりセキュアです。キーペアを利用することは、"
"X.509 認証と PSK 認証の双方を IPsec トンネルに許可することに注意してください。"
#. Type: boolean
#. Description
#: ../strongswan-starter.templates:5001
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:6001
msgid "Do you have an existing X.509 certificate file for strongSwan?"
msgstr "既に存在している X.509 証明書ファイルを strongSwan で利用しますか?"
#. Type: boolean
#. Description
#: ../strongswan-starter.templates:6001
msgid ""
"This installer can automatically extract the needed information 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. If you have such an existing "
"certificate and key file and want to use it for authenticating IPSec "
"connections, then please answer yes."
msgstr ""
"このインストーラは既に存在している X.509 証明書から RSA 秘密鍵と照らし合わせて"
"必要な情報を自動的に展開する事が可能です。 PEM 形式の場合、双方を一つのファイ"
"ルにまとめることも可能です。そのような証明書と鍵のファイルがあり、これらを "
"IPSec 通信での認証に使用したい場合は「はい」と答えてください。"
#. Type: string
#. Description
#: ../strongswan-starter.templates:7001
msgid "File name of your X.509 certificate in PEM format:"
msgstr "PEM 形式の X.509 証明書のファイル名:"
#. Type: string
#. Description
#: ../strongswan-starter.templates:7001
msgid ""
"Please enter the full location of the file containing your X.509 certificate "
"in PEM format."
msgstr ""
"PEM 形式の X.509 証明書を含むファイルの場所を絶対パスで入力してください。"
#. Type: string
#. Description
#: ../strongswan-starter.templates:8001
msgid "File name of your X.509 private key in PEM format:"
msgstr "PEM 形式の X.509 秘密鍵のファイル名:"
#. Type: string
#. Description
#: ../strongswan-starter.templates:8001
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 "
"that contains the X.509 certificate."
msgstr ""
"PEM 形式の X.509 証明書に対応する RSA 秘密鍵を含んでいるファイルの場所を絶対パ"
"スで入力してください。これは X.509 証明書を含んでいるファイルと同じで構いませ"
"ん。"
#. Type: string
#. Description
#: ../strongswan-starter.templates:9001
msgid "The length of the created RSA key (in bits):"
msgstr "RSA 鍵の鍵長（ビット数）:"
#. Type: string
#. Description
#: ../strongswan-starter.templates:9001
msgid ""
"Please enter the length of the created RSA key. It should not be less than "
"1024 bits because this should be considered unsecure and you will probably "
"not need anything more than 2048 bits because it only slows the "
"authentication process down and is not needed at the moment."
msgstr ""
"生成する RSA 鍵の長さを入力してください。安全のため、1024 ビット未満にすべき"
"ではありません。2048 ビットより大きなものにする必要もないでしょう。認証プロセ"
"スが遅くなりますし、現時点ではおそらく必要ありません。"
#. Type: boolean
#. Description
#: ../strongswan-starter.templates:10001
msgid "Do you want to create a self-signed X.509 certificate?"
msgstr "自己署名 X.509 証明書を生成しますか?"
#. Type: boolean
#. Description
#: ../strongswan-starter.templates:10001
msgid ""
"This installer can only create self-signed X.509 certificates automatically, "
"because otherwise a certificate authority is needed to sign the certificate "
"request. If you want to create a self-signed certificate, you can use it "
"immediately to connect to other IPSec hosts that support X.509 certificate "
"for authentication of IPSec connections. However, if you want to use the new "
"PKI features of strongSwan >= 1.91, you will need to have all X.509 "
"certificates signed by a single certificate authority to create a trust path."
msgstr ""
"証明書要求に署名するためには認証局が必要となるので、このインストーラでは自己"
"署名 X.509 証明書を自動的に生成する事だけが可能です。自己署名証明書を生成した"
"い場合、これを使用してすぐに X.509 証明書をサポートしている他の IPSec ホストに"
"接続可能です。しかし、strongSwan バージョン 1.91 以上での新しい PKI 機能を使"
"いたい場合は、trust path を生成するために単一の認証局によってすべての X.509 証"
"明書に署名してもらう必要があります。"
#. Type: boolean
#. Description
#: ../strongswan-starter.templates:10001
msgid ""
"If you do not want to create a self-signed certificate, then this installer "
"will only create the RSA private key and the certificate request and you "
"will have to get the certificate request signed by your certificate "
"authority."
msgstr ""
"自己署名証明書を生成したくないという場合は、このインストーラでは RSA 秘密鍵と"
"証明書要求のみを生成します。そのため、認証局に証明書要求へ署名をしてもらう必"
"要があります。"
#. Type: string
#. Description
#: ../strongswan-starter.templates:11001
msgid "Country code for the X.509 certificate request:"
msgstr "X.509 証明書要求に記載する国コード:"
#. Type: string
#. Description
#: ../strongswan-starter.templates:11001
msgid ""
"Please enter the 2 letter country code for your country. This code will be "
"placed in the certificate request."
msgstr ""
"あなたの国の国コードを2文字で入力してください。このコードは証明書要求に記載さ"
"れます。"
#. Type: string
#. Description
#: ../strongswan-starter.templates:11001
msgid ""
"You really need to enter a valid country code here, because openssl will "
"refuse to generate certificates without one. An empty field is allowed for "
"any other field of the X.509 certificate, but not for this one."
msgstr ""
"openssl が国コードなしでは証明書の生成を拒否するので、正しい国コードをここで"
"入力する必要があります。X.509 証明書では、他のフィールドについては空でも構い"
"ませんが、これについては許可されていません。"
#. Type: string
#. Description
#: ../strongswan-starter.templates:11001
msgid "Example: AT"
msgstr "例: JP"
#. Type: string
#. Description
#: ../strongswan-starter.templates:12001
msgid "State or province name for the X.509 certificate request:"
msgstr "X.509 証明書要求に記載する都道府県名:"
#. Type: string
#. Description
#: ../strongswan-starter.templates:12001
msgid ""
"Please enter the full name of the state or province you live in. This name "
"will be placed in the certificate request."
msgstr ""
"あなたが在住している都道府県を入力してください。これは証明書要求に記載されま"
"す。"
#. Type: string
#. Description
#: ../strongswan-starter.templates:12001
msgid "Example: Upper Austria"
msgstr "例: Tokyo"
#. Type: string
#. Description
#: ../strongswan-starter.templates:13001
msgid "Locality name for the X.509 certificate request:"
msgstr "X.509 証明書要求に記載する地域名:"
#. Type: string
#. Description
#: ../strongswan-starter.templates:13001
msgid ""
"Please enter the locality (e.g. city) where you live. This name will be "
"placed in the certificate request."
msgstr ""
"あなたの在住している地域の名前 (例: 市町村名) を入力してください。これは証明"
"書要求に記載されます。"
#. Type: string
#. Description
#: ../strongswan-starter.templates:13001
msgid "Example: Vienna"
msgstr "例: Shinjuku-ku"
#. Type: string
#. Description
#: ../strongswan-starter.templates:14001
msgid "Organization name for the X.509 certificate request:"
msgstr "X.509 証明書要求に記載する組織名:"
#. Type: string
#. Description
#: ../strongswan-starter.templates:14001
msgid ""
"Please enter the organization (e.g. company) that the X.509 certificate "
"should be created for. This name will be placed in the certificate request."
msgstr ""
"X.509 証明書の生成対象となるべき組織 (例: 会社) を入力してください。これは証明"
"書要求に記載されます。"
#. Type: string
#. Description
#: ../strongswan-starter.templates:14001
msgid "Example: Debian"
msgstr "例: Debian"
#. Type: string
#. Description
#: ../strongswan-starter.templates:15001
msgid "Organizational unit for the X.509 certificate request:"
msgstr "X.509 証明書要求に記載する組織単位:"
#. Type: string
#. Description
#: ../strongswan-starter.templates:15001
msgid ""
"Please enter the organizational unit (e.g. section) that the X.509 "
"certificate should be created for. This name will be placed in the "
"certificate request."
msgstr ""
"X.509 証明書の生成対象となるべき組織単位 (例: 部署名) を入力してください。これ"
"は証明書要求に記載されます。"
#. Type: string
#. Description
#: ../strongswan-starter.templates:15001
msgid "Example: security group"
msgstr "例: security group"
#. Type: string
#. Description
#: ../strongswan-starter.templates:16001
msgid "Common name for the X.509 certificate request:"
msgstr "X.509 証明書要求に記載するコモンネーム:"
#. Type: string
#. Description
#: ../strongswan-starter.templates:16001
msgid ""
"Please enter the common name (e.g. the host name of this machine) for which "
"the X.509 certificate should be created for. This name will be placed in the "
"certificate request."
msgstr ""
"X.509 証明書の生成対象となるべきコモンネーム (例: このマシンのホスト名) を入力"
"してください。これは証明書要求に記載されます。"
#. Type: string
#. Description
#: ../strongswan-starter.templates:16001
msgid "Example: gateway.debian.org"
msgstr "例: gateway.debian.org"
#. Type: string
#. Description
#: ../strongswan-starter.templates:17001
msgid "Email address for the X.509 certificate request:"
msgstr "X.509 証明書要求に記載するメールアドレス:"
#. Type: string
#. Description
#: ../strongswan-starter.templates:17001
msgid ""
"Please enter the email address of the person or organization who is "
"responsible for the X.509 certificate. This address will be placed in the "
"certificate request."
msgstr ""
"X.509 証明書の責任者となる人物・団体のメールアドレスを入力してください。このア"
"ドレスは証明書要求に記載されます。"
#. Type: boolean
#. Description
#: ../strongswan-starter.templates:18001
msgid "Do you wish to enable opportunistic encryption in strongSwan?"
msgstr "strongSwan で opportunistic encryption を有効にしますか?"
#. Type: boolean
#. Description
#: ../strongswan-starter.templates:18001
msgid ""
"strongSwan comes with support for opportunistic encryption (OE), which "
"stores IPSec authentication information (i.e. RSA public keys) in "
"(preferably secure) DNS records. Until this is widely deployed, activating "
"it will cause a significant slow-down for every new, outgoing connection. "
"Since version 2.0, strongSwan upstream comes with OE enabled by default and "
"is thus likely to break your existing connection to the Internet (i.e. your "
"default route) as soon as pluto (the strongSwan keying daemon) is started."
msgstr ""
"strongSwan は、IPSec 認証情報 (例: RSA 公開鍵) を (願わくはセキュアな) DNS レ"
"コード内に保存する opportunistic encryption (OE) をサポートしています。これは"
"広く利用されるようになるまで、有効にすると外部への新規接続は全て格段に遅くな"
"ります。バージョン 2.0 より strongSwan の開発元はデフォルトで OE を有効にして"
"います。そのため pluto (strongSwan 鍵署名デーモン) が開始するとすぐ、既存のイ"
"ンターネット接続 (つまりデフォルトルート) が中断されるかもしれません。"
#. Type: boolean
#. Description
#: ../strongswan-starter.templates:18001
msgid ""
"Please choose whether you want to enable support for OE. If unsure, do not "
"enable it."
msgstr ""
"OE のサポートを有効にするかどうかを選んでください。よくわからない場合は、有効"
"にはしないでください。"
--- End Message ---
--- Begin Message ---
Source: strongswan
Source-Version: 4.3.2-1
We believe that the bug you reported is fixed in the latest version of
strongswan, which is due to be installed in the Debian FTP archive:
libstrongswan_4.3.2-1_i386.deb
to pool/main/s/strongswan/libstrongswan_4.3.2-1_i386.deb
strongswan-ikev1_4.3.2-1_i386.deb
to pool/main/s/strongswan/strongswan-ikev1_4.3.2-1_i386.deb
strongswan-ikev2_4.3.2-1_i386.deb
to pool/main/s/strongswan/strongswan-ikev2_4.3.2-1_i386.deb
strongswan-nm_4.3.2-1_i386.deb
to pool/main/s/strongswan/strongswan-nm_4.3.2-1_i386.deb
strongswan-starter_4.3.2-1_i386.deb
to pool/main/s/strongswan/strongswan-starter_4.3.2-1_i386.deb
strongswan_4.3.2-1.diff.gz
to pool/main/s/strongswan/strongswan_4.3.2-1.diff.gz
strongswan_4.3.2-1.dsc
to pool/main/s/strongswan/strongswan_4.3.2-1.dsc
strongswan_4.3.2.orig.tar.gz
to pool/main/s/strongswan/strongswan_4.3.2.orig.tar.gz
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Rene Mayrhofer <[email protected]> (supplier of updated strongswan package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Sat, 18 Apr 2009 20:28:51 +0200
Source: strongswan
Binary: strongswan libstrongswan strongswan-starter strongswan-ikev1
strongswan-ikev2 strongswan-nm
Architecture: source i386
Version: 4.3.2-1
Distribution: unstable
Urgency: HIGH
Maintainer: Rene Mayrhofer <[email protected]>
Changed-By: Rene Mayrhofer <[email protected]>
Description:
libstrongswan - strongSwan utility and crypto library
strongswan - IPsec VPN solution metapackage
strongswan-ikev1 - strongSwan Internet Key Exchange (v1) daemon
strongswan-ikev2 - strongSwan Internet Key Exchange (v2) daemon
strongswan-nm - strongSwan plugin to interact with NetworkManager
strongswan-starter - strongSwan daemon starter and configuration file parser
Closes: 525234 525652 526037 526486 526487 526488 528073 528323 528370 529027
529063 529071 529592 529638 529661 529742 530273 531612 533837
Changes:
strongswan (4.3.2-1) unstable; urgency=HIGH
.
Urgency high because of security issue and FTBFS.
* New upstream release, fixes security bug.
* Fix padlock handling for i386 in debian/rules.
Closes: #525652 (FTBFS on i386)
* Acknowledge NMUs by security team.
Closes: #533837, #531612
* Add "Conflicts: strongswan (< 4.2.12-1)" to libstrongswan,
strongswan-starter, strongswan-ikev1, and strongswan-ikev2 to force
update of the strongswan package on installation and avoid conflicts
caused by package restructuring.
Closes: #526037: strongswan-ikev2 and strongswan: error when trying to
install together
Closes: #526486: strongswan and libstrongswan: error when trying to
install together
Closes: #526487: strongswan-ikev1 and strongswan: error when trying to
install together
Closes: #526488: strongswan-starter and strongswan: error when trying to
install together
* Debconf templates and debian/control reviewed by the debian-l10n-
english team as part of the Smith review project. Closes: #528073
* Debconf translation updates:
Closes: #525234: [INTL:ja] Update po-debconf template translation (ja.po)
Closes: #528323: [INTL:sv] po-debconf file for strongswan
Closes: #528370: [INTL:vi] Vietnamese debconf templates translation update
Closes: #529027: [INTL:pt] Updated Portuguese translation for debconf
messages
Closes: #529071: [INTL:fr] French debconf templates translation update
Closes: #529592: nb translation of debconf PO for strongSWAN
Closes: #529638: [INTL:ru] Russian debconf templates translation
Closes: #529661: Updated Czech translation of strongswan debconf messages
Closes: #529742: [INTL:eu] strongswan debconf basque translation
Closes: #530273: [INTL:fi] Finnish translation of the debconf templates
Closes: #529063: [INTL:gl] strongswan 4.2.14-2 debconf translation update
Checksums-Sha1:
f2512185664e43d6e17107b825b6fdc7b39a87c1 1487 strongswan_4.3.2-1.dsc
a01ef1adc4ff82b2f3673cbea9dbe497ef61b33c 3541466 strongswan_4.3.2.orig.tar.gz
6338406111afb3f59607ddaea485f3c1ad1c59b5 78372 strongswan_4.3.2-1.diff.gz
dc420ad41d4129e7930db01be88670a43d2d9dcf 170386 libstrongswan_4.3.2-1_i386.deb
3c2f22459c2c7fe1763545e34cd7b2d73deb9508 266028
strongswan-starter_4.3.2-1_i386.deb
8a54ab9bea3b78b93397c45657755f9799f6b4d6 331536
strongswan-ikev1_4.3.2-1_i386.deb
09fc51b19d756ad063d1214e85b10d2a40129ceb 225718
strongswan-ikev2_4.3.2-1_i386.deb
638563070a1cc9c201b69732e3340b987ed08d95 43796 strongswan-nm_4.3.2-1_i386.deb
Checksums-Sha256:
34ca69ffd71ff9b80032d5d5aeb2d614ca914b682174e2178670f8fdb043a6e1 1487
strongswan_4.3.2-1.dsc
6ca31f8d6b3f50b6d255af1fb567664abd41e9fe028ac84bbc5ab1085ae7db5f 3541466
strongswan_4.3.2.orig.tar.gz
e284d738ac25634535a5203ba66356b3709c9978f8bc4159dd5695a931ef4340 78372
strongswan_4.3.2-1.diff.gz
7d0fd8fee14ad9e19a44c5a2345f10388add7a4151ba5ba1cf0b20b93764daef 170386
libstrongswan_4.3.2-1_i386.deb
8821b2a5f54c4ae0ca57598d4978b2593d5e380e0325cefbaf1629a95817b17a 266028
strongswan-starter_4.3.2-1_i386.deb
803c53ab4100b8d8dfbba3240e3186402dfa1f8a01846e46adbb861129ebb162 331536
strongswan-ikev1_4.3.2-1_i386.deb
b92ad1e5cdc13b33840106f9eaea7a0cc90970f756a17f053dede8715f5b5d71 225718
strongswan-ikev2_4.3.2-1_i386.deb
d9ce457310e45c1c4ca0a5f9cf77f579eb11c132899313f44551b6b7bf8ffbab 43796
strongswan-nm_4.3.2-1_i386.deb
Files:
e3941351431fe4253b7a8d163966d58d 1487 net optional strongswan_4.3.2-1.dsc
bc2584a0811e0de9737836a4602146d2 3541466 net optional
strongswan_4.3.2.orig.tar.gz
f636c349e51f481876424469bd76f640 78372 net optional strongswan_4.3.2-1.diff.gz
6bc4ca52b9e56c90ebf1f0ca6a0a60ff 170386 net optional
libstrongswan_4.3.2-1_i386.deb
4e70a71df3c62623f2bd0530865bc3f2 266028 net optional
strongswan-starter_4.3.2-1_i386.deb
8cefa4e70aaa86eff409cc39992d92b8 331536 net optional
strongswan-ikev1_4.3.2-1_i386.deb
30458ff637f4c477b28d373c6cf30246 225718 net optional
strongswan-ikev2_4.3.2-1_i386.deb
4a47bb10be9e4ab4b6bd9fa7d10510dd 43796 net optional
strongswan-nm_4.3.2-1_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkpB31UACgkQq7SPDcPCS95MPgCcDzFKgDbWAYv16S738Xlcdh+6
9n4AoMtywo2aTzDPshw0mLANd2LcOk6n
=yNOR
-----END PGP SIGNATURE-----
--- End Message ---
