Your message dated Fri, 22 Nov 2002 21:17:11 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#163531: fixed in ubit 2.6.0-2
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; 6 Oct 2002 14:58:39 +0000
>From [EMAIL PROTECTED] Sun Oct 06 09:58:39 2002
Return-path: <[EMAIL PROTECTED]>
Received: from atlrel6.hp.com [156.153.255.205] 
        by master.debian.org with esmtp (Exim 3.12 1 (Debian))
        id 17yCrf-00047X-00; Sun, 06 Oct 2002 09:58:39 -0500
Received: from debian.fc.hp.com (whatone.fc.hp.com [15.238.0.60])
        by atlrel6.hp.com (Postfix) with ESMTP id AC4A8202
        for <[EMAIL PROTECTED]>; Sun,  6 Oct 2002 10:58:38 -0400 (EDT)
Received: by debian.fc.hp.com (Postfix, from userid 1000)
        id 8C0971D4825; Sun,  6 Oct 2002 08:58:38 -0600 (MDT)
Date: Sun, 6 Oct 2002 08:58:38 -0600
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: ubit_2.6.0-1(hppa/unstable): FTBFS: g++ 3.0 errors
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.25i
Delivered-To: [EMAIL PROTECTED]

Package: ubit
Version: 2.6.0-1
Severity: serious

There was an error while trying to autobuild your package:

Build fails with g++ errors, the first of which isbelow.

lamont

> Automatic build of ubit_2.6.0-1 on sarti by sbuild/hppa 1.169
> Build started at 20021006-0830

[...]

> ** Using build dependencies supplied by package:
> Build-Depends: debhelper (>= 4), libungif4-dev, xlibs-dev

[...]

> Making all in src
> make[3]: Entering directory `/build/buildd/ubit-2.6.0/src'
> /bin/sh ../libtool --mode=compile c++ -DHAVE_CONFIG_H -I. -I. -I..     
> -I/usr/X11R6/include -O2 -Wall -ffast-math -fomit-frame-pointer 
> -fexpensive-optimizations -fstrict-aliasing -funroll-loops -c uuappli.cc
> mkdir .libs
> c++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/X11R6/include -O2 -Wall -ffast-math 
> -fomit-frame-pointer -fexpensive-optimizations -fstrict-aliasing 
> -funroll-loops -c uuappli.cc  -fPIC -DPIC -o .libs/uuappli.lo
> In file included from uuappli.cc:47:
> uedit.hh:137: friend declaration requires class-key, i.e. `friend class 
> UAppli'
> uedit.hh:138: friend declaration requires class-key, i.e. `friend class UStr'
> make[3]: *** [uuappli.lo] Error 1
> make[3]: Leaving directory `/build/buildd/ubit-2.6.0/src'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory `/build/buildd/ubit-2.6.0'
> make[1]: *** [all-recursive-am] Error 2
> make[1]: Leaving directory `/build/buildd/ubit-2.6.0'
> make: *** [build-stamp] Error 2

A full build log can be found at:
http://buildd.debian.org/build.php?arch=hppa&pkg=ubit&ver=2.6.0-1


---------------------------------------
Received: (at 163531-close) by bugs.debian.org; 23 Nov 2002 02:23:11 +0000
>From [EMAIL PROTECTED] Fri Nov 22 20:23:02 2002
Return-path: <[EMAIL PROTECTED]>
Received: from auric.debian.org [206.246.226.45] (mail)
        by master.debian.org with esmtp (Exim 3.12 1 (Debian))
        id 18FPwk-0005rO-00; Fri, 22 Nov 2002 20:23:02 -0600
Received: from katie by auric.debian.org with local (Exim 3.35 1 (Debian))
        id 18FPr5-00057i-00; Fri, 22 Nov 2002 21:17:11 -0500
From: Rene Engelhard <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.28 $
Subject: Bug#163531: fixed in ubit 2.6.0-2
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Fri, 22 Nov 2002 21:17:11 -0500
Delivered-To: [EMAIL PROTECTED]

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

libubit-dev_2.6.0-2_i386.deb
  to pool/main/u/ubit/libubit-dev_2.6.0-2_i386.deb
libubit2.6.0_2.6.0-2_i386.deb
  to pool/main/u/ubit/libubit2.6.0_2.6.0-2_i386.deb
ubit_2.6.0-2.diff.gz
  to pool/main/u/ubit/ubit_2.6.0-2.diff.gz
ubit_2.6.0-2.dsc
  to pool/main/u/ubit/ubit_2.6.0-2.dsc



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.
Rene Engelhard <[EMAIL PROTECTED]> (supplier of updated ubit 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, 23 Nov 2002 02:21:59 +0100
Source: ubit
Binary: libubit2.6.0 libubit-dev
Architecture: source i386
Version: 2.6.0-2
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group <[EMAIL PROTECTED]>
Changed-By: Rene Engelhard <[EMAIL PROTECTED]>
Description: 
 libubit-dev - Development files for libubit2.6.0
 libubit2.6.0 - Ubiquitous Brick Interactive Toolkit
Closes: 163531
Changes: 
 ubit (2.6.0-2) unstable; urgency=low
 .
   * QA upload
   * Added patch fixing compilation with newer g++'s and changed 'friend'
     to 'friend class' on 2 places (closes: #163531)
Files: 
 ce87891c80bf50d2fe32ff65cfc7fa96 600 libs optional ubit_2.6.0-2.dsc
 53dc3b6e3b3fc6f77e3e0f12cd5748ea 5012 libs optional ubit_2.6.0-2.diff.gz
 f6f851886a1b0f7db8cc835d8aac2218 260428 libs optional 
libubit2.6.0_2.6.0-2_i386.deb
 ab3f633acd71736e349c44cd9f2bf9f4 356680 devel optional 
libubit-dev_2.6.0-2_i386.deb

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

iD8DBQE93uKw+FmQsCSK63MRArNJAJ94ygGlC+krfpuAT8RuHr7f8xHMlQCeP6Gf
xEQb+Hmqt2nyTpGdXldj1HA=
=xLV7
-----END PGP SIGNATURE-----

Reply via email to