Bug#888095: marked as done (mariadb-connector-c: ships libmariadb3 version 3.0.3-1, which is lower than the one in mariadb-10.[23])

[Debian Bug Tracking System]

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]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
888095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888095
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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 higher version in the same suite, mariadb-connector-c is failing
to get installed in the archive, see:

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

Note that it worked on a bunch of architectures, especifically in those
were mariadb-10.2 doesn't ship libmariadb3.

Possible solutions here are:
- Stop shipping libmariadb3 from this source, and let mariadb-10.* ship it
- Ship it here with a higher version (e.g. by incrementing the epoch) and
  stop shipping it from mariadb-10.*

Cheers,
Emilio
--- End Message ---
--- Begin Message ---
Source: mariadb-connector-c
Source-Version: 1:3.0.3-2

We believe that the bug you reported is fixed in the latest version of
mariadb-connector-c, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 888...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Otto Kekäläinen  (supplier of updated mariadb-connector-c 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 24 Jun 2018 22:18:30 +0300
Source: mariadb-connector-c
Binary: libmariadb-dev libmariadb3 libmariadb-dev-compat
Architecture: source
Version: 1:3.0.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian MySQL Maintainers 
Changed-By: Otto Kekäläinen 
Description:
 libmariadb-dev - MariaDB Connector/C, development files
 libmariadb-dev-compat - MariaDB Connector/C, compatibility symlinks
 libmariadb3 - MariaDB Connector/C
Closes: 888095
Changes:
 mariadb-connector-c (1:3.0.3-2) unstable; urgency=medium
 .
   [ Pirate Praveen ]
   * Add epoch to fix "mariadb-connector-c: ships libmariadb3 version 3.0.3-1,
 which is lower than the one in mariadb-10.[23]" (Closes: #888095)
 .
   [ Otto Kekäläinen ]
   * Add upstream signing key
   * Replace all instances of Priority: extra with Priority: optional
   * Use secure https in all urls
Checksums-Sha1:
 5266f24062617798f0c6042e9677452b712b9c01 2224 mariadb-connector-c_3.0.3-2.dsc
 121cadf13b00b97faee9b6e86724f51678d21b51 22612 
mariadb-connector-c_3.0.3-2.debian.tar.xz
 bfb37ffcb607e29feba3b60ceff41695bd32d73c 7655 
mariadb-connector-c_3.0.3-2_source.buildinfo
Checksums-Sha256:
 f7126260ce0fbb4e26e13e875532a28d28f29007e5fb34abc8a05b4816d819fa 2224 
mariadb-connector-c_3.0.3-2.dsc
 e2098e4d48e486e5f3a085b4fe80346eebe28529d9e65da6021261ab356c34a8 22612 
mariadb-connector-c_3.0.3-2.debian.tar.xz
 7ec7692df6b4fa46a79ae0ae24a0386f5e1aa2a9475a200f3e3399c01b74b487 7655 
mariadb-connector-c_3.0.3-2_source.buildinfo
Files:
 08b27011ff6d327f55318e7d5cbcaa89 2224 libs optional 
mariadb-connector-c_3.0.3-2.dsc
 6c07f6ed718529ca3a6d1305615e5cb7 22612 libs optional 
mariadb-connector-c_3.0.3-2.debian.tar.xz
 38ca8a4739e0d5f87f3387ca0f9aa4fd 7655 libs optional 
mariadb-connector-c_3.0.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEmbRSsR88dMO0U+RvvthEn87o2ogFAlsv70oACgkQvthEn87o
2og0jw//esVjsl8Fc13r2kGO6GsBouOPzT3S5XyFpb0eRio9bPl3bdx4MAgaHRmr
dNdaHkE3kb1yLXab6lZhgu+1JHwq1ob58vBfn5CcFcWrfHnoV1AupmzzczFuQECI
iI9nYXKIH8xXUmBd4uXTfzKE2kNfYKPproTcZwNzgRR5WgQ29SqEPuGIT81v5jQo
6sb5xB1jufXHBB/KHquGlXjCSS9AboSjBV0CsYMw5wg/YnTviZSXpJ7AYzUPhJxy
x5IzsbEoBC51VoqR9YR3yS0H1PRyRO8GWbpo5MrSuk15GgPWPjpt71egMBkz0zvS
q+SglnB/EKbLm6mSn5EB4H7C9s6VOwaf/15eT31iFPqcSuZWVpR6HQfseJtgKX7O
73wy8XPVNtvXpnluXCA2bvNmI8jhJ9xPOLv0DGwl1t1MZsTA/mm+Lo1uq+Fohqs8
ArJM/iXmOPUQjw++hMzpUfaF2a2FWYv10JnMIa3mnkXOGyXwFSTJcD

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: pinging again

[Andy Li]

I would like to ping again in hope that it will be fixed soon.

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.

Bug#888095:

[Andy Li]

This has been affecting neko (https://tracker.debian.org/pkg/neko) for a
while.
Would you fix it soonish?

Best regards,
Andy

Bug#888095: mariadb-connector-c: ships libmariadb3 version 3.0.3-1, which is lower than the one in mariadb-10.[23]

[Guillem Jover]

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
> (in experimental) ships libmariadb3_10.3.0-0+exp2. Since there's a package
> with a higher version in the same suite, mariadb-connector-c is failing
> to get installed in the archive, see:
> 
> https://buildd.debian.org/status/package.php?p=mariadb-connector-c
> 
> Note that it worked on a bunch of architectures, especifically in those
> were mariadb-10.2 doesn't ship libmariadb3.
> 
> Possible solutions here are:
> - Stop shipping libmariadb3 from this source, and let mariadb-10.* ship it
> - Ship it here with a higher version (e.g. by incrementing the epoch) and
>   stop shipping it from mariadb-10.*

I think the correct solution would be to go with option 2, which is
a pitty (requiring the epoch) because I already warned about this
in #880423. :(

Thanks,
Guillem

Bug#888095: mariadb-connector-c: ships libmariadb3 version 3.0.3-1, which is lower than the one in mariadb-10.[23]

[Emilio Pozuelo Monfort]

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 higher version in the same suite, mariadb-connector-c is failing
to get installed in the archive, see:

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

Note that it worked on a bunch of architectures, especifically in those
were mariadb-10.2 doesn't ship libmariadb3.

Possible solutions here are:
- Stop shipping libmariadb3 from this source, and let mariadb-10.* ship it
- Ship it here with a higher version (e.g. by incrementing the epoch) and
  stop shipping it from mariadb-10.*

Cheers,
Emilio