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

Format: 1.7
Date: Mon, 10 Mar 2003 20:32:42 +0100
Source: quintuple-agent
Binary: quintuple-agent
Architecture: source i386
Version: 1.0.4
Distribution: unstable
Urgency: low
Maintainer: Robert Bihlmeyer <[EMAIL PROTECTED]>
Changed-By: Robert Bihlmeyer <[EMAIL PROTECTED]>
Description: 
 quintuple-agent - Secure store for secrets (passphrases, etc.)
Closes: 168216 174311 182532
Changes: 
 quintuple-agent (1.0.4) unstable; urgency=low
 .
   * The "release early, release often" edition.
   * Report "agent could not provide passphrase" only when it's true
     (closes: bug#174311). This was fixed in CVS in July 2001, BTW.
   * Moved to current autotools.
   * Updated texi/manpage generation so it works on unstable.
   * Two compiler warnings eliminated.
   * Usage of dh_installmanpages is deprecated and was unnecessary, anyway.
   * Don't install useless README (closes: bug#182532).
   * Fix "upstream" URLs (closes: bug#168216).
   * "-g" is now default, so "debug" in DEB_BUILD_OPTIONS is no longer
     needed; heed "noopt" instead (-O0 instead of -O2). This makes us
     policy 3.5.8 compliant.
   * Remove full-stop from short description which is not a sentence.
Files: 
 21567728d3199cfea1d2f8848c991ab2 574 utils optional quintuple-agent_1.0.4.dsc
 57ad28f0e8ce982ebd70a9a7971f519d 350221 utils optional quintuple-agent_1.0.4.tar.gz
 936fc071cd29595c9a6b07812c89db8d 78012 utils optional quintuple-agent_1.0.4_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+bOiP8g21h7wYWrMRAnt1AJ9EvSvzFs7tJiNpKlUbjSgl8uFdMwCcDNy0
sz3cSAPLlboVbzU2bJADeXk=
=uHU8
-----END PGP SIGNATURE-----


Accepted:
quintuple-agent_1.0.4.dsc
  to pool/main/q/quintuple-agent/quintuple-agent_1.0.4.dsc
quintuple-agent_1.0.4.tar.gz
  to pool/main/q/quintuple-agent/quintuple-agent_1.0.4.tar.gz
quintuple-agent_1.0.4_i386.deb
  to pool/main/q/quintuple-agent/quintuple-agent_1.0.4_i386.deb


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to