> … The logs are certainly full of warnings about something …
>
> And indeed, yet another bug squashed. Has been fixed and pushed. The
problem
> is that there was some odd data in the database and the failure path
didn't
> clean up the resources properly. Can you check it works now?
>
> As for how the data got that way is a separate question. But at least it
> should be more robust now. BTW, language sk had the same issue
apparently.
>
Once again: Thank you very much, Martijn!
13 old translations made it into "Recently translated", the error
message has
vanished, and accepting an old translation propagated it into the database.
Have a nice day as well
Martin
_______________________________________________
Debian-l10n-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-l10n-devel
