Import from bzr branch not occurring

Have you tried renaming the pot file to avant_window_navigator.pot ?

I don't know exactly how the import script works and if it also sets the domain name for a POT file and automaticaly convers hypens to underscores.

Dashes are actually better than underscores, because template names in Launchpad can have the former but not the latter.

I don't see any reason why this shouldn't work. Import from a branch is triggered by changes to the branch. If the template was not updated since import from the branch was set up, you'll probably need to request a one-time import as well—or push a change to the branch.

A clarification about the underscores: using underscores will work, but the template name as it will be displayed in Launchpad will convert them to dashes. Templates also have domains, which can have underscores; so you end up with underscores in the filename, dashes in the template name, and one of the two in the template domain. If you use dashes from the start, we can use the same spelling throughout, which is nicer and less confusing.

I'm pretty sure that the PO template file and the PO files have been updated at least twice since the "import from the branch" configuration was set up, and I've pressed the "one-time import" button several different times.

This looks like it may be caused by a generic problem with branch import processing, where some jobs get held up for a long time. I've alerted the Code team to it.

I've linked it to a bug. As a quick workaround, we'll just poke it a bit so your import job happens, and we'll work on the proper fix, hoping to have it in the next few days.

Hi, we did some database magic now to get the job unstuck but it was not possible to restart it. Can you please request another import and tell us how it went?

https://translations.launchpad.net/awn/trunk/+request-bzr-import

Thank you for your patience.

OK, we found the bug that caused us not to notice that the uploads are failing. The fix for that will be in today's 2nd roll-out.

But we still need to find out *why* it is failing. This seems to happen for particular branches only and yours is one of currently two affected branches. With this fix in we hope to be able to find out what is going on here but please don't expect a solution before next week.

I am really sorry for this.

It doesn't seem to be fixed...I've tried to request a one-time import twice in the past week, with no change in the state of translations in that series.

It seems that I spoke too soon. My last import request finally went through.

Thanks Jeroen T. Vermeulen, that solved my question.