Translations import script on staging fails

[Henning Eggers]

The rosetta-poimport script on staging fails with the following traceback.

Traceback (most recent call last):
  File "/srv/staging.launchpad.net/staging/launchpad/lib/lp/translations/scripts/po_import.py", line 189, in main
    self._importEntry(entry)
  File "/srv/staging.launchpad.net/staging/launchpad/lib/lp/translations/scripts/po_import.py", line 134, in _importEntry
    (mail_subject, mail_body) = target.importFromQueue(entry, self.logger)
  File "/srv/staging.launchpad.net/staging/launchpad/lib/lp/translations/model/potemplate.py", line 901, in importFromQueue
    entry_to_import, logger)
  File "/srv/staging.launchpad.net/staging/launchpad/lib/lp/translations/utilities/translation_import.py", line 359, in importFile
    return file_importer.importFile()
  File "/srv/staging.launchpad.net/staging/launchpad/lib/lp/translations/utilities/translation_import.py", line 557, in importFile
    self.importMessage(message)
  File "/srv/staging.launchpad.net/staging/launchpad/lib/lp/translations/utilities/translation_import.py", line 666, in importMessage
    potmsgset = self.getOrCreatePOTMsgSet(message)
  File "/srv/staging.launchpad.net/staging/launchpad/lib/lp/translations/utilities/translation_import.py", line 416, in getOrCreatePOTMsgSet
    context=message.context))
  File "/srv/staging.launchpad.net/staging/launchpad/lib/lp/translations/model/potemplate.py", line 876, in getOrCreateSharedPOTMsgSet
    singular_text, plural_text, context, sequence=0)
  File "/srv/staging.launchpad.net/staging/launchpad/lib/lp/translations/model/potemplate.py", line 859, in createMessageSetFromText
    " primary msgid and context '%r'" % context)
AssertionError: There is already a message set for this template, file and primary msgid and context 'None'

[Launchpad QA Bot (lpqabot)]

Fixed in db-stable r10118 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/db-stable/revision/10118>.

[j.c.sackett (jcsackett)]

Marking of bug 611668 qa-ok implies this is qa-ok, as it was to fix the error making 611668 qa-bad.