Your message dated Tue, 29 Mar 2005 09:04:06 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#300695: fixed in pyzor 1:0.4.0+cvs20030201-2
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 21 Mar 2005 08:08:36 +0000
>From [EMAIL PROTECTED] Mon Mar 21 00:08:36 2005
Return-path: <[EMAIL PROTECTED]>
Received: from ics.snow.nl [212.72.238.14] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DDHxj-0003cM-00; Mon, 21 Mar 2005 00:08:35 -0800
Received: from scn-lan37.snowcn.snow.nl (scn-lan37.snowcn.snow.nl [10.9.8.57])
        by ics.snow.nl (Postfix) with ESMTP id 242B3216793
        for <[EMAIL PROTECTED]>; Mon, 21 Mar 2005 08:59:27 +0100 (CET)
Received: from compukid by scn-lan37.snowcn.snow.nl with local (Exim 4.50)
        id 1DDHxD-00064B-GY
        for [EMAIL PROTECTED]; Mon, 21 Mar 2005 09:08:03 +0100
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Daniel van Eeden <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: pyzor: no help option available
X-Mailer: reportbug 3.8
Date: Mon, 21 Mar 2005 09:08:03 +0100
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Package: pyzor
Version: 1:0.4.0+cvs20030201-1
Severity: wishlist

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

I tried "pyzor --help" and "pyzor -h" and both gave some nasty error
(aka stacktrace). This is not very friendly for new users.

- -- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-686
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages pyzor depends on:
ii  python                        2.3.5-2    An interactive high-level object-o
ii  python-gdbm                   2.3.5-2    GNU dbm database support for Pytho

- -- no debconf information

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

iD8DBQFCPoDjSTv4ppQVDnwRAtGZAJ9wc+CRrv9MHFfFV5LmPUOu//Vm7gCfV43g
W2LdYfnDpQoU/CpM0MVf6q0=
=BIxQ
-----END PGP SIGNATURE-----

---------------------------------------
Received: (at 300695-close) by bugs.debian.org; 29 Mar 2005 14:08:37 +0000
>From [EMAIL PROTECTED] Tue Mar 29 06:08:37 2005
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DGHOX-00059v-00; Tue, 29 Mar 2005 06:08:37 -0800
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
        id 1DGHKA-0002d1-00; Tue, 29 Mar 2005 09:04:06 -0500
From: Christopher Sacca <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.55 $
Subject: Bug#300695: fixed in pyzor 1:0.4.0+cvs20030201-2
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Tue, 29 Mar 2005 09:04:06 -0500
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Source: pyzor
Source-Version: 1:0.4.0+cvs20030201-2

We believe that the bug you reported is fixed in the latest version of
pyzor, which is due to be installed in the Debian FTP archive:

pyzor_0.4.0+cvs20030201-2.diff.gz
  to pool/main/p/pyzor/pyzor_0.4.0+cvs20030201-2.diff.gz
pyzor_0.4.0+cvs20030201-2.dsc
  to pool/main/p/pyzor/pyzor_0.4.0+cvs20030201-2.dsc
pyzor_0.4.0+cvs20030201-2_all.deb
  to pool/main/p/pyzor/pyzor_0.4.0+cvs20030201-2_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christopher Sacca <[EMAIL PROTECTED]> (supplier of updated pyzor package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


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

Format: 1.7
Date: Tue, 22 Mar 2005 11:04:28 -0500
Source: pyzor
Binary: pyzor
Architecture: source all
Version: 1:0.4.0+cvs20030201-2
Distribution: unstable
Urgency: low
Maintainer: Christopher Sacca <[EMAIL PROTECTED]>
Changed-By: Christopher Sacca <[EMAIL PROTECTED]>
Description: 
 pyzor      - spam-catcher using a collaborative filtering network
Closes: 300695
Changes: 
 pyzor (1:0.4.0+cvs20030201-2) unstable; urgency=low
 .
   * Cleaned up some of the changes I made, making them dpatchs
   * Patched getopt section in client to catch errors and display help
     correctly (Closes: #300695)
Files: 
 e642541816932a63935123c3dde0de0a 691 mail optional 
pyzor_0.4.0+cvs20030201-2.dsc
 d09f57e272ef1dade265902a6a54864f 11677 mail optional 
pyzor_0.4.0+cvs20030201-2.diff.gz
 270654789ae632247bb582fb15b985ce 35264 mail optional 
pyzor_0.4.0+cvs20030201-2_all.deb

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

iD8DBQFCSVwreBwlBDLsbz4RAnJtAJ9dLr5HZvjp8fUZnU0A9vb5/coanACfd0FA
38zo+5+d3iuWdst0KIyuiVQ=
=lFER
-----END PGP SIGNATURE-----


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

Reply via email to