Your message dated Sat, 6 Jun 2009 17:45:40 +0200
with message-id <[email protected]>
and subject line Re: Bug#528549: [python-distutils-extra] build_i18n should 
only update po template if merging
has caused the Debian Bug report #528549,
regarding [python-distutils-extra] build_i18n should only update po template if 
merging
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.)


-- 
528549: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528549
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: python-distutils-extra
Version: 1.92
Severity: minor


The build_i18n command should only call intltool-update if the template is 
merged with the
existing translations afterwards (i.e. -m is specified). Otherwise this always 
creates
spurious changes in the templates, which is moderately annoying when used in 
package building.


best,

Torsten

--- System information. ---
Architecture: amd64
Kernel:       Linux 2.6.29-1-amd64

Debian Release: squeeze/sid
  500 unstable        mirror.switch.ch 
  500 unstable        emacs.orebokech.com 
  500 testing         mirror.switch.ch 
    1 experimental    mirror.switch.ch 

--- Package information. ---
Depends              (Version) | Installed
==============================-+-============
python                         | 2.5.4-3
python-central     (>= 0.6.11) | 0.6.11
intltool                       | 0.40.6-2


Package's Recommends field is empty.

Package's Suggests field is empty.







--- End Message ---
--- Begin Message ---
Hello Torsten,

Torsten Marek [2009-05-13 17:24 +0200]:
> The build_i18n command should only call intltool-update if the
> template is merged with the existing translations afterwards (i.e.
> -m is specified). Otherwise this always creates spurious changes in
> the templates, which is moderately annoying when used in package
> building.

IMHO the template should always be updated, since otherwise you can't
ascertain that it's current. You might have added a new patch which
adds/modifies strings, etc.

You shouldn't put .pot files under revision control, so I don't think
the noise outweighs the benefit of ensuring an up to date .pot file.

Since it's working as intended, I'm closing this.

Thanks for your report, and have a nice weekend!

Martin

-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to