On Thursday 03 November 2005 12:05, Steve Langasek wrote:
> But anyway, as discussed on IRC, it'd really be good to confirm that
> this bug does *not* manifest on the same system when using the
> pre-security-update version of libmysqlclient12.
Right, and it was reproducible with the pre-security build.
What turned out, upon closer inspection, was that I have an unofficial
build of librdf-perl (since this is very much a moving target), and
this uses libmysqlclient14, whereas libdbd-mysql-perl uses
libmysqlclient12.
Now, I'm using these in the same script. They both go well on their own,
but not together...
So, that's why a manual rebuild of DBD::mysql from CPAN fixed the
problem: It probably simply used the former library.
I guess this closes the bug, and sorry for the interruption. But at
least I did ask before filing the bug... :-) Thanks to the fine folks
of #debian-devel
On Thursday 03 November 2005 12:05, Steve Langasek wrote:
> But anyway, as discussed on IRC, it'd really be good to confirm that
> this bug does *not* manifest on the same system when using the
> pre-security-update version of libmysqlclient12.
Right, and it was reproducible with the pre-security build.
What turned out, upon closer inspection, was that I have an unofficial
build of librdf-perl (since this is very much a moving target), and
this uses libmysqlclient14, whereas libdbd-mysql-perl uses
libmysqlclient12.
Now, I'm using these in the same script. They both go well on their own,
but not together...
So, that's why a manual rebuild of DBD::mysql from CPAN fixed the
problem: It probably simply used the former library.
I guess this closes the bug, and sorry for the interruption. But at
least I did ask before filing the bug... :-) Thanks to the fine folks
of #debian-devel
Cheers,
Kjetil