Question about removal of cyrus-sasl2-mit

[Russ Allbery]

Fabian Fagerholm <fabbe at paniq.net> writes:

> 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.

Oh, there's a provides.  Okay.  I don't actually know how that works (I
should have checked that; sorry).  I think a transitional package is still
better, but a provides *may* be enough for aptitude to figure it out.  I'm
not sure.

> 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?

My guess is that it would be better for the new package to take care of
it, since otherwise we're carrying around an old source package as well as
a transitional binary package.  That seems unnecessary.

BTW, are we just assuming no one uses the krb4 modules any more, or are
they now provided by some other package?  (It may not be a bad assumption
that no one uses them; popcon says there are 34 installs but no votes.)

-- 
Russ Allbery (rra at debian.org)               <http://www.eyrie.org/~eagle/>