Package: openvpn
Version: N/A
Severity: normal
Tags: patch
Dear Debian maintainer,
On Monday, January 07, 2008, I notified you of the beginning of a review process
concerning debconf templates for openvpn.
The debian-l10n-english contributors have now reviewed these templates,
and the proposed changes are attached to this bug report.
Please review the suggested changes are suggested, and if you have any
objections, let me know in the next 3 days.
Please try to avoid uploading openvpn with these changes right now.
The second phase of this process will begin on Friday, January 25, 2008, when I
will
coordinate updates to translations of debconf templates.
The existing translators will be notified of the changes: they will
receive an updated PO file for their language.
Simultaneously, a general call for new translations will be sent to
the debian-i18n mailing list.
Both these calls for translations will request updates to be sent as
individual bug reports. That will probably trigger a lot of bug
reports against your package, but these should be easier to deal with.
The call for translation updates and new translations will run until
about Friday, February 15, 2008. Please avoid uploading a package with fixed or
changed
debconf templates and/or translation updates in the meantime. Of
course, other changes are safe.
Please note that this is an approximative delay, which depends on my
own availability to process this work and is influenced by the fact
that I simultaneously work on many packages.
Around Saturday, February 16, 2008, I will contact you again and will send a
final patch
summarizing all the updates (changes to debconf templates,
updates to debconf translations and new debconf translations).
Again, thanks for your attention and cooperation.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.23-1-686 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
--- openvpn.old/debian/templates 2007-12-20 05:54:09.106495297 +0100
+++ openvpn/debian/templates 2008-01-22 07:34:00.648072803 +0100
@@ -1,6 +1,16 @@
+# These templates have been reviewed by the debian-l10n-english
+# team
+#
+# If modifications/additions/rewording are needed, please ask
+# [EMAIL PROTECTED] for advice.
+#
+# Even minor modifications require translation updates and such
+# changes should be coordinated with translators and reviewers.
+
Template: openvpn/change_init
Type: boolean
Default: false
+# NOT REVIEWED, obsolete
_Description: Would you like to start openvpn sooner?
Previous versions of openvpn started at the same time as most of other
services. This means that most of these services couldn't use openvpn
@@ -15,30 +25,29 @@
Template: openvpn/create_tun
Type: boolean
Default: false
-_Description: Would you like a TUN/TAP device to be created?
- If you accept here, the package will make a special device called
- /dev/net/tun for openvpn's use. If you refuse, the device won't be made
- now. Read README.Debian for details on how to make it. If you are using
- devfs refuse here.
+_Description: Create the TUN/TAP device?
+ If you choose this option, the /dev/net/tun device
+ needed by OpenVPN will be created.
+ .
+ You should not choose this option if you're using devfs.
Template: openvpn/stop2upgrade
Type: boolean
Default: false
-_Description: Would you like to stop openvpn before it gets upgraded?
- In some cases you may be upgrading openvpn in a remote server using
- a VPN to do so. The upgrade process stops the running daemon before
- installing the new version, in that case you may lose your connection,
- the upgrade may be interrupted, and you may not be able to reconnect to
- the remote host.
- .
- Unless you do your upgrades locally, it is advised NOT to stop openvpn
- before it gets upgraded. The installation process will restart it once
- it's done.
+_Description: Stop OpenVPN when upgraded?
+ The upgrade process stops the running daemon before
+ installing the new version. If you are installing or upgrading the
+ system remotely, that could break the upgrade process.
+ .
+ Unless upgrades are performed locally, you should choose to not stop
+ OpenVPN before it is upgraded. The installation process will restart it once
+ the upgrade is completed.
.
- This option will take effect in your next upgrade.
+ This option will take effect for the next upgrade.
Template: openvpn/default_port
Type: note
+# NOT REVIEWED, obsolete
_Description: Default port has changed
OpenVPN's default port has changed from 5000 to 1194 (IANA assigned).
If you don't specify the port to be used on your VPNs, this upgrade
@@ -51,6 +60,7 @@
Template: openvpn/change_init2
Type: boolean
Default: false
+# NOT REVIEWED, obsolete
_Description: Would you like to stop openvpn later?
Previous versions of openvpn stopped at the same time as most of other
services. This meant that some of services stopping later couldn't use
--- openvpn.old/debian/control 2007-12-20 05:54:09.106495297 +0100
+++ openvpn/debian/control 2008-01-19 08:09:52.212418349 +0100
@@ -9,15 +9,16 @@
Architecture: any
Depends: debconf | debconf-2.0, ${shlibs:Depends}
Suggests: openssl, resolvconf
-Description: Virtual Private Network daemon
- An application to securely tunnel IP networks over a single UDP or TCP port.
- It can be used to access remote sites, make secure point to point connections,
- enhance WiFi security, etc.
+Description: virtual private network daemon
+ OpenVPN is an application to securely tunnel IP networks over a
+ single UDP or TCP port. It can be used to access remote sites, make
+ secure point-to-point connections, enhance wireless security, etc.
.
- OpenVPN uses all of the encryption, authentication, and certification features
- of the OpenSSL library (any cipher, key size, or HMAC digest).
+ OpenVPN uses all of the encryption, authentication, and certification
+ features provided by the OpenSSL library (any cipher, key size, or
+ HMAC digest).
.
- OpenVPN may use static, pre-shared keys or TLS-based dynamic key exchange. It
+ OpenVPN may use static, pre-shared keys or TLS-based dynamic key exchange. It
also supports VPNs with dynamic endpoints (DHCP or dial-up clients), tunnels
- over NAT or connection-oriented stateful firewalls (like Linux's iptables).
+ over NAT or connection-oriented stateful firewalls (such as Linux's iptables).
