On Tue, 12 Mar 2013 14:33:21 +0100, Honza Horak wrote:
On 03/12/2013 02:03 PM, Norvald H. Ryeng wrote:
On Mon, 11 Mar 2013 19:00:29 +0100, Honza Horak
wrote:
if I understand it correctly that the problem is caused by conflicting
library names, then it should be solved today (the enhanced pa
On 03/12/2013 02:03 PM, Norvald H. Ryeng wrote:
On Mon, 11 Mar 2013 19:00:29 +0100, Honza Horak wrote:
if I understand it correctly that the problem is caused by conflicting
library names, then it should be solved today (the enhanced package is
already building).
Why not have non-conflicting
On Mon, 11 Mar 2013 19:00:29 +0100, Honza Horak wrote:
On 03/11/2013 06:55 PM, Sérgio Basto wrote:
Hi ,
On Qua, 2013-03-06 at 09:25 -0600, Richard Shaw wrote:
" Looks like mariadb has hit rawhide now and I can't build mythtv.
I've added conditionals for the direct mysql Requires and BR's but
On 03/11/2013 06:55 PM, Sérgio Basto wrote:
Hi ,
On Qua, 2013-03-06 at 09:25 -0600, Richard Shaw wrote:
" Looks like mariadb has hit rawhide now and I can't build mythtv.
I've added conditionals for the direct mysql Requires and BR's but
until some of the dependent packages are fixed, MySQL-pyth
Hi ,
On Qua, 2013-03-06 at 09:25 -0600, Richard Shaw wrote:
" Looks like mariadb has hit rawhide now and I can't build mythtv.
I've added conditionals for the direct mysql Requires and BR's but
until some of the dependent packages are fixed, MySQL-python,
qt4-mysql, etc. "
How (and when) we fix