[Bug 788685] Re: Enable translating selected Ubuntu universe packages in Launchpad

David Planella david.planella at ubuntu.com
Mon Sep 10 09:31:03 UTC 2012

There is still a bit that needs fixing: see bug 1048556 as a follow-up

You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to pkgbinarymangler in Ubuntu.

  Enable translating selected Ubuntu universe packages in Launchpad

Status in Launchpad itself:
  Fix Released
Status in OEM Priority Project:
Status in Ubuntu Translations:
  Fix Released
Status in “pkgbinarymangler” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: pkgbinarymangler

  Following a conversation at UDS and subsequent follow-ups with the OEM
  group, I'd like to request the possibility to enable the translation
  of selected universe packages in Launchpad.

  That would require:
  * Changes in pkgbinarymangler to create a whitelisting system to be able to selectively build
  * Changes in Launchpad to stop ignoring translation imports coming from universe packages and start importing any translation tarball that pkgbinarymangler provides.

  Note that for source packages with upstream translations sharing
  enabled in Launchpad, this might not be even necessary (is there any
  check to ignore sharing if the Ubuntu source package comes from
  universe?), but it will be to import translations for packages not
  supported by upstream imports sharing (i.e. any project not based on

  Background notes

  (from conversations with pitti and danilo)

  In order to import universe translations and ship them in language packs we need:
  * A trivial patch to pkgbinarymangler and get its tests updated. Estimated time 15 m.
  * A small patch in Launchpad to stop ignoring universe translation tarball uploads.
  * Research on how the amount of universe translations compare with those from main. Results:
    - We ship a total of ~1.25 GB (1252512038 bytes) of translation data as the sum of all language packs
    - We ship a total of ~0.85 GB (845977204 bytes) of translation data as the sum of all universe packages
    - This means universe translations have roughly 70% of the size of the translations we ship in language packs
  * A decision from the research action above on whether to ship separate language packs or not
  * If we decide to ship separate universe language packs, a (not too hard) modification to langpack-o-matic to generate them.

  Other notes:
  * IIRC, from the previous UDS discussion in Brussels, we'd only want to enable this for selected universe packages, those which are well maintained, since this would introduce a delta with those packages coming from debian (the delta being the .pot building rules).
  * The discussion at UDS-O was not about mass-enabling universe translations, but rather the context was about enabling them for some packages in which we'd want to have more flexibility with translations and be able to ship updates in language packs without requiring a main inclusion request for the package. An example is the nanny package, which OEM distributes in their images.
  * So as we're not talking about enabling all universe, a start would be to add a way to whitelist selected universe packages and decide to ship them in the regular language packs


   * pkgbinarymangler: Stop building translation tarballs for universe packages, i. e. for packages which it does not strip.
   * pkgbinarymangler: Check "XS-Ubuntu-Use-Langpack: yes" header in debian/control. If present, force stripping/translation tarball building. This can be used for particular universe packages. That way, we don't need a static whitelist in pkgbinarymangler, and it will also work for PPAs, etc.
   * Launchpad: Stop ignoring universe translation tarballs.

To manage notifications about this bug go to:

More information about the foundations-bugs mailing list