Thanks, William, that seems to move this issue forward quite a bit. As regards the latest example I posted about (comment #17), the build for s390x created a snappy.pot with precisely 452 strings. Apparently that one was the latest to be imported to LP.
https://launchpad.net/ubuntu/bionic/+upload/18265691/+files/snapd_2.32.9+18.04_s390x_translations.tar.gz So something needs to be done on the snapd side about it. Is there a reasonable explanation why not all the strings are extracted during the builds for all architectures? When monitoring this issue, I've consequently looked at the tarballs built for amd64, and they seem to be more reliable. So a possible workaround might be to only run the update-pot script when building for amd64. LP only needs one template, after all. ** Changed in: snapd (Ubuntu) Milestone: ubuntu-18.04 => None -- 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/1758684 Title: LP only imported a fraction of the snappy translation template Status in Launchpad itself: Invalid Status in Ubuntu Translations: In Progress Status in snapd package in Ubuntu: Confirmed Bug description: Now when bug #1747272 finally has been fixed, I have noticed a snappy import issue. Below I have attached the version of snappy.pot which was created during the snapd build on 2018-03-24 and stripped. Next attachment is the version of snappy.pot which was actually imported to bionic. The latter includes 37 strings instead of 398... To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1758684/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-translations-coordinators Post to : ubuntu-translations-coordinators@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators More help : https://help.launchpad.net/ListHelp
