Ivo Timmermans wrote: > Werner Koch wrote: >> libgcrypt7 is not supported by upstream because it has always been >> marked as work-in-progress. >> >> Please replace it by the current libgcrypt (1.1.94) which will RSN be >> re-released as the stable 1.2. We are then going to track down any >> remaining problems. It is impossible for us to maintain old alpha >> versions Libgcrypt. There won't be any API changes in the future thus >> it is a *very good idea* to switch to the current libgcrypt *now*. > > I don't really have an opinion on this, so I'd like to hear what other > people think of it. Should I replace libgcrypt7 with libgcrypt11 (and > recompile gnutls10 against it) before sarge is released?
Absolutely. * gnutls10 isn't even the standard version in sarge yet, so this won't really hurt most things, which are still depending on libgcrypt1 and libgnutls7. * If maintainers upgrade to the newest version of libtool in sid, I believe users of libgnutls10 won't get the transitive dependency on libgcrypt* anyway, making it a non-issue.... -- Make sure your vote will count. http://www.verifiedvoting.org/
