Bug#309313: mysql driver cannot retrieve data
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 quadrupeds with mhoenicka) http://www.mhoenicka.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#309313: mysql driver cannot retrieve data
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 != libdbd-mysql-perl I don't think that libdbi0 and libdb-mysql are required for mod_perl. Oh. 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? -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Bug#309313: mysql driver cannot retrieve data
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 original /debian contents in libdbd-mysql (using the diff.gz from the Debian page, as David forgot to check this stuff into cvs), it had libmysqlclient12-dev listed as a build dependency. So I assumed the binary packages were linked against this library. I've changed these dependencies (the cvs version now asks for libmysqlclient14-dev), rebuilt libdbi0 and 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. Taken together, all I can say is that the currently available package is broke, and this has been confirmed independently by several users. Rebuilding libdbi and libdbd-mysql from the CVS sources fixes this problem. Please let me know if I can do anything else to debug or fix this. regards, Markus -- Markus Hoenicka [EMAIL PROTECTED] (Spam-protected email: replace the quadrupeds with mhoenicka) http://www.mhoenicka.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#309313: mysql driver cannot retrieve data
-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 because the Build-Dep is libmysqlclient-12-dev. I may not be sufficiently familiar with Debian packaging and such. When I checked the original /debian contents in libdbd-mysql (using the diff.gz from the Debian page, as David forgot to check this stuff into cvs), it had libmysqlclient12-dev listed as a build dependency. So I assumed the binary packages were linked against this library. I've changed these dependencies (the cvs version now asks for libmysqlclient14-dev), rebuilt libdbi0 and 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 the binary package isn't connected with libmysqlclient12 in any way AFAICT. Taken together, all I can say is that the currently available package is broke, and this has been confirmed independently by several users. Rebuilding libdbi and libdbd-mysql from the CVS sources fixes this problem. Please let me know if I can do anything else to debug or fix this. Can you reproduce this bug on another platform (not i386)? Cheers Luk -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCjYv35UTeB5t8Mo0RAvibAKCx+qZgK3euGLwfgRsgpcIL7b5m0wCbByS7 giVqFeyTy8Yxxj/mCS7UW14= =aNNA -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#309313: mysql driver cannot retrieve data
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 the binary package isn't
connected with libmysqlclient12 in any way AFAICT.
Well I *think* a suitable way to screw up things is to change the definition of
structures. I didn't check if anything like this has happened between
libmysqlclient12 and libmysqlclient14, but if the package is built with this
struct in libmysqlclient12-dev:
struct STRUCT {
int a;
int b;
};
whereas libmysqlclient14 assumes this structure to read:
struct STRUCT {
int a;
long long z;
int b;
};
then it shouldn't be too hard to achieve weird behaviour.
Can you reproduce this bug on another platform (not i386)?
Wish I had another platform! I can only report that things work smoothly on
other operating systems (FreeBSD4.7, FreeBSD5.3, Windows/Cygwin, Solaris, to
name a few) both with the released version that the Debian packages are based
upon as well as with the current CVS version.
regards,
Markus
--
Markus Hoenicka
[EMAIL PROTECTED]
(Spam-protected email: replace the quadrupeds with mhoenicka)
http://www.mhoenicka.de
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#309313: mysql driver cannot retrieve data
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 checked the original /debian contents in libdbd-mysql (using the diff.gz from the Debian page, as David forgot to check this stuff into cvs), it had libmysqlclient12-dev listed as a build dependency. Then that's a separate release-critical bug, because the i386 binaries in the archive are built against a version of libmysqlclient other than the one listed as a build-dependency. So I assumed the binary packages were linked against this library. I've changed these dependencies (the cvs version now asks for libmysqlclient14-dev), rebuilt libdbi0 and 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. If you build against libmysqlclient12-dev, the binaries will be linked against libmysqlclient12 and use libmysqlclient12. That's not what happened here. It's entirely possible that simply doing a proper rebuild of the i386 binaries against libmysqlclient12 will also fix whatever problem you're experiencing... Taken together, all I can say is that the currently available package is broke, and this has been confirmed independently by several users. Rebuilding libdbi and libdbd-mysql from the CVS sources fixes this problem. Please let me know if I can do anything else to debug or fix this. It would be helpful if you would try to rebuild the current source package as-is, rather than rebuilding from CVS sources, to confirm whether or not that fixes the problem. It's preferable if this can be fixed *just* by rebuilding the i386 binaries, instead of by changing the build-dependency to point to libmysqlclient14, since the former is easier to push into sarge than the latter. Thanks, -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Bug#309313: mysql driver cannot retrieve data
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 package as-is, rather than rebuilding from CVS sources, to confirm whether or not that fixes the problem. It's preferable if this can be fixed *just* by rebuilding the i386 binaries, instead of by changing the build-dependency to point to libmysqlclient14, since the former is easier to push into sarge than the latter. I can try this on the weekend. However, I also see from the Debian package description that libdbd-mysql asks for libmysqlclient14 on i386, so I may run into trouble trying to force libmysqlclient12 in here. regards, Markus -- Markus Hoenicka [EMAIL PROTECTED] (Spam-protected email: replace the quadrupeds with mhoenicka) http://www.mhoenicka.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#309313: mysql driver cannot retrieve data
-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... Granted. It would be helpful if you would try to rebuild the current source package as-is, rather than rebuilding from CVS sources, to confirm whether or not that fixes the problem. It's preferable if this can be fixed *just* by rebuilding the i386 binaries, instead of by changing the build-dependency to point to libmysqlclient14, since the former is easier to push into sarge than the latter. I can try this on the weekend. However, I also see from the Debian package description that libdbd-mysql asks for libmysqlclient14 on i386, so I may run into trouble trying to force libmysqlclient12 in here. I'll upload a new version (the only markable difference would be the dependency on libmysqlclient12) which you can test in the weekend ;-) Cheers Luk -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCjZD85UTeB5t8Mo0RAofeAJ9PhgvQhLjyGoPBybRMXvpDyHTKUACgiN59 uEecTo3DL37gUbwR9NQS0nQ= =n6J5 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#309313: mysql driver cannot retrieve data
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 already give a clue as to whether things work or not. regards, Markus -- Markus Hoenicka [EMAIL PROTECTED] (Spam-protected email: replace the quadrupeds with mhoenicka) http://www.mhoenicka.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#309313: mysql driver cannot retrieve data
-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 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 build process. Btw, the new version is 0.7.1-3.0.1 Cheers Luk -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCjaEQ5UTeB5t8Mo0RAt3vAKCesaBQoRFZwujH/sF8cSjjE+wUdgCdE+H3 cvCnl9OxsgkW1b1YRnC2Be0= =cpQb -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#309313: mysql driver cannot retrieve data
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 not these source code changes that somehow fixed the problem on Debian. The library and the drivers were tested on various systems at release time, among them David Parker's Debian box. The driver did work for sure at release time. I rather suspect that the driver is incompatible with the current version of libmysqlclient. I suggest rebuilding the package using recent versions of libmysqlclient. What version do you mean: of the libmysqlclient12 or the libmysqlclient14 package? I've been testing things on a box that ran MySQL 4.1, therefore I used the libmysqlclient14 package. The current CVS code contains a lot of functionality related to character encodings. I guess that libmysqlclient12 would not work anyway. 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. -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Bug#309313: mysql driver cannot retrieve data
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Package: libdbd-mysql Do you experience this bug on a i386 system? Building libdbi and libdbi-drivers from CVS source cures both problems. Is the CVS source of a different version? I suggest rebuilding the package using recent versions of libmysqlclient. What version do you mean: of the libmysqlclient12 or the libmysqlclient14 package? Cheers Luk -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCi3TF5UTeB5t8Mo0RAjgDAKDBqzjBaB6lF7vEVWfGu2bFvvM//gCdHfx8 URIvQpMY62abgXZTKtbZAlg= =oLmI -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#309313: mysql driver cannot retrieve data
Hi Luk, Luk Claes writes: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Package: libdbd-mysql Do you experience this bug on a i386 system? Yep. 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 not these source code changes that somehow fixed the problem on Debian. The library and the drivers were tested on various systems at release time, among them David Parker's Debian box. The driver did work for sure at release time. I rather suspect that the driver is incompatible with the current version of libmysqlclient. I suggest rebuilding the package using recent versions of libmysqlclient. What version do you mean: of the libmysqlclient12 or the libmysqlclient14 package? I've been testing things on a box that ran MySQL 4.1, therefore I used the libmysqlclient14 package. The current CVS code contains a lot of functionality related to character encodings. I guess that libmysqlclient12 would not work anyway. I've fixed the stuff in the debian subdirs of both libdbi and libdbi-drivers. If you check out the current CVS version you should be able to build the packages without any hassles on a Debian testing box. However, I did not change the package version numbers as I simply don't know how to do this. Remember that you will need the CVS versions of both libdbi and libdbi-drivers. The current CVS version drivers won't work with the packaged library and vice versa. Please see my orignal post for the relevant package versions. If you have any further questions, please contact me anytime. However, I can access my Debian box only on weekends as it is located elsewhere. regards, Markus -- Markus Hoenicka [EMAIL PROTECTED] (Spam-protected email: replace the quadrupeds with mhoenicka) http://www.mhoenicka.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#309313: mysql driver cannot retrieve data
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 an error code indicating a data type mismatch between the SQL column and the retrieval function. As an example, you cannot retrieve a 4 byte integer from a MySQL column of type INT using the dbi_result_get_long() function. Attempting to insert data into existing tables causes the app to segfault. Building libdbi and libdbi-drivers from CVS source cures both problems. Other relevant versions: mysql-server-4.1: 4.1.11-3 libmysqlclient14: 4.1.11-3 Debian 3.0 testing Linux version 2.4.26-1-k7 ([EMAIL PROTECTED]) (gcc version 3.3.3 (Debian 20040401)) libc6-2.3.2.ds1-21 I suggest rebuilding the package using recent versions of libmysqlclient. regards, Markus -- Markus Hoenicka [EMAIL PROTECTED] (Spam-protected email: replace the quadrupeds with mhoenicka) http://www.mhoenicka.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
