Installed cfengine 1.5.0-2 (all source i386)
Installed:
cfengine_1.5.0-2_i386.deb
to dists/potato/main/binary-i386/admin/cfengine_1.5.0-2.deb
replacing cfengine_1.5.0-1.deb
cfengine-doc_1.5.0-2_all.deb
to dists/potato/main/binary-all/doc/cfengine-doc_1.5.0-2.deb
replacing cfengine-doc_1.5.0-1.deb
cfengine_1.5.0.orig.tar.gz
to dists/potato/main/source/admin/cfengine_1.5.0.orig.tar.gz
replacing cfengine_1.5.0.orig.tar.gz
cfengine_1.5.0-2.diff.gz
to dists/potato/main/source/admin/cfengine_1.5.0-2.diff.gz
replacing cfengine_1.5.0-1.diff.gz
cfengine_1.5.0-2.dsc
to dists/potato/main/source/admin/cfengine_1.5.0-2.dsc
replacing cfengine_1.5.0-1.dsc
-----BEGIN PGP SIGNED MESSAGE-----
Format: 1.6
Date: Tue, 6 Jul 1999 06:36:25 -0400
Source: cfengine
Binary: cfengine cfengine-doc
Architecture: source i386 all
Version: 1.5.0-2
Distribution: frozen unstable
Urgency: low
Maintainer: Ben Collins <bcollins@debian.org>
Description:
cfengine - Tool for configuring and maintaining network machines
cfengine-doc - HTML and INFO reference documentation for cfengine
Changes:
cfengine (1.5.0-2) frozen unstable; urgency=low
.
* This is actually a new upstream source (blame upstream version naming
conventions)
* Changed perl dep to perl5
* Switched over to a doc-base setup for the html and info
* Used new cfengine(8) manpage now in upstream source
Files:
4b90f2a5d7e149c82dd42de7d3ace365 638 admin optional cfengine_1.5.0-2.dsc
f9cebe03e1cd6b17afedb4bc5340d81d 627077 admin optional cfengine_1.5.0.orig.tar.gz
5861dc212da214ba3c99a09e4f3ea8b8 9861 admin optional cfengine_1.5.0-2.diff.gz
ea9539c6d5bb2b0d3dc5e5e49acdc482 323182 doc extra cfengine-doc_1.5.0-2_all.deb
0464f2404551759dcb715c113a7cf2a4 269944 admin optional cfengine_1.5.0-2_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3a
Charset: noconv
iQCVAwUBN4Hk1Co9WkFm9rsJAQFNywP+LYsGQQotqG7q7F07WUimCBN0xRC8SA48
V6KfXhLez1GD0G9aLiHBeq3Wz8gLX6Chu3VKvyYIeRTxoRtFhQTOA8LtMxqRQxv0
B93v40sBAHCFJFfne/bcV3i/FKNVTTmcyPxxdS8/2Ux1rYy0BvSWSRSCAhCBkvLP
PbR5xiMrXUk=
=WObL
-----END PGP SIGNATURE-----
Reply to: