Processing of gnat-4.8_4.8.2-1_amd64.changes

gnat-4.8_4.8.2-1_amd64.changes uploaded successfully to localhost along with the files: gnat-4.8_4.8.2-1.dsc gnat-4.8_4.8.2-1.tar.gz gnat-4.8-base_4.8.2-1_amd64.deb libgnat-4.8_4.8.2-1_amd64.deb libgnat-4.8-dbg_4.8.2-1_amd64.deb libgnatvsn4.8-dev_4.8.2-1_amd64.deb libgnatvsn4.8_4.8.2-

gnat-4.8_4.8.2-1_amd64.changes is NEW

binary:libgnat-4.8 is NEW. binary:libgnatprj4.8-dev is NEW. binary:gnat-4.8 is NEW. binary:gnat-4.8-base is NEW. binary:libgnat-4.8-dbg is NEW. binary:libgnatvsn4.8 is NEW. binary:libgnatprj4.8 is NEW. binary:libgnatvsn4.8-dev is NEW. binary:gnat-4.8-sjlj is NEW. binary:libgnatvsn4.8-dbg is NEW. bi

Bug#727621: armel: std::future appears to be broken?

Package: g++-4.8 Version: 4.8.1-10 Severity: normal Hello, thank you for maintaining GCC. When I tried to compile cupt 2.6.x in unstable/experimental, an armel build (out of all) failed. This unfortunately blocks cupt's migration to testing. unstable, used g++ 4.8 - [1] unstable, used g++ 4.6 -

Results for 4.9.0 20131021 (experimental) [trunk revision 203899] (Debian 20131021-1) testsuite on s390x-ibm-linux-gnu

LAST_UPDATED: Mon Oct 21 16:22:58 UTC 2013 (revision 203899) Target: s390x-linux-gnu gcc version 4.9.0 20131021 (experimental) [trunk revision 203899] (Debian 20131021-1) === acats tests === FAIL: c52103x FAIL: c52104x FAIL: c52104y FAIL: cb1010a === aca

Results for 4.7.3 (Debian 4.7.3-8) testsuite on arm-unknown-linux-gnueabi

LAST_UPDATED: Sun Oct 20 20:56:37 UTC 2013 (revision 203880) Native configuration is arm-unknown-linux-gnueabi === boehm-gc tests === Running target unix === boehm-gc Summary === # of expected passes12 # of unsupported tests 1

Results for 4.7.3 (Debian 4.7.3-8) testsuite on s390x-ibm-linux-gnu

LAST_UPDATED: Sun Oct 20 20:56:37 UTC 2013 (revision 203880) Target: s390x-linux-gnu gcc version 4.7.3 (Debian 4.7.3-8) Native configuration is s390x-ibm-linux-gnu === g++ tests === Running target unix FAIL: g++.dg/init/const9.C -std=c++98 scan-assembler-not rodata FAIL: g++.d

Bug#727621: armel: std::future appears to be broken?

On Thu, Oct 24, 2013 at 08:03:24PM +0300, Eugene V. Lyubimkin wrote: > When I tried to compile cupt 2.6.x in unstable/experimental, an armel > build (out of all) failed. This unfortunately blocks cupt's migration to > testing. Please fix cupt to show the complete command-line. The build-logs are

Bug#727621: armel: std::future appears to be broken?

Hi, 2013-10-24 21:45, Bastian Blank: > Please fix cupt to show the complete command-line. The build-logs are > near to useless. In general, I tend to disagree, for noise-to-signal and readability ratio. Now if this particular report is near to useless given the information I provided, I would b

Bug#727621: armel: std::future appears to be broken?

On Fri, Oct 25, 2013 at 12:12:59AM +0300, Eugene V. Lyubimkin wrote: > 2013-10-24 21:45, Bastian Blank: > > Please fix cupt to show the complete command-line. The build-logs are > > near to useless. > In general, I tend to disagree, for noise-to-signal and readability > ratio. Log from buildds ar

Processing of gcc-doc-defaults_5_amd64.changes

gcc-doc-defaults_5_amd64.changes uploaded successfully to localhost along with the files: gcc-doc-defaults_5.dsc gcc-doc-defaults_5.tar.gz gcc-doc-base_4.8.0-1_all.deb cpp-doc_4.8.0-1_amd64.deb gcc-doc_4.8.0-1_amd64.deb gfortran-doc_4.8.0-1_amd64.deb gnat-doc_4.6.3-1_amd64.deb gcj-d

gcc-doc-defaults_5_amd64.changes REJECTED

ACL dm: NEW uploads are not allowed === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns. -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trou