Debian Bug report logs - #588962
schroot: Please provide documentation as po4a for translation

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Thomas Blein <tblein@tblein.eu>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: schroot: Please provide documentation as po4a for translation

Date: Tue, 13 Jul 2010 22:00:03 +0200

Package: schroot
Version: 5
Severity: wishlist
Tags: l10n

Hi,

I am currently taking care of the French translation of the schroot debconf 
messages. I saw that the documentation of the schroot package is not translated
in any language. I would like to translate it French. For this, there is a 
need to change the source organisation so the documentation use po4a to
allow us to translate it. 

I would like to know if such changes could be me made.

Thanks a lot,

Thomas

Message #10 received at 588962@bugs.debian.org (full text, mbox, reply):

From: Roger Leigh <rleigh@codelibre.net>

To: Thomas Blein <tblein@tblein.eu>, 588962@bugs.debian.org

Subject: Re: [buildd-tools-devel] Bug#588962: schroot: Please provide documentation as po4a for translation

Date: Tue, 13 Jul 2010 23:23:11 +0100

[Message part 1 (text/plain, inline)]

On Tue, Jul 13, 2010 at 10:00:03PM +0200, Thomas Blein wrote:
> I am currently taking care of the French translation of the schroot debconf 
> messages. I saw that the documentation of the schroot package is not translated
> in any language. I would like to translate it French. For this, there is a 
> need to change the source organisation so the documentation use po4a to
> allow us to translate it. 
> 
> I would like to know if such changes could be me made.

I'd be happy to make this sort of change, or accept patches to do this.
Currently the documentation is all in manual page format with some
GNU troff extensions; can po4a cope with this?  In particular, all
the nice formatting you get in the PDF documentation ("make pdf") is
something I'd like to preserve.

  https://alioth.debian.org/docman/view.php/30471/4113/schroot.pdf


Regards,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux             http://people.debian.org/~rleigh/
 `. `'   Printing on GNU/Linux?       http://gutenprint.sourceforge.net/
   `-    GPG Public Key: 0x25BFB848   Please GPG sign your mail.

[signature.asc (application/pgp-signature, inline)]

Message #15 received at 588962@bugs.debian.org (full text, mbox, reply):

From: David Prévot <david@tilapin.org>

To: Roger Leigh <rleigh@codelibre.net>, 588962@bugs.debian.org

Cc: Thomas Blein <tblein@tblein.eu>

Subject: [Was: Bug#588962: schroot: Please provide documentation as po4a for translation]

Date: Tue, 13 Jul 2010 22:06:44 -0400

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

Le 13/07/2010 18:23, Roger Leigh a écrit :
> On Tue, Jul 13, 2010 at 10:00:03PM +0200, Thomas Blein wrote:

>> [...] to change the source organisation so the documentation use po4a to
>> allow us to translate it. 
>>
>> I would like to know if such changes could be me made.
> 
> I'd be happy to make this sort of change, or accept patches to do this.

I would be happy to try and propose a patch to do so (I must admit
I never did such thing yet, but I already proposed Thomas to give
it a try).

> Currently the documentation is all in manual page format with some
> GNU troff extensions; can po4a cope with this?

Sure, it is presented as such in po4a(7). Some native packages
already provide a way to do so (for example adduser), and some not
native packages too (for example man-db). Some quality advices are
probably available in "Internationalisation and localisation in
Debian" [1] too.

[1] http://people.debian.org/~jfs/debconf6/html/x790.html#AEN797

> In particular, all
> the nice formatting you get in the PDF documentation ("make pdf") is
> something I'd like to preserve.

Since it seems to be created directly from the manual page (that
shouldn't be modified in the process), the only change I can
think of will be the ability to provides such document in foreign
languages.

Cheers

David

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAkw9G7EACgkQ18/WetbTC/r+DQCcD1pwcWJVQqB3KQicl+xmOh4I
idwAn3HgBSdxjS6+CKOVq5RRRuNSb/2k
=fX5c
-----END PGP SIGNATURE-----

Message #20 received at 588962@bugs.debian.org (full text, mbox, reply):

From: David Prévot <david@tilapin.org>

To: 588962@bugs.debian.org

Cc: Thomas Blein <tblein@tblein.eu>

Subject: Re: Bug#588962: [buildd-tools-devel] Bug#588962: schroot: Please provide documentation as po4a for translation

Date: Mon, 19 Jul 2010 13:24:12 -0400

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Le 13/07/2010 18:23, Roger Leigh a écrit :
> On Tue, Jul 13, 2010 at 10:00:03PM +0200, Thomas Blein wrote:
>> I am currently taking care of the French translation of the schroot debconf 
>> messages. I saw that the documentation of the schroot package is not translated
>> in any language. I would like to translate it French. For this, there is a 
>> need to change the source organisation so the documentation use po4a to
>> allow us to translate it. 
>>
>> I would like to know if such changes could be me made.
> 
> I'd be happy to make this sort of change, or accept patches to do this.
> Currently the documentation is all in manual page format with some
> GNU troff extensions; can po4a cope with this?

Actually, a tiny problem in the Locale::Po4a::Man module don't permit it
for the moment, but a patch is already on it's way [1]. Once po4a
updated, I will be happy to provide a patch in order to permit manual
pages translation.

[1]http://lists.alioth.debian.org/pipermail/po4a-devel/2010-July/001850.html

Anyway, in order to make translators life easier, Denis Barbier, in the
pointed message [1], proposed another version of schroot.1.in [2], fully
compatible with the actual one (as far as I tried the manual pages and
pdf generation, it provides exactly the same result). I fully agree with
him : PO files are much more understandable this way (and sources too I
think), so I ask you to consider similar changes into other manual pages.

[2]http://lists.alioth.debian.org/pipermail/po4a-devel/attachments/20100719/8962358d/attachment-0001.obj

Cheers

David

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAkxEijoACgkQ18/WetbTC/rOJQCfeS6p3NP9U85JkgDFIoGAAM/X
sQ0AoIMNNX27zRTjT6VXTux4cqdezhFk
=Uzq8
-----END PGP SIGNATURE-----

Message #25 received at 588962@bugs.debian.org (full text, mbox, reply):

From: David Prévot <david@tilapin.org>

To: 588962@bugs.debian.org, control@bugs.debian.org

Cc: Thomas Blein <tblein@tblein.eu>

Subject: schroot: Please include po4a material for translated documentation

Date: Wed, 28 Jul 2010 23:05:14 -0400

[Message part 1 (text/plain, inline)]

tag 588962 patch
thanks

Hi Roger, Thomas,

Le 19/07/2010 13:24, David Prévot a écrit :
> Le 13/07/2010 18:23, Roger Leigh a écrit :
>> On Tue, Jul 13, 2010 at 10:00:03PM +0200, Thomas Blein wrote:

>>> [...] I saw that the documentation of the schroot package is not translated
>>> in any language. I would like to translate it French. For this, there is a 
>>> need to change the source organisation so the documentation use po4a to
>>> allow us to translate it. 
>>>
>>> I would like to know if such changes could be me made.
> 
>> I'd be happy to make this sort of change, or accept patches to do this.

Please find attached a patch against the current git repository in order
to provide POT files to translators, and build translated documentation.

1. You first want to run "po4a man/po4a/po4a.cfg" in order to populate
the POT file (man/po4a/po/schroot-man.pot here, the name is arbitrary).

2. The POT file should then be proposed to translators. Once you
received one (fr.po for example), you just have to put it in
man/po4a/po/. If you receive an addendum (fr.add for example), just put
it a the new sub-directory man/po4a/add_fr/.

3. If there are some translations, run "po4a man/po4a/po4a.cfg" in order
to update PO and POT files and build the translated documentation (for
example, French translation of man/schroot.1.in will be build in
man/translated/fr/schroot.1.in).

4. You also probably want to add a clean rule in order to delete the
directory man/translated (which will contain, in subdirectories, the
translated documentation build by "po4a man/po4a/po4a.cfg"): it doesn't
need to be saved in your VCS, just keep the PO and POT files.

I'm not sure of how you want to configure stuff with Autotools, but:
point 1: just need to be done once you've applied the patch.
point 2: just need to be done once you receive a translation.
point 3: it should be done before creating the tarball, thus the
 	proposed rule added in the dist-hook target.
point 4: you should add a clean rule somewhere.

You also off course need to actually build and install the translated
manual pages (from man/translated/$lang/manpages.#.in), but it can wait
until you actually receive some translation. translated pdf and ps can
also be provided.

>> Currently the documentation is all in manual page format with some
>> GNU troff extensions; can po4a cope with this?
> 
> Actually, a tiny problem in the Locale::Po4a::Man module don't permit it
> for the moment, but a patch is already on it's way.

po4a 0.40 released yesterday is now OK with GNU troff extensions used in
your manual pages.

> Anyway, in order to make translators life easier, Denis Barbier [...]
> proposed another version of schroot.1.in [2], fully
> compatible with the actual one (as far as I tried the manual pages and
> pdf generation, it provides exactly the same result). I fully agree with
> him : PO files are much more understandable this way (and sources too I
> think), so I ask you to consider similar changes into other manual pages.
> 
> [2]http://lists.alioth.debian.org/pipermail/po4a-devel/attachments/20100719/8962358d/attachment-0001.obj

The patch includes Denis' proposition, it's updated against the current
version (in git) of schroot.1.in.

Cheers

David

[add-translation.patch (text/x-diff, attachment)]

[signature.asc (application/pgp-signature, attachment)]

Message #32 received at 588962@bugs.debian.org (full text, mbox, reply):

From: Roger Leigh <rleigh@codelibre.net>

To: David Prévot <david@tilapin.org>, 588962@bugs.debian.org

Cc: control@bugs.debian.org, Thomas Blein <tblein@tblein.eu>

Subject: Re: [buildd-tools-devel] Bug#588962: schroot: Please include po4a material for translated documentation

Date: Sun, 15 Aug 2010 12:32:45 +0100

[Message part 1 (text/plain, inline)]

On Wed, Jul 28, 2010 at 11:05:14PM -0400, David Prévot wrote:
> tag 588962 patch
> thanks
> 
> Hi Roger, Thomas,
> 
> Le 19/07/2010 13:24, David Prévot a écrit :
> > Le 13/07/2010 18:23, Roger Leigh a écrit :
> >> On Tue, Jul 13, 2010 at 10:00:03PM +0200, Thomas Blein wrote:
> 
> >>> [...] I saw that the documentation of the schroot package is not translated
> >>> in any language. I would like to translate it French. For this, there is a 
> >>> need to change the source organisation so the documentation use po4a to
> >>> allow us to translate it. 
> >>>
> >>> I would like to know if such changes could be me made.
> > 
> >> I'd be happy to make this sort of change, or accept patches to do this.
> 
> Please find attached a patch against the current git repository in order
> to provide POT files to translators, and build translated documentation.
> 
> 1. You first want to run "po4a man/po4a/po4a.cfg" in order to populate
> the POT file (man/po4a/po/schroot-man.pot here, the name is arbitrary).
> 
> 2. The POT file should then be proposed to translators. Once you
> received one (fr.po for example), you just have to put it in
> man/po4a/po/. If you receive an addendum (fr.add for example), just put
> it a the new sub-directory man/po4a/add_fr/.
> 
> 3. If there are some translations, run "po4a man/po4a/po4a.cfg" in order
> to update PO and POT files and build the translated documentation (for
> example, French translation of man/schroot.1.in will be build in
> man/translated/fr/schroot.1.in).
> 
> 4. You also probably want to add a clean rule in order to delete the
> directory man/translated (which will contain, in subdirectories, the
> translated documentation build by "po4a man/po4a/po4a.cfg"): it doesn't
> need to be saved in your VCS, just keep the PO and POT files.
> 
> I'm not sure of how you want to configure stuff with Autotools, but:
> point 1: just need to be done once you've applied the patch.
> point 2: just need to be done once you receive a translation.
> point 3: it should be done before creating the tarball, thus the
>  	proposed rule added in the dist-hook target.
> point 4: you should add a clean rule somewhere.
> 
> You also off course need to actually build and install the translated
> manual pages (from man/translated/$lang/manpages.#.in), but it can wait
> until you actually receive some translation. translated pdf and ps can
> also be provided.

Many thanks for all your help with this.  I'm afraid I'm quite
busy with my PhD at the moment, but I hope to get this included
soon, hopefully for Squeeze but that might not be possible.


Thanks again,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux             http://people.debian.org/~rleigh/
 `. `'   Printing on GNU/Linux?       http://gutenprint.sourceforge.net/
   `-    GPG Public Key: 0x25BFB848   Please GPG sign your mail.

[signature.asc (application/pgp-signature, inline)]

Message #37 received at 588962@bugs.debian.org (full text, mbox, reply):

From: Roger Leigh <rleigh@codelibre.net>

To: David Prévot <david@tilapin.org>, 588962@bugs.debian.org

Cc: Thomas Blein <tblein@tblein.eu>

Subject: Re: [buildd-tools-devel] Bug#588962: [Was: Bug#588962: schroot: Please provide documentation as po4a for translation]

Date: Sun, 27 Nov 2011 22:37:55 +0000

On Tue, Jul 13, 2010 at 10:06:44PM -0400, David Prévot wrote:
> > Currently the documentation is all in manual page format with some
> > GNU troff extensions; can po4a cope with this?
> 
> Sure, it is presented as such in po4a(7). Some native packages
> already provide a way to do so (for example adduser), and some not
> native packages too (for example man-db). Some quality advices are
> probably available in "Internationalisation and localisation in
> Debian" [1] too.
> 
> Since it seems to be created directly from the manual page (that
> shouldn't be modified in the process), the only change I can
> think of will be the ability to provides such document in foreign
> languages.

Hi there,

Sorry for the long delay--I had to finish my PhD, and this got
pushed to the back of my TODO list.

Many thanks for doing the patch for po4a.
I've had a look at applying your patch to the current schroot
sources.  It's available at
  git://git.debian.org/git/users/rleigh/schroot.git
(branch po4a)

Due to changes in the meantime, I've not been able to apply
it directly.  I've separately done the .EX/.EE example fixes,
and then applied your patch afterward.  Note it's lacking the
translator comments in the manual page--I think I'll generate
the examples and include them directly with .so, rather than
requiring translators to update them by hand; we can probably
even generate localised examples automatically this way,
providing that we have the appropriate locales available on
the system.

I'm having some difficulty in initially getting things working;
while being familiar with gettext for over a decade, po4a is a
bit new, and I'm not sure if your patch includes the needed
logic for actually generating the .pot file or if that needs
doing in addition.  Some pointers would be much appreciated.
I'm also unsure of how to generate the localised manpages and
include them in the build infrastructure.


Regards,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux             http://people.debian.org/~rleigh/
 `. `'   Printing on GNU/Linux?       http://gutenprint.sourceforge.net/
   `-    GPG Public Key: 0x25BFB848   Please GPG sign your mail.

Message #42 received at 588962@bugs.debian.org (full text, mbox, reply):

From: David Prévot <david@tilapin.org>

To: 588962@bugs.debian.org

Cc: Thomas Blein <tblein@tblein.eu>

Subject: Re: [buildd-tools-devel] Bug#588962: [Was: Bug#588962: schroot: Please provide documentation as po4a for translation]

Date: Sun, 27 Nov 2011 19:23:36 -0400

[Message part 1 (text/plain, inline)]

Hi Roger, Thomas,

On 27/11/2011 18:37, Roger Leigh wrote:

> Sorry for the long delay--I had to finish my PhD, and this got
> pushed to the back of my TODO list.

Well, if this imply you've finished your PhD, let me just congratulate you!

> […] we can probably
> even generate localised examples automatically this way,
> providing that we have the appropriate locales available on
> the system.

Good idea, a Build-Depends on locales-all is not that expensive ;-).

> I'm having some difficulty in initially getting things working;

> […] I'm not sure if your patch includes the needed
> logic for actually generating the .pot file or if that needs
> doing in addition.

It indeed needs an empty POT file in the accurate directory (my patch
aimed to contain this empty file, but I obviously missed it):

	mkdir man/po4a/po
	touch man/po4a/po/schroot-man.pot
	po4a --force man/po4a/po4a.cfg

You can either choose to ship the POT file in the the Git repository, or
to remove it at clean time, and regenerate it using “touch” and “po4a
--force …”, as you prefer.

> Some pointers would be much appreciated.

po4a(1) gives some information (see EXAMPLE section),
/usr/share/doc/po4a/README.maintainers.gz is also useful, and I tried to
point the needed stuff on my patch message [0].

	0: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588962#25

Since then, I've learned a few more stuff on po4a, so I may offer more
accurate advices now.

> I'm also unsure of how to generate the localised manpages and
> include them in the build infrastructure.

If Thomas is still willing to translate the pages, I think the best
approach is to let him begin, and once an initial (incomplete and even
not reviewed yet) PO file will be available, we'll try to provide a few
more patches (or direction of things to do, since I'm still not really
aware of the Makefile stuff). We've recently succeeded with that
approach in grep-dctrl and packaging-tutorial.

Regards

David

[signature.asc (application/pgp-signature, attachment)]

Message #47 received at 588962@bugs.debian.org (full text, mbox, reply):

From: Thomas Blein <tblein@tblein.eu>

To: David Prévot <david@tilapin.org>, 588962@bugs.debian.org

Subject: Re: Bug#588962: [buildd-tools-devel] Bug#588962: [Was: Bug#588962: schroot: Please provide documentation as po4a for translation]

Date: Mon, 28 Nov 2011 10:21:54 +0100

Hi Roger and David,

Le dimanche 27 nov. 2011 à 19:23:36 (-0400), David Prévot a écrit :
> On 27/11/2011 18:37, Roger Leigh wrote:
> 
> > Sorry for the long delay--I had to finish my PhD, and this got
> > pushed to the back of my TODO list.
> 
> Well, if this imply you've finished your PhD, let me just congratulate you!

Right, congratulation!

> > I'm also unsure of how to generate the localised manpages and
> > include them in the build infrastructure.
> 
> If Thomas is still willing to translate the pages, I think the best
> approach is to let him begin, and once an initial (incomplete and even
> not reviewed yet) PO file will be available, we'll try to provide a few
> more patches (or direction of things to do, since I'm still not really
> aware of the Makefile stuff). We've recently succeeded with that
> approach in grep-dctrl and packaging-tutorial.

I am still interested in the translation. I will started I think
quickly so we can have an idea of the different problem we will have.
However I do not think to be able to finish the translation before the
end of the year: I need to write a big research project before Christmas.
I will do at least one part so you can look at the integration of the
translation.

Regards,

Thomas

Message #52 received at 588962@bugs.debian.org (full text, mbox, reply):

From: Roger Leigh <rleigh@codelibre.net>

To: Thomas Blein <tblein@tblein.eu>, 588962@bugs.debian.org

Cc: David Prévot <david@tilapin.org>

Subject: Re: [buildd-tools-devel] Bug#588962: Bug#588962: [Was: Bug#588962: schroot: Please provide documentation as po4a for translation]

Date: Mon, 28 Nov 2011 23:45:07 +0000

On Mon, Nov 28, 2011 at 10:21:54AM +0100, Thomas Blein wrote:
> Hi Roger and David,
> 
> Le dimanche 27 nov. 2011 à 19:23:36 (-0400), David Prévot a écrit :
> > On 27/11/2011 18:37, Roger Leigh wrote:
> > 
> > > Sorry for the long delay--I had to finish my PhD, and this got
> > > pushed to the back of my TODO list.
> > 
> > Well, if this imply you've finished your PhD, let me just congratulate you!
> 
> Right, congratulation!

Well, I handed in my thesis, but have to wait until mid-January for
my viva!

> > > I'm also unsure of how to generate the localised manpages and
> > > include them in the build infrastructure.
> > 
> > If Thomas is still willing to translate the pages, I think the best
> > approach is to let him begin, and once an initial (incomplete and even
> > not reviewed yet) PO file will be available, we'll try to provide a few
> > more patches (or direction of things to do, since I'm still not really
> > aware of the Makefile stuff). We've recently succeeded with that
> > approach in grep-dctrl and packaging-tutorial.
> 
> I am still interested in the translation. I will started I think
> quickly so we can have an idea of the different problem we will have.
> However I do not think to be able to finish the translation before the
> end of the year: I need to write a big research project before Christmas.
> I will do at least one part so you can look at the integration of the
> translation.

That would be much appreciated, thanks.  I think schroot-faq.7.man
is the shortest page; it includes authors.man and
copyright.man which are tiny.

With David's advice, I've now got it to generate a pot file.  I've
put it all on the po4a branch at
git://anonscm.debian.org/users/rleigh/schroot.git

The potfile may be downloaded directly from
http://anonscm.debian.org/gitweb/?p=users/rleigh/schroot.git;a=blob_plain;f=man/po4a/po/schroot-man.pot;hb=po4a

I'll work on adding translated manpage (and example) generation once
we have something translated to work with.


Many thanks,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux             http://people.debian.org/~rleigh/
 `. `'   Printing on GNU/Linux?       http://gutenprint.sourceforge.net/
   `-    GPG Public Key: 0x25BFB848   Please GPG sign your mail.

Message #57 received at 588962@bugs.debian.org (full text, mbox, reply):

From: Roger Leigh <rleigh@codelibre.net>

To: Thomas Blein <tblein@tblein.eu>, 588962@bugs.debian.org

Cc: David Prévot <david@tilapin.org>

Subject: Re: [buildd-tools-devel] Bug#588962: Bug#588962: Bug#588962: [Was: Bug#588962: schroot: Please provide documentation as po4a for translation]

Date: Mon, 23 Jan 2012 09:42:12 +0000

On Mon, Nov 28, 2011 at 11:45:07PM +0000, Roger Leigh wrote:
> On Mon, Nov 28, 2011 at 10:21:54AM +0100, Thomas Blein wrote:
> > Hi Roger and David,
> > 
> > Le dimanche 27 nov. 2011 à 19:23:36 (-0400), David Prévot a écrit :
> > > On 27/11/2011 18:37, Roger Leigh wrote:
> > > 
> > > If Thomas is still willing to translate the pages, I think the best
> > > approach is to let him begin, and once an initial (incomplete and even
> > > not reviewed yet) PO file will be available, we'll try to provide a few
> > > more patches (or direction of things to do, since I'm still not really
> > > aware of the Makefile stuff). We've recently succeeded with that
> > > approach in grep-dctrl and packaging-tutorial.
> > 
> > I am still interested in the translation. I will started I think
> > quickly so we can have an idea of the different problem we will have.
> > However I do not think to be able to finish the translation before the
> > end of the year: I need to write a big research project before Christmas.
> > I will do at least one part so you can look at the integration of the
> > translation.
> 
> That would be much appreciated, thanks.  I think schroot-faq.7.man
> is the shortest page; it includes authors.man and
> copyright.man which are tiny.

Just to let you know, I've merged the po4a branch into our master
branch, and made a test release which may be downloaded from

  http://people.debian.org/~rleigh/schroot-1.5.2.tar.xz

If you have time to do a translation of one of the manpages, I'll
then be able to complete the job of actually generating the
translated manpages, and installing them.


Regards,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux             http://people.debian.org/~rleigh/
 `. `'   Printing on GNU/Linux?       http://gutenprint.sourceforge.net/
   `-    GPG Public Key: 0x25BFB848   Please GPG sign your mail.

Message #62 received at 588962@bugs.debian.org (full text, mbox, reply):

From: Thomas Blein <tblein@tblein.eu>

To: Roger Leigh <rleigh@codelibre.net>, 588962@bugs.debian.org

Cc: David Prévot <david@tilapin.org>

Subject: Re: Bug#588962: [buildd-tools-devel] Bug#588962: Bug#588962: [Was: Bug#588962: schroot: Please provide documentation as po4a for translation]

Date: Sat, 4 Feb 2012 18:18:10 +0100

[Message part 1 (text/plain, inline)]

Hi,

I use a cold afternoon for some translation of the po file you send.
Sorry for the delay, I am quite overload at the moment.

I think I translated schroot-faq.7.man, schroot-script-config.5.man and I
hope all the common headers. It is not yet proof read by the
debian-l10n-french team.

I let you work with this partially translated file hopping it is sufficient
to help you working on its integration.

Best regards,

Thomas

[fr.po (text/plain, attachment)]

Message #67 received at 588962@bugs.debian.org (full text, mbox, reply):

From: Thomas Blein <tblein@tblein.eu>

To: 588962@bugs.debian.org

Cc: Roger Leigh <rleigh@codelibre.net>, David Prévot <david@tilapin.org>

Subject: Re: Bug#588962: schroot: Please provide documentation as po4a for translation

Date: Wed, 18 Apr 2012 01:51:10 +0200

[Message part 1 (text/plain, inline)]

Hi Roger,

I just finished the first draft translation of all the man pages into
French.
You have to not that it need still some review, first from me and then
from the French translation team before real integration since it is not
completely proof-readed.

However with this file you may certainly do some test of integration of
it.

Best regards,

Thomas

[fr.po (text/plain, attachment)]

Message #72 received at 588962@bugs.debian.org (full text, mbox, reply):

From: Roger Leigh <rleigh@codelibre.net>

To: Thomas Blein <tblein@tblein.eu>

Cc: 588962@bugs.debian.org, David Prévot <david@tilapin.org>

Subject: Re: Bug#588962: schroot: Please provide documentation as po4a for translation

Date: Wed, 18 Apr 2012 09:39:18 +0100

On Wed, Apr 18, 2012 at 01:51:10AM +0200, Thomas Blein wrote:
> Hi Roger,
> 
> I just finished the first draft translation of all the man pages into
> French.
> You have to not that it need still some review, first from me and then
> from the French translation team before real integration since it is not
> completely proof-readed.
> 
> However with this file you may certainly do some test of integration of
> it.

Many thanks for all the effort you have put into this.  Hopefully I'll
have time to work on this at the weekend, time permitting, or in the
evening next week sometime if not.


Many thanks,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux    http://people.debian.org/~rleigh/
 `. `'   schroot and sbuild  http://alioth.debian.org/projects/buildd-tools
   `-    GPG Public Key      F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800

Message #77 received at 588962@bugs.debian.org (full text, mbox, reply):

From: Thomas Blein <tblein@tblein.eu>

To: Roger Leigh <rleigh@codelibre.net>

Cc: 588962@bugs.debian.org, David Prévot <david@tilapin.org>

Subject: Re: Bug#588962: schroot: Please provide documentation as po4a for translation

Date: Thu, 19 Apr 2012 10:30:52 +0200

[Message part 1 (text/plain, inline)]

Hi Roger,

Le mercredi 18 avril 2012 à 09:39:18 (+0100), Roger Leigh a écrit :
> Many thanks for all the effort you have put into this.  Hopefully I'll
> have time to work on this at the weekend, time permitting, or in the
> evening next week sometime if not.

I made a small test of integration on the po4a branch of schroot:
- put the French file at the correct place
- run the po4a command

Only one error came out due to a missing "I" in front of a "<". After
correction the creation of the French manpage went perfectly.

Therefore attached a new version of the French translation that correct
this small problem.

Best regards,

Thomas

[fr.po.gz (application/octet-stream, attachment)]

Message #82 received at 588962@bugs.debian.org (full text, mbox, reply):

From: Roger Leigh <rleigh@codelibre.net>

To: debian-i18n@codelibre.net

Cc: Thomas Blein <tblein@tblein.eu>, 588962@bugs.debian.org

Subject: po4a using both builddir and srcdir

Date: Tue, 15 May 2012 00:48:25 +0100

Hi folks,

I've been working on #588962 to implement po4a for the schroot
documentation.  However, I'm running into a few difficulties
which I hope some old hands can provide some guidance on
fixing.

I have added Thomas' fr translation, and got it to produce
fr manpages and PDF documentation.  This is in a prerelease
version at
  http://people.debian.org/~rleigh/schroot_1.5.1.orig.tar.xz

The main issues are:

- I'm getting a "translated" directory in both the source
  directory and build directory
  (man/translated/fr and debian/build/man/translated/fr).
  It's a bug to dirty the source tree--I really only want
  them generating in the build tree.
  I set srcdir and destdir, but I'm not sure if I'm doing the
  right thing (see: man/Makefile.am update-po rule).

- The fr manpages are output in UTF-8.  The man program results
  in readable output, but the PDF/PS documentation looks awful
  due to lots of junk in the output.
  While UTF-8 is fine in the .po file, would recoding to latin1
  or into groff symbols for non-ASCII characters be feasible?
  Or can groff now process UTF-8 input?
  (./configure && make pdf to test)

- There have been several manpage changes since the translation
  was done.  Thomas, would it be possible to update the
  translation?  It's in man/po/fr.po of the above source
  archive, though I can send you the file if you need.

Other than these hopefully minor issues, the translated manpages
look beautiful, and I'll be happy to install them into the .deb
once they are fixed.


Thanks everyone,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux    http://people.debian.org/~rleigh/
 `. `'   schroot and sbuild  http://alioth.debian.org/projects/buildd-tools
   `-    GPG Public Key      F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800

Message #87 received at 588962@bugs.debian.org (full text, mbox, reply):

From: Roger Leigh <rleigh@codelibre.net>

To: debian-i18n@lists.debian.org

Cc: Thomas Blein <tblein@tblein.eu>, 588962@bugs.debian.org

Subject: po4a using both builddir and srcdir

Date: Tue, 15 May 2012 00:50:11 +0100

Hi folks,

I've been working on #588962 to implement po4a for the schroot
documentation.  However, I'm running into a few difficulties
which I hope some old hands can provide some guidance on
fixing.

I have added Thomas' fr translation, and got it to produce
fr manpages and PDF documentation.  This is in a prerelease
version at
  http://people.debian.org/~rleigh/schroot_1.5.1.orig.tar.xz

The main issues are:

- I'm getting a "translated" directory in both the source
  directory and build directory
  (man/translated/fr and debian/build/man/translated/fr).
  It's a bug to dirty the source tree--I really only want
  them generating in the build tree.
  I set srcdir and destdir, but I'm not sure if I'm doing the
  right thing (see: man/Makefile.am update-po rule).

- The fr manpages are output in UTF-8.  The man program results
  in readable output, but the PDF/PS documentation looks awful
  due to lots of junk in the output.
  While UTF-8 is fine in the .po file, would recoding to latin1
  or into groff symbols for non-ASCII characters be feasible?
  Or can groff now process UTF-8 input?
  (./configure && make pdf to test)

- There have been several manpage changes since the translation
  was done.  Thomas, would it be possible to update the
  translation?  It's in man/po/fr.po of the above source
  archive, though I can send you the file if you need.

Other than these hopefully minor issues, the translated manpages
look beautiful, and I'll be happy to install them into the .deb
once they are fixed.


Thanks everyone,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux    http://people.debian.org/~rleigh/
 `. `'   schroot and sbuild  http://alioth.debian.org/projects/buildd-tools
   `-    GPG Public Key      F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800

Message #92 received at 588962@bugs.debian.org (full text, mbox, reply):

From: Thomas Blein <tblein@tblein.eu>

To: Roger Leigh <rleigh@codelibre.net>, 588962@bugs.debian.org

Cc: debian-i18n@lists.debian.org

Subject: Re: Bug#588962: po4a using both builddir and srcdir

Date: Tue, 15 May 2012 16:48:29 +0200

Hi Roger,

Quoting Roger Leigh <rleigh@codelibre.net>:
> - The fr manpages are output in UTF-8.  The man program results
>   in readable output, but the PDF/PS documentation looks awful
>   due to lots of junk in the output.
>   While UTF-8 is fine in the .po file, would recoding to latin1
>   or into groff symbols for non-ASCII characters be feasible?
>   Or can groff now process UTF-8 input?
>   (./configure && make pdf to test)

For me I can do the both (latin1 and groff symbols). After I don't
know how it should be for long term integration.

> - There have been several manpage changes since the translation
>   was done.  Thomas, would it be possible to update the
>   translation?

No problem. I take care of it.

Regards,

Thomas

Message #97 received at 588962@bugs.debian.org (full text, mbox, reply):

From: Roger Leigh <rleigh@codelibre.net>

To: Thomas Blein <tblein@tblein.eu>, 588962@bugs.debian.org

Cc: debian-i18n@lists.debian.org

Subject: Re: [buildd-tools-devel] Bug#588962: po4a using both builddir and srcdir

Date: Tue, 15 May 2012 16:46:58 +0100

On Tue, May 15, 2012 at 04:48:29PM +0200, Thomas Blein wrote:
> Hi Roger,
> 
> Quoting Roger Leigh <rleigh@codelibre.net>:
> >- The fr manpages are output in UTF-8.  The man program results
> >  in readable output, but the PDF/PS documentation looks awful
> >  due to lots of junk in the output.
> >  While UTF-8 is fine in the .po file, would recoding to latin1
> >  or into groff symbols for non-ASCII characters be feasible?
> >  Or can groff now process UTF-8 input?
> >  (./configure && make pdf to test)
> 
> For me I can do the both (latin1 and groff symbols). After I don't
> know how it should be for long term integration.

I would definitely prefer the text to remain as plain UTF-8 in
the .po file--it will make it easier all around to both work on
and use.  Ideally I'd just like to be able to ask po4a to
recode it to latin1 when it comes to generating the translation,
and/or replace accented characters with groff escapes.  Hopefully
this is doable with po4a.  If not, I can always just recode the
documentation before processing it with groff.

BTW, I could, if it made translation easier, switch to a different
format than troff, for example DocBook.  My only issue with
DocBook was that all the tools to convert to manpage format were
awful.  But if there are alternatives I should consider, I'll be
happy to do so.

> >- There have been several manpage changes since the translation
> >  was done.  Thomas, would it be possible to update the
> >  translation?
> 
> No problem. I take care of it.

Much appreciated, thanks!  It will look really nice when complete.


Regards,
Roger
-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux    http://people.debian.org/~rleigh/
 `. `'   schroot and sbuild  http://alioth.debian.org/projects/buildd-tools
   `-    GPG Public Key      F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800

Message #102 received at 588962@bugs.debian.org (full text, mbox, reply):

From: David Prévot <taffit@debian.org>

To: Roger Leigh <rleigh@codelibre.net>, 588962@bugs.debian.org

Cc: debian-i18n@lists.debian.org, Thomas Blein <tblein@tblein.eu>, po4a-devel@lists.alioth.debian.org

Subject: Re: Bug#588962: po4a using both builddir and srcdir

Date: Tue, 15 May 2012 12:46:08 -0400

[Message part 1 (text/plain, inline)]

Hi,

Le 14/05/2012 19:50, Roger Leigh a écrit :

> I've been working on #588962 to implement po4a for the schroot
> documentation.

Thanks Roger!

>   http://people.debian.org/~rleigh/schroot_1.5.1.orig.tar.xz

I guess you actually meant:

	http://people.debian.org/~rleigh/schroot-1.5.2.tar.xz

> - I'm getting a "translated" directory in both the source
>   directory and build directory
>   (man/translated/fr and debian/build/man/translated/fr).
>   It's a bug to dirty the source tree--I really only want
>   them generating in the build tree.
>   I set srcdir and destdir, but I'm not sure if I'm doing the
>   right thing (see: man/Makefile.am update-po rule).

I can't see what's wrong at first sight, adding the po4a-devel list in
the loop in case we're missing something. The actual call is:

[ -n "$(PO4A)" ] && $(PO4A) --package-name $(PACKAGE) --package-version
$(VERSION) --copyright-holder "Roger Leigh <rleigh@debian.org>"
"--srcdir=$(srcdir)" "--destdir=$(builddir)" "$(srcdir)/po4a.cfg"

Indeed, simply running “po4a --destdir=../debian/build/man/ po4a.cfg”
from the man directory builds everything where expected (even with
“--srcdir=.”), but when run from the root directory, it builds them in
both the --srcdir and the --destdir, so it may be a bug in po4a. As a
workaround, you could remove the sloppy man/translated directory in the
update-po rule, after the po4a call.

> - The fr manpages are output in UTF-8.  The man program results
>   in readable output, but the PDF/PS documentation looks awful
>   due to lots of junk in the output.
>   While UTF-8 is fine in the .po file, would recoding to latin1
>   or into groff symbols for non-ASCII characters be feasible?

Charset of the files containing the localized documents can be change
with the -L option of po4a, but, there is better:

>   Or can groff now process UTF-8 input?

“groff -k -KUTF-8” seems to do the work quite nicely.

Regards

David

[signature.asc (application/pgp-signature, attachment)]

Message #107 received at 588962@bugs.debian.org (full text, mbox, reply):

From: Roger Leigh <rleigh@codelibre.net>

To: David Prévot <taffit@debian.org>, 588962@bugs.debian.org

Cc: Thomas Blein <tblein@tblein.eu>, po4a-devel@lists.alioth.debian.org, debian-i18n@lists.debian.org

Subject: Re: [buildd-tools-devel] Bug#588962: po4a using both builddir and srcdir

Date: Tue, 15 May 2012 20:33:04 +0100

On Tue, May 15, 2012 at 12:46:08PM -0400, David Prévot wrote:
> Hi,
> 
> Le 14/05/2012 19:50, Roger Leigh a écrit :
> 
> > I've been working on #588962 to implement po4a for the schroot
> > documentation.
> 
> Thanks Roger!
> 
> >   http://people.debian.org/~rleigh/schroot_1.5.1.orig.tar.xz
> 
> I guess you actually meant:
> 
> 	http://people.debian.org/~rleigh/schroot-1.5.2.tar.xz

Yes, sorry about that--I was working on this quite late, and that
was a copy-paste error.  schroot-1.5.2.tar.xz is the correct file.

> > - I'm getting a "translated" directory in both the source
> >   directory and build directory
> >   (man/translated/fr and debian/build/man/translated/fr).
> >   It's a bug to dirty the source tree--I really only want
> >   them generating in the build tree.
> >   I set srcdir and destdir, but I'm not sure if I'm doing the
> >   right thing (see: man/Makefile.am update-po rule).
> 
> I can't see what's wrong at first sight, adding the po4a-devel list in
> the loop in case we're missing something. The actual call is:
> 
> [ -n "$(PO4A)" ] && $(PO4A) --package-name $(PACKAGE) --package-version
> $(VERSION) --copyright-holder "Roger Leigh <rleigh@debian.org>"
> "--srcdir=$(srcdir)" "--destdir=$(builddir)" "$(srcdir)/po4a.cfg"
> 
> Indeed, simply running “po4a --destdir=../debian/build/man/ po4a.cfg”
> from the man directory builds everything where expected (even with
> “--srcdir=.”), but when run from the root directory, it builds them in
> both the --srcdir and the --destdir, so it may be a bug in po4a. As a
> workaround, you could remove the sloppy man/translated directory in the
> update-po rule, after the po4a call.

We can do this as a workaround for now.  (Actually, for the release
I'm making today, I'll probably temporarily disable it entirely
until the updated translation is ready.  It'll be enabled for the
next release release though.)

In general though, it breaks building from a read-only source tree
of building several diffrent builds from a common source tree, so
I would hope to be able to fix it.  It should be possible to use
symlinks to work around this by faking that everything is in the
build dir if it really can't be fixed.

> > - The fr manpages are output in UTF-8.  The man program results
> >   in readable output, but the PDF/PS documentation looks awful
> >   due to lots of junk in the output.
> >   While UTF-8 is fine in the .po file, would recoding to latin1
> >   or into groff symbols for non-ASCII characters be feasible?
> 
> Charset of the files containing the localized documents can be change
> with the -L option of po4a, but, there is better:
> 
> >   Or can groff now process UTF-8 input?
> 
> “groff -k -KUTF-8” seems to do the work quite nicely.

Ah, fantastic stuff.  The PDF manpage looks great, bar a few
formatting issues (.TH might be broken).

http://people.debian.org/~rleigh/schroot-fr.pdf
http://people.debian.org/~rleigh/schroot-en.pdf

I did see an issue with missing words in some files such as
\*[PROGRAM] at the beginning of the line, but I couldn't see
a reason for it.  But I'm sure such minor details are easily
fixable though.

Hopefully in a future release I'll be able to localise all
the output of the program examples, too.  But that's quite a
lot more work, and will require writing programs to generate
the output, too, so it might have to wait until after wheezy.


Regards,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux    http://people.debian.org/~rleigh/
 `. `'   schroot and sbuild  http://alioth.debian.org/projects/buildd-tools
   `-    GPG Public Key      F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800

Message #112 received at 588962@bugs.debian.org (full text, mbox, reply):

From: David Prévot <taffit@debian.org>

To: Roger Leigh <rleigh@codelibre.net>

Cc: 588962@bugs.debian.org, Thomas Blein <tblein@tblein.eu>, po4a-devel@lists.alioth.debian.org, debian-i18n@lists.debian.org

Subject: Re: [buildd-tools-devel] Bug#588962: po4a using both builddir and srcdir

Date: Tue, 15 May 2012 16:03:19 -0400

[Message part 1 (text/plain, inline)]

Le 15/05/2012 15:33, Roger Leigh a écrit :
> On Tue, May 15, 2012 at 12:46:08PM -0400, David Prévot wrote:

>> Indeed, simply running “po4a --destdir=../debian/build/man/ po4a.cfg”
>> from the man directory builds everything where expected (even with
>> “--srcdir=.”), but when run from the root directory, it builds them in
>> both the --srcdir and the --destdir, so it may be a bug in po4a. As a
>> workaround, you could remove the sloppy man/translated directory in the
>> update-po rule, after the po4a call.
> 
> We can do this as a workaround for now.
[…]
> In general though, it breaks building from a read-only source tree
> of building several diffrent builds from a common source tree, so
> I would hope to be able to fix it.

I thought about a bit less ugly workaround: “cd man && po4a $stuff”
since this issue is not triggered if po4a is run with --srcdir=. (or
implied).

Another workaround could be to rewrite man/po4a.cfg to document the
files path from the root directory (attached, but I haven't tested it:
it may need extra care about $(builddir) in the Makefile call since it
should now point the debian/build/ directory instead of
debian/build/man/). I also took the liberty to simplify the addenda
handling (they should now be added as man/addenda/$lang.add, Thomas
should be able to provide one for his translation (and I will be happy
to help if needed).

Regards

David

[po4a.cfg (text/plain, attachment)]

[signature.asc (application/pgp-signature, attachment)]

Message #117 received at 588962-close@bugs.debian.org (full text, mbox, reply):

From: Roger Leigh <rleigh@debian.org>

To: 588962-close@bugs.debian.org

Subject: Bug#588962: fixed in schroot 1.5.2-1

Date: Tue, 15 May 2012 22:37:15 +0000

Source: schroot
Source-Version: 1.5.2-1

We believe that the bug you reported is fixed in the latest version of
schroot, which is due to be installed in the Debian FTP archive:

dchroot-dsa_1.5.2-1_amd64.deb
  to main/s/schroot/dchroot-dsa_1.5.2-1_amd64.deb
dchroot_1.5.2-1_amd64.deb
  to main/s/schroot/dchroot_1.5.2-1_amd64.deb
libsbuild-dev_1.5.2-1_amd64.deb
  to main/s/schroot/libsbuild-dev_1.5.2-1_amd64.deb
libsbuild-doc_1.5.2-1_all.deb
  to main/s/schroot/libsbuild-doc_1.5.2-1_all.deb
schroot-common_1.5.2-1_all.deb
  to main/s/schroot/schroot-common_1.5.2-1_all.deb
schroot-dbg_1.5.2-1_amd64.deb
  to main/s/schroot/schroot-dbg_1.5.2-1_amd64.deb
schroot_1.5.2-1.debian.tar.gz
  to main/s/schroot/schroot_1.5.2-1.debian.tar.gz
schroot_1.5.2-1.dsc
  to main/s/schroot/schroot_1.5.2-1.dsc
schroot_1.5.2-1_amd64.deb
  to main/s/schroot/schroot_1.5.2-1_amd64.deb
schroot_1.5.2.orig.tar.xz
  to main/s/schroot/schroot_1.5.2.orig.tar.xz



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 588962@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Roger Leigh <rleigh@debian.org> (supplier of updated schroot 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 ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Mon, 14 May 2012 23:29:22 +0100
Source: schroot
Binary: schroot-common libsbuild-dev schroot-dbg libsbuild-doc schroot dchroot dchroot-dsa
Architecture: source all amd64
Version: 1.5.2-1
Distribution: experimental
Urgency: low
Maintainer: Debian buildd-tools Developers <buildd-tools-devel@lists.alioth.debian.org>
Changed-By: Roger Leigh <rleigh@debian.org>
Description: 
 dchroot    - Execute commands in a chroot environment
 dchroot-dsa - Execute commands in a chroot environment
 libsbuild-dev - development files for the Debian source builder
 libsbuild-doc - development documentation for the Debian source builder
 schroot    - Execute commands in a chroot environment
 schroot-common - common files for schroot
 schroot-dbg - schroot, dchroot and dchroot-dsa debugging symbols
Closes: 477937 588962 625202 625205 648450 653732 658544 659524 659967 660040 661514 666274 666497 670881 672113
Changes: 
 schroot (1.5.2-1) experimental; urgency=low
 .
   * New upstream development release.
   * Build with current Boost libraries (1.49).
   * debian/control:
     - Fix typo (debuggging, Closes: #653732).  Thanks to Vincent Blut.
     - Build-Depend on debhelper 9, and po4a 0.40.
     - Upgrade to Standards-Version 3.9.3.
   * schroot preinst: Remove default (script-config) conffiles on
     upgrade.  These are deprecated and support will be dropped in
     the future.
   * /etc/default/schroot supports ending sessions on stop
     (Closes: #625202).  The existing SESSIONS_RECOVER option has been
     renamed to START_ACTION, and an additional STOP_ACTION option has
     been added.  Both of these may be set to "end" to cause all
     sessions to be ended when run with a "start" or "stop" argument,
     respectively.
   * Support translation of the documentation with po4a
     (Closes: #588962).  A French translation of the manual pages has
     been added, and translated manual pages are built, but is not yet
     installed.  Thanks to David Prévot.
   * Support for overlayfs has been added in addition to aufs and
     unionfs (Closes: #648450).  Thanks to Evan Broder.
   * Arbitrary options may now be set in a chroot definition in
     schroot.conf.  These options are also set in the environment when
     running setup scripts, making this a simple means by which setup
     scripts may be customised without writing code.  As part of this
     change, the error message for invalid keys has been reworded to
     make it more helpful (Closes: #666274).
   * The gshadow database is now copied into the chroot using the
     nssdatabases setup script, rather than copyfiles.
   * Services may be started and stopped inside the chroot on session
     creation and session ending (Closes: #625205).  These are specified
     using the new setup.services key, and are started and stopped using
     invoke-rc.d.  See schroot.conf(5) for further details.
   * 15killprocs kills processes under CHROOT_PATH rather than
     CHROOT_MOUNT_LOCATION (Closes: #672113).  Thanks to Julien Viard de
     Galbert.
   * The above options may be set (where permitted) on the schroot
     command-line by using the new --option command-line option to set
     the option to a user-defined value, which will permit users to
     customise the behaviour of setup scripts.  Note that only keys
     specified in the new user-modifiable-keys or root-modifiable-keys
     settings are permitted to be set, for security reasons.
   * A new "custom" chroot type has been added (Closes: #477937).  This
     permits the testing and development of new specialised chroot
     types without the need to write any C++ chroot modules.  It just
     requires a custom setup script, which can use arbitrary options
     set in your schroot.conf for configuration.  Options are provided
     to set up the session cloning and purging behaviour for the custom
     chroot.  See schroot.conf(5) for further details.
   * Exceptions thrown for command-line options validation errors no
     longer use the Boost validation_error exception, which formatted
     the exception reason text badly (Closes: #666497).
   * schroot(1): Update overview text, including explaining the
     restriction of the plain chroot type not running setup scripts
     (Closes: #670881).
   * PATH is now set when running setup scripts.
   * Updated translations:
     - da (Closes: #658544).  Thanks to Joe Hansen.
     - de (Closes: #659524).  Thanks to Holger Wansing.
     - fr (Closes: #661514).  Thanks to Thomas Blein.
     - pt (Closes: #660040).  Thanks to Pedro Ribeiro.
     - zh_CN (Closes: #659967).  Thanks to Ji ZhengYu.
Checksums-Sha1: 
 46d95ae57ef81ae04d2bb942011a034791913c4e 2424 schroot_1.5.2-1.dsc
 40377167864c508901882951a1c18ad65cbf744a 718344 schroot_1.5.2.orig.tar.xz
 9eaf97eac6c0635ea18a37224b3e86255107b5c5 26764 schroot_1.5.2-1.debian.tar.gz
 ea69f4484ca60bf980e71fc4fb4fc5c59f9610a6 252632 schroot-common_1.5.2-1_all.deb
 b39961b61ce9d66f7263f622c882ed448b5e4dcc 2289162 libsbuild-dev_1.5.2-1_amd64.deb
 b507d22255106284de74fcf04fd5eefc083180de 29677682 schroot-dbg_1.5.2-1_amd64.deb
 0bbfcaa044a879c89a0f2a59e9914380c30b8eb6 7763476 libsbuild-doc_1.5.2-1_all.deb
 4f055759337a3fd59358c1c03bfb50bcbaba028d 953368 schroot_1.5.2-1_amd64.deb
 1ad84ef5033632d2ac6d3b6719bd6531811390db 370280 dchroot_1.5.2-1_amd64.deb
 ebaace85d3790af293b5bad0f216099a02650a14 369528 dchroot-dsa_1.5.2-1_amd64.deb
Checksums-Sha256: 
 985e7a881b2a3e8b6060418c7b1a5601180986d1a7a0cab4dc2ac325622d8672 2424 schroot_1.5.2-1.dsc
 14ea4c1fcd13fbccc4ac287d33e70ef26a804d85b803b60ee9d75a8f2c8eb9fc 718344 schroot_1.5.2.orig.tar.xz
 70bc839e0671412f741d3cbf6a7553102464b0267e00bc744a4fcce24ce7f054 26764 schroot_1.5.2-1.debian.tar.gz
 6d8610683e68a1df86c3b34cc563c832c8bae2c8cbaee3ab94c9032e61bc723f 252632 schroot-common_1.5.2-1_all.deb
 ab4a95e673ee7a40b690d41cf78af152c2512a828fa5792acbb69b60876da779 2289162 libsbuild-dev_1.5.2-1_amd64.deb
 5f9336e5b57b068be3c9402710dc4214dca940a547b0a860e66e38c43afa6a3a 29677682 schroot-dbg_1.5.2-1_amd64.deb
 c01b9db96f89bf82ad216f24fad5bb006fa5069ad9bc983d6d14c35ae41125b8 7763476 libsbuild-doc_1.5.2-1_all.deb
 06f8da78707c2296ee7c6e6df901f514155261d4747de74007faa8a5e351f9e5 953368 schroot_1.5.2-1_amd64.deb
 cadf5c34c73eb39f834decc5f810bb7b4f82a929ffb9ca656a10019e46b291ca 370280 dchroot_1.5.2-1_amd64.deb
 65edb882f2439af91bed0f558c8680ecc0160d1dacf0e3903c2b35a09f255897 369528 dchroot-dsa_1.5.2-1_amd64.deb
Files: 
 b6a925b56f5088359e2656a98cae4d0c 2424 admin optional schroot_1.5.2-1.dsc
 7504d34970697b951896a4e36bb07bd3 718344 admin optional schroot_1.5.2.orig.tar.xz
 92721f1e16d859c2373217a444d64f5d 26764 admin optional schroot_1.5.2-1.debian.tar.gz
 4b568fe66dec35daca987dbaf8396e2a 252632 admin optional schroot-common_1.5.2-1_all.deb
 1655225f16ac6632e0d04827b06c2173 2289162 libdevel optional libsbuild-dev_1.5.2-1_amd64.deb
 48188da135046620adea7a2b6e88caee 29677682 debug extra schroot-dbg_1.5.2-1_amd64.deb
 ff44d0b8eacc08ad16ec99b1f2e10f83 7763476 doc optional libsbuild-doc_1.5.2-1_all.deb
 980c18a88ff2a6d2d0cbb29b2fea87f7 953368 admin optional schroot_1.5.2-1_amd64.deb
 5d615c646ece726b00c420e72b9b1be4 370280 admin optional dchroot_1.5.2-1_amd64.deb
 1fc394e3a7065f9661eefde1f0db6178 369528 admin optional dchroot-dsa_1.5.2-1_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCgAGBQJPstEUAAoJEOJSSsUKn1xZwBIQALGJpz3JiKJK2xe2zAO9d5OT
PFdr3OzbjmFFVGnZHHde/0KohZ9OdAlMDUNr5CiDT73CcMkUOwSJJkSIhFsAUi5M
1awCYcsejTAUxSyKXimqDPdvI+e2jkWZ5xwaQX5fmCJ8fwN6pFyNizE83TepdiOU
jV0o6kJKKbXYtQCRGufxQPuxQAMWn8r4zdGLnLX8sucvznnFQoH33OhhJwhdaDj5
u3tJATFGvpcgoJ4G6OXHpeEc6t/S14Pm8XybFV03uFjQy/8WVSPLG5zYjvTnm2qx
5TZpUyIo9BMCzJgil1ZSa2Kw86nt/wwwmTa+ARDPokZIkHhh9hld9ma8P5EKkyqh
aNfPejbHm4xZ8s0zEWKjwK+Y+A5Dqdhf7oM7nMjewfgdrGSpPiVXuAbF2xImjt/T
iOzqoz+qRQ/PHLmPLfEZd1o3R84hN1kwPP9m0v8alUs8lAZahXHgpYIK0zrMMj2C
QjCcRLY3tU5Qbmh+XH5znSrdaRrnzOLggnT0Zl3/OXuZ0BYW/yEELvkb3fwC9dqO
6DrJu0kbcmU7QJudAQZs/nFXPrPGOmZLRHlo/nOl72k9Pvy/wvHVm4nQU2W3+YlE
BCiuc6M6u6CGChlmlIh9DSWCBLhyQsxnUxZ122ozROxgIEJiTzd1FbWKaFMwHDS5
ef8AeAx73TI91bVK4rpG
=r2bS
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.