Diverged translation cannot be converged again.

Bug #716586 reported by Henning Eggers
6
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-translation-sharing feature (aka recife). After diverging a translation to a specific series, the shared translation is displayed under it. Selecting the shared translation and submitting the form should converge (i.e. undiverge) the translation but nothing happens. Fail.

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

Deryck Hodge (deryck)
Changed in launchpad:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Jeroen T. Vermeulen (jtv) wrote :

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.

Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
Changed in launchpad:
assignee: nobody → Aaron Bentley (abentley)
milestone: none → 11.03
tags: added: qa-needstesting
Changed in launchpad:
status: Triaged → Fix Committed
tags: added: qa-ok
removed: qa-needstesting
William Grant (wgrant)
Changed in launchpad:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.