Your message dated Wed, 20 Jul 2005 22:48:17 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in 3.4.2-5
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; 4 Jun 2005 12:00:30 +0000
>From [EMAIL PROTECTED] Sat Jun 04 05:00:30 2005
Return-path: <[EMAIL PROTECTED]>
Received: from pop-canoe.atl.sa.earthlink.net [207.69.195.66] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DeXKI-0003UR-00; Sat, 04 Jun 2005 05:00:30 -0700
Received: from user-0ce2kt7.cable.mindspring.com ([24.225.83.167] 
helo=localhost.localdomain)
        by pop-canoe.atl.sa.earthlink.net with esmtp (Exim 3.36 #10)
        id 1DeXKI-00055r-00; Sat, 04 Jun 2005 08:00:30 -0400
Received: from jonathan by localhost.localdomain with local (Exim 4.50)
        id 1DeXKH-0001E2-M4; Sat, 04 Jun 2005 08:00:29 -0400
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Jonathan Brandmeyer <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: bittorrent-gui: 297824 still alive (dangling symlinks)
X-Mailer: reportbug 3.12
Date: Sat, 04 Jun 2005 08:00:29 -0400
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-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: bittorrent-gui
Version: 3.4.2-4
Severity: important


After upgrading bittorrent-gui last night, this morning's Cron run shows
that /usr/share/man/man1/btcompletedirgui.1.gz is a dangling symlink.  I
was not getting this warning before the upgrade.

Tagging as important for consistancy with the last round of reports on
this issue.

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11.6-jdb
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages bittorrent-gui depends on:
ii  bittorrent                    3.4.2-4    Scatter-gather network file transf
ii  libwxgtk2.4-python            2.4.3.1    wxWindows Cross-platform C++ GUI t
ii  python                        2.3.5-2    An interactive high-level object-o

-- no debconf information

---------------------------------------
Received: (at 311933-close) by bugs.debian.org; 21 Jul 2005 03:40:00 +0000
>From [EMAIL PROTECTED] Wed Jul 20 20:40:00 2005
Return-path: <[EMAIL PROTECTED]>
Received: from base0.net (nene.base0.net) [69.93.91.90] 
        by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
        id 1DvRui-0004tq-00; Wed, 20 Jul 2005 20:40:00 -0700
Received: by nene.base0.net (Postfix, from userid 1000)
        id 7AC576E8007; Wed, 20 Jul 2005 22:48:17 -0500 (CDT)
Date: Wed, 20 Jul 2005 22:48:17 -0500
From: Michael Janssen <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Fixed in 3.4.2-5
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-NoSPAM: I don't want spam. EVER.
User-Agent: Mutt/1.5.9i
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=-3.0 required=4.0 tests=BAYES_00 autolearn=no 
        version=2.60-bugs.debian.org_2005_01_02
X-CrossAssassin-Score: 2


Both of these bugs were fixed in 3.4.2-5, but I failed to put the
Closes: int he changelog, so I am closing them this way. 

-- 
Michael Janssen --- Jamuraa --- [EMAIL PROTECTED] --- [EMAIL PROTECTED]


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

Reply via email to