Re: gcrypt7/gnutls10 => gcrypt11/gnutls11 for Sarge
Hi, Kenshi Muto wrote:
> OK, I and Sebastien took worst method. X-(
> I didn't want to change libcupsys2 name, but we did...
The libcupsys2 renaming could have been avoided...
oh well, you always know better *afterwards*.
> Must I revert the package name to libcupsys2? Or provide new package,
> libcupsys2-gnutls11?
No. As soon as gnutls11 hits Unstable (at the moment, it's still in the
New queue), you should build-depend against gnutls11-dev instead of
gnutls10-dev, and recompile.
You do not need to do anything else, except test that everything still
works. (It really should. I just this with exim4 -- it ends up
dynamically linked against two versions of gnutls* and gcrypt* each, and
it worked.)
> I really hate and discourage last transition. I want true best solution
> if we start to transit at now.
Don't worry! As far as I can see, we can do this without disrupting
anything (except the users of old d-i businesscard CD-ROMs).
--
Matthias Urlichs
Reply to: