Ubuntu upstream translation imports overwrite Ubuntu translations

Bug #710591 reported by Jeroen T. Vermeulen on 2011-01-31
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Critical
Henning Eggers

Bug Description

Ubuntu's upstream translation imports (from Soyuz package builds) are overwriting Ubuntu's own translations.

The design of the Recife translations model change called for the upstream translations of Ubuntu packages (as uploaded by Soyuz) to be imported as upstream translations. Since these translations are still uploaded to the Ubuntu packages, not upstream productseries, they will need special treatment: the "by_maintainer" flag on the upload should cause them to be made current from the upstream perspective, even though they happen on ubuntu templates¹. The Ubuntu translations should track those translations only when appropriate as per the sharing policy².

We never got around to doing this. As a result, the upstream translations that Soyuz uploads when it builds a package are made current from the Ubuntu perspective, not the upstream one, and effectively ignore sharing policy.


¹) At least, for packages that have no upstream productseries in Launchpad. We'd want to be careful with packages whose upstream translations do originate in Launchpad, or the "upstream" translations from the package build might revert newer ones by the upstream translators.
²) The sharing policy says that upstream updates should generally also update Ubuntu translations, but not where there is an Ubuntu translation that differs from a pre-existing upstream translation.

Related branches

David Planella (dpm) wrote :

The precedence/sharing policy for Ubuntu, explained:

https://wiki.ubuntu.com/Translations/KnowledgeBase/TranslationsPrecedence

David Planella (dpm) wrote :

Just to add more info from previous e-mail and IRC conversations, all of the active imports queue were disabled on Friday 28th Jan to minimize the impact while this is being solved.

Ubuntu translators were notified by an announcement [1].

This means no translations from Ubuntu packages are being imported right now.

[1] https://lists.ubuntu.com/archives/ubuntu-translators/2011-January/004374.html

tags: added: upstream-translations-sharing
removed: translations-sharing
Deryck Hodge (deryck) on 2011-01-31
Changed in launchpad:
status: New → Triaged
assignee: nobody → Henning Eggers (henninge)
status: Triaged → In Progress
Launchpad QA Bot (lpqabot) wrote :

Fixed in stable r12320 (http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/12320) by a commit, but not testable.

Changed in launchpad:
milestone: none → 11.02
tags: added: qa-untestable
Changed in launchpad:
status: In Progress → Fix Committed
Henning Eggers (henninge) wrote :

Sorry to get everybody excited, I don't know where the QA Bot got that idea from. The branch is not linked to this bug and the commit message does not mention it either.

Changed in launchpad:
status: Fix Committed → In Progress
milestone: 11.02 → none
tags: removed: qa-untestable
William Grant (wgrant) on 2011-02-04
tags: added: qa-untestable
Launchpad QA Bot (lpqabot) wrote :
Changed in launchpad:
milestone: none → 11.02
Changed in launchpad:
milestone: 11.02 → 11.03
milestone: 11.03 → none
Launchpad QA Bot (lpqabot) wrote :
Changed in launchpad:
milestone: none → 11.03
tags: added: qa-needstesting
removed: qa-untestable
Changed in launchpad:
status: In Progress → Fix Committed
Fabien Tassin (fta) wrote :

I really hope it won't break the chromium translations.. again
http://ftagada.wordpress.com/2011/02/10/chromium-translations-explained-part-2b/

Henning Eggers (henninge) wrote :

It should not, this change mainly concerns imports on source packages and chromium imports are on a project.

tags: added: qa-ok
removed: qa-needstesting
William Grant (wgrant) on 2011-02-17
Changed in launchpad:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers