QA.
The machine was in a not very good state, I am giving the package
back. If the problem persists I can try to look at it closer during
the weekend.
Cheers.
--
Manuel A. Fernandez Montecelo
ibffi.call/call.exp ...
Running ../../testsuite/libffi.complex/complex.exp ...
Running ../../testsuite/libffi.go/go.exp ...
=== libffi Summary ===
# of expected passes3495
# of unsupported tests 30
--
Manuel A. Fernandez Montecelo
just be removed as well.
(just doing some bug triaging...)
Is this still an issue?
The bug was closed by spam and then reopened, but it looks to me that if
the only remaining issues were with mips and mipsel back in 2015,
there's a good chance that this has since been fixed.
Cheers.
--
Man
Source: libiberty
Version: 20131116-1
Severity: normal
Tags: patch
Please use autotools-dev (or dh-autoreconf) to keep the
config.{sub,guess} files up to date.
I can do an NMU if you want, but probably it's a better idea if you
make the changes yourself.
Cheers.
--
Manuel A. Fern
forwarded 686645 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54569
stop
Setting forwarded address to better keep track of changes in upstream BTS.
Cheers.
--
Manuel A. Fernandez Montecelo
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubs
Hello,
Thanks for the detailed bug reports and your interest in improving
Debian. I'm just doing some cleanup, I am not involved with the GCC package.
It seems that very recently the issue was picked by somebody upstream
and they fixed it. According to the information in the upstream bug
report
tags 173513 - fixed-upstream
stop
Hello,
It seems that the bug is not fixed-upstream despite being tagged as
such a while ago, so removing the tag by hand.
Regards.
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@li
2012/4/14, Matthias Klose :
> I think any reassigments would be wrong. It needs somebody to go through the
> list of bugs to see if these are fixed. if yes, close them, if not, then
> reassign them to the package they can be reproduced with. Do you volunteer
> to do this?
I can try. But I'm leav
Hello
I noticed that there are these orphan bugs (no maintainer set, the
package that they are filed against is not present in Debian anymore).
Perhaps there are some false positives or missing ones.
They were gathered from [1], and the ones related to GCC are filteerd
and pasted in the attached
2011/11/24 Peter De Wachter :
> Package: gdc-4.6
> Version: 0.29.1-4.6.2-1
> Severity: normal
>
> If no '-c' option is specified, gdc doesn't generate the right output file
> name:
>
> $ gdc-4.6 -c HelloWorld.d
> $ ls
> HelloWorld.d
> HelloWorl.o
I spotted that one too, and I was about to report i
more than 6 to a year by the time the release happens), if there is not a
specific problem with the new version.
Fast forward 1.5 to 2 years, when Squeeze is about to be EOL'd. Why would
you use software 3 years old, with maintainance releases maybe stopped since
long, w
ts or suggestions? Should I reassign the bug to gcc-4.4 or
something?
Cheers.
--
Manuel A. Fernandez Montecelo
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://l
12 matches
Mail list logo
