ubuntu-translations-coordinators team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

Steve Langasek [2013-05-17 14:45 -0000]:
> Regenerating the .pot file at package build time changes timestamps,
> which means the .mo files shipped in the package are not identical
> across architectures.

I don't understand this. This would only happen if the package updates
its *.po files during package build, which is evil and unnecessary.
But build systems which do that would already create different *.mo
files on each build, so whether or not you update the *.pot as well
should make little difference.

In the ordinary case, the build sytem just builds *.mo from the source
*.po files, and completely ignores the *.pot. Most binary packages get
their *.mo files stripped out anyway, and for the remaining ones we
just need to make sure that we don't put *.mo files into arch specific
packages (either packages are arch:all anyway, or we put translations
into an arch:all -common binary, which is quite common for GNOME
packages).

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/978724

Title:
  pkgbinarymangler should build a tarball for pot import even when
  translations are not stripped

Status in Ubuntu Translations:
  Triaged
Status in “pkgbinarymangler” package in Ubuntu:
  Triaged

Bug description:
  Currently, the translation template is not being built, so the new
  strings are not being picked up by LP Translations.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/978724/+subscriptions