Your message dated Sun, 24 Jun 2018 19:51:48 +
with message-id
and subject line Bug#888095: fixed in mariadb-connector-c 1:3.0.3-2
has caused the Debian Bug report #888095,
regarding mariadb-connector-c: ships libmariadb3 version 3.0.3-1, which is
lower than the one in mariadb-10.[23
On Monday 18 June 2018 04:09 AM, Otto Kekäläinen wrote:
> If you want to help, please make a pull request on Salsa or even at
> upstream. I would prefer nobody forces a substandard version of
> MariaDB 10.3 into Debian because the cost of fixing it afterwards
> becomes so high.
>
I think you are
On Mon, Jun 18, 2018 at 12:39 AM, Otto Kekäläinen wrote:
> su 17. kesäk. 2018 klo 10.27 Pirate Praveen (prav...@debian.org) kirjoitti:
>>
>> On Thu, 14 Jun 2018 15:57:18 +0800 Andy Li wrote:
>> > I'm sure you have been busy, but this issue has been there unfixed for
>> > several months.
>> > I
su 17. kesäk. 2018 klo 10.27 Pirate Praveen (prav...@debian.org) kirjoitti:
>
> On Thu, 14 Jun 2018 15:57:18 +0800 Andy Li wrote:
> > I'm sure you have been busy, but this issue has been there unfixed for
> > several months.
> > I would appreciate if you can spend a few minutes to answer our
to 14. kesäk. 2018 klo 9.57 Andy Li (a...@onthewings.net) kirjoitti:
..
> I'm sure you have been busy, but this issue has been there unfixed for
> several months.
> I would appreciate if you can spend a few minutes to answer our questions.
> If you lack the time to maintain the package, would you
On Thu, 14 Jun 2018 15:57:18 +0800 Andy Li wrote:
> I'm sure you have been busy, but this issue has been there unfixed for
> several months.
> I would appreciate if you can spend a few minutes to answer our questions.
> If you lack the time to maintain the package, would you let the Debian
>
Hi Otto,
On Fri, May 11, 2018 at 9:53 AM, Andy Li wrote:
>
>
>> > On 10/05/18 20:24, Otto Kekäläinen wrote:
>> >> MariaDB 10.3 needs to be finalized and imported into Debian. After
>> >> that all the mess that are a fallout of a misfortunate upload of
>> >> mariadb-10.2 to Debian unstable will
I would like to ping again in hope that it will be fixed soon.
Best regards,
Andy
On Thu, May 10, 2018 at 8:24 PM, Otto Kekäläinen wrote:
> Hello!
>
> MariaDB 10.3 needs to be finalized and imported into Debian. After
> that all the mess that are a fallout of a misfortunate upload of
> mariadb-10.2 to Debian unstable will start to become resolved. Until
> then
On 10/05/18 21:28, Otto Kekäläinen wrote:
> 2018-05-10 21:59 GMT+03:00 Emilio Pozuelo Monfort :
>> Hi Otto,
>>
>> On 10/05/18 20:24, Otto Kekäläinen wrote:
>>> Hello!
>>>
>>> MariaDB 10.3 needs to be finalized and imported into Debian. After
>>> that all the mess that are a
> > On 10/05/18 20:24, Otto Kekäläinen wrote:
> >> MariaDB 10.3 needs to be finalized and imported into Debian. After
> >> that all the mess that are a fallout of a misfortunate upload of
> >> mariadb-10.2 to Debian unstable will start to become resolved.
>
What do you mean by finalized? Are we
2018-05-10 21:59 GMT+03:00 Emilio Pozuelo Monfort :
> Hi Otto,
>
> On 10/05/18 20:24, Otto Kekäläinen wrote:
>> Hello!
>>
>> MariaDB 10.3 needs to be finalized and imported into Debian. After
>> that all the mess that are a fallout of a misfortunate upload of
>> mariadb-10.2 to
Hi Otto,
On 10/05/18 20:24, Otto Kekäläinen wrote:
> Hello!
>
> MariaDB 10.3 needs to be finalized and imported into Debian. After
> that all the mess that are a fallout of a misfortunate upload of
> mariadb-10.2 to Debian unstable will start to become resolved. Until
> then we need to live with
Hello!
MariaDB 10.3 needs to be finalized and imported into Debian. After
that all the mess that are a fallout of a misfortunate upload of
mariadb-10.2 to Debian unstable will start to become resolved. Until
then we need to live with this, sorry.
Sorry but I would like to bring this up again.
If Otto is not available for fixing this, can anyone in the Debian MySQL
Maintainers team help?
Best regards,
Andy
Hi Otto,
On Sun, 4 Mar 2018 00:06:53 +0200 =?UTF-8?B?T3R0byBLZWvDpGzDpGluZW4=?=
wrote:
> It was not intended for the mariadb-10.x packages to ship the new LGPL
> based client library. For that we have the separate
> mariadb-connector-c package.
>
> The package mariadb-10.2 is
I'm still not sure what I can do for the neko package, which failed to be
build with errors like:
Dependency installability problem for neko on amd64:
neko build-depends on:
- libmariadb-dev-compat:amd64
libmariadb-dev-compat depends on missing:
- libmariadb-dev:amd64 (= 2.3.3-1)
>From the
It was not intended for the mariadb-10.x packages to ship the new LGPL
based client library. For that we have the separate
mariadb-connector-c package.
The package mariadb-10.2 is to be removed from Debian unstable and the
next versions of mariadb-10.3 uploaded to Debian will not include this
This has been affecting neko (https://tracker.debian.org/pkg/neko) for a
while.
Would you fix it soonish?
Best regards,
Andy
Hi!
On Tue, 2018-01-23 at 11:08:42 +0100, Emilio Pozuelo Monfort wrote:
> Source: mariadb-connector-c
> Version: 3.0.3-1
> Severity: serious
> Since 3.0.3-1, mariadb-connector-c ships libmariadb3 at version 3.0.3-1.
> However, src:mariadb-10.2 ships libmariadb3_10.2.7-1, and src:mariadb-10.3
>
Source: mariadb-connector-c
Version: 3.0.3-1
Severity: serious
Hi,
Since 3.0.3-1, mariadb-connector-c ships libmariadb3 at version 3.0.3-1.
However, src:mariadb-10.2 ships libmariadb3_10.2.7-1, and src:mariadb-10.3
(in experimental) ships libmariadb3_10.3.0-0+exp2. Since there's a package
with a
21 matches
Mail list logo