Your message dated Sat, 5 Feb 2005 17:22:21 -0800
with message-id <[EMAIL PROTECTED]>
and subject line closing
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 Jan 2004 16:45:38 +0000
>From [EMAIL PROTECTED] Tue Jan 13 10:45:37 2004
Return-path: <[EMAIL PROTECTED]>
Received: from mail.physik.uni-muenchen.de [192.54.42.129]
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1AgMct-0000UV-00; Tue, 13 Jan 2004 05:22:27 -0600
Received: from localhost (unknown [127.0.0.1])
by mail.physik.uni-muenchen.de (Postfix) with ESMTP id 5645F20215
for <[EMAIL PROTECTED]>; Tue, 13 Jan 2004 11:22:26 +0000 (UTC)
Received: from mail.physik.uni-muenchen.de ([127.0.0.1])
by localhost (mail.physik.uni-muenchen.de [127.0.0.1]) (amavisd-new, port
10024)
with LMTP id 09056-01 for <[EMAIL PROTECTED]>;
Tue, 13 Jan 2004 12:22:05 +0100 (CET)
Received: from mailhost.cip.physik.uni-muenchen.de
(kaiser.cip.physik.uni-muenchen.de [141.84.136.1])
by mail.physik.uni-muenchen.de (Postfix) with ESMTP id 5F1F02021B
for <[EMAIL PROTECTED]>; Tue, 13 Jan 2004 12:21:32 +0100 (CET)
Received: from seekar.cip.physik.uni-muenchen.de
(seekar.cip.physik.uni-muenchen.de [141.84.136.52])
by mailhost.cip.physik.uni-muenchen.de (Postfix) with ESMTP id
4A84285113
for <[EMAIL PROTECTED]>; Tue, 13 Jan 2004 12:21:32 +0100 (CET)
Received: by seekar.cip.physik.uni-muenchen.de (Postfix, from userid 3092)
id 3BE4879FD; Tue, 13 Jan 2004 12:21:32 +0100 (CET)
Received: from localhost (localhost [127.0.0.1])
by seekar.cip.physik.uni-muenchen.de (Postfix) with ESMTP id 3987479FC
for <[EMAIL PROTECTED]>; Tue, 13 Jan 2004 12:21:32 +0100 (CET)
Date: Tue, 13 Jan 2004 12:21:32 +0100 (CET)
From: Thomas Fischbacher <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Wishlist: apt-get should be strace-able
Message-ID: <[EMAIL PROTECTED]>
X-BOFH: Daemons did it
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanned: by amavisd-new at physik.uni-muenchen.de
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin
2.60-master.debian.org_2003_11_25-bugs.debian.org_2004_01_13
(1.212-2003-09-23-exp) on master.debian.org
X-Spam-Status: No, hits=-5.0 required=4.0 tests=HAS_PACKAGE autolearn=no
version=2.60-master.debian.org_2003_11_25-bugs.debian.org_2004_01_13
X-Spam-Level:
Package: apt
Version: 0.5.14
Severity: wishlist
For some applications(*), it would be highly desirable(*) to obtain a list
of files that have been seen/touched/transformed as a result of an apt-get
update.
Unfortunately, an
strace -o apt.trace -f -e trace=files apt-get upgrade
causes the sub-processes dealing with the various access method protocols
to fail.
(*) While this clearly is a "wishlist" issue, It nevertheless should be
considered as important, since some people may want to use such a
mechanism to easily maintain a tripwire-like database.
--
regards, [EMAIL PROTECTED] (o_
Thomas Fischbacher - http://www.cip.physik.uni-muenchen.de/~tf //\
(lambda (n) ((lambda (p q r) (p p q r)) (lambda (g x y) V_/_
(if (= x 0) y (g g (- x 1) (* x y)))) n 1)) (Debian GNU)
---------------------------------------
Received: (at 227447-done) by bugs.debian.org; 6 Feb 2005 01:22:22 +0000
>From [EMAIL PROTECTED] Sat Feb 05 17:22:22 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mail21.sea5.speakeasy.net [69.17.117.23]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Cxb82-0001At-00; Sat, 05 Feb 2005 17:22:22 -0800
Received: (qmail 17410 invoked from network); 6 Feb 2005 01:22:22 -0000
Received: from gateway.sf.frob.com ([64.81.54.130])
(envelope-sender <[EMAIL PROTECTED]>)
by mail21.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP
for <[EMAIL PROTECTED]>; 6 Feb 2005 01:22:22 -0000
Received: from magilla.sf.frob.com (magilla.sf.frob.com [198.49.250.228])
by gateway.sf.frob.com (Postfix) with ESMTP id 6167D357B
for <[EMAIL PROTECTED]>; Sat, 5 Feb 2005 17:22:21 -0800 (PST)
Received: from magilla.sf.frob.com (localhost.localdomain [127.0.0.1])
by magilla.sf.frob.com (8.12.11/8.12.9) with ESMTP id j161ML2Q008159
for <[EMAIL PROTECTED]>; Sat, 5 Feb 2005 17:22:21 -0800
Received: (from [EMAIL PROTECTED])
by magilla.sf.frob.com (8.12.11/8.12.11/Submit) id j161MLJ6008156;
Sat, 5 Feb 2005 17:22:21 -0800
Date: Sat, 5 Feb 2005 17:22:21 -0800
Message-Id: <[EMAIL PROTECTED]>
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: closing
Emacs: no job too big... no job.
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=-0.4 required=4.0 tests=BAYES_00,NO_REAL_NAME,ONEWORD
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
I cannot reproduce any problem and this report is very old. If there is a
real problem, it needs be reported with exact details to reproduce it that
can be applied today.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
