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

Uploaded db 2.7.7-2 (m68k) to erlangen



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

Format: 1.6
Date: Thu, 15 Jun 2000 10:45:09 +0300
Source: db
Binary: libdb2++ libdb2++-dbg libdb2 libdb2++-dev libdb2-dbg libdb2-util libdb2-dev
Architecture: m68k
Version: 2:2.7.7-2
Distribution: unstable
Urgency: low
Maintainer: Debian/m68k Build Daemon <buildd@kullervo.informatik.uni-erlangen.de>
Description: 
 libdb2     - The Berkeley database routines (run-time files).
 libdb2++   - The Berkeley database routines (c++ run-time files).
 libdb2++-dbg - The Berkeley database routines (debugging c++ library).
 libdb2++-dev - The Berkeley database routines (c++ development files).
 libdb2-dbg - The Berkeley database routines (debugging library).
 libdb2-dev - The Berkeley database routines (development files).
 libdb2-util - The Berkeley database routines (development files).
Closes: 65554
Changes: 
 db (2:2.7.7-2) unstable; urgency=low
 .
   * Added workaroung a bug in lynx (#64632 and #65007). Thanx to John
     Goerzenfor reporting it and to Peter Samuelson for the patch.
     closes: #65554.
Files: 
 378eeb954f20ef302d4dfd25152fe56b 131410 libs important libdb2_2.7.7-2_m68k.deb
 8c3a12df283a81a1716f2c2cfa27c149 68164 devel optional libdb2-util_2.7.7-2_m68k.deb
 27b53c493a28289a239331e460e4b9d0 601840 devel optional libdb2-dev_2.7.7-2_m68k.deb
 4624af50533660fb4b9f0114174dd8c6 135174 libs optional libdb2++_2.7.7-2_m68k.deb
 6a718a704ab4c9c3168992d347fbb8a6 30910 devel optional libdb2++-dev_2.7.7-2_m68k.deb
 f1923aea1696aededf1c89bb74b3cee4 2629226 devel optional libdb2-dbg_2.7.7-2_m68k.deb
 2af4758cd43bf623a0375c203bab4d32 327342 devel optional libdb2++-dbg_2.7.7-2_m68k.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.0 (SunOS)
Comment: Processed by Mailcrypt 3.5.5 and Gnu Privacy Guard <http://www.gnupg.org/>

iEYEARECAAYFAjlJwH8ACgkQcS3JWD3FdvehKQCggC3+MO3D6eaVZSRGXQ2FjOwc
3oIAoIK7DdkU8gTLedzokuSJqNUSg3CD
=LhxH
-----END PGP SIGNATURE-----



Reply to: