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]

Reply via email to