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