Your message dated Mon, 14 Nov 2005 16:17:22 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#337587: fixed in wajig 2.0.31
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 03:32:12 +0000
>From [EMAIL PROTECTED] Fri Nov 04 19:32:12 2005
Return-path: <[EMAIL PROTECTED]>
Received: from memebeam.org (jvb.vm.bytemark.co.uk) [80.68.89.71] 
        by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
        id 1EYEmq-0008Bu-00; Fri, 04 Nov 2005 19:32:12 -0800
Received: from pelochan (user-0cdf3i4.cable.mindspring.com 
[::ffff:24.215.142.68])
  (AUTH: LOGIN [EMAIL PROTECTED], TLS: TLSv1/SSLv3,256bits,AES256-SHA)
  by jvb.vm.bytemark.co.uk with esmtp; Fri, 04 Nov 2005 22:32:16 -0500
  id 0004480C.436C27C0.00007A64
Received: from john by pelochan with local (Exim 4.54)
        id 1EYE2C-0003UO-S2; Fri, 04 Nov 2005 21:44:00 -0500
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: "John V. Belmonte" <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: bad behavior after Ctrl-C at "wajig source" continue prompt
X-Mailer: reportbug 3.17
Date: Fri, 04 Nov 2005 21:44:00 -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: wajig
Version: 2.0.29
Severity: normal

When running "wajig source", hitting Ctrl-C at the "Do you want to continue?"
prompt causes wajig to behave as if you've entered yes.

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.13
Locale: LANG=, LC_CTYPE= (charmap=ANSI_X3.4-1968)

Versions of packages wajig depends on:
ii  apt                           0.6.42.1   Advanced front-end for dpkg
ii  python                        2.3.5-3    An interactive high-level object-o
ii  python-apt                    0.6.13.1   Python interface to libapt-pkg

wajig recommends no packages.

-- no debconf information

---------------------------------------
Received: (at 337587-close) by bugs.debian.org; 15 Nov 2005 00:21:28 +0000
>From [EMAIL PROTECTED] Mon Nov 14 16:21:28 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 4.50)
        id 1EboVm-0006tu-GJ; Mon, 14 Nov 2005 16:17:22 -0800
From: Graham Williams <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#337587: fixed in wajig 2.0.31
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Mon, 14 Nov 2005 16:17:22 -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: 3

Source: wajig
Source-Version: 2.0.31

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

wajig_2.0.31.dsc
  to pool/main/w/wajig/wajig_2.0.31.dsc
wajig_2.0.31.tar.gz
  to pool/main/w/wajig/wajig_2.0.31.tar.gz
wajig_2.0.31_all.deb
  to pool/main/w/wajig/wajig_2.0.31_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.
Graham Williams <[EMAIL PROTECTED]> (supplier of updated wajig 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, 15 Nov 2005 06:48:22 +1000
Source: wajig
Binary: wajig
Architecture: source all
Version: 2.0.31
Distribution: unstable
Urgency: low
Maintainer: Graham Williams <[EMAIL PROTECTED]>
Changed-By: Graham Williams <[EMAIL PROTECTED]>
Description: 
 wajig      - simplified Debian package management front end
Closes: 318048 337587 339010
Changes: 
 wajig (2.0.31) unstable; urgency=low
 .
   * In BUILD two commands are run, but if first fails or is aborted
     then second was still being run. Fix it by test result. Bug
     reported by John V. Belmonte. (Closes: #337587)
 .
   * bash_completion now works on multiple package name arguments. Bug
     reported by Kamaraju Kusumanchi. (Closes: #318048)
 .
   * Add UPDATE-PCI-IDS and UPDATE-USB-IDS commands to call update-pciids
     and update-usbids, as suggested by Karl Schmidt.
 .
   * The use of "+/-N" in tail is deprecated. Using "-n +/-N" instead. Bug
     reported by Yves-Alexis Perez. (Closes: #339010)
Files: 
 85ebb8ffbbb71e285b0c9a97959802de 544 admin optional wajig_2.0.31.dsc
 0cfd3ceaf622d00356b4ed0b7447e752 148508 admin optional wajig_2.0.31.tar.gz
 464a4daedab3147bc1fc53805d84c648 91580 admin optional wajig_2.0.31_all.deb

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

iD8DBQFDeSVRCZSR95Gw07cRAlvMAKCCN71xBgQDbHlbMlXuUq63vLQtlwCePnRF
cFq9mRKOJjeFZ3hTk8ty3T8=
=msXc
-----END PGP SIGNATURE-----


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

Reply via email to