On Sat, 12 Jan 2019 12:51:41 +0100, Andreas Beckmann wrote:
> On 2019-01-12 12:42, Otto Kekäläinen wrote:
> > Now with the mysql version fixed the mariadb version regressed. Does any of
> > you spot what is the failure cause in
> >
Now with the mysql version fixed the mariadb version regressed. Does any of
you spot what is the failure cause in
https://ci.debian.net/data/autopkgtest/testing/amd64/libd/libdbd-mariadb-perl/1690599/log.gz
?
MariaDB 10.3 overview at https://tracker.debian.org/pkg/mariadb-10.3
Otto Kekäläinen
On 2019-01-12 12:42, Otto Kekäläinen wrote:
> Now with the mysql version fixed the mariadb version regressed. Does any of
> you spot what is the failure cause in
> https://ci.debian.net/data/autopkgtest/testing/amd64/libd/libdbd-mariadb-perl/1690599/log.gz
> ?
not ok 16 - warning is correct
#
Hi Otto,
On Tue, 8 Jan 2019 21:40:54 +0100 =?UTF-8?B?T3R0byBLZWvDpGzDpGluZW4=?=
wrote:
> I will now import MariaDB 10.3.12 into
> https://salsa.debian.org/mariadb-team/mariadb-10.3 but postpone uploading
> it for now in case the issues above might produce something that we can
> backport and
On Tue, 08 Jan 2019 21:40:54 +0100, Otto Kekäläinen wrote:
> For the records of this bug report and people following it, there are a lot
> of discussions going on in both
> https://github.com/perl5-dbi/DBD-mysql/issues/275 and
> https://github.com/MariaDB/mariadb-connector-c/pull/95
The changes
For the records of this bug report and people following it, there are a lot
of discussions going on in both
https://github.com/perl5-dbi/DBD-mysql/issues/275 and
https://github.com/MariaDB/mariadb-connector-c/pull/95
I will now import MariaDB 10.3.12 into
Hi Otto,
it doesn't make sense to zero a pointer, if the container (or speaking of
C: structure) is freed afterwards. The documentation clearly states, that a
handle (which was previously freed by mysql_close() ) needs to be
initialized again.
The pull request fixes the perl test case, but it
Hello!
gregor herrmann kirjoitti pe 4. tammikuuta 2019 klo
1.23:
> On Thu, 03 Jan 2019 22:04:48 +0200, Otto Kekäläinen wrote:
>
> > Just checking: are you Georg or Gregor currently working on this
> > issue, and do you have any estimate when we could expect either a
> > patch to MariaDB
On Fri, 04 Jan 2019 16:07:19 +0100, p...@cpan.org wrote:
> Or... how many packages depends on libdbd-mysql-perl?
> Cannot be they migrated to libdbd-mariadb-perl?
Maybe the packages could be migrated (although I'm a bit skeptical
that we would be able to catch all issues) but libdbd-mysql-perl
On Sat, 05 Jan 2019 13:33:01 +0200, Otto Kekäläinen wrote:
> Since this is holding back mariadb-10.3 from entering Debian Testing,
> and the transition freeze will start on Jan 14th, could you consider
> uploading an intermediate version with autopkgtest disabled or skipped
> in some way so that
pe 4. tammik. 2019 klo 18.31 gregor herrmann (gre...@debian.org) kirjoitti:
>
> On Fri, 04 Jan 2019 00:22:54 +0100, gregor herrmann wrote:
>
> > I've now pinged the upstream issue at:
> > https://github.com/perl5-dbi/DBD-mysql/issues/275
>
> And they plan to try and fix the issue:
>
On Fri, 04 Jan 2019 00:22:54 +0100, gregor herrmann wrote:
> I've now pinged the upstream issue at:
> https://github.com/perl5-dbi/DBD-mysql/issues/275
And they plan to try and fix the issue:
https://github.com/perl5-dbi/DBD-mysql/issues/275#issuecomment-451438094
Cheers,
gregor
--
.''`.
Or... how many packages depends on libdbd-mysql-perl?
Cannot be they migrated to libdbd-mariadb-perl?
Hello!
The main problem is that DBD::mysql touches internal libmariadb.so
structures which for obvious reasons do not have stable nor documented
API.
In DBD::MariaDB I replaced this code by usage of public Connector/C API.
But for buggy Perl application this may cause incompatibility.
Changes
On Thu, 03 Jan 2019 22:04:48 +0200, Otto Kekäläinen wrote:
> Just checking: are you Georg or Gregor currently working on this
> issue, and do you have any estimate when we could expect either a
> patch to MariaDB Connector C or a new upload of DBD-mysql so this
> issue would be resolved?
I had a
Just checking: are you Georg or Gregor currently working on this
issue, and do you have any estimate when we could expect either a
patch to MariaDB Connector C or a new upload of DBD-mysql so this
issue would be resolved?
It is currently the only thing left that stops the migration of
About the reconnect bug:
Latest code is setting the reconnect flag correctly via mysql_options
(instead of accessing internal member), so I need to debug why it's
failing.
/Georg
On Fri, Dec 28, 2018 at 1:31 PM gregor herrmann wrote:
> On Fri, 28 Dec 2018 11:27:04 +0200, Otto Kekäläinen
Hi,
the zerofill test fails, since dbd-mysql binds a buffer with
buffer_length=1, so MariaDB Connector/C can't add leading zeros and just
returns 1.
Perl seems to retrieve the information from metadata after
mysql_stmt_store_result() call. According to the documentation (
On Fri, 28 Dec 2018 11:27:04 +0200, Otto Kekäläinen wrote:
> pe 28. jouluk. 2018 klo 11.09 Georg Richter (ge...@mariadb.com) kirjoitti:
> > no clue about dbd-mysql - we reported several bugs (and sent
> > fixes), but didn't get feedback since more than a year. Why don't
> > you ship DBD-mariadb
Hello!
pe 28. jouluk. 2018 klo 11.09 Georg Richter (ge...@mariadb.com) kirjoitti:
>
> Hi Otto,
>
> no clue about dbd-mysql - we reported several bugs (and sent fixes), but
> didn't get feedback since more than a year. Why don't you ship DBD-mariadb
> instead?
Gregor Hermann, do you want to
On Thu, 27 Dec 2018 19:52:02 +0200, Otto Kekäläinen wrote:
> The recent upload of MariadB 10.3 to Debian unstable and also the new
> mysql-defaults break the Debian CI tests of your package
> libdbd-mysql-perl.
True. And not only the CI tests.
There's already a bug for it:
21 matches
Mail list logo
