On Friday 05 March 2010 10:31:22 Bartosz Fabianowski wrote:
> Hi Raphael
>
> Sorry I did not reply sooner. I was away on holidays.
>
> As I am sure you noticed yourself, MySQL 5.1.44 alone does not fix the
> bug - but an appropriate fix has been developed and committed since.
>
> - Bartosz
Repl
On Monday 22 February 2010 17:28:08 Bartosz Fabianowski wrote:
> > By the way, have you contacted the MySQL port maintainer to see if this
> > patch can go into the ports tree?
>
> No. I figured MySQL AB (now Sun) would be most qualified to decide
> whether the patch introduced more problems than
On Monday 22 February 2010 22:41:57 Bartosz Fabianowski wrote:
> For reference, this is now ports/144219.
>
> - Bartosz
>From a GNATS newbie: is there a way for me to "subscribe to the report" so
that I receive further updates on it via email?
___
kde-
For reference, this is now ports/144219.
- Bartosz
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information
> By the way, have you contacted the MySQL port maintainer to see if this patch
> can go into the ports tree?
No. I figured MySQL AB (now Sun) would be most qualified to decide
whether the patch introduced more problems than it fixed. So I wanted to
see what kind of feedback the bug gets in MySQ
On Saturday 20 February 2010 14:43:50 Bartosz Fabianowski wrote:
> Heya list
>
> After installing KDE 4.4, I ran into the problem that Akonadi would not
> start. With the help of krop on #akonadi, I found the following
> explanation:
>
> A patch fixing MySQL bug 45058 was committed to MySQL 5.1.4
Heya list
After installing KDE 4.4, I ran into the problem that Akonadi would not
start. With the help of krop on #akonadi, I found the following explanation:
A patch fixing MySQL bug 45058 was committed to MySQL 5.1.43 and 5.5.1
[1]. This was meant to address a race condition but also broke char
