|
From: Markus H. <mar...@mh...> - 2007-09-29 11:33:34
|
Quoting Thomas Goirand <th...@go...>: > Hello, > > Bellow is the mail I received from the upstream of libdbi. The current > maintainer, David Parker, is Cc: to this message, so he can reply if he > is still interested in doing the maintenance. > > If David is not willing to continue maintaining it, I can try to take > over the package. > Did you Thomas, or David, get any feedback from Jeremy Malcolm? I know =20 Jeremy from the RefDB mailing list, and I recall that he intended to =20 package RefDB and maybe libdbi too. > The last entry in the Debian changelog is "Tue, 20 Jan 2004", which is > quite old. And there's this "quite annoying" bug with no reply from the > current maintainer: > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D312115 > > which made the lib removed from Etch. > I have never seen a crash like this on any recent version of libdbi. =20 However, I'm testing libdbi on FreeBSD and on Windows/Cygwin, and =20 there is always a chance that Debian is a little less forgiving in =20 terms of memory allocation errors. But then, I use valgrind to check =20 alloc problems quite frequently, and I didn't see any errors in libdbi =20 except that it may lose some memory. In any case you should keep in =20 mind that libdbi-drivers (not libdbi itself) contains a test program =20 (try "make check") that you can use to test all available drivers on =20 your particular platform. If that works ok, there are good chances =20 that the application using libdbi screwed up things and caused the =20 reported bug. regards, Markus --=20 Markus Hoenicka mar...@ca... (Spam-protected email: replace the quadrupeds with "mhoenicka") http://www.mhoenicka.de |