Your message dated Fri, 9 Dec 2005 15:33:35 +0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#342381: qterm - FTBFS: error: unknown escape sequence '\='
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; 7 Dec 2005 16:43:36 +0000
>From [EMAIL PROTECTED] Wed Dec 07 08:43:36 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mx02.uni-tuebingen.de ([134.2.3.12])
by spohr.debian.org with esmtp (Exim 4.50)
id 1Ek2OF-00072l-VB
for [EMAIL PROTECTED]; Wed, 07 Dec 2005 08:43:36 -0800
Received: from mobilewave.waldi.eu.org (vpn0254.extern.uni-tuebingen.de
[134.2.165.4])
by mx02.uni-tuebingen.de (8.12.3/8.12.3) with ESMTP id jB7GhYkQ009617
for <[EMAIL PROTECTED]>; Wed, 7 Dec 2005 17:43:34 +0100
Received: by mobilewave.waldi.eu.org (Postfix, from userid 1000)
id 805FD184A5; Wed, 7 Dec 2005 17:43:52 +0100 (CET)
Date: Wed, 7 Dec 2005 17:43:52 +0100
From: Bastian Blank <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: qterm - FTBFS: error: unknown escape sequence '\='
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.5.11
X-AntiVirus: checked by AntiVir Milter (version: 1.1.0-7; AVE: 6.33.0.11; VDF:
6.33.0.11; host: mx02)
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: qterm
Version: 0.4.0pre3-2+b1
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of qterm_0.4.0pre3-2+b1 on debian-31 by sbuild/s390 79
[...]
> if g++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/share/qt3/include
> -I/usr/X11R6/include -I/usr/include/python2.3 -I/usr/include/kde/arts
> -I/usr/include -DQT_THREAD_SUPPORT -D_REENTRANT -Wnon-virtual-dtor
> -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align
> -Wconversion -Wchar-subscripts -Wall -W -Wpointer-arith -Wwrite-strings -O2
> -g -Wall -O2 -Wformat-security -Wmissing-format-attribute -fno-exceptions
> -fno-check-new -fno-common -I/usr/include -I/usr/share/qt3/include
> -I/usr/X11R6/include -MT qtermhttp.o -MD -MP -MF ".deps/qtermhttp.Tpo" \
> -c -o qtermhttp.o `test -f 'qtermhttp.cpp' || echo './'`qtermhttp.cpp; \
> then mv -f ".deps/qtermhttp.Tpo" ".deps/qtermhttp.Po"; \
> else rm -f ".deps/qtermhttp.Tpo"; exit 1; \
> fi
> /usr/share/qt3/include/qnetworkprotocol.h:58: warning: 'class
> QNetworkProtocolFactoryBase' has virtual functions but non-virtual destructor
> qtermhttp.cpp: In member function 'void QTermHttp::httpResponse(const
> QHttpResponseHeader&)':
> qtermhttp.cpp:94: error: unknown escape sequence '\='
> qtermhttp.cpp:112: warning: comparison between signed and unsigned integer
> expressions
> make[4]: *** [qtermhttp.o] Error 1
> make[4]: Leaving directory `/build/buildd/qterm-0.4.0pre3/qterm'
> make[3]: *** [all-recursive] Error 1
> make[3]: Leaving directory `/build/buildd/qterm-0.4.0pre3/qterm'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory `/build/buildd/qterm-0.4.0pre3'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/build/buildd/qterm-0.4.0pre3'
> make: *** [debian/stamp-makefile-build] Error 2
> ******************************************************************************
> Build finished at 20051205-0108
> FAILED [dpkg-buildpackage died]
Bastian
---------------------------------------
Received: (at 342381-done) by bugs.debian.org; 9 Dec 2005 07:33:36 +0000
>From [EMAIL PROTECTED] Thu Dec 08 23:33:36 2005
Return-path: <[EMAIL PROTECTED]>
Received: from zproxy.gmail.com ([64.233.162.205])
by spohr.debian.org with esmtp (Exim 4.50)
id 1Ekcl6-0004wt-LQ
for [EMAIL PROTECTED]; Thu, 08 Dec 2005 23:33:36 -0800
Received: by zproxy.gmail.com with SMTP id l1so848899nzf
for <[EMAIL PROTECTED]>; Thu, 08 Dec 2005 23:33:36 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=beta; d=gmail.com;
h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
b=g2LCzfKAWzH6I32tWiY3u7uAy50TAt2GRrYlgNIdMN2dWwzjBvwwnWP+WX7mSfB3CkbrAVMiUaYCHXwz0wseS1t2F8S5aV7SMbYnfgN8wQDgMuZXpFItrtxqgClEEoqPHXUENvvD+kxEnlU9efUrXGgc01wPXr1s2WhhYe10V/Y=
Received: by 10.36.227.80 with SMTP id z80mr3244106nzg;
Thu, 08 Dec 2005 23:33:35 -0800 (PST)
Received: by 10.36.178.8 with HTTP; Thu, 8 Dec 2005 23:33:35 -0800 (PST)
Message-ID: <[EMAIL PROTECTED]>
Date: Fri, 9 Dec 2005 15:33:35 +0800
From: LI Daobing <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Bug#342381: qterm - FTBFS: error: unknown escape sequence '\='
In-Reply-To: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[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=-5.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER,
RCVD_IN_BL_SPAMCOP_NET autolearn=no
version=2.60-bugs.debian.org_2005_01_02
On 12/9/05, Adeodato Sim=F3 <[EMAIL PROTECTED]> wrote:
> FWIW, this failure is caused only by g++_4.0.2-4. If you closely watch
> a build of 0.4.0pre3-2 with g++_4.0.2-5, the same warning about \=3D is
> emitted, but the build succeeds.
>
> So, this upload is really not necessary: qterm will get rescheduled to
> build when all buildds have g++_4.0.2-5 installed. But you may as well
> proceed: it really seems it builds fine with -4 and the patch applied.
> (Odd.)
>
confirm that g++_4.0.2-5 works well, so I close this bug.
--
LI Daobing
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
