On Thu, Apr 12, 2012 at 06:05:29PM -0000, Gabor Kelemen wrote:
> This is where dh_translations would help. Only having a pot file in po/
> is not enough for LP Translations to import it, a new one needs to be
> generated during build.
It does *not* need to be generated during build. In fact, generating .pot
files during build is actively harmful if you have gettext domains for
multiarch libraries.
I investigated this with Sebastien Bacher on IRC; from the build log, it
appears the problem is actually that pkgbinarymangler has update-notifier
blacklisted, which means the translations tarball (containing the .pot file)
is never generated. We don't want to directly revert that because that
would cause pkgbinarymangler to *also* strip out the .mo files from the
binary packages... so a more subtle fix is required.
On Thu, Apr 12, 2012 at 06:05:29PM -0000, Gabor Kelemen wrote:
> This is where dh_translations would help. Only having a pot file in po/
> is not enough for LP Translations to import it, a new one needs to be
> generated during build.
It does *not* need to be generated during build. In fact, generating .pot
files during build is actively harmful if you have gettext domains for
multiarch libraries.
I investigated this with Sebastien Bacher on IRC; from the build log, it
appears the problem is actually that pkgbinarymangler has update-notifier
blacklisted, which means the translations tarball (containing the .pot file)
is never generated. We don't want to directly revert that because that
would cause pkgbinarymangler to *also* strip out the .mo files from the
binary packages... so a more subtle fix is required.
In the meantime, thanks for the manual upload.