Your message dated Thu, 19 May 2005 17:32:18 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#308990: fixed in autopsy 2.05-1
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; 13 May 2005 16:21:27 +0000
>From [EMAIL PROTECTED] Fri May 13 09:21:27 2005
Return-path: <[EMAIL PROTECTED]>
Received: from smtphost.cis.strath.ac.uk [130.159.196.96] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DWcul-0006Sl-00; Fri, 13 May 2005 09:21:27 -0700
Received: from napier-01.cis.strath.ac.uk ([EMAIL PROTECTED] [130.159.184.55])
        by smtphost.cis.strath.ac.uk (8.13.3/8.13.3/Debian-6) with ESMTP id 
j4DGKsSX003721
        (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT);
        Fri, 13 May 2005 17:20:54 +0100
Received: from kd by napier-01.cis.strath.ac.uk with local (Exim 4.50)
        id 1DWcuE-0002Pb-MO; Fri, 13 May 2005 17:20:54 +0100
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Kenny Duffus <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: autopsy: #304675 and #291548, #291550 make this unusable
X-Mailer: reportbug 3.12
Date: Fri, 13 May 2005 17:20:54 +0100
Message-Id: <[EMAIL PROTECTED]>
X-CIS-MailScanner: Found to be clean
X-CIS-MailScanner-SpamCheck: not spam (whitelisted), SpamAssassin (score=0,
        required 6, autolearn=disabled)
X-CIS-MailScanner-From: [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: autopsy
Version: 2.05-0.1
Severity: grave
Justification: renders package unusable

#304675 is caused by this package being so old compared to the sleuthkit
version now in sarge, these packages are designed to work with each
other.  autopsy 2.04 was changed quite a bit for sleuthkit 2.xx,
these versions are designed to work together so autopsy needs
to be upgraded aswell.

autopsy 2.05 was released over a month ago fixing a few bugs in 2.04, so
replacing 2.03 with 2.05 would make more sense.

#291550 makes it impossible to use autopsy for forensic analysis as you
can't generate hashes to prove data hasn't been changed.

#291548 means you are unable to use a very usefull part of autopsy

---------------------------------------
Received: (at 308990-close) by bugs.debian.org; 19 May 2005 21:39:55 +0000
>From [EMAIL PROTECTED] Thu May 19 14:39:55 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 1DYskE-0000T3-00; Thu, 19 May 2005 14:39:55 -0700
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
        id 1DYscs-0008OI-00; Thu, 19 May 2005 17:32:18 -0400
From: Lorenzo Martignoni <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.55 $
Subject: Bug#308990: fixed in autopsy 2.05-1
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Thu, 19 May 2005 17:32:18 -0400
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: autopsy
Source-Version: 2.05-1

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

autopsy_2.05-1.diff.gz
  to pool/main/a/autopsy/autopsy_2.05-1.diff.gz
autopsy_2.05-1.dsc
  to pool/main/a/autopsy/autopsy_2.05-1.dsc
autopsy_2.05-1_all.deb
  to pool/main/a/autopsy/autopsy_2.05-1_all.deb
autopsy_2.05.orig.tar.gz
  to pool/main/a/autopsy/autopsy_2.05.orig.tar.gz



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.
Lorenzo Martignoni <[EMAIL PROTECTED]> (supplier of updated autopsy 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: Thu, 19 May 2005 23:11:55 +0200
Source: autopsy
Binary: autopsy
Architecture: source all
Version: 2.05-1
Distribution: unstable
Urgency: high
Maintainer: Lorenzo Martignoni <[EMAIL PROTECTED]>
Changed-By: Lorenzo Martignoni <[EMAIL PROTECTED]>
Description: 
 autopsy    - graphical interface to TASK
Closes: 308990
Changes: 
 autopsy (2.05-1) unstable; urgency=high
 .
   * New upstream release (Closes: #308990)
Files: 
 54a2cffd3e03319b2e7de2782afe0cdd 591 admin optional autopsy_2.05-1.dsc
 adfbb31ce665cc8efdbf8711bbd97483 381966 admin optional autopsy_2.05.orig.tar.gz
 736a766c3afef24c5f3ceba6436b45d9 6895 admin optional autopsy_2.05-1.diff.gz
 114f1844554afd7223be242cdbe5614d 375480 admin optional autopsy_2.05-1_all.deb

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

iD8DBQFCjQFUbFctcIsUOXURAuvaAJwJE8V7YH4ZYoU9mEoGdyezrOp7kQCfZ8ST
Z+zypLAbA4cQGhjpsC67N/0=
=nDUZ
-----END PGP SIGNATURE-----


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

Reply via email to