Your message dated Sun, 27 Nov 2005 08:17:05 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#339153: fixed in beast 0.6.6-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; 15 Nov 2005 06:55:28 +0000
>From [EMAIL PROTECTED] Mon Nov 14 22:55:27 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mail.cs.tu-berlin.de ([130.149.17.13] ident=root)
by spohr.debian.org with esmtp (Exim 4.50)
id 1Ebuj1-0006kW-Id
for [EMAIL PROTECTED]; Mon, 14 Nov 2005 22:55:27 -0800
Received: from mailhost.cs.tu-berlin.de ([EMAIL PROTECTED] [130.149.17.13])
by mail.cs.tu-berlin.de (8.9.3p2/8.9.3) with ESMTP id HAA25025
for <[EMAIL PROTECTED]>; Tue, 15 Nov 2005 07:55:25 +0100 (MET)
Received: from localhost (localhost [127.0.0.1])
by mailhost.cs.tu-berlin.de (Postfix) with ESMTP id 89BE2F212
for <[EMAIL PROTECTED]>; Tue, 15 Nov 2005 07:55:25 +0100 (MET)
Received: from mailhost.cs.tu-berlin.de ([127.0.0.1])
by localhost (bueno [127.0.0.1]) (amavisd-new, port 10224) with ESMTP
id 26075-20 for <[EMAIL PROTECTED]>;
Tue, 15 Nov 2005 07:55:25 +0100 (MET) 13910
Received: from bolero.cs.tu-berlin.de (bolero.cs.tu-berlin.de [130.149.19.1])
by mailhost.cs.tu-berlin.de (Postfix) with ESMTP
for <[EMAIL PROTECTED]>; Tue, 15 Nov 2005 07:55:25 +0100 (MET)
Received: (from [EMAIL PROTECTED])
by bolero.cs.tu-berlin.de (8.12.10+Sun/8.12.8/Submit) id jAF6tPUo008725
for [EMAIL PROTECTED]; Tue, 15 Nov 2005 07:55:25 +0100 (MET)
Date: Tue, 15 Nov 2005 07:55:25 +0100 (MET)
From: Matthias Klose <[EMAIL PROTECTED]>
Message-Id: <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: library package needs to be renamed (libstdc++ allocator change)
X-Virus-Scanned: by amavisd-new at cs.tu-berlin.de
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: beast
Severity: important
Please do not take any action before reading
http://lists.debian.org/debian-devel-announce/2005/11/msg00010.html
This bug report is filed against the source package which builds
a library depending on libstdc++6 and defining or referencing
*mt_alloc* symbols. The package has to be rebuilt with either
g++-4.0_4.0.2-4 or g++-3.4_3.4.4-10 (or newer). Please rename the
library package to a name with a "c2a" suffix, and adjust the build
dependencies if dependencies on another renamed library do exist.
Do *not* yet upload the package, but wait for a followup mail to this
bug report.
If this bug report is for some reason invalid, please close it with
a short reasoning.
---------------------------------------
Received: (at 339153-close) by bugs.debian.org; 27 Nov 2005 16:21:24 +0000
>From [EMAIL PROTECTED] Sun Nov 27 08:21:24 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 4.50)
id 1EgPD7-0002ZQ-SS; Sun, 27 Nov 2005 08:17:05 -0800
From: Sam Hocevar (Debian packages) <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.60 $
Subject: Bug#339153: fixed in beast 0.6.6-3
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Sun, 27 Nov 2005 08:17:05 -0800
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: beast
Source-Version: 0.6.6-3
We believe that the bug you reported is fixed in the latest version of
beast, which is due to be installed in the Debian FTP archive:
beast_0.6.6-3.diff.gz
to pool/main/b/beast/beast_0.6.6-3.diff.gz
beast_0.6.6-3.dsc
to pool/main/b/beast/beast_0.6.6-3.dsc
beast_0.6.6-3_i386.deb
to pool/main/b/beast/beast_0.6.6-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.
Sam Hocevar (Debian packages) <[EMAIL PROTECTED]> (supplier of updated beast
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: Sun, 27 Nov 2005 16:19:10 +0100
Source: beast
Binary: beast
Architecture: source i386
Version: 0.6.6-3
Distribution: unstable
Urgency: low
Maintainer: Sam Hocevar (Debian packages) <[EMAIL PROTECTED]>
Changed-By: Sam Hocevar (Debian packages) <[EMAIL PROTECTED]>
Description:
beast - music synthesis and composition framework
Closes: 339153
Changes:
beast (0.6.6-3) unstable; urgency=low
.
* Rebuilt package due to a new C++ ABI change (Closes: #339153).
* debian/control:
+ Conflict with older versions of bse-alsa.
+ Build-depend on g++-4.0 (>= 4.0.2-4) because we did no soname bump.
* debian/rules:
+ Tightened shlib dependencies.
* debian/compat:
+ Set level to 4.
Files:
61c1f566a9c04e18bca44be65254e7c2 817 gnome extra beast_0.6.6-3.dsc
31092e063926b6fdbe604702a4f0ba59 8354 gnome extra beast_0.6.6-3.diff.gz
49341a10e7d38b4f915c540c65320249 4165328 gnome extra beast_0.6.6-3_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDidmDfPP1rylJn2ERAn2dAJ9sVXgn2JT4dSYMx+TrjmpB4z0COgCfbGgh
yZhdeDBbbth7822vTzVLlG4=
=JCMp
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
