Export to branch is not working for a fresh branch creating using LP UI

[Adi Roiban]

I create a new personal branch from the LP UI and then configured the template to synchronize to this new branch.

During setup there were no working and the branch was recognized. Still the translations are not exported.

Here is the template:
https://translations.edge.launchpad.net/ubuntu-start-page/trunk/+translations

Here is the branch
https://code.edge.launchpad.net/~adiroiban/ubuntu-start-page/trunk-l10n-export

Cheers,

[Данило Шеган (danilo)]

I talked to Aaron about this. He says branch not being there is the right thing to do. We definitely want users to populate the branch, either by branching off their main branch, or by pushing an empty branch up.

What we must do for this is to write up an email explaining this stuff when branch export fails due to branch not existing, and we can also stop people from using these branches if they have not been pushed to yet. (Aaron also tells me that as soon as activity is noticed on the branch, it's marked as being pushed to, so there's no lag between it being pushed and it being scanned)

[Jeroen T. Vermeulen (jtv)]

The email body could be something like:

You have configured automatic exports of your project's translations to a bzr branch. The exports are currently failing because the branch does not exist, probably because you have registered the branch with Launchpad but not actually created it yet.

You can fix this by creating a bzr branch locally on your system, then pushing it onto Launchpad. The exact "bzr push" command line to use will be shown on the Launchpad page for your branch. You can get there by going to the release series that you set up exports for. From there, go to the Translations settings; there you will see a link to the branch.

The reason we do not create the branch for you automatically is that you may set up different kinds of branch. If you want just the exported translation files in isolation, then you can create a completely new branch. But if you ever want to merge the translations back into another branch, then the two branches you're planning to merge must be "related." In that case, you'd have to create your translations export branch based on your existing branch.

You may find this Bazaar documentation helpful: https://help.launchpad.net/Code/UploadingABranch

More about translation exports to branches: https://help.launchpad.net/Translations/YourProject/Exports

More about Bazaar: http://doc.bazaar.canonical.com/bzr.dev/en/mini-tutorial/index.html