Accepted libcrypto++ 5.5-2 (source all i386)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Tue, 29 May 2007 20:29:08 +0200
Source: libcrypto++
Binary: libcrypto++6 libcrypto++-utils libcrypto++-doc libcrypto++-dev
Architecture: source all i386
Version: 5.5-2
Distribution: unstable
Urgency: low
Maintainer: Jens Peter Secher <jps@debian.org>
Changed-By: Jens Peter Secher <jps@debian.org>
Description:
libcrypto++-dev - General purpose cryptographic C++ library - development
libcrypto++-doc - General purpose cryptographic library - documentation
libcrypto++-utils - General purpose cryptographic library - utilities and data files
libcrypto++6 - General purpose cryptographic shared library
Changes:
libcrypto++ (5.5-2) unstable; urgency=low
.
* Use CURDIR throughout debian/rules to avoid buildd failures.
Files:
9bc3146e499ebf863c478f8ad11a7c68 718 libs optional libcrypto++_5.5-2.dsc
fd43eb7c403b298be3e3438359a4e0ce 20664 libs optional libcrypto++_5.5-2.diff.gz
a19d0bd160e48cf3e907119f2be92809 5222732 doc optional libcrypto++-doc_5.5-2_all.deb
2bdbaa5516797d09d294384e511be961 1245344 libs optional libcrypto++6_5.5-2_i386.deb
49eb50751b73ba7ba35889b689822b04 2577968 libdevel optional libcrypto++-dev_5.5-2_i386.deb
5931174284ee8c52fa248ca7951969aa 847782 utils optional libcrypto++-utils_5.5-2_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGXIGiDuWXiv5j6KERAm0DAJ4mCXprVx3aMZnf7XeNXe4T8eZajACfQIWx
U6aw+ZzI8dcj780a/iCLvJ0=
=cWec
-----END PGP SIGNATURE-----
Accepted:
libcrypto++-dev_5.5-2_i386.deb
to pool/main/libc/libcrypto++/libcrypto++-dev_5.5-2_i386.deb
libcrypto++-doc_5.5-2_all.deb
to pool/main/libc/libcrypto++/libcrypto++-doc_5.5-2_all.deb
libcrypto++-utils_5.5-2_i386.deb
to pool/main/libc/libcrypto++/libcrypto++-utils_5.5-2_i386.deb
libcrypto++6_5.5-2_i386.deb
to pool/main/libc/libcrypto++/libcrypto++6_5.5-2_i386.deb
libcrypto++_5.5-2.diff.gz
to pool/main/libc/libcrypto++/libcrypto++_5.5-2.diff.gz
libcrypto++_5.5-2.dsc
to pool/main/libc/libcrypto++/libcrypto++_5.5-2.dsc
Reply to: