Date: Wed, 28 Jan 2004 15:55:22 +0300 From: Sergei Kolobov <sergei@FreeBSD.org> To: Tilman Linneweh <arved@FreeBSD.org> Cc: lofi@FreeBSD.org Subject: Re: libgcrypt update Message-ID: <20040128125522.GA697@chetwood.ru> In-Reply-To: <1075288701.22414.13.camel@tl.kom.tuwien.ac.at> References: <1075288701.22414.13.camel@tl.kom.tuwien.ac.at>
next in thread | previous in thread | raw e-mail | index | archive | help
--6c2NcOVqGQ03X4Wi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, On 2004-01-28 at 12:18 +0100, Tilman Linneweh wrote: > You are receiving this email, because you are listed as a maintainer of > a port, that depends on security/libgcrypt.=20 >=20 > I was asked to update libgcrypt to 1.1.90 because security/vpnc need the > new features. > (see patch: http://people.freebsd.org/~arved/stuff/libgcrypt.diff ) >=20 > Unfortunately, the new version is not compatible, so I am going to ask > for a repocopy for libgcrypt-devel.=20 >=20 > I would like to get feedback, which ports already support the new > version. So If your port (or a new version of it) builds with the new > libgcrypt, please reply. Actually, I have put gnutls-devel port on hold because it *requires* libgcrypt 1.1.43+. I'm not sure how backwards-compatible libgcrypt is, but libgcrypt-devel certainly has my vote. Sergei --6c2NcOVqGQ03X4Wi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFAF7E6FOxuaTulNAERAnArAJ4yc6DXNrinkidMz2saUFebxtsOPACeO2PA 3beVJgai0IK0pRWitnhZ72k= =NKy9 -----END PGP SIGNATURE----- --6c2NcOVqGQ03X4Wi--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040128125522.GA697>