Your message dated Sat, 22 Oct 2005 13:34:00 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#334999: fixed in monotone 0.23-3
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; 21 Oct 2005 11:54:34 +0000
>From [EMAIL PROTECTED] Fri Oct 21 04:54:34 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mail.lenk.info [217.160.183.176] 
        by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
        id 1ESvTm-00060a-00; Fri, 21 Oct 2005 04:54:34 -0700
Received: from smtp.lenk.info ([82.165.24.235] ident=Debian-exim)
        by mail.lenk.info with esmtpsa 
        (Cipher TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.50 1)
        id 1ESvUO-0008BB-EJ
        for <[EMAIL PROTECTED]>; Fri, 21 Oct 2005 13:55:12 +0200
Received: from p54a3f9f3.dip.t-dialin.net ([84.163.249.243] 
helo=feynman.djpig.de)
        by smtp.lenk.info with esmtpsa 
        (Cipher TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.50 1)
        id 1ESvTk-0007LL-Rf
        for <[EMAIL PROTECTED]>; Fri, 21 Oct 2005 13:54:34 +0200
Received: from djpig by feynman.djpig.de with local (Exim 4.54)
        id 1ESvTe-000483-GI
        for [EMAIL PROTECTED]; Fri, 21 Oct 2005 13:54:26 +0200
Date: Fri, 21 Oct 2005 13:54:26 +0200
From: Frank Lichtenheld <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: FTBFS on arm/hppa/m68k: please use g++-3.4
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.9i
Sender: Frank Lichtenheld <[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-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

Subject: FTBFS on arm/hppa/m68k with ICE, please use gcc-3.4 there
Package: monotone
Version: 0.23-1
Severity: serious

monotone suffers from a very usual GCC 4.0 ICE on arm (and probably
hppa and m68k, but they didn't reach this point yet).
Please try to use gcc-3.4 on these architectures to work around it.

See http://lists.debian.org/debian-devel/2005/09/msg00020.html
for more information.

Gruesse,
        Frank Lichtenheld

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-1-k7
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
-- 
Frank Lichtenheld <[EMAIL PROTECTED]>
www: http://www.djpig.de/

---------------------------------------
Received: (at 334999-close) by bugs.debian.org; 22 Oct 2005 20:47:47 +0000
>From [EMAIL PROTECTED] Sat Oct 22 13:47:47 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
        id 1ETQ40-0002hQ-00; Sat, 22 Oct 2005 13:34:00 -0700
From: Tomas Fasth <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#334999: fixed in monotone 0.23-3
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Sat, 22 Oct 2005 13:34:00 -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=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02

Source: monotone
Source-Version: 0.23-3

We believe that the bug you reported is fixed in the latest version of
monotone, which is due to be installed in the Debian FTP archive:

monotone_0.23-3.diff.gz
  to pool/main/m/monotone/monotone_0.23-3.diff.gz
monotone_0.23-3.dsc
  to pool/main/m/monotone/monotone_0.23-3.dsc
monotone_0.23-3_i386.deb
  to pool/main/m/monotone/monotone_0.23-3_i386.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.
Tomas Fasth <[EMAIL PROTECTED]> (supplier of updated monotone 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: Sat, 22 Oct 2005 16:46:26 +0000
Source: monotone
Binary: monotone
Architecture: source i386
Version: 0.23-3
Distribution: unstable
Urgency: low
Maintainer: Tomas Fasth <[EMAIL PROTECTED]>
Changed-By: Tomas Fasth <[EMAIL PROTECTED]>
Description: 
 monotone   - A distributed version (revision) control system
Closes: 334999
Changes: 
 monotone (0.23-3) unstable; urgency=low
 .
   * The build script is now configured to explicitly use g++-3.4 for arm,
     hppa and m68k architectures as requested by Frank Lichtenheld.
   * Closes: #334999: FTBFS on arm/hppa/m68k: please use g++-3.4
Files: 
 1ccc2673867dfcd46b07bcaa329bade0 766 devel optional monotone_0.23-3.dsc
 cf65bc66d110224edf92fb0e7e85da8f 3306 devel optional monotone_0.23-3.diff.gz
 5dc5abc6c4d26e3172bb9901b8df96fa 3747602 devel optional 
monotone_0.23-3_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDWoFMwYdzVZ/o1QQRApljAJ9JFArqufX2PYdQTjmxMdfdALrRFgCfW5ii
KpzU/CvXMS8mq3rNxtiVKb4=
=x0MF
-----END PGP SIGNATURE-----


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

Reply via email to