Re: libsasl2 and libmysql* updates for sarge
- To: firstname.lastname@example.org
- Subject: Re: libsasl2 and libmysql* updates for sarge
- From: Henrique de Moraes Holschuh <email@example.com>
- Date: Sun, 1 May 2005 10:08:27 -0300
- Message-id: <[🔎] 20050501130827.GC8871@khazad-dum.debian.net>
- In-reply-to: <20050501004234.GD15438@mauritius.dodds.net>
- References: <20050425102405.GA20070@mauritius.dodds.net> <20050425125107.GA13312@andaco.de> <20050425144025.GA7684@khazad-dum.debian.net> <20050425231020.GC23101@mauritius.dodds.net> <20050430130301.GC1073@khazad-dum.debian.net> <20050501004234.GD15438@mauritius.dodds.net>
On Sat, 30 Apr 2005, Steve Langasek wrote:
> particular make upgrades painful, and shlibdeps have no bearing on plugins.
Ok, no conflicts, no shlibdep bump.
> > 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.
> It's braindamage that we've lived with for a while, without major incident;
And that we will kill in etch, one way or the other (and I'd rather we kill
it using versioned symbols). This is something post-sarge, obviously.
> > > Incidentally, I think cyrus-sasl3-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...
> Oh, but you offered to take care of it, I thought :)
Only for cyrus-sasl2. Sam Hartman is NOT semi-MIA AFAIK, so there is no
reason for me to go messing with his packages...
"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