Your message dated Wed, 29 Jun 2005 04:47:57 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#250264: fixed in mason 1.0.0-3
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 21 May 2004 16:13:35 +0000
>From [EMAIL PROTECTED] Fri May 21 09:13:35 2004
Return-path: <[EMAIL PROTECTED]>
Received: from (manitee.cs.ucsb.edu) [140.77.13.9]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1BRCeM-00029M-00; Fri, 21 May 2004 09:13:34 -0700
Received: from mquinson by manitee.cs.ucsb.edu with local (Exim 3.36 #1
(Debian))
id 1BQuZo-0000lK-00; Thu, 20 May 2004 22:55:40 +0200
Content-Type: multipart/mixed; boundary="===============2099889805=="
MIME-Version: 1.0
From: Martin Quinson <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: mason: Please switch to gettext-based debconf templates
X-Mailer: reportbug 2.56
Date: Thu, 20 May 2004 22:55:40 +0200
Message-Id: <[EMAIL PROTECTED]>
Sender: Martin Quinson <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-5.3 required=4.0 tests=BAYES_20,DATE_IN_PAST_12_24,
HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
This is a multi-part MIME message sent by reportbug.
--===============2099889805==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Package: mason
Version: n/a
Severity: wishlist
Tags: patch l10n
Using the "new" gettext format for debconf templates helps for templates
translations. For instance, detecting outdated or untranslated strings
becomes considerably easier. It also keeps track of who did which
translation.
Patch description:
------------------
The attached patch does the required modifications:
- debian/control modification for dependencies:
build-dep: debhelper (>= 4.1.16) which depends on po-debconf
depend: debconf (>= 1.2.0) since old versions have problems with templates
specifying the encoding of their content
- Add 'debconf-updatepo' to the clean target of your debian/rules
(to make sure that the relevant files are ready for translation in the
distributed source packages, and thus help translators)
- execute "debconf-gettextize debian/*templates*". This does:
- generate po/ directory containing all the translation mecanism
- change the template file to mark some strings as translatable by putting
a _ before the field name.
- mark the right strings as translatable in the templates. This is a manual
check to make sure that fields containing stuff which cannot be
translated such as kernel module name, and the one not shown to the users
are not marked as translatable.
- removed files left by debconf-gettextize (*.templates.XX which are the
old-style translations and now live in debian/po/XX.po)
The previously existing translation were not lost in the process, but
automatically converted to po files. You may however want to ask your
previous translator to review them and update them if needed. Also ask
them to add their name in the header of the po files, to ease future
maintainance and update of the file.
- update the style to the best current practice (see below)
- document the most caracteristic of those changes in debian/changelog
For more details, see po-debconf documentation, especially "man 7
po-debconf"
This patch also document the most important modifications in the changelog.
Use this as a sample, and please feel free to change it to fit your taste.
If you want to give me credit for this, write my name but avoid to publish
my email address there since I already get enough spam.
About backports:
----------------
Please note that the suggested modifications will make your
package a little bit harder to backport to earlier Debian releases. If
this is a concern to you, you may try to adopt the method used by the
openssh package and detailed by Colin Watson in
http://lists.debian.org/debian-i18n/2003/debian-i18n-200307/msg00026.html
This patch does not includes this method as this would make it too
invasive, IMHO. So, preserving backportability is up to you...
What to do with this:
---------------------
While I was working on the convertion to po-debconf, I noticed that the
templates of your package may be easily improved by applying the advices
contained at the following address:
http://people.debian.org/~bubulle/dtsg.txt
I applied the advices from this document concerning the short descriptions,
but you may want to change the long descriptions accordingly as well, for
example to make them clearer even to newbies. Don't get me wrong, I don't
want to criticize, I just want the template to reach a translatable state
(ie quite stable) rather soon.
Future:
-------
Once the switch is achieved, and the style improvement are done (if any), I
guess that you will receive translations of your templates rather soon. They
will consist in XX.po files where XX is the code of the language they
contain. Simply put them to debian/po, add a changelog entry, and your
package is ready for rebuilding and uploading after the usual checks.
If you modify your templates in the future, no action is absolutely
mandatory from you to take care of the translations (outdated translations
will be automatically discarded). But it is nicer to your translators and
your not english speaking users to include the updated translations in the
same upload. For that, run debconf-updatepo, and mail each translator the
XX.po file they provided you. Their adress can be found in the headers of
the po file. Wait a few days so that they can do their work, and put the new
version of the po file back in position in debian/po before upload.
Thanks for helping the translators, and thus your non english speaker
end-users.
Bye, Mt.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.3
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED]
--===============2099889805==
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: attachment; filename="diff-switch-mason"
diff -ruN mason-1.0.0.cpy/debian/changelog mason-1.0.0/debian/changelog
--- mason-1.0.0.cpy/debian/changelog 2004-05-20 11:45:36.000000000 +0200
+++ mason-1.0.0/debian/changelog 2004-05-20 22:42:05.000000000 +0200
@@ -1,3 +1,12 @@
+mason (1.0.0-3) unstable; urgency=low
+
+ * [Martin Quinson]
+ - switch to gettext based debconf templates
+ - Reword some templates to follow the best current practices
+ Closes #?????
+
+ --
+
mason (1.0.0-2) unstable; urgency=low
* fix masonlib to support iptables static in kernel
diff -ruN mason-1.0.0.cpy/debian/control mason-1.0.0/debian/control
--- mason-1.0.0.cpy/debian/control 2004-05-20 11:45:36.000000000 +0200
+++ mason-1.0.0/debian/control 2004-05-20 11:46:57.000000000 +0200
@@ -3,11 +3,11 @@
Priority: extra
Maintainer: Thomas Scheffczyk <[EMAIL PROTECTED]>
Standards-Version: 3.5.6
-Build-Depends-Indep: debhelper
+Build-Depends-Indep: debhelper (>= 4.1.16)
Package: mason
Architecture: all
-Depends: bash (>= 2.04-1), debconf
+Depends: bash (>= 2.04-1), debconf (>= 1.2.0)
Description: Interactively creates a Linux packet filtering firewall.
Mason creates a firewall that exactly matches the types of
TCP/IP traffic flowing in, out and through a Linux computer.
diff -ruN mason-1.0.0.cpy/debian/po/da.po mason-1.0.0/debian/po/da.po
--- mason-1.0.0.cpy/debian/po/da.po 1970-01-01 01:00:00.000000000 +0100
+++ mason-1.0.0/debian/po/da.po 2004-05-20 11:51:02.000000000 +0200
@@ -0,0 +1,93 @@
+#
+# 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.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2004-05-20 11:49+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=ISO-8859-1\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Type: select
+#. Description
+#: ../templates:5
+msgid "Default action for new firewall rules:"
+msgstr ""
+
+#. Type: select
+#. Description
+#: ../templates:5
+msgid ""
+"When Mason detects a new kind of traffic and creates a rule for it, what "
+"action should the rule take?"
+msgstr ""
+"Når Mason opdager en nye type trafik og laver en regel for det, hvilken "
+"handling skal reglen så tage?"
+
+#. Type: select
+#. Description
+#: ../templates:5
+msgid ""
+"The \"accept\" action will allow the packet through. \"Reject\" will stop "
+"the packet with a rejection reply, while \"deny\" will drop the packet "
+"silently."
+msgstr ""
+"\"accept\" handlingen vil tillade pakken. \"Reject\" vil stoppe pakken med "
+"et afvisnings svar, imens \"deny\" vil droppe pakken uden at melde tilbage."
+
+#. Type: select
+#. Choices
+#: ../templates:14
+msgid "accept, reject, deny"
+msgstr ""
+
+#. Type: select
+#. Description
+#: ../templates:16
+msgid "Default action for rulesets:"
+msgstr ""
+
+#. Type: select
+#. Description
+#: ../templates:16
+#, fuzzy
+msgid ""
+"What should the default action be when a packet does not match any of the "
+"rules set up by Mason?"
+msgstr ""
+"Hvad skal være standard handling, når en pakke ikke passer til nogen af "
+"reglerne sat opaf Mason?"
+
+#. Type: select
+#. Description
+#: ../templates:16
+msgid ""
+"Again, \"accept\" allows the packet through, \"reject\" drops the packet "
+"with a reply, and \"deny\" silently drops the packet."
+msgstr ""
+"Igen, \"accept\" handlingen vil tillade pakken, \"reject\" vil stoppe pakken "
+"med et afvisnings svar, imens \"deny\" vil droppe pakken uden at melde "
+"tilbage."
+
+#~ msgid "Which action should Mason use by default for new firewall rules?"
+#~ msgstr ""
+#~ "Hvilken handling skal Mason bruge som standard for nye firewall regler?"
+
+#~ msgid "Which action should be Mason's default action for rulesets?"
+#~ msgstr "Hvilken handling skal være Masons standard handling for regelsæt?"
diff -ruN mason-1.0.0.cpy/debian/po/POTFILES.in
mason-1.0.0/debian/po/POTFILES.in
--- mason-1.0.0.cpy/debian/po/POTFILES.in 1970-01-01 01:00:00.000000000
+0100
+++ mason-1.0.0/debian/po/POTFILES.in 2004-05-20 11:47:14.000000000 +0200
@@ -0,0 +1 @@
+[type: gettext/rfc822deb] templates
diff -ruN mason-1.0.0.cpy/debian/po/templates.pot
mason-1.0.0/debian/po/templates.pot
--- mason-1.0.0.cpy/debian/po/templates.pot 1970-01-01 01:00:00.000000000
+0100
+++ mason-1.0.0/debian/po/templates.pot 2004-05-20 11:49:03.000000000 +0200
@@ -0,0 +1,76 @@
+#
+# 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.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2004-05-20 11:49+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
+#. Description
+#: ../templates:5
+msgid "Default action for new firewall rules:"
+msgstr ""
+
+#. Type: select
+#. Description
+#: ../templates:5
+msgid ""
+"When Mason detects a new kind of traffic and creates a rule for it, what "
+"action should the rule take?"
+msgstr ""
+
+#. Type: select
+#. Description
+#: ../templates:5
+msgid ""
+"The \"accept\" action will allow the packet through. \"Reject\" will stop "
+"the packet with a rejection reply, while \"deny\" will drop the packet "
+"silently."
+msgstr ""
+
+#. Type: select
+#. Choices
+#: ../templates:14
+msgid "accept, reject, deny"
+msgstr ""
+
+#. Type: select
+#. Description
+#: ../templates:16
+msgid "Default action for rulesets:"
+msgstr ""
+
+#. Type: select
+#. Description
+#: ../templates:16
+msgid ""
+"What should the default action be when a packet does not match any of the "
+"rules set up by Mason?"
+msgstr ""
+
+#. Type: select
+#. Description
+#: ../templates:16
+msgid ""
+"Again, \"accept\" allows the packet through, \"reject\" drops the packet "
+"with a reply, and \"deny\" silently drops the packet."
+msgstr ""
diff -ruN mason-1.0.0.cpy/debian/rules mason-1.0.0/debian/rules
--- mason-1.0.0.cpy/debian/rules 2004-05-20 11:45:36.000000000 +0200
+++ mason-1.0.0/debian/rules 2004-05-20 11:46:28.000000000 +0200
@@ -19,6 +19,7 @@
dh_testdir
dh_testroot
rm -f build-stamp install-stamp
+ debconf-updatepo
# Add here commands to clean up after the build process.
-$(MAKE) clean
diff -ruN mason-1.0.0.cpy/debian/templates mason-1.0.0/debian/templates
--- mason-1.0.0.cpy/debian/templates 2004-05-20 11:45:36.000000000 +0200
+++ mason-1.0.0/debian/templates 2004-05-20 11:48:21.000000000 +0200
@@ -1,22 +1,21 @@
Template: mason/newrulepolicy
Type: select
-Choices: accept, reject, deny
+_Choices: accept, reject, deny
Default: accept
-Description: Which action should Mason use by default for new firewall rules?
- When Mason detects a new kind of traffic and creates a rule for it,
- what action should the rule take?
+_Description: Default action for new firewall rules:
+ When Mason detects a new kind of traffic and creates a rule for it, what
+ action should the rule take?
.
- The "accept" action will allow the packet through. "Reject" will
- stop the packet with a rejection reply, while "deny" will drop the
- packet silently.
+ The "accept" action will allow the packet through. "Reject" will stop the
+ packet with a rejection reply, while "deny" will drop the packet silently.
Template: mason/defaultpolicy
Type: select
-Choices: accept, reject, deny
+_Choices: accept, reject, deny
Default: accept
-Description: Which action should be Mason's default action for rulesets?
- What should the default action be when a packet does not match any of
- the rules set up by Mason?
+_Description: Default action for rulesets:
+ What should the default action be when a packet does not match any of the
+ rules set up by Mason?
.
- Again, "accept" allows the packet through, "reject" drops the packet
- with a reply, and "deny" silently drops the packet.
+ Again, "accept" allows the packet through, "reject" drops the packet with
+ a reply, and "deny" silently drops the packet.
diff -ruN mason-1.0.0.cpy/debian/templates.da mason-1.0.0/debian/templates.da
--- mason-1.0.0.cpy/debian/templates.da 2004-05-20 11:45:36.000000000 +0200
+++ mason-1.0.0/debian/templates.da 1970-01-01 01:00:00.000000000 +0100
@@ -1,34 +0,0 @@
-Template: mason/newrulepolicy
-Type: select
-Choices: accept, reject, deny
-Choices-da:
-Default: accept
-Description: Which action should Mason use by default for new firewall rules?
- When Mason detects a new kind of traffic and creates a rule for it, what
- action should the rule take?
- .
- The "accept" action will allow the packet through. "Reject" will stop the
- packet with a rejection reply, while "deny" will drop the packet silently.
-Description-da: Hvilken handling skal Mason bruge som standard for nye
firewall regler?
- Når Mason opdager en nye type trafik og laver en regel for det, hvilken
- handling skal reglen så tage?
- .
- "accept" handlingen vil tillade pakken. "Reject" vil stoppe pakken med et
- afvisnings svar, imens "deny" vil droppe pakken uden at melde tilbage.
-
-Template: mason/defaultpolicy
-Type: select
-Choices: accept, reject, deny
-Choices-da:
-Default: accept
-Description: Which action should be Mason's default action for rulesets?
- What should the default action be when a packet does not match any of the
- rules set up by Mason?
- .
- Again, "accept" allows the packet through, "reject" drops the packet with
- a reply, and "deny" silently drops the packet.
-Description-da: Hvilken handling skal være Masons standard handling for
regelsæt?
- Hvad skal være standard handling, når en pakke ikke passer til nogen af
- reglerne sat opaf Mason?
- Igen, "accept" handlingen vil tillade pakken, "reject" vil stoppe pakken
- med et afvisnings svar, imens "deny" vil droppe pakken uden at melde tilbage.
--===============2099889805==--
---------------------------------------
Received: (at 250264-close) by bugs.debian.org; 29 Jun 2005 12:55:25 +0000
>From [EMAIL PROTECTED] Wed Jun 29 05:55:25 2005
Return-path: <[EMAIL PROTECTED]>
Received: from gluck.debian.org [192.25.206.10]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DnbpC-0004ZE-01; Wed, 29 Jun 2005 05:37:54 -0700
Received: from newraff.debian.org [208.185.25.31] (mail)
by gluck.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DnYJc-0007dL-00; Wed, 29 Jun 2005 02:53:04 -0600
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
id 1DnYEf-00023V-00; Wed, 29 Jun 2005 04:47:57 -0400
From: Thomas Scheffczyk <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#250264: fixed in mason 1.0.0-3
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Wed, 29 Jun 2005 04:47:57 -0400
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
X-CrossAssassin-Score: 2
Source: mason
Source-Version: 1.0.0-3
We believe that the bug you reported is fixed in the latest version of
mason, which is due to be installed in the Debian FTP archive:
mason_1.0.0-3.diff.gz
to pool/main/m/mason/mason_1.0.0-3.diff.gz
mason_1.0.0-3.dsc
to pool/main/m/mason/mason_1.0.0-3.dsc
mason_1.0.0-3_all.deb
to pool/main/m/mason/mason_1.0.0-3_all.deb
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.
Thomas Scheffczyk <[EMAIL PROTECTED]> (supplier of updated mason 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.7
Date: Fri, 24 Jun 2005 11:41:10 +0200
Source: mason
Binary: mason
Architecture: source all
Version: 1.0.0-3
Distribution: unstable
Urgency: low
Maintainer: Thomas Scheffczyk <[EMAIL PROTECTED]>
Changed-By: Thomas Scheffczyk <[EMAIL PROTECTED]>
Description:
mason - Interactively creates a Linux packet filtering firewall.
Closes: 222384 250264 301321 312752
Changes:
mason (1.0.0-3) unstable; urgency=low
.
* Incorporated NMU changes (Thanks to Lucas Wall) (closes: #250264,
#301321)
* fix postinst to correctly install startup links (closes: #222384)
* upgrade to policy 3.6.1.0
* Added Vietnamese debconf template translation (Thanks to Clytie
Siddall) (closes: #312752)
Files:
328b4c36b4f52718ff47df0d4b8db449 602 net extra mason_1.0.0-3.dsc
f379575eedc36f1f4e1274767444cacb 8349 net extra mason_1.0.0-3.diff.gz
2207fe8c8ee7d321568a6856ffb77870 461316 net extra mason_1.0.0-3_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFCwk49ICWLj6LjFjIRAtzUAKCskG8L7aLYHZkEtK/doesDQkAabACcDYnz
rPiP8Cg9GaLwDva0pqZs6vM=
=3/VC
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
