For bugs that result from SeaMonkey build problems. ("Building" is the process of converting the thousands of Mozilla source code files into a actual executable software.) If a file in a newly-downloaded build is missing or corrupted, file the bug in this component.
Examples of appropriate bugs: Build date in browser window is incorrect; DLL files are missing from the ZIP file; or Build contains a zero K executable.

It's definitely a bug that langpacks end up with that, they should end up with e.g. "2.30.*" in this case.
That said, if you have an online connection and that version of the langpack is up on AMO, I thought that we'd request the compat data from AMO where the correct data is set and then things should work fine.

This is a patch that special-cases SeaMonkey to give it an appropriate maxVersion, as it uses a version scheme where the second number changes for every Gecko version but the first doesn't.
I have tested this with current SeaMonkey beta by enabling debugQA, which also uses this maxVersion definition (language repack is a bit hard, and pre-beta versions do not use this .* thing at all).
Mike, you reviewed bug 940973, which caused this issue, so I hope you are the peer with best knowledge of this code.

Comment on attachment 8587116[details][diff][review]
patch v2: special-case seamonkey maxVersion
tl;dr: This patch will only take actual effect once in beta and doesn't affect Firefox at all, it only adds a special case for SeaMonkey.
Approval Request Comment
[Feature/regressing bug #]: bug 940973
[User impact if declined]: no impact for Firefox in either direction; if we don't take this, official SeaMonkey langpacks continue to break the whole application after a SeaMonkey update is installed, and for uploading to AMO, langpacks need to be repacked to fix this.
[Describe test coverage new/current, TreeHerder]: Has passed tests fine on inbound, but this patch really only takes effect on beta/release. I did local SeaMonkey testing for beta.
[Risks and why]: There shouldn't be any risk for Firefox, as the new rule only gets invoked for SeaMonkey.
[String/UUID change made/needed]: -

Comment on attachment 8587116[details][diff][review]
patch v2: special-case seamonkey maxVersion
Taking as the risk should be minimal for Firefox (especially in the configure), early in the cycle and we want to help our Seamonkey friends.