This is the latest failure du jour, happening for wordpress-1.5/ja.mo:
http://librarian.launchpad.net/565008/565041/3M9Tgl1we2eJBPuJsDOsdjjMviG.txt
Traceback (most recent call last):
File "/srv/launchpad.net/production/launchpad/cronscripts/../lib/canonical/launchpad/scripts/po_export_queue.py", line 240, in process_single_object_request
url = handler.get_librarian_url()
File "/srv/launchpad.net/production/launchpad/cronscripts/../lib/canonical/launchpad/scripts/po_export_queue.py", line 109, in get_librarian_url
mo_contents = self.get_contents()
File "/srv/launchpad.net/production/launchpad/cronscripts/../lib/canonical/launchpad/scripts/po_export_queue.py", line 99, in get_contents
return compiler.compile(po_contents)
File "/srv/launchpad.net/production/launchpad/cronscripts/../lib/canonical/launchpad/components/poexport.py", line 567, in compile
raise MOCompilationError("PO file compilation failed:\n" + stdout)
MOCompilationError: PO file compilation failed:
<stdin>:4692:13: parse error
/usr/bin/msgfmt: found 1 fatal error
In order to debug this, we need to have a copy of the PO file we were trying to compile into a MO file. I'll try and export the PO file myself and see if I can reproduce the problem.
Steve has suggested that we use OOPS files for cronscripts, and that for this particular operation, the PO file that was being compiled could be somehow included with the OOPS.