TransationMessage.pofile: not set on edge, still used on production
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Critical
|
Jeroen T. Vermeulen |
Bug Description
Edge now creates TranslationMessages without their pofile set, and knows how to deal with those. But production still has the old code that relies on TranslationMess
OOPS-1709C1437, OOPS-1709E1482, OOPS-1709E1483, OOPS-1709F1512, OOPS-1709H1502
OOPS-1709C1572, OOPS-1709C1647, OOPS-1709C1680, OOPS-1709D1231, OOPS-1709D1649
OOPS-1709E1807, OOPS-1709F1107, OOPS-1709F1484, OOPS-1709K1086, OOPS-1709K1655
OOPS-1709C1431, OOPS-1709D1453, OOPS-1709K1427, OOPS-1709L1202, OOPS-1709N1317
OOPS-1709D1101, OOPS-1709E1075, OOPS-1709H1061
This is a temporary problem, caused by the edge (beta) server and the main production server having different ideas about what these entries in the database should look like. It will disappear with the 10.09 rollout.
Related branches
- Tim Penhey (community): Approve (release-critical)
- Michael Hudson-Doyle: Approve
- Launchpad code reviewers: Pending (code) requested
-
Diff: 50 lines (+20/-0)2 files modifiedlib/lp/translations/model/potmsgset.py (+2/-0)
lib/lp/translations/tests/test_translationmessage.py (+18/-0)
Changed in rosetta: | |
status: | Triaged → In Progress |
Changed in rosetta: | |
assignee: | nobody → Jeroen T. Vermeulen (jtv) |
See bug 597539 for the change that causes this. We've seen no oopses on edge, so it looks as if the code is good otherwise.