Your message dated Tue, 8 Feb 2005 12:37:22 +1100
with message-id <[EMAIL PROTECTED]>
and subject line Debian bug #241715 (tripwire: Cannot read its generated report
file)
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; 2 Apr 2004 15:08:33 +0000
>From [EMAIL PROTECTED] Fri Apr 02 07:08:33 2004
Return-path: <[EMAIL PROTECTED]>
Received: from s4.uklinux.net (mail2.uklinux.net) [80.84.72.14]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1B9QHZ-0001jc-00; Fri, 02 Apr 2004 07:08:33 -0800
Received: from arcadia (adsl-static-1-21.uklinux.net [62.245.36.21])
by mail2.uklinux.net (Postfix) with ESMTP
id E0763409FBD; Fri, 2 Apr 2004 15:08:31 +0000 (UTC)
Received: by arcadia (Postfix, from userid 1000)
id 259AF2BEDA; Fri, 2 Apr 2004 16:09:21 +0100 (BST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Anthony Campbell <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: tripwire: Cannot read its generated report file
X-Mailer: reportbug 2.54
Date: Fri, 02 Apr 2004 16:09:20 +0100
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.5 required=4.0 tests=BAYES_01,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
Package: tripwire
Severity: normal
I installed and ran tripwire, to produce a report file in
/var/lib/tripwire/report/
The file is there and tripwire finds it, but says it cannot be opened
and then denies that it exists!
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.25
Locale: LANG=C, LC_CTYPE=C
---------------------------------------
Received: (at 241715-done) by bugs.debian.org; 8 Feb 2005 01:37:53 +0000
>From [EMAIL PROTECTED] Mon Feb 07 17:37:53 2005
Return-path: <[EMAIL PROTECTED]>
Received: from wproxy.gmail.com [64.233.184.194]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CyKK9-0000dt-00; Mon, 07 Feb 2005 17:37:53 -0800
Received: by wproxy.gmail.com with SMTP id 70so1999172wra
for <[EMAIL PROTECTED]>; Mon, 07 Feb 2005 17:37:22 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=beta; d=gmail.com;
h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references;
b=CczLdBGe+AoQ1f1hqaZ4SUerHa+KgpiveQiTO01xbQx6AnZFGrWcMoJSJUL6zTW+dbVBEGgWIvReIOloJ4YDHhBnfGSXa5blnStqn9FzyrePxxd+hxTWTltjf7g1caWl4JrpWl8AQ+Z1Us/0aNTU1pVCVrk2oQztJUvue5L8tCs=
Received: by 10.54.51.61 with SMTP id y61mr330008wry;
Mon, 07 Feb 2005 17:37:22 -0800 (PST)
Received: by 10.54.22.7 with HTTP; Mon, 7 Feb 2005 17:37:22 -0800 (PST)
Message-ID: <[EMAIL PROTECTED]>
Date: Tue, 8 Feb 2005 12:37:22 +1100
From: Nick Jenkins <[EMAIL PROTECTED]>
Reply-To: Nick Jenkins <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Debian bug #241715 (tripwire: Cannot read its generated report
file)
Cc: Anthony Campbell <[EMAIL PROTECTED]>
In-Reply-To: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <[EMAIL PROTECTED]>
<[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=-3.0 required=4.0 tests=BAYES_00 autolearn=no
version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
I think this report can be closed now. I sent a follow-up message to
Anthony, and received the reply shown below.
Cheers,
Nick.
> Thanks: I did manage to sort this out at the time. It was some
> misunderstanding on my part; I'm sorry I didn't inform you to close the
> bug. Actually I removed tripwire shortly afterwards because I found it
> wasn't suitable for a system like mine which I update very frequently
> from unstable.
>
> Best wishes,
>
> Anthony
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
