Bug#325564:

2005-10-16 Thread Duck
0.10.1-3 built with gcc 4.0.2 fixed the problem (see [EMAIL PROTECTED]). -- Marc Dequènes (Duck) pgp5WBtvZ7Ly9.pgp Description: PGP signature

Bug#325564: Processed: tagging 325564

2005-09-06 Thread Steve Langasek
Hi Marc, On Tue, Sep 06, 2005 at 07:48:38AM -0700, Debian Bug Tracking System wrote: > > # Automatically generated email from bts, devscripts version 2.9.7 > > tags 325564 + wontfix > Bug#325564: soya_0.10.1-1(m68k/unstable/poseidon): FTBFS on m68k > Tags were: sid > Tags a

Bug#325564: Bug#325565: Processed: tagging 325564

2005-09-07 Thread Ben Armstrong
You have inadvertently CC'd this message that seems applicable only to bug #325564 to bug #325565 against my package, gtypist. Please omit 325565 from any followup messages. Thanks, Ben Armstrong -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". T

Bug#325563: Bug#325564: Processed: tagging 325564

2005-09-07 Thread Duck
Steve Langasek <[EMAIL PROTECTED]> writes: > Hi Marc, Coin Vorlon, > So, I wonder what exactly your intent is here. Do you mean to say that > you don't care about being able to get new versions of pyopenal and soya > into testing until the toolchain bug is fixed, and that you don't care > wheth

Bug#325563: Bug#325564: Processed: tagging 325564

2005-09-11 Thread Steve Langasek
On Thu, Sep 08, 2005 at 02:30:29AM +0200, Marc Dequènes wrote: > Steve Langasek <[EMAIL PROTECTED]> writes: > > So, I wonder what exactly your intent is here. Do you mean to say that > > you don't care about being able to get new versions of pyopenal and soya > > into testing until the toolchain

Bug#325563: Bug#325564: Processed: tagging 325564

2005-09-11 Thread Duck
Coin, Steve Langasek <[EMAIL PROTECTED]> writes: >> I don't see any reason to work around plenty of packages when this is >> for sure an important toolchain bug which cannot be delayed for long and >> my packages are not important ones and are already available >> (unaffected) for most architect

Bug#325563: Bug#325564: Processed: tagging 325564

2005-09-12 Thread Steve Langasek
clone 325564 -1 reassign -1 python2.3-dev thanks On Sun, Sep 11, 2005 at 05:41:31PM +0200, Marc Dequènes wrote: > Steve Langasek <[EMAIL PROTECTED]> writes: > >> I don't see any reason to work around plenty of packages when this is > >> for sure an important toolchain bug which cannot be delayed

Processed: Re: Bug#325563: Bug#325564: Processed: tagging 325564

2005-09-12 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > clone 325564 -1 Bug#325564: soya_0.10.1-1(m68k/unstable/poseidon): FTBFS on m68k Bug 325564 cloned as bug 327835. > reassign -1 python2.3-dev Bug#327835: soya_0.10.1-1(m68k/unstable/poseidon): FTBFS on m68k Bug reassigned from package `so

Bug#325564: soya_0.10.1-1(m68k/unstable/poseidon): FTBFS on m68k

2005-08-29 Thread Stephen R Marenka
Package: soya Version: 0.10.1-1 Severity: serious Justification: fails to build on release candidate arch. Tags: sid soya fails to build from source on m68k. This is likely due to bug #317475 on gcc-4.0. As a workaround, you might try compiling with less optimization or gcc-3.3/gcc-3.4. A full

Bug#325564: marked as done (soya_0.10.1-1(m68k/unstable/poseidon): FTBFS on m68k)

2005-10-17 Thread Debian Bug Tracking System
Your message dated Mon, 17 Oct 2005 10:38:19 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#325564 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 responsibil