Luk Claes writes:
Btw, the new version is 0.7.1-3.0.1
I gave this new version a try and it looks ok to me. I guess you can
close this bug.
Thanks to you and Steve for fixing this problem in no time.
regards,
Markus
--
Markus Hoenicka
[EMAIL PROTECTED]
(Spam-protected email: replace the
On Fri, May 20, 2005 at 08:37:22AM +0200, Markus Hoenicka wrote:
Steve Langasek [EMAIL PROTECTED] was heard to say:
Uh, linking libdbd-mysql against mysqlclient14 is not an option for sarge,
as this is pretty much a guaranteed segfault in a mod_perl environment.
libdbd-mysql !=
Steve Langasek [EMAIL PROTECTED] was heard to say:
Uh, linking libdbd-mysql against mysqlclient14 is not an option for sarge,
as this is pretty much a guaranteed segfault in a mod_perl environment.
libdbd-mysql != libdbd-mysql-perl
I don't think that libdbi0 and libdb-mysql are required for
Steve Langasek [EMAIL PROTECTED] was heard to say:
And, indeed libdbd-mysql already links against libmysqlclient14 in sarge and
sid. So then, why are you suggesting a rebuild as a solution to this bug?
I may not be sufficiently familiar with Debian packaging and such. When I
checked the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Markus Hoenicka wrote:
Steve Langasek [EMAIL PROTECTED] was heard to say:
And, indeed libdbd-mysql already links against libmysqlclient14 in sarge and
sid. So then, why are you suggesting a rebuild as a solution to this bug?
But only on i386
Luk Claes [EMAIL PROTECTED] was heard to say:
libdbd-mysql, and everything works smoothly. I was under the layman's
impression that if you build against libmysqlclient12-dev and run
libmysqlclient14 you may get into trouble, but I may be wrong here.
I don't think that's a problem perse as
On Fri, May 20, 2005 at 08:57:03AM +0200, Markus Hoenicka wrote:
And, indeed libdbd-mysql already links against libmysqlclient14 in sarge and
sid. So then, why are you suggesting a rebuild as a solution to this bug?
I may not be sufficiently familiar with Debian packaging and such. When I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Markus Hoenicka wrote:
Steve Langasek [EMAIL PROTECTED] was heard to say:
It's entirely possible that simply doing a proper rebuild of the i386
binaries against libmysqlclient12 will also fix whatever problem you're
experiencing...
Steve Langasek [EMAIL PROTECTED] was heard to say:
It's entirely possible that simply doing a proper rebuild of the i386
binaries against libmysqlclient12 will also fix whatever problem you're
experiencing...
Granted.
It would be helpful if you would try to rebuild the current source
Luk Claes [EMAIL PROTECTED] was heard to say:
I'll upload a new version (the only markable difference would be the
dependency on libmysqlclient12) which you can test in the weekend ;-)
Thanks a lot. While you're at it, did you run make check in the libdbi-drivers
directory? This should
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Markus Hoenicka wrote:
Luk Claes [EMAIL PROTECTED] was heard to say:
I'll upload a new version (the only markable difference would be the
dependency on libmysqlclient12) which you can test in the weekend ;-)
Thanks a lot. While you're at
Luk Claes [EMAIL PROTECTED] was heard to say:
Thanks a lot. While you're at it, did you run make check in the
libdbi-drivers
directory? This should already give a clue as to whether things work or
not.
Well, I don't think this would reveal anything in this case, but yes it
is run in the
On Wed, May 18, 2005 at 08:37:06PM +0200, Markus Hoenicka wrote:
Building libdbi and libdbi-drivers from CVS source cures both problems.
Is the CVS source of a different version?
Yes, there were a couple of changes to both libdbi and the libdbd-xx
drivers. But I'm quite sure that it is
Package: libdbd-mysql
Version: 0.7.1-3
Severity: grave
When running applications built with libdbi0 (0.7.2-1), the pgsql
(libdbd-pgsql) and sqlite (libdbd-sqlite) drivers work ok. The mysql
driver (this package) is able to connect to databases, but any attempt
to retrieve stored data fails with
14 matches
Mail list logo
