ubuntu-translations-coordinators team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

Steve Langasek [2013-05-24 23:18 -0000]:
> If the .pot has not changed, a .po update will be a null merge and generate
> idempotent .mo output on all builds.

That's right, but most build systems don't automatically update .po
files (and rightly so, as that's rather pointless); also,
pkgbinarymangler works after the upstream build system, so changing
the .pot won't invoke any "make" rules any more.

> But that implies having to change the library packages which *don't* use a
> -common to work around the behavior of pkgbinarymangler, which I don't think
> is what we want.

This can only potentially affect the handful of packages which are
blacklisted from stripping (dpkg, apt, debconf-i18n, update-notifier,
and some stragglers). I don't think we ever had problems with any of
them, and together with the above (.pot build happens after upstream
build) it seems to me we are fairly safe here?

-- 
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