Bug#888095: [debian-mysql] Bug#888095: Bug#888095:

[Pirate Praveen]

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 missing the main issue here, no one wants to upload a
new mariadb version. We are just asking you to add an epoch to
mariadb-connect-c NOW as it does not have to wait for mariadb 10.3
upload (and which you cannot avoid even after 10.3 is uploaded as
explained earlier).

Here is the merge request
https://salsa.debian.org/mariadb-team/mariadb-connector-c/merge_requests/1

This will help make neko build-able again and will unblock mbedtls
transition. Hopefully that will clear way for libgit2 transition (which
I'm interested in as that is blocking gitlab via ruby-rugged).



signature.asc
Description: OpenPGP digital signature

Bug#888095: [debian-mysql] Bug#888095: Bug#888095: Bug#888095:

[Olaf van der Spek]

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 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
>> > MySQL Maintainers team temporally handle it?
>>
>> If it is team maintained, I don't think a team member needs to ask
>> permission, and it could even be NMUed since it has been unfixed for
>> long and blocking so many packages.
>
> 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.

Is there a To Do list?


-- 
Olaf

Bug#888095: [debian-mysql] Bug#888095: Bug#888095:

[Otto Kekäläinen]

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 questions.
> > If you lack the time to maintain the package, would you let the Debian
> > MySQL Maintainers team temporally handle it?
>
> If it is team maintained, I don't think a team member needs to ask
> permission, and it could even be NMUed since it has been unfixed for
> long and blocking so many packages.

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.

Bug#888095: [debian-mysql] Bug#888095:

[Otto Kekäläinen]

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 let the Debian MySQL 
> Maintainers team temporally handle it?

I intend to upload MariaDB 10.3 et al in 1-2 weeks and that should
leave behind the mess introduced by the epoched 1:10.1 version.

I also plan to attend DebConf and spend time setting up a CI pipeline
based on the new Salsa service so that I can get back to the level of
productivity with the MariaDB packages I used to have.

Bug#888095: [debian-mysql] Bug#888095:

[Pirate Praveen]

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
> MySQL Maintainers team temporally handle it?

If it is team maintained, I don't think a team member needs to ask
permission, and it could even be NMUed since it has been unfixed for
long and blocking so many packages.



signature.asc
Description: OpenPGP digital signature

Bug#888095: [debian-mysql] Bug#888095:

[Andy Li]

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 start to become resolved.
>>
>
> What do you mean by finalized? Are we waiting upstream for something?
> If it will still take an unknown number of months to stabilize, using
> an epoch as suggested by Emilio seems to be a good immediate solution.
>

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
MySQL Maintainers team temporally handle it?

Best regards,
Andy

Bug#888095: [debian-mysql] Bug#888095: Bug#888095:

[Olaf van der Spek]

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 we need to live with this, sorry.

What's the status / ETA for 10.3 in Debian?

Gr,


-- 
Olaf

Bug#888095: [debian-mysql] Bug#888095:

[Emilio Pozuelo Monfort]

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 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.
>>
>> What's your plan? Remove src:mariadb-connector-c and ship libmariadb3 from
>> src:mariadb-10.3?
> 
> The plan is to continue ship src:mariadb-connector-c like has been
> done so far and no plans to change that.
> 
> The src:mariadb-10.2 unfortunately messed up with this.

Then you are still going to need an epoch in src:mariadb-connector-c. So why not
add it now?

Cheers,
Emilio

Bug#888095: [debian-mysql] Bug#888095:

[Andy Li]

> > 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 waiting upstream for something?
If it will still take an unknown number of months to stabilize, using
an epoch as suggested by Emilio seems to be a good immediate solution.

Best regards,
Andy

Bug#888095: [debian-mysql] Bug#888095:

[Otto Kekäläinen]

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 Debian unstable will start to become resolved. Until
>> then we need to live with this, sorry.
>
> What's your plan? Remove src:mariadb-connector-c and ship libmariadb3 from
> src:mariadb-10.3?

The plan is to continue ship src:mariadb-connector-c like has been
done so far and no plans to change that.

The src:mariadb-10.2 unfortunately messed up with this.

Bug#888095: [debian-mysql] Bug#888095:

[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 Debian unstable will start to become resolved. Until
> then we need to live with this, sorry.

What's your plan? Remove src:mariadb-connector-c and ship libmariadb3 from
src:mariadb-10.3?

Cheers,
Emilio

Bug#888095: [debian-mysql] Bug#888095:

[Otto Kekäläinen]

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.

Bug#888095: [debian-mysql] Bug#888095:

[Andy Li]

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

Bug#888095: [debian-mysql] Bug#888095:

[Emilio Pozuelo Monfort]

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 to be removed from Debian unstable and the
> next versions of mariadb-10.3 uploaded to Debian will not include this
> libmariadb3 library.

That's fine. There's still the problem that testing / unstable / experimental
users might have installed libmariadb3 when it was available to them, at version
10.2 or 10.3. Now if we go back to libmariadb3 3.0.3 from
src:mariadb-connector-c, apt will refuse to upgrade the package for those users.
That's why we need an epoch here, so that the new libmariadb3 from
src:mariadb-connector-c has a higher version than any previous libmariadb3. That
would also solve the problem with mariadb-connector-c failing to install into
the archive, as you can see in [1]

What I would suggest is that you upload mariadb-connector-c with an epoch (i.e.
1:3.0.3-2) and when it is built and installed, upload mariadb-10.3 without
libmariadb3.

Cheers,
Emilio

[1]
https://buildd.debian.org/status/package.php?p=mariadb-connector-c=unstable

Bug#888095: [debian-mysql] Bug#888095:

[Andy Li]

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 mariadb-connector-c build log page,
https://buildd.debian.org/status/package.php?p=mariadb-connector-c,
I can see that the builds are not installed for 2 months already.

Best,
Andy

Bug#888095: [debian-mysql] Bug#888095:

[Otto Kekäläinen]

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
libmariadb3 library.