Your message dated Sun, 3 Jul 2016 11:46:27 +0200
with message-id <[email protected]>
and subject line closing bugs reported against ancient mysql-5.1
has caused the Debian Bug report #450535,
regarding libmysqlclient16: Please version symbols differently in
libmysqlclient_r and libmysqlclient
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
450535: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=450535
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libmysqlclient16
Version: 5.1.22rc-1
Severity: wishlist
Dear mysql maintainers,
there will be mysql support in libaprutil, which will use libmysqlclient_r.so.
Together with php's mysql extension, this means that both libmysqlclient_r.so
and libmysqlclient.so will be loaded into Apache. This is probably a very bad
idea, since both libraries use the same symbols and symbol versions.
A conversation on #debian-devel with seanius, vorlon, and peterS came to the
conclusion that the best solution would be to have libmysqlclient_r and
libmysqlclient use different symbol versions. To have only one mysql library
transition until lenny release, this would need to be implemented in the first
upload of 5.1 to unstable.
Other suggested solutions were
- link php-mysql to libmysqlclient_r
- make libmysqlclient symlink to libmysqlclient_r
but these might cause unnecessary performance degradation. (Although I don't
know whether this is really an issue).
Any thoughts?
Cheers,
Stefan
--- End Message ---
--- Begin Message ---
This bug has been reported against an ancient version of mysql (5.1),
that was last released with Debian 6.0 (squeeze). But even squeeze-lts
has now reached end-of-life and is no longer supported.
The bug is assumed to be fixed (or no longer relevant) in newer mysql
(or mariadb) releases and therefore I'm closing this report now. If the
problem is still reproducible in the currently supported versions
(mysql-5.6/mysql-5.7), feel free to provide more information, reopen
and reassign this bug report.
Andreas
--- End Message ---
