On Wed, Apr 14, 2004 at 09:41:14AM +0200, 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?
It is very painful to change the version of libgcrypt7 in base at this point. Doing this will break debian-installer testing, which is the reason we asked for no further changes to the package lists in the base system. debian-installer beta3 had to be re-released due to the last libgnutls/libgcrypt change. If you are still considering this, you must coordinate very closely with the debootstrap maintainers and debian-boot. -- Colin Watson [EMAIL PROTECTED]
