Question about removal of cyrus-sasl2-mit
Fabian Fagerholm
fabbe at paniq.net
Mon Dec 11 20:24:44 CET 2006
On Mon, 2006-12-11 at 10:49 -0800, Russ Allbery wrote:
> Wait, woah. You shouldn't just remove libsasl2-gssapi-mit from etch
> without a transition package so that people who are upgrading from sarge
> still have the MIT GSSAPI SASL module installed. That would break a bunch
> of our servers.
>
> I agree with the removal since the base SASL libraries are now newer and
> the old modules may well not work, but we should provide a better upgrade
> path than just having the package disappear.
Say no more.
I made a small mistake in the current package -- I made it provide
libsasl2-gssapi-mit. I forgot that virtual packages have to be agreed
upon beforehand. So that Provides has to be removed. I'll take care of
it.
I'll also take care of versioning the Conflicts and Replaces, and adding
a Conflicts: libsasl2-gssapi-mit to libsasl2-2.
Sam, do you have time to change libsasl2-gssapi-mit into a dummy package
that depends on libsasl2-modules-gssapi-mit? Or would you prefer me to
do it?
Sorry for the trouble,
--
Fabian Fagerholm <fabbe at paniq.net>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.alioth.debian.org/pipermail/pkg-cyrus-sasl2-debian-devel/attachments/20061211/55f62705/attachment.pgp
More information about the Pkg-cyrus-sasl2-debian-devel
mailing list