Bug#763278: wheezy-pu: gcc-4.9/4.9.1-14~deb7u1

2014-10-08 Thread Adam D. Barratt
On Thu, 2014-10-02 at 20:26 -0400, Michael Gilbert wrote: On Tue, Sep 30, 2014 at 2:10 PM, Adam D. Barratt wrote: Control: tags -1 + moreinfo On Sun, 2014-09-28 at 16:00 -0400, Michael Gilbert wrote: In order to continue providing security updates for chromium in wheezy, I would like to

Re: Bug#763278: wheezy-pu: gcc-4.9/4.9.1-14~deb7u1

2014-10-03 Thread Moritz Mühlenhoff
Adam D. Barratt a...@adam-barratt.org.uk schrieb: On 2014-10-01 13:25, Moritz Mühlenhoff wrote: Adam D. Barratt a...@adam-barratt.org.uk schrieb: The alternative is to drop chromium security support for wheezy way too soon. They're not the only alternatives. Granted, they may be the only

Re: Bug#763278: wheezy-pu: gcc-4.9/4.9.1-14~deb7u1

2014-10-02 Thread Moritz Mühlenhoff
Adam D. Barratt a...@adam-barratt.org.uk schrieb: The alternative is to drop chromium security support for wheezy way too soon. They're not the only alternatives. Granted, they may be the only ones which you're willing to support. What other alternatives do you have in mind? Cheers,

Re: Bug#763278: wheezy-pu: gcc-4.9/4.9.1-14~deb7u1

2014-10-02 Thread Adam D. Barratt
On 2014-10-01 13:25, Moritz Mühlenhoff wrote: Adam D. Barratt a...@adam-barratt.org.uk schrieb: The alternative is to drop chromium security support for wheezy way too soon. They're not the only alternatives. Granted, they may be the only ones which you're willing to support. What other

Re: Bug#763278: wheezy-pu: gcc-4.9/4.9.1-14~deb7u1

2014-10-02 Thread Michael Gilbert
On Thu, Oct 2, 2014 at 5:48 AM, Adam D. Barratt wrote: Well, someone could attempt to persuade upstream to delay the change, or work on fixing things up to work with 4.7 where required. Starting with chromium 38, they're using C++ features only implemented in gcc = 4.8, and it seems like

Bug#763278: wheezy-pu: gcc-4.9/4.9.1-14~deb7u1

2014-10-02 Thread Michael Gilbert
On Tue, Sep 30, 2014 at 2:10 PM, Adam D. Barratt wrote: Control: tags -1 + moreinfo On Sun, 2014-09-28 at 16:00 -0400, Michael Gilbert wrote: chromium 38 is currently planning to drop support for all compilers less than gcc 4.8 (and all clang not built against = gcc 4.8). So wheezy will

Bug#763278: wheezy-pu: gcc-4.9/4.9.1-14~deb7u1

2014-09-30 Thread Adam D. Barratt
Control: tags -1 + moreinfo On Sun, 2014-09-28 at 16:00 -0400, Michael Gilbert wrote: chromium 38 is currently planning to drop support for all compilers less than gcc 4.8 (and all clang not built against = gcc 4.8). So wheezy will soon have no way to compile an up to date chromium. Can we

Processed: Re: Bug#763278: wheezy-pu: gcc-4.9/4.9.1-14~deb7u1

2014-09-30 Thread Debian Bug Tracking System
Processing control commands: tags -1 + moreinfo Bug #763278 [release.debian.org] wheezy-pu: gcc-4.9/4.9.1-14~deb7u1 Added tag(s) moreinfo. -- 763278: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763278 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To

Bug#763278: wheezy-pu: gcc-4.9/4.9.1-14~deb7u1

2014-09-28 Thread Michael Gilbert
Package: release.debian.org User: release.debian@packages.debian.org Usertags: pu Severity: normal Tags: security chromium 38 is currently planning to drop support for all compilers less than gcc 4.8 (and all clang not built against = gcc 4.8). So wheezy will soon have no way to compile an