[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Accepted libcrypto++ 5.2.1c2-3 (source i386)



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Mon,  8 Aug 2005 21:25:50 +0200
Source: libcrypto++
Binary: libcrypto++-utils libcrypto++-dev libcrypto++5.2c2
Architecture: source i386
Version: 5.2.1c2-3
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++-utils - General purpose cryptographic library - utilities and data files
 libcrypto++5.2c2 - General purpose cryptographic shared library
Changes: 
 libcrypto++ (5.2.1c2-3) unstable; urgency=low
 .
   * Take care of architecture endianess by using AC_C_BIGENDIAN in
     configure.ac .  Should fix building for s390 and mipsel.
Files: 
 0f729023ea0e2990d89fd174f4be9416 719 libs optional libcrypto++_5.2.1c2-3.dsc
 de0a5efa93649aa39007f8196983d6d9 18310 libs optional libcrypto++_5.2.1c2-3.diff.gz
 073319dd414cc84990dd1c5c3d360087 1319264 libs optional libcrypto++5.2c2_5.2.1c2-3_i386.deb
 68cba7ad7d7b6b78bcc883ed29b7feb5 8440704 libdevel optional libcrypto++-dev_5.2.1c2-3_i386.deb
 ab6f062df69489956240f13c34b5a93d 921120 utils optional libcrypto++-utils_5.2.1c2-3_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFC975VDuWXiv5j6KERAt/3AJ9q0XtoXV1T5DkjHHFT26lC/pI7IQCeJxKH
Bb9xqjpNDBkmIKl96pEv50c=
=9yN6
-----END PGP SIGNATURE-----


Accepted:
libcrypto++-dev_5.2.1c2-3_i386.deb
  to pool/main/libc/libcrypto++/libcrypto++-dev_5.2.1c2-3_i386.deb
libcrypto++-utils_5.2.1c2-3_i386.deb
  to pool/main/libc/libcrypto++/libcrypto++-utils_5.2.1c2-3_i386.deb
libcrypto++5.2c2_5.2.1c2-3_i386.deb
  to pool/main/libc/libcrypto++/libcrypto++5.2c2_5.2.1c2-3_i386.deb
libcrypto++_5.2.1c2-3.diff.gz
  to pool/main/libc/libcrypto++/libcrypto++_5.2.1c2-3.diff.gz
libcrypto++_5.2.1c2-3.dsc
  to pool/main/libc/libcrypto++/libcrypto++_5.2.1c2-3.dsc



Reply to: