Change the translations export branch

Asked by Emilien Klein

While setting up the translations for my project https://launchpad.net/issuetrackertracker, I tried to put
    lp:issuetrackertracker
as the branch to which export the .po files. However, this was not recognized, so I wanted to add
    lp:~itt-devs/issuetrackertracker/main
which is the same branch as lp:issuetrackertracker.

In order to add this branch, I put "main" in the search box. It returned one branch:
    lp:~emilien-klein/issuetrackertracker/main
which is the original development branch that I don't use anymore.

It was my mistake to not have seen that the wrong branch got returned from the search, but now the export has been done to the wrong branch. Now I am trying to change the branch, but if I enter "~itt-devs/issuetrackertracker/main" I always get an error message.

Could someone change the export branch for trunk to point to lp:issuetrackertracker, i.e. lp:~itt-devs/issuetrackertracker/main?

Thanks,
Emilien.

Edit: I originally hadn't seen the yellow edit button, doh...

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
Launchpad Translations Administrators Edit question
Solved by:
Henning Eggers
Solved:
Last query:
Last reply:
Revision history for this message
Emilien Klein (emilien-klein) said :
#1

Changed the affected project from rosetta to launchpad.

Revision history for this message
Emilien Klein (emilien-klein) said :
#2

It seems that Launchpad does only want me to add branches for which I am personally the owner, but the branch that I want to add has the developer's group as owner. I'm the administrator of this group, so I would like to be able to add this branch as the synchronization branch...

Revision history for this message
Best Henning Eggers (henninge) said :
#3

Yes, you are hitting bug 407260. Please use the workaround described there.

Henning

Revision history for this message
Emilien Klein (emilien-klein) said :
#4

As explained, I've made myself the owner of the branch, set it as synchronization branch, and set the original owning group back, and it worked. Thanks for the link to the bug, and I hope it will be corrected some day.

Revision history for this message
Emilien Klein (emilien-klein) said :
#5

Thanks Henning Eggers, that solved my question.