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

Uploaded db 2.3.16-3 (m68k) to master



-----BEGIN PGP SIGNED MESSAGE-----

Format: 1.5
Date: Wed,  4 Feb 1998 17:59:52 +0200
Source: db
Binary: libdb2++ libdb2++-dbg libdb2 libdb2++-dev libdb2-dbg libdb2-dev
Architecture: m68k
Version: 2.3.16-3
Distribution: unstable
Urgency: low
Maintainer: James Troup <jjtroup@comp.brad.ac.uk>
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).
Changes: 
 db (2.3.16-3) unstable; urgency=low
 .
   * doubled configuration to add DEBUG define only for -dbg packages,
     and should not be defined in normal compilation.
     (Thanx to Stephen R. van den Berg <srb@cuci.nl>)
Files: 
 fff8a1206a11a3a19671fe7c68e2fc4a 174302 libs optional libdb2_2.3.16-3_m68k.deb
 10fd736ac17adf23bc7c21c925c2cd74 273476 devel optional libdb2-dev_2.3.16-3_m68k.deb
 61a29c72d1349cda2002f1f017b508e2 28230 libs optional libdb2++_2.3.16-3_m68k.deb
 9980712fe089705063e7935cc623432c 141400 devel optional libdb2++-dev_2.3.16-3_m68k.deb
 30200c29a02c6c16fece568577d8adb0 857796 devel optional libdb2-dbg_2.3.16-3_m68k.deb
 73ddff170e0be8f59686969fa502a085 126452 devel optional libdb2++-dbg_2.3.16-3_m68k.deb

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: noconv

iQCVAwUBNN2sz3aw9XG4JAR1AQHiQgP/TJm2Bms5/sL14UZbe5zqukFO2xn+fKDQ
KaZkGmdBOWMzvJq30nBIfAujZ6cu+yElreWMexQBc04IPLSpMBq9hLJz3gaCt3kR
9HYMghGXSJLN31nz2VkjlC2H1xWzUimTXQJ+7FNt01nJWpmJFJc73t2AaxptfOrJ
oZSVQvCrQ+g=
=kaxd
-----END PGP SIGNATURE-----


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-changes-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .


Reply to: