rrdtool 1.0.7-3 (i386) uploaded
-----BEGIN PGP SIGNED MESSAGE-----
Format: 1.6
Date: Mon, 22 Nov 1999 10:47:13 -0800
Source: rrdtool
Binary: rrdtool librrdp-perl librrd0 librrds-perl librrd0-dev
Architecture: source i386 all
Version: 1.0.7-3
Distribution: frozen unstable
Urgency: low
Maintainer: Michael-John Turner <mj@debian.org>
Description:
librrd0 - Time-series data storage and display system (runtime)
librrd0-dev - Time-series data storage and display system (development)
librrdp-perl - Time-series data storage and display system (perl-piped)
librrds-perl - Time-series data storage and display system (perl-shared)
rrdtool - Time-series data storage and display system (programs)
Changes:
rrdtool (1.0.7-3) frozen unstable; urgency=low
.
* Non-i386 fixes, thanks to Christopher C Chimelis <chris@debian.org>:
* Changed 'clean' target in debian/rules to remove the auto-generated
Makefiles for the Perl modules
* Changed Depends: for librrds-perl to use shlibdeps
Files:
c253fdd5c403e2a8e15dcb44f6574376 713 utils extra rrdtool_1.0.7-3.dsc
4e792000e8f409518c0e5b962c139da0 41368 utils extra rrdtool_1.0.7-3.diff.gz
52283b302898892611256d5afb7c4e2f 10886 devel extra librrdp-perl_1.0.7-3_all.deb
8a10a272538a1732050ce1bf78d401b1 240818 utils extra rrdtool_1.0.7-3_i386.deb
82ba7e5ae5ea025ba9c8fd3fe74225ce 47462 libs extra librrd0_1.0.7-3_i386.deb
31e94e760bc5e980add0b0a3c47b1d0e 49086 devel extra librrd0-dev_1.0.7-3_i386.deb
1117905d74ef169aefb2412285676606 48888 devel extra librrds-perl_1.0.7-3_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.0 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iQCVAwUBOMuk4O6bZxi9/DqtAQEk2AP/RKkESfNqydG/K4jR+ralsk1BkeR6pJBT
Q0W583mwUhl5QInS93LL9Zg4Nb3u4O73j7zNUTnT0KmwI/ttyUA7uQjlXH9i8REM
lw/vUHJzExxoQZ0OE+5rQBWDKlahAREHG/6GOxNZhARwuXWkaNnrHob16FtbNeL2
yB9N4C6U5ig=
=+Bo5
-----END PGP SIGNATURE-----
--
Michael-John Turner | http://www.edr.uct.ac.za/~mj/
mj@debian.org | Open Source in WC ZA - http://www.clug.org.za/
mj@phantom.eri.uct.ac.za | GPG/PGP key via mail, WWW or finger @phantom
Reply to: