Originally Posted by NullNix
You might want to treat en_* as a special case, as I get a similar warning here in en_GB, and I suspect en_AU and en_CA would see something similar.
(In general, locale foo is supposed to be used instead of foo_BLAH if foo_BLAH is active but no specific localization data is available for that locale.)
en_GB is explicitly supported (at least, it should be according to the code). But you're right, I might just tell JBPatch to accept anything "en_*", because it will resolve to the default localization anyway.