On Mon, Sep 12, 2005 at 09:28:30AM +0200, Matthias Klose wrote:
> that's unreproducible on crest/sid, although I can reproduce it on
> another machine with the very same versions of gcc-4.0 and libc6. So
> why not file it for libc6?
What cpu type is that other machine? I assume that ska is a 040?
=20
> The point of reassigning the report to an unknown package is to ask,
> if it's time to drop m68k from the release architectures or just set
> the severity of all m68k reports to wishlist. There's currently nobody
> interested in forwarding m68k related bug reports upstream and testing
> m68k compiler versions. There are at least six more unhandled m68k
> reports.
> My email from July (http://lists.debian.org/debian-release/2005/07/msg000=
69.html)
> is left unanswered, so I have to assume, that m68k isn't supported
> anymore and will start to downgrade all m68k related reports to a
> non-RC severity.
Uhm? Unanswered? I thought Wouter and Adam step up to fill the gap?
Message-ID: <20050912075906 .GF6149@ 2004.bluespice. org> bluespice. org>
Date: Mon, 12 Sep 2005 09:59:06 +0200
From: Ingo Juergensmann <ij@2005.
To: Matthias Klose <email address hidden>
Cc: Wouter Verhelst <email address hidden>, <email address hidden>,
<email address hidden>, <email address hidden>, <email address hidden>
Subject: Re: Bug#327780: current gcc-4.0 is utterly useless on m68k
--4VrXvz3cwkc87Wze Disposition: inline Transfer- Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Content-
Content-
On Mon, Sep 12, 2005 at 09:28:30AM +0200, Matthias Klose wrote:
> that's unreproducible on crest/sid, although I can reproduce it on
> another machine with the very same versions of gcc-4.0 and libc6. So
> why not file it for libc6?
What cpu type is that other machine? I assume that ska is a 040? lists.debian. org/debian- release/ 2005/07/ msg000=
=20
> The point of reassigning the report to an unknown package is to ask,
> if it's time to drop m68k from the release architectures or just set
> the severity of all m68k reports to wishlist. There's currently nobody
> interested in forwarding m68k related bug reports upstream and testing
> m68k compiler versions. There are at least six more unhandled m68k
> reports.
> My email from July (http://
69.html)
> is left unanswered, so I have to assume, that m68k isn't supported
> anymore and will start to downgrade all m68k related reports to a
> non-RC severity.
Uhm? Unanswered? I thought Wouter and Adam step up to fill the gap?
--=20
Ciao... // Fon: 0381-2744150=20
Ingo \X/ SIP: <email address hidden>
gpg pubkey: http:// www.juergensman n.de/ij/ public_ key.asc
--4VrXvz3cwkc87Wze pgp-signature; name="signature .asc" Description: Digital signature Disposition: inline
Content-Type: application/
Content-
Content-
-----BEGIN PGP SIGNATURE-----
CZmI+zY0RArAaAK Cx3cr9LWKdrVvau Yt0BlQxRD1qNQCf X3eq Ke5ump6Q=
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFDJTVKlCn
geJEg/uNgf1wkq+
=7nHw
-----END PGP SIGNATURE-----
--4VrXvz3cwkc87 Wze--