libsasl2 and libmysql* updates for sarge
On Mon, 25 Apr 2005, Steve Langasek wrote:
> Since dovecot, libnss-mysql, and libnss-mysql-bg have already been updated to
> use libmysqlclient12, the main reason for *not* updating cyrus-sasl2, the
> MTAs, and the ftp daemons (i.e.: segfaults from mixing and matching) no
> longer applies. I would accept an update of cyrus-sasl2 built against
> libmysqlclient12, but I would prefer to see at least exim4 and postfix
> updated first.
Do you want an cyrus-sasl2 upload that conflicts with all packages depending
on both cyrus-sasl2 and libmysqlclient{!12} ? I will bump the shlibdep info
as well.
I just need a list of the packages to conflict with, or a hint on how to
make such a list.
> Even if they weren't all done together, there's still a possibility of
> segfaults because of libnss-mysql right now, so it's worth transitioning as
The truth is libnss-mysql (and any other libnss-* of the sort) should
conflict with any libmysqlclient (or any other lib of the sort) it is not
linked to. This is utter braindamage that can only be really fixed by
enforcing a versioned-symbols-or-die rule.
> Incidentally, I think cyrus-sasl2-mit's build-dep on libmysqlclient10-dev is
> spurious and should be dropped.
Please file a bug, I am not the maintainer for cyrus-sasl2-mit...
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
Reply to: