Could you review the import queue of Scilab ?

Asked by Sylvestre Ledru


I uploaded about two weeks ago some localization files:
Could you review them ?

By the way, I have two minor questions:
* how can I connect rosetta on a branch (I imported Scilab source tree on lp) ?
* Can I have an exception on my lp account to bypass the review process ? (I am upstream on Scilab and I am familiar with lp & gettext)


Question information

English Edit question
Launchpad itself Edit question
No assignee Edit question
Solved by:
Henning Eggers
Last query:
Last reply:
Revision history for this message
Henning Eggers (henninge) said :

I am sorry about the delay, I got a bit behind on reviewing the import queue.

Your current imports were not automatically approved because the path of the file changed and the auto-approval script does not assume too much here. Updating all the paths is quite some work that we'd like to avoid, though. ;-)

You could do it yourself since the last release of Launchpad added this capability for project maintainers, for example here:

But I would suggest a different solution. You already asked about importing translations from your project's bazaar branch. That actually is the best solution becuase that feature is smarter about matching file paths to templates as long as the file name stays the same, which is the case with your templates. They will be added to the queue as approved entries, to be imported straight away.
Read all about it here:
Your settings page is this:

Unfortunately the last imports of your branch failed. Please have a look at it to find out what went wrong or file a request for the code team to check on it.

If you decide to go that way, please set the existing queue entries to "Deleted".

There is no way to add an exception to your account to be able to bypass review. But you can avoid review by importing your translations from a bazaar branch and by being consistent about template and po file naming.


Revision history for this message
Sylvestre Ledru (sylvestre) said :

For now, could you review the waiting localization files ?

I will try with the import of the branch later: I haven't been able to set a specific git branch and the fail on the import is problematic.


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

Sorry, I think I wasn't clear here. :-/

There are 61 files to approve, that is quite some work that I don't really want to do because you can do it yourself ;-)

Update the path on each of these 61 templates to be the same as the file you want to import and the automatic approval script will approve them for you. You can reach the "Edit" page for each template easily from here:
For you to be able to edit this is a new feature, so this option was not available previously.


Revision history for this message
Sylvestre Ledru (sylvestre) said :

OK, thanks but my problem here is that I would like to sync launchpad against the branch 5.2 and not master ... :/

Revision history for this message
Sylvestre Ledru (sylvestre) said :

Thanks for the permission by the way. I updated path to all localization files.

Revision history for this message
Данило Шеган (danilo) said :

Sylvestre, to achieve that, Launchpad should have the appropriate structure for scilab project. "Branch" in Launchpad-speak is a "(project) series" (which can have an actual code branch, translations, targetted bugs, etc), and you get "trunk" by default when creating a project. You can create a 5.2 series as well, set up a branch for it, and set it up for translations import. Translations will be shared between "trunk" and 5.2 automatically, so no duplication of work will be needed.

Of course, before you can do that, you need to make sure branch is imported correctly. Please do as Henning suggested and ask about that on (I can make sure they look at this question, but it'll be hard to make sure they keep the communication going so it's best if you do it).

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

Also, the current import (approval) has not succeeded yet because the paths still don't match - the templates are at "scilab/modules" whereas the import queue entries start at "modules". You'll have to remove the "scilab/" from the templates, I am afraid, for the auto-approver to accept them.