Diverged translation cannot be converged again.
Bug #716586 reported by
Henning Eggers
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Aaron Bentley |
Bug Description
This seems to be a regression introduced by the upstream-
On a related note, it is possible to select an upstream translation (I tried this locally on a source package) and submit the form after which the current translation will be a *diverged copy* of the upstream translation ... (shudder). I am not sure if this is the same bug or a different one. Or is this even intentional?
Related branches
lp:~abentley/launchpad/fix-undiverging
- Jeroen T. Vermeulen (community): Approve (code)
-
Diff: 41 lines (+17/-3)2 files modifiedlib/lp/translations/model/potmsgset.py (+3/-3)
lib/lp/translations/tests/test_potmsgset.py (+14/-0)
Changed in launchpad: | |
status: | New → Triaged |
importance: | Undecided → High |
tags: |
added: qa-ok removed: qa-needstesting |
Changed in launchpad: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
About that "related note": if the current Ubuntu-side translation is diverged, then it's correct for the new translation to be a diverged Ubuntu-side copy of the upstream translation. If the current Ubuntu-side translation is shared, then the new translation should be shared also.