Your message dated Wed, 28 Dec 2005 23:47:05 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#345010: fixed in tkdiff 1:4.0.2-1sarge1
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; 28 Dec 2005 13:14:13 +0000
>From [EMAIL PROTECTED] Wed Dec 28 05:14:13 2005
Return-path: <[EMAIL PROTECTED]>
Received: from smtp-vbr11.xs4all.nl ([194.109.24.31])
by spohr.debian.org with esmtp (Exim 4.50)
id 1Erb89-0006Oo-J5
for [EMAIL PROTECTED]; Wed, 28 Dec 2005 05:14:13 -0800
Received: from zeno.lan (coopernet.xs4all.nl [80.127.52.47])
by smtp-vbr11.xs4all.nl (8.13.3/8.13.3) with ESMTP id jBSDEAE8094729
for <[EMAIL PROTECTED]>; Wed, 28 Dec 2005 14:14:10 +0100 (CET)
(envelope-from [EMAIL PROTECTED])
Received: from hkuiper by zeno.lan with local (Exim 4.50)
id 1Erb88-0001JE-8v
for [EMAIL PROTECTED]; Wed, 28 Dec 2005 14:14:12 +0100
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: tkdiff: Tkdiff broken in 4.0.2-1sarge0 (security update)
X-Debbugs-CC: H. Kuiper <[EMAIL PROTECTED]>
From: "H. Kuiper" <[EMAIL PROTECTED]>
Date: 28 Dec 2005 14:14:12 +0100
Message-ID: <[EMAIL PROTECTED]>
Lines: 52
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Virus-Scanned: by XS4ALL Virus Scanner
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=-11.0 required=4.0 tests=BAYES_00,HAS_PACKAGE,
X_DEBBUGS_CC autolearn=ham version=2.60-bugs.debian.org_2005_01_02
Package: tkdiff
Version: 1:4.0.2-1sarge0
Severity: grave
When I run tkdiff from tkcvs I get the following error:
Error in startup script: can not find channel named "fid"
while executing
"close fid"
(procedure "tmpfile" line 11)
invoked from within
"tmpfile $index"
(procedure "get-file-rev" line 30)
invoked from within
"get-file-rev "$f" 1"
(procedure "init-files" line 149)
invoked from within
"init-files"
(procedure "check-error" line 22)
invoked from within
"check-error $result $output"
(procedure "do-new-diff" line 23)
invoked from within
"do-new-diff"
("eval" body line 1)
invoked from within
"eval do-new-diff"
(procedure "main" line 56)
invoked from within
"main"
(file "/usr/bin/tkdiff" line 10332)
This looks like the same problem reported in November for
4.0.2-2. Maybe the wrong package version ended up on
security.debian.org?
Thanks,
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.14
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages tkdiff depends on:
ii tk8.4 8.4.9-1 Tk toolkit for Tcl and X11, v8.4 -
-- no debconf information
--
Harry Kuiper [EMAIL PROTECTED]
Haarlem, The Netherlands
---------------------------------------
Received: (at 345010-close) by bugs.debian.org; 29 Dec 2005 07:50:45 +0000
>From [EMAIL PROTECTED] Wed Dec 28 23:50:45 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 4.50)
id 1ErsV7-0003h1-Sk; Wed, 28 Dec 2005 23:47:05 -0800
From: Adrian Bridgett <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.65 $
Subject: Bug#345010: fixed in tkdiff 1:4.0.2-1sarge1
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Wed, 28 Dec 2005 23:47:05 -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
Source: tkdiff
Source-Version: 1:4.0.2-1sarge1
We believe that the bug you reported is fixed in the latest version of
tkdiff, which is due to be installed in the Debian FTP archive:
tkdiff_4.0.2-1sarge1.diff.gz
to pool/main/t/tkdiff/tkdiff_4.0.2-1sarge1.diff.gz
tkdiff_4.0.2-1sarge1.dsc
to pool/main/t/tkdiff/tkdiff_4.0.2-1sarge1.dsc
tkdiff_4.0.2-1sarge1_all.deb
to pool/main/t/tkdiff/tkdiff_4.0.2-1sarge1_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.
Adrian Bridgett <[EMAIL PROTECTED]> (supplier of updated tkdiff 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: Wed, 28 Dec 2005 17:34:57 +0000
Source: tkdiff
Binary: tkdiff
Architecture: source all
Version: 1:4.0.2-1sarge1
Distribution: stable-security
Urgency: high
Maintainer: Adrian Bridgett <[EMAIL PROTECTED]>
Changed-By: Adrian Bridgett <[EMAIL PROTECTED]>
Description:
tkdiff - graphical side by side "diff" utility
Closes: 345010
Changes:
tkdiff (1:4.0.2-1sarge1) stable-security; urgency=high
.
* working fix from tkdiff-4.0.2-4 rather than my earlier broken
one that Steve used (closes: #345010)
* Fix insecure temporary file usage. [CVE-2005-3343].
Files:
e7f0e00f3690e6d068a8c99bf5580b63 571 text optional tkdiff_4.0.2-1sarge1.dsc
a03c42f6a6187b0e0ad93ce0fab105c8 4337 text optional
tkdiff_4.0.2-1sarge1.diff.gz
262e45adcc1e6c73d2f14727520e984d 85536 text optional
tkdiff_4.0.2-1sarge1_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFDssxUflgj9+6E5x0RAoCnAJ9ngWKWO58T/riJbFKx2X7cZr7wQQCgxf5I
e/rMAEinMdSFDpFTM7wd+fA=
=8APB
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
