[packages/mysql] - don't mark db error messages files with lang as these depend on db client settings and not db serv

Jakub Bogusz qboosh at pld-linux.org
Thu Jul 7 07:13:52 CEST 2016

On Wed, Jul 06, 2016 at 04:05:35PM +0200, Arkadiusz Miśkiewicz wrote:
> On Wednesday 06 of July 2016, Elan Ruusamäe wrote:
> > vote: no
> > 
> > %lang has always been used in system way you want locale/localization
> > stuff installed
> mysql is kind of special that doesn't fit well into typical %lang rules.
> mysql server settings are not the ones that decide which error messages to 
> use.
> It's remote clients who decide on error messages. What's worse - if client 
> wants some "locale" it won't silently switch to english. It will return error 
> instead.
> These missing files break phpmyadmin functionality for switching languages.
> 15:54:48 mysql{2}> SET lc_messages = 'ru_RU';
> ERROR 1231 (42000): Variable 'lc_messages' can't be set to the value of 
> 'ru_RU'
> Warning (Code 1105): Can't process error message file for locale 'ru_RU'
> Error (Code 1231): Variable 'lc_messages' can't be set to the value of 'ru_RU'

Is this the same behaviour that when trying to set locale not supported
at all (i.e. not included with mysql)?

Setting %_install_langs means that system will support messages/documentation
only in specified languages - so (if the answer for first question is
"yes") - it would be consistent.

Jakub Bogusz    http://qboosh.pl/

More information about the pld-devel-en mailing list