Gwibber needs to create a translation template on build
Bug #525726 reported by
David Planella
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Translations |
Fix Released
|
High
|
Unassigned | ||
gwibber (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
Binary package hint: gwibber
Gwibber needs to create a translation template during the build process, so it can be uploaded to Launchpad Translations and translators can do their work.
For more information, see:
* https:/
* https:/
* https:/
Changed in ubuntu-translations: | |
status: | New → Triaged |
importance: | Undecided → High |
tags: | added: needs-pot-on-build |
Changed in gwibber (Ubuntu): | |
importance: | Undecided → High |
tags: | added: gwibber-i18n |
To post a comment you must log in.
I've built the package locally and the template is generated just fine.
I think the problem is just that gwibber might have gotten promoted to main with a no change upload. This might mean it simply needs to be rebuilt and uploaded.
I tried to manually upload translations in the meantime, but since gwibber still has no templates, I could only try with the lp-translations -tools (https:/ /code.launchpad .net/~jtv/ lp-translations -tools/ trunk). However, when testing the upload, it seems that there is a problem when logging in to staging (OOPS on https:/ /staging. launchpad. net/+login), so I could not do it (I don't want to mess around with the production servers without having tested that on staging).
In short, I think gwibber just needs to be rebuilt and uploaded again.