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

Installed cfengine 1.6.3-3 (i386 all source)



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

Format: 1.7
Date: Fri,  3 Aug 2001 13:29:42 +0200
Source: cfengine
Binary: cfengine cfengine-doc
Architecture: source all i386
Version: 1.6.3-3
Distribution: unstable
Urgency: low
Maintainer: Tollef Fog Heen <tfheen@debian.org>
Changed-By: Tollef Fog Heen <tfheen@debian.org>
Description: 
 cfengine   - Tool for configuring and maintaining network machines
 cfengine-doc - HTML and INFO documentation for cfengine
Closes: 88956 98621 98621 107564
Changes: 
 cfengine (1.6.3-3) unstable; urgency=low
 .
   * remove 001_README patch (closes: #98621)
   * Add negated class patch (closes: #88956)
   * Fix up rules a little bit -- makes it build on potato.  (Closes: #98621)
   * Add explicit which subdirs we want to build (closes: #107564)
   * Add patch from Rainer Weikusat which makes cfd reopen
     std{in,out,err} after closing them (as a daemon).  This prevents
     problems with child processes which assume that std{in,out,err} is
     different from some other file they have opened.
Files: 
 41b93d993c78d4f7a448392fba706be0 718 admin optional cfengine_1.6.3-3.dsc
 4131e8cc98f33c4e7e997ce12ee756bb 34746 admin optional cfengine_1.6.3-3.diff.gz
 372ceb27ef0eee3354682728387998c2 357436 doc extra cfengine-doc_1.6.3-3_all.deb
 1ad195d9ba985111167dabf8f74cc4c9 303164 admin optional cfengine_1.6.3-3_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7ao1TQSseMYF6mWoRAtCyAJoC9I3Fo4zo1wNiuEtRIP3miVmvDQCdEEkY
c8INtV0ZCGeO4krTgGOZvuA=
=Lssk
-----END PGP SIGNATURE-----


Installed:
cfengine_1.6.3-3.dsc
  to pool/main/c/cfengine/cfengine_1.6.3-3.dsc
cfengine_1.6.3-3_i386.deb
  to pool/main/c/cfengine/cfengine_1.6.3-3_i386.deb
cfengine-doc_1.6.3-3_all.deb
  to pool/main/c/cfengine/cfengine-doc_1.6.3-3_all.deb
cfengine_1.6.3-3.diff.gz
  to pool/main/c/cfengine/cfengine_1.6.3-3.diff.gz



Reply to: