Kalle Olavi Niemitalo writes:
> If you need more information, please ask.
yes. how to detect and remove the diversion?
Accepted:
gcc-snapshot_20020907-1.diff.gz
to pool/main/g/gcc-snapshot/gcc-snapshot_20020907-1.diff.gz
gcc-snapshot_20020907-1.dsc
to pool/main/g/gcc-snapshot/gcc-snapshot_20020907-1.dsc
gcc-snapshot_20020907-1_i386.deb
to pool/main/g/gcc-snapshot/gcc-snapshot_20020907-1_i386.deb
gcc-snapshot
Your message dated Sat, 07 Sep 2002 12:47:22 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#157130: fixed in gcc-snapshot 20020907-1
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 c
Maybe this is because gcc 2.96 is not an official release of gcc and
instead is a buggy snapshot?
What would I be expected to do if one of my packages were to trigger
bugs in gcc 2.96?
IMHO the IA64 port should stop using a broken compiler instead of
filing bugs on packages that expose bugs in it
Package: gcc-snapshot
Version: 20020907-1
Severity: important
There was an error while trying to autobuild your package:
> Automatic build of gcc-snapshot_20020907-1 on sarti by sbuild/hppa 1.169
> Build started at 20020907-1830
[...]
> ** Using build dependencies supplied by package
5 matches
Mail list logo