On Thursday 07 of July 2016, Jakub Bogusz wrote:
> 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
> >
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
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 messag
vote: no
%lang has always been used in system way you want locale/localization
stuff installed
On 06.07.2016 10:04, arekm wrote:
commit 1968f8231ca8d92c0b2b53579e7233e0e97cad48
Author: Arkadiusz Miśkiewicz
Date: Wed Jul 6 09:04:48 2016 +0200
- don't mark db error messages files with
On Wednesday 06 of July 2016, Arkadiusz Miśkiewicz wrote:
> Did anyone noticed that php segfaults for ssl related stuff?
>
> Previously the problem was in freeing SSL resources when there were
> multiple libs using openssl (and both tried to incorrectly free the same
> resources)
>
> Looks like t
Did anyone noticed that php segfaults for ssl related stuff?
Previously the problem was in freeing SSL resources when there were multiple
libs using openssl (and both tried to incorrectly free the same resources)
Looks like the issue is back... php5.3 is also affected. I wonder what
important
