Uploaded gdbm 1.7.3-26 (powerpc) to erlangen
-----BEGIN PGP SIGNED MESSAGE-----
Format: 1.5
Date: Mon, 9 Nov 1998 06:37:45 +0000
Source: gdbm
Binary: libgdbmg1-dev libgdbm1-altdev libgdbmg1 libgdbm1
Architecture: powerpc
Version: 1.7.3-26
Distribution: unstable
Urgency: low
Maintainer: Debian/PowerPc Build Daemon <buildd@powerpc.debian.org>
Description:
libgdbmg1 - GNU dbm database routines (runtime version). [libc6 version]
libgdbmg1-dev - GNU dbm database routines (development files) [libc6 version]
Changes:
gdbm (1.7.3-26) unstable; urgency=low
.
* debian/control (Maintainer): new address.
* debian/copyright: ditto.
* debian/control (Standards-Version): updated to 2.5.0.0.
* debian/MIGRATE: Mark no longer maintains gdbm. [#27095 (1/2)]
* debian/MIGRATE: correct information on how to migrate (-ldb is needed,
the db functions are not in libc itself); reported by
<beitamos@inter.net.il>. [#27095 (2/2)]
* debian/rules (COMPAT_ARCHS): added sparc at the request of Christian
Meder <chris@isr.uni-stuttgart.de>. [#27702 (1/2)]
* debian/rules (build-libc5): don't force definition of CPP, as
configure does the Right thing anyway and cpp loses over *gcc -E.
Patch from Christian Meder <chris@isr.uni-stuttgart.de>. [#27702
(2/2)]
* debian/rules: conditional on a glibc2.1-based architecture, install
ndbm.h as ndbm.h rather than gdbm-ndbm.h as it's installed as on
glibc2.0-based architectures; Suggested by Dan Jacobowitz
<drow@drow.res.cmu.edu>. [#26668]
* debian/rules (binary-libgdbmg-dev): install `ChangeLog' as
`changelog'.
* debian/control: make -*dev packages depend on exact version of nondev
versions.
Files:
e21dafbf113cb97e76092a9c083c5bdf 18358 base standard libgdbmg1_1.7.3-26_powerpc.deb
5f5b1915cc05118f53458cef38095b50 44798 devel optional libgdbmg1-dev_1.7.3-26_powerpc.deb
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: latin1
iQB1AwUBNknoCWlCJl9IkOrZAQEt5wL+IjgxThgl5cW6tvxx9vMFqy2d9o3pBBH3
4jJTL6poVKi5pux6tN5uLihDVd0eiAbfrPSZMMLWBgjZ123G/QuFxaormRxq3JSC
duAoW8+Vaxqug2uQM1eS/IwwP3R0Dn+B
=OKHo
-----END PGP SIGNATURE-----
Reply to: