Christian,

The wording in the template was changed as the racoon-tool script has had a
major refresh, and I will be expanding and maintaining it in the future.
 The previous wording was saying that it was deprecated as the NetBSD
ipsec-tools people did not like it....  I don't have access to that email
conversation, but the message had a considerable bias that does not reflect
the current state of affairs.  The "direct" mode is pointed out clearly for
the purpose it serves, and is mentioned first.  However, racoon is rather
uninformative in its log messages when it fails due to mis-configuration,
and it does not manage the SPD like openswan/strongswan, hence racoon-tool
perl script.

OK, The only thing changing here is the content of the message.  Any
variables, script logic is not being touched for stability reasons for
Wheezy freeze.  I have checked the new racoon-tool (I am its original
author) for functionality carefully, and it is a lot better than the older
version that was not even working. There are no translations yet of the
debconf messages for this package as far as I can remember, so another
patch to clean up typos and make it clearer as Justin Rye may be warranted
if only just for the sake of getting the English correct and up to policy
standard, as this is an improvement on the status quo, and does not affect
install logic.

Thanks heaps for your help,

Matthew Grant

On Mon, Jun 18, 2012 at 5:04 PM, Christian PERRIER <bubu...@debian.org>wrote:

> Quoting Justin B Rye (j...@edlug.org.uk):
>
> > > debconf template messages/translations I believe can be changed during
> > > freeze, no?
> >
> > That sort of question is best addressed to d-l-e rather than me!
>
>
> Translations, yes.
>
> Debconf templates, I would insist you don't unless:
> - deeply required
> - fully coordinated with i18n team (particularly handling the
> translation update round and wait for a GO before uploading-->we're
> targeting full completion for a fewlanguages and I track them  one by
> one
>
>
>

Reply via email to