Import: Translation for POTMsgSet matches 2 existing translations
Bug #666660 reported by
Jeroen T. Vermeulen
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
lp:~henninge/launchpad/devel-bug-666660-poimport-oops
- Jonathan Lange (community): Approve
- Steve Kowalik (community): Approve (code*)
- Launchpad code reviewers: Pending (code) requested
-
Diff: 25 lines (+1/-3)2 files modifiedlib/lp/translations/doc/potmsgset.txt (+0/-2)
lib/lp/translations/model/potmsgset.py (+1/-1)
Changed in rosetta: | |
status: | New → Triaged |
importance: | Undecided → High |
tags: |
added: qa-untestable removed: qa-needstesting |
Changed in rosetta: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
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.