Export branch should have real bzr branch attached
Bug #409686 reported by
Jeroen T. Vermeulen
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Medium
|
Jeroen T. Vermeulen | ||
Bug Description
For a branch to be set as a translations export branch, we should require that it have actual bzr data attached. Otherwise the export just fails with "Not a branch: ..."
We can enforce this by making the vocabulary for candidate branches also check for the flag that gets set when a branch has been scanned and published to the read-only area.
Related branches
lp:~jtv/launchpad/bug-409686
- Abel Deuring (community): Approve (code)
-
Diff: 356 lines (+205/-15)4 files modifiedlib/lp/translations/doc/translations-export-to-branch.txt (+57/-8)
lib/lp/translations/emailtemplates/unpushed-branch.txt (+38/-0)
lib/lp/translations/scripts/tests/test_translations_to_branch.py (+68/-4)
lib/lp/translations/scripts/translations_to_branch.py (+42/-3)
| Changed in rosetta: | |
| status: | Triaged → In Progress |
| milestone: | none → 10.05 |
| assignee: | nobody → Jeroen T. Vermeulen (jtv) |
| Changed in rosetta: | |
| milestone: | 10.05 → 10.06 |
Revision history for this message
| Ursula Junque (ursinha) wrote Bug fixed by a commit | #1 |
| Changed in rosetta: | |
| milestone: | 10.06 → 10.05 |
| status: | In Progress → Fix Committed |
| tags: | added: qa-needstesting |
| Changed in rosetta: | |
| milestone: | 10.05 → 10.06 |
| tags: |
added: qa-ok removed: qa-needstesting |
| Changed in rosetta: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fixed in stable r10941 <http://