Your message dated Sat, 04 Feb 2006 15:28:36 -0500
with message-id <[EMAIL PROTECTED]>
and subject line (no subject)
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)
--- Begin Message ---
>From [EMAIL PROTECTED] Thu Aug 11 03:07:55 2005
Received: (at submit) by bugs.debian.org; 11 Aug 2005 10:07:55 +0000
Return-path: <[EMAIL PROTECTED]>
Received: from ylpvm43-ext.prodigy.net (ylpvm43.prodigy.net) [207.115.57.74]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1E39yd-0001A7-00; Thu, 11 Aug 2005 03:07:55 -0700
Received: from pimout1-ext.prodigy.net (pimout1-int.prodigy.net [207.115.5.65])
by ylpvm43.prodigy.net (8.12.10 outbound/8.12.10) with ESMTP id
j7BA7xfU013093
for <[EMAIL PROTECTED]>; Thu, 11 Aug 2005 06:08:00 -0400
X-ORBL: [69.226.148.8]
Received: from [127.0.0.1] (adsl-69-226-148-8.dsl.sndg02.pacbell.net
[69.226.148.8])
by pimout1-ext.prodigy.net (8.13.4 outbound domainkey aix/8.13.4) with
ESMTP id j7BA7p4V214992;
Thu, 11 Aug 2005 06:07:51 -0400
Message-Id: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Max <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: mmv is unusable bacause of constant hangs / segmentation fault
X-Mailer: reportbug 3.15
Date: Thu, 11 Aug 2005 03:04:26 -0700
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=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Package: mmv
Version: 1.01b-12.1
Severity: grave
Justification: renders package unusable
Under debian-amd64 mmv 1.01b-12.1 constantly segfaults.
Even when run without parameters or with --help:
$ mmv
Segmentation fault
Under debian-i386 mmv 1.01b-12.1 does not segfault but hangs on any input.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12.2.64
Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R)
Versions of packages mmv depends on:
ii libc6 2.3.5-3 GNU C Library: Shared libraries an
mmv recommends no packages.
-- debconf-show failed
--- End Message ---
--- Begin Message ---
>From [EMAIL PROTECTED] Sat Feb 04 12:28:44 2006
Received: (at 322541-done) by bugs.debian.org; 4 Feb 2006 20:28:44 +0000
Return-path: <[EMAIL PROTECTED]>
Received: from sojourner.alienhosting.com ([216.40.217.206])
by spohr.debian.org with esmtp (Exim 4.50)
id 1F5U1U-0005Sq-E5
for [EMAIL PROTECTED]; Sat, 04 Feb 2006 12:28:44 -0800
Received: from [192.168.1.60] (c-24-34-119-11.hsd1.ma.comcast.net
[24.34.119.11])
(authenticated bits=0)
by sojourner.alienhosting.com (8.12.11/8.12.11) with ESMTP id
k14KSgHX023159
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
for <[EMAIL PROTECTED]>; Sat, 4 Feb 2006 15:28:43 -0500
Message-ID: <[EMAIL PROTECTED]>
Date: Sat, 04 Feb 2006 15:28:36 -0500
From: Ari Pollak <[EMAIL PROTECTED]>
User-Agent: Debian Thunderbird 1.0.7 (X11/20051017)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: [EMAIL PROTECTED]
Subject: (no subject)
X-Enigmail-Version: 0.93.0.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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=-2.0 required=4.0 tests=BAYES_00,RCVD_IN_SORBS
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Version: 4.0.2-3
It seems this was actually fixed some time before November 20th, 2005,
without me noticing. I assume a different bug was related to this one.
--- End Message ---