Import: Translation for POTMsgSet matches 2 existing translations

Bug #666660 reported by Jeroen T. Vermeulen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Henning Eggers

Bug Description

We got a few oopses from the import script on 2010-10-20 and 2010-10-22:

Translation for POTMsgSet <id> into '<language code>' matches 2 existing translations.

Unfortunately these show up as "None: None" in the oops logs, and are associated with bug 54005.

        OOPS-1754POI1, OOPS-1754POI2
        OOPS-1756POI1, OOPS-1756POI2, OOPS-1756POI3, OOPS-1756POI4, OOPS-1756POI5

Related branches

Changed in rosetta:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Henning Eggers (henninge) wrote :

These messages are not errors because the code still deals with the situation gracefully. Lowering the logging priority from "WARN" to "INFO" will prevent OOOPSes from being generated.

Changed in rosetta:
assignee: nobody → Henning Eggers (henninge)
milestone: none → 10.11
status: Triaged → In Progress
Revision history for this message
Launchpad QA Bot (lpqabot) wrote : Bug fixed by a commit
tags: added: qa-needstesting
Changed in rosetta:
status: In Progress → Fix Committed
tags: added: qa-untestable
removed: qa-needstesting
Changed in rosetta:
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.