Your message dated Thu, 31 Mar 2005 07:03:08 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#293797: fixed
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; 5 Feb 2005 20:06:29 +0000
>From [EMAIL PROTECTED] Sat Feb 05 12:06:29 2005
Return-path: <[EMAIL PROTECTED]>
Received: from (boa.b9.com) [216.184.11.2] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1CxWCK-0006Ax-00; Sat, 05 Feb 2005 12:06:28 -0800
Received: from tiger.med-info.com (tiger.med-info.com [216.184.11.129])
        by boa.b9.com (8.13.2/8.13.2/Debian-1) with SMTP id j15K5BFA014369;
        Sat, 5 Feb 2005 13:05:11 -0700
Received: from tiger.med-info.com ([EMAIL PROTECTED] [127.0.0.1])
        by tiger.med-info.com (8.13.3/8.13.3/Debian-5) with ESMTP id 
j15K5Btm017691
        (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
        Sat, 5 Feb 2005 13:05:11 -0700
Received: (from [EMAIL PROTECTED])
        by tiger.med-info.com (8.13.3/8.13.3/Submit) id j15K5A6d017688;
        Sat, 5 Feb 2005 13:05:10 -0700
Message-Id: <[EMAIL PROTECTED]>
X-Authentication-Warning: tiger.med-info.com: kevin set sender to [EMAIL 
PROTECTED] using -f
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: "Kevin M. Rosenberg" <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: ftp.debian.org: Please remove SBCL binary packages for mips and mipsel
X-Mailer: reportbug 3.7.1
Date: Sat, 05 Feb 2005 13:05:10 -0700
X-Scanned-By: MIMEDefang 2.48 on 172.16.1.2
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: ftp.debian.org
Severity: normal


I also sent an email to James Troup to add AMD64 to P-A-S for SBCL and
also explained why the SBCL binary packages for mips and mipsel should
be removed. I'm quoting it below:

Thanks!

==============================================================

Hi James,

I've helped upstream add AMD64 support to the SBCL source package.
It's now in the alioth amd64 distribution.

Would you please add amd64 to the SBCL entry. Also, upstream sbcl has been
broken[1] on mips/mipsel for about 5 months. There are no plans to fix
this. Would you remove mips and mipsel from the entry as well?

I'll file a bug report against ftp.debian.org to remove the binary
packages so that newer versions of sbcl can migrate to testing.

Thanks,

Kevin

[1] Specifically, sbcl seems to have a cache flushing problem on
mips/mipsel. So that builds only succeed about 10% of the time.
 



-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

---------------------------------------
Received: (at 293797-close) by bugs.debian.org; 31 Mar 2005 12:10:31 +0000
>From [EMAIL PROTECTED] Thu Mar 31 04:10:31 2005
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DGyVL-0002jw-00; Thu, 31 Mar 2005 04:10:31 -0800
Received: from jeroen by newraff.debian.org with local (Exim 3.35 1 (Debian))
        id 1DGyOC-000335-00; Thu, 31 Mar 2005 07:03:08 -0500
From: Debian Archive Maintenance <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: melanie $Revision: 1.43 $
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED] 
Subject: Bug#293797: fixed
Message-Id: <[EMAIL PROTECTED]>
Sender: Jeroen van Wolffelaar <[EMAIL PROTECTED]>
Date: Thu, 31 Mar 2005 07:03:08 -0500
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=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

      sbcl | 1:0.8.17-2 | mips
      sbcl | 1:0.8.19.10-1 | mipsel

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive (ftp-master.debian.org) and will not propagate to any
mirrors (ftp.debian.org included) until the next cron.daily run at the
earliest.

Packages are never removed from testing by hand.  Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED]

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[EMAIL PROTECTED]

Debian distribution maintenance software
pp.
Jeroen van Wolffelaar (the ftpmaster behind the curtain)


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

Reply via email to