Processing of gcc-defaults_1.118_amd64.changes
gcc-defaults_1.118_amd64.changes uploaded successfully to localhost along with the files: gcc-defaults_1.118.dsc gcc-defaults_1.118.tar.gz libgcj-common_4.6.3-6_all.deb cpp_4.7.0-6_amd64.deb gcc_4.7.0-6_amd64.deb gcc-multilib_4.7.0-6_amd64.deb gdc_4.6.3-6_amd64.deb gdc-v1_4.6.3-6_amd64.deb g++_4.7.0-6_amd64.deb g++-multilib_4.7.0-6_amd64.deb gobjc_4.7.0-6_amd64.deb gobjc-multilib_4.7.0-6_amd64.deb gobjc++_4.7.0-6_amd64.deb gobjc++-multilib_4.7.0-6_amd64.deb gfortran_4.7.0-6_amd64.deb gfortran-multilib_4.7.0-6_amd64.deb gccgo_4.7.0-6_amd64.deb gccgo-multilib_4.7.0-6_amd64.deb libgcj-bc_4.7.0-6_amd64.deb gcj-jre-headless_4.7.0-6_amd64.deb gcj-jre_4.7.0-6_amd64.deb gcj-jdk_4.7.0-6_amd64.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1srqo0-0002g1...@franck.debian.org
gcc-defaults_1.118_amd64.changes ACCEPTED into unstable
Accepted: cpp_4.7.0-6_amd64.deb to main/g/gcc-defaults/cpp_4.7.0-6_amd64.deb g++-multilib_4.7.0-6_amd64.deb to main/g/gcc-defaults/g++-multilib_4.7.0-6_amd64.deb g++_4.7.0-6_amd64.deb to main/g/gcc-defaults/g++_4.7.0-6_amd64.deb gcc-defaults_1.118.dsc to main/g/gcc-defaults/gcc-defaults_1.118.dsc gcc-defaults_1.118.tar.gz to main/g/gcc-defaults/gcc-defaults_1.118.tar.gz gcc-multilib_4.7.0-6_amd64.deb to main/g/gcc-defaults/gcc-multilib_4.7.0-6_amd64.deb gcc_4.7.0-6_amd64.deb to main/g/gcc-defaults/gcc_4.7.0-6_amd64.deb gccgo-multilib_4.7.0-6_amd64.deb to main/g/gcc-defaults/gccgo-multilib_4.7.0-6_amd64.deb gccgo_4.7.0-6_amd64.deb to main/g/gcc-defaults/gccgo_4.7.0-6_amd64.deb gcj-jdk_4.7.0-6_amd64.deb to main/g/gcc-defaults/gcj-jdk_4.7.0-6_amd64.deb gcj-jre-headless_4.7.0-6_amd64.deb to main/g/gcc-defaults/gcj-jre-headless_4.7.0-6_amd64.deb gcj-jre_4.7.0-6_amd64.deb to main/g/gcc-defaults/gcj-jre_4.7.0-6_amd64.deb gdc-v1_4.6.3-6_amd64.deb to main/g/gcc-defaults/gdc-v1_4.6.3-6_amd64.deb gdc_4.6.3-6_amd64.deb to main/g/gcc-defaults/gdc_4.6.3-6_amd64.deb gfortran-multilib_4.7.0-6_amd64.deb to main/g/gcc-defaults/gfortran-multilib_4.7.0-6_amd64.deb gfortran_4.7.0-6_amd64.deb to main/g/gcc-defaults/gfortran_4.7.0-6_amd64.deb gobjc++-multilib_4.7.0-6_amd64.deb to main/g/gcc-defaults/gobjc++-multilib_4.7.0-6_amd64.deb gobjc++_4.7.0-6_amd64.deb to main/g/gcc-defaults/gobjc++_4.7.0-6_amd64.deb gobjc-multilib_4.7.0-6_amd64.deb to main/g/gcc-defaults/gobjc-multilib_4.7.0-6_amd64.deb gobjc_4.7.0-6_amd64.deb to main/g/gcc-defaults/gobjc_4.7.0-6_amd64.deb libgcj-bc_4.7.0-6_amd64.deb to main/g/gcc-defaults/libgcj-bc_4.7.0-6_amd64.deb libgcj-common_4.6.3-6_all.deb to main/g/gcc-defaults/libgcj-common_4.6.3-6_all.deb Changes: gcc-defaults (1.118) unstable; urgency=low . * Default to GCC 4.7 for gcc, g++, gfortran on amd64, i386, kfreebsd-amd64, kfreebsd-i386 and hurd-i386. Override entries for your package: cpp_4.7.0-6_amd64.deb - optional interpreters g++-multilib_4.7.0-6_amd64.deb - optional devel g++_4.7.0-6_amd64.deb - optional devel gcc-defaults_1.118.dsc - source devel gcc-multilib_4.7.0-6_amd64.deb - optional devel gcc_4.7.0-6_amd64.deb - optional devel gccgo-multilib_4.7.0-6_amd64.deb - optional devel gccgo_4.7.0-6_amd64.deb - optional devel gcj-jdk_4.7.0-6_amd64.deb - optional java gcj-jre-headless_4.7.0-6_amd64.deb - optional java gcj-jre_4.7.0-6_amd64.deb - optional java gdc-v1_4.6.3-6_amd64.deb - optional devel gdc_4.6.3-6_amd64.deb - optional devel gfortran-multilib_4.7.0-6_amd64.deb - optional devel gfortran_4.7.0-6_amd64.deb - optional devel gobjc++-multilib_4.7.0-6_amd64.deb - optional devel gobjc++_4.7.0-6_amd64.deb - optional devel gobjc-multilib_4.7.0-6_amd64.deb - optional devel gobjc_4.7.0-6_amd64.deb - optional devel libgcj-bc_4.7.0-6_amd64.deb - optional java libgcj-common_4.6.3-6_all.deb - optional java Announcing to debian-devel-chan...@lists.debian.org Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1srqek-0004d2...@franck.debian.org
Processed: GCC-4.7 now the default for x86 archs, raising severity of GCC 4.7 related build failures
Processing commands for cont...@bugs.debian.org: > severity 667373 serious Bug #667373 [simgear] simgear: ftbfs with GCC-4.7 Ignoring request to change severity of Bug 667373 to the same value. > severity 671438 serious Bug #671438 [insighttoolkit] insighttoolkit headers cause build failures with GCC 4.7 Ignoring request to change severity of Bug 671438 to the same value. > severity 671475 serious Bug #671475 [libclaw] libclaw headers ftbfs with gcc-4.7 Ignoring request to change severity of Bug 671475 to the same value. > severity 667094 serious Bug #667094 [adanaxisgpl] adanaxisgpl: ftbfs with GCC-4.7 Severity set to 'serious' from 'important' > severity 667101 serious Bug #667101 [ardour] ardour: ftbfs with GCC-4.7 Severity set to 'serious' from 'important' > severity 667105 serious Bug #667105 [audex] audex: ftbfs with GCC-4.7 Severity set to 'serious' from 'important' > severity 667109 serious Bug #667109 [barry] barry: ftbfs with GCC-4.7 Severity set to 'serious' from 'important' > severity 667111 serious Bug #667111 [bcov] bcov: ftbfs with GCC-4.7 Severity set to 'serious' from 'important' > severity 667114 serious Bug #667114 [bitcoin] bitcoin: ftbfs with GCC-4.7 Severity set to 'serious' from 'important' > severity 667118 serious Bug #667118 [blockattack] blockattack: ftbfs with GCC-4.7 Severity set to 'serious' from 'important' > severity 667127 serious Bug #667127 [cantor] cantor: ftbfs with GCC-4.7 Severity set to 'serious' from 'important' > severity 667129 serious Bug #667129 [cb2bib] cb2bib: ftbfs with GCC-4.7 Severity set to 'serious' from 'important' > severity 667131 serious Bug #667131 [cbmc] cbmc: ftbfs with GCC-4.7 Severity set to 'serious' from 'important' > severity 667135 serious Bug #667135 [chasen] chasen: ftbfs with GCC-4.7 Severity set to 'serious' from 'important' > severity 667136 serious Bug #667136 [clam] clam: ftbfs with GCC-4.7 Severity set to 'serious' from 'important' > severity 667137 serious Bug #667137 [clam-networkeditor] clam-networkeditor: ftbfs with GCC-4.7 Severity set to 'serious' from 'important' > severity 667138 serious Bug #667138 [codeblocks] codeblocks: ftbfs with GCC-4.7 Severity set to 'serious' from 'important' > severity 667139 serious Bug #667139 [coin3] coin3: ftbfs with GCC-4.7 Severity set to 'serious' from 'important' > severity 667141 serious Bug #667141 [config-manager] config-manager: ftbfs with GCC-4.7 Severity set to 'serious' from 'important' > severity 667143 serious Bug #667143 [critterding] critterding: ftbfs with GCC-4.7 Severity set to 'serious' from 'important' > severity 667145 serious Bug #667145 [ctemplate] ctemplate: ftbfs with GCC-4.7 Severity set to 'serious' from 'important' > severity 667151 serious Bug #667151 [digikam] digikam: ftbfs with GCC-4.7 Severity set to 'serious' from 'important' > severity 667152 serious Bug #667152 [dmtcp] dmtcp: ftbfs with GCC-4.7 Severity set to 'serious' from 'important' > severity 667158 serious Bug #667158 [esys-particle] esys-particle: ftbfs with GCC-4.7 Severity set to 'serious' from 'important' > severity 667160 serious Bug #667160 [fakeroot-ng] fakeroot-ng: ftbfs with GCC-4.7 Severity set to 'serious' from 'important' > severity 667168 serious Bug #667168 [fparser] fparser: ftbfs with GCC-4.7 Severity set to 'serious' from 'important' > severity 667169 serious Bug #667169 [fqterm] fqterm: ftbfs with GCC-4.7 Severity set to 'serious' from 'important' > severity 667171 serious Bug #667171 [ftpgrab] ftpgrab: ftbfs with GCC-4.7 Severity set to 'serious' from 'important' > severity 667195 serious Bug #667195 [gtkmathview] gtkmathview: ftbfs with GCC-4.7 Severity set to 'serious' from 'important' > severity 667202 serious Bug #667202 [hoichess] hoichess: ftbfs with GCC-4.7 Severity set to 'serious' from 'important' > severity 667203 serious Bug #667203 [hydrogen] hydrogen: ftbfs with GCC-4.7 Severity set to 'serious' from 'important' > severity 667204 serious Bug #667204 [ibam] ibam: ftbfs with GCC-4.7 Severity set to 'serious' from 'important' > severity 667215 serious Bug #667215 [jffi] jffi: ftbfs with GCC-4.7 Severity set to 'serious' from 'important' > severity 667218 serious Bug #667218 [kaffeine] kaffeine: ftbfs with GCC-4.7 Severity set to 'serious' from 'important' > severity 667220 serious Bug #667220 [kdepimlibs] kdepimlibs: ftbfs with GCC-4.7 Severity set to 'serious' from 'important' > severity 667230 serious Bug #667230 [kredentials] kredentials: ftbfs with GCC-4.7 Severity set to 'serious' from 'important' > severity 667239 serious Bug #667239 [libapache2-mod-encoding] libapache2-mod-encoding: ftbfs with GCC-4.7 Severity set to 'serious' from 'important' > severity 667244 serious Bug #667244 [libevocosm] libevocosm: ftbfs with GCC-4.7 Severity set to 'serious' from 'important' > severity 667247 serious Bug #667247 [libkml] libkml: ftbfs with GCC-4.7 Severity set to 'serious' from 'important' > severity 667249 serious Bug #667249 [libmsn] libmsn: ftbfs with GCC-4.7 Severity set
Re: Accepted gcc-defaults 1.118 (source all amd64)
On Mon, May 7, 2012 at 16:19:00 +, Matthias Klose wrote: > gcc-defaults (1.118) unstable; urgency=low > . >* Default to GCC 4.7 for gcc, g++, gfortran on amd64, i386, > kfreebsd-amd64, kfreebsd-i386 and hurd-i386. Please revert this change. There are still too many open bugs on http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-gcc@lists.debian.org;tag=ftbfs-gcc-4.7, and it's too late in the release cycle, to change this, IMO. Cheers, Julien signature.asc Description: Digital signature
GCC 4.7 is now the default for x86 architectures
GCC 4.7 is now the default for x86 architectures for all frontends except the D frontends, including KFreeBSD and the Hurd. There are still some build failures which need to be addressed. Out of the ~350 bugs filed, more than the half are fixed, another quarter has patches available, and the remaining quarter isn't blocking any other 4.7 build failures. Many thanks to the patch submitters and NMUers, including Cyril Brulebois, Gregor Herrmann, Paul Tagliamonte for the fixes. This will add one more transition for x86 (libobjc3 -> libobjc4), which needs starting with uploads of some GNUstep base packages. The D v2 frontend is likely to be updated to 4.7 before the freeze (no build dependencies). Matthias -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fa7ffd8.9010...@debian.org
Re: GCC 4.7 is now the default for x86 architectures
On 07.05.2012 19:35, Thorsten Glaser wrote: > Matthias Klose dixit: > >> GCC 4.7 is now the default for x86 architectures for all frontends except >> the D >> frontends, including KFreeBSD and the Hurd. > > How are the plans for other architectures? I don't have plans to change any other architectures. If a port is not a release architectures (and port maintainers don't plan to make it a release architecture), people can change the default at any time from my point of view. > As for gcc-4.7 in general: a friend (authoring an ObjC framework _and_ > runtime) told me that it dropped support for an old method of doing > things while not fulfilling the promise to get the new method of doing > it (don’t exactly remember what it was, /msg js on freenode for details) > fixed, with the effect that gobjc-4.7 is virtually useless/broken. > > This is hearsay, but ask him for details, and check them against > reality. I didn't rely on hearsay, but did ask the GNUstep maintainers for feedback. Please join the Debian GNUstep package maintainers ML if you want to add something, or review the past discussion. Matthias -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fa80a89.8070...@debian.org
Re: GCC 4.7 is now the default for x86 architectures
Matthias Klose dixit: >GCC 4.7 is now the default for x86 architectures for all frontends except the D >frontends, including KFreeBSD and the Hurd. How are the plans for other architectures? The m68k status (which obviously can’t influence the release decisions) is as follows: gcc-4.7 builds, last time I looked gcj-4.7 didn’t but it is currently building again (so let’s see whether it does this time); gcc-4.6 and gnat-4.6 are getting development and bugfixes (I’ve queued up some patches, but am not entirely ready with all of them, plus some for binutils and gdb), and I’ve asked for help re. the gcj-4.4/gcj-4.6 recent problems. But nothing has tested gcj-4.7, and I fear of new and old bugs… so I’d rather not switch default compiler to it anytime soon. As for gcc-4.7 in general: a friend (authoring an ObjC framework _and_ runtime) told me that it dropped support for an old method of doing things while not fulfilling the promise to get the new method of doing it (don’t exactly remember what it was, /msg js on freenode for details) fixed, with the effect that gobjc-4.7 is virtually useless/broken. This is hearsay, but ask him for details, and check them against reality. bye, //mirabilos -- Yay for having to rewrite other people's Bash scripts because bash suddenly stopped supporting the bash extensions they make use of -- Tonnerre Lombard in #nosec -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pine.bsm.4.64l.1205071730550.28...@herc.mirbsd.org
Re: Accepted gcc-defaults 1.118 (source all amd64)
Julien Cristau (07/05/2012): > On Mon, May 7, 2012 at 16:19:00 +, Matthias Klose wrote: > > > gcc-defaults (1.118) unstable; urgency=low > > . > >* Default to GCC 4.7 for gcc, g++, gfortran on amd64, i386, > > kfreebsd-amd64, kfreebsd-i386 and hurd-i386. > > Please revert this change. There are still too many open bugs on > http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-gcc@lists.debian.org;tag=ftbfs-gcc-4.7, > […] Seconded. Furthermore, doing so without an ACK from the release team isn't very nice. Too many transitions going on/to do already, we don't need that kind of fun. Why do we need to take that extra blast? Mraw, KiBi. signature.asc Description: Digital signature
Re: Accepted gcc-defaults 1.118 (source all amd64)
On 07.05.2012 20:19, Cyril Brulebois wrote: > Julien Cristau (07/05/2012): >> On Mon, May 7, 2012 at 16:19:00 +, Matthias Klose wrote: >> >>> gcc-defaults (1.118) unstable; urgency=low . * Default to GCC 4.7 for >>> gcc, g++, gfortran on amd64, i386, kfreebsd-amd64, kfreebsd-i386 and >>> hurd-i386. >> >> Please revert this change. There are still too many open bugs on >> http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-gcc@lists.debian.org;tag=ftbfs-gcc-4.7, >> >> […] > > Seconded. Furthermore, doing so without an ACK from the release team isn't > very nice. Too many transitions going on/to do already, we don't need that > kind of fun. Why do we need to take that extra blast? see my email to -release. It's ahead of the freeze, and the fix rate for the build failures shows that all these issues can be fixed even before the freeze. It is not a transition which requires binNMU's itself (except for the libobjc stuff), and shouldn't affect other ongoing transitions. If there are fixes needed for an ongoing transition, please bring these to my attention. Matthias -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fa81b6a.8000...@debian.org
