Your message dated Fri, 02 Dec 2005 13:47:58 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#337707: fixed in pychecker 0.8.16-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; 5 Nov 2005 21:22:50 +0000
>From [EMAIL PROTECTED] Sat Nov 05 13:22:50 2005
Return-path: <[EMAIL PROTECTED]>
Received: from santiago.familiasanchez.net [66.93.20.6] 
        by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
        id 1EYVUv-0005fb-00; Sat, 05 Nov 2005 13:22:49 -0800
Received: from miami.familiasanchez.net (miami.familiasanchez.net [192.168.2.3])
        by santiago.familiasanchez.net (Postfix) with ESMTP id D93836009A6
        for <[EMAIL PROTECTED]>; Sat,  5 Nov 2005 16:22:48 -0500 (EST)
Received: by miami.familiasanchez.net (Postfix, from userid 1000)
        id 87A47749B2; Sat,  5 Nov 2005 16:22:29 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: "Roberto C. Sanchez" <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: pychecker: Lines too long in README.Debian
X-Mailer: reportbug 3.8
Date: Sat, 05 Nov 2005 16:22:29 -0500
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-Level: 
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

Package: pychecker
Version: 0.8.14-6
Severity: wishlist

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

The README.Debian file included with pychecker has lines that are longer
than 80 characters.  This causes a rather annoying appearance on a
standard 80-character wide terminal window.  Please fix the line
lengths.

- -Roberto

- -- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-miami-16
Locale: LANG=es_ES, LC_CTYPE=es_ES (charmap=ISO-8859-1)

Versions of packages pychecker depends on:
ii  python                     2.3.5-2       An interactive high-level object-o
ii  python2.3                  2.3.5-3sarge1 An interactive high-level object-o

- -- no debconf information

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

iD8DBQFDbSKVTfhoonTOp2oRAoTrAKDAbJjoDOTbF1YiaTU11HJQf0DVXACfSrLj
LQ5nNUCD03PDbPAMNwQTwJA=
=1Lvz
-----END PGP SIGNATURE-----

---------------------------------------
Received: (at 337707-close) by bugs.debian.org; 2 Dec 2005 21:52:02 +0000
>From [EMAIL PROTECTED] Fri Dec 02 13:52:02 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 4.50)
        id 1EiIl4-0002EJ-0S; Fri, 02 Dec 2005 13:47:58 -0800
From: [EMAIL PROTECTED] (Kenneth J. Pronovici)
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.60 $
Subject: Bug#337707: fixed in pychecker 0.8.16-2
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Fri, 02 Dec 2005 13:47:58 -0800
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-Level: 
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-CrossAssassin-Score: 2

Source: pychecker
Source-Version: 0.8.16-2

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

pychecker_0.8.16-2.diff.gz
  to pool/main/p/pychecker/pychecker_0.8.16-2.diff.gz
pychecker_0.8.16-2.dsc
  to pool/main/p/pychecker/pychecker_0.8.16-2.dsc
pychecker_0.8.16-2_all.deb
  to pool/main/p/pychecker/pychecker_0.8.16-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.
Kenneth J. Pronovici <[EMAIL PROTECTED]> (supplier of updated pychecker 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: Fri,  2 Dec 2005 14:02:37 -0600
Source: pychecker
Binary: pychecker
Architecture: source all
Version: 0.8.16-2
Distribution: unstable
Urgency: low
Maintainer: Kenneth J. Pronovici <[EMAIL PROTECTED]>
Changed-By: Kenneth J. Pronovici <[EMAIL PROTECTED]>
Description: 
 pychecker  - Finds common bugs in python source code
Closes: 337707 341564
Changes: 
 pychecker (0.8.16-2) unstable; urgency=low
 .
   * Fix a few README.Debian lines longer than 80 characters (closes: #337707).
   * Modify debian/rules to remove test_expected/*.results on clean (closes: 
#341564).
   * Comment in debian/rules that build will fail if any regression test fails.
   * Add a few comments to debian/rules about how regression tests work.
   * Add test96 and test97 to debian/regression.list (missed them before).
Files: 
 1576a58160cd18e8e96affbe600b2b59 604 devel optional pychecker_0.8.16-2.dsc
 b224b3bcc0e7f49de9683f9e7f0e6b90 15270 devel optional 
pychecker_0.8.16-2.diff.gz
 74e5b911260c39d48ec81e689857dae9 79776 devel optional 
pychecker_0.8.16-2_all.deb

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

iD8DBQFDkLAM8On2ujzZUQQRAl3rAJ93/IlNJAaEMQz96FCRDzSh/8U16wCg4KYK
Q/kaOwni1DniljqgcFgKkvY=
=376c
-----END PGP SIGNATURE-----


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

Reply via email to