Bug#763278: wheezy-pu: gcc-4.9/4.9.1-14~deb7u1
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 propose a gcc wheezy-pu. I haven't tried to get this working yet, and am sending this to see whether the release team would even consider this. Have you discussed this with the gcc maintainers? What's their opinion on the idea, in terms of feasibility and supportability? Haven't yet, but I'll start a conversation. Any news on that? Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1412797236.1325.11.ca...@jacala.jungle.funky-badger.org
Re: Bug#763278: wheezy-pu: gcc-4.9/4.9.1-14~deb7u1
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 ones which you're willing to support. What other alternatives do you have in mind? Well, someone could attempt to persuade upstream to delay the change, or work on fixing things up to work with 4.7 where required. I didn't say they were great alternatives, simply that they exist. Unfortunately they're not viable: Upstream wants to use C++11 features and even if someone were to start on a Debian-specific patchset it would only get bigger with every new Chromium release (and they make new releases every few weeks). Cheers, Moritz -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/slrnm2qvkk.3ef@inutil.org
Re: Bug#763278: wheezy-pu: gcc-4.9/4.9.1-14~deb7u1
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, Moritz -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/slrnm2nskv.3qp@inutil.org
Re: Bug#763278: wheezy-pu: gcc-4.9/4.9.1-14~deb7u1
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 alternatives do you have in mind? Well, someone could attempt to persuade upstream to delay the change, or work on fixing things up to work with 4.7 where required. I didn't say they were great alternatives, simply that they exist. Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/66ef3b1ae286fef82777e42b64059...@mail.adsl.funky-badger.org
Re: Bug#763278: wheezy-pu: gcc-4.9/4.9.1-14~deb7u1
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 they're gung-ho about that, brazenly announcing that they don't care about breaking old os versions in the process. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CANTw=mozfwogerts95be_3zjeenay87eglv4_wrql82ngkd...@mail.gmail.com
Bug#763278: wheezy-pu: gcc-4.9/4.9.1-14~deb7u1
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 soon have no way to compile an up to date chromium. Can we quantify soon? 38 will be released in he next couple weeks, which is quite soon. In order to continue providing security updates for chromium in wheezy, I would like to propose a gcc wheezy-pu. I haven't tried to get this working yet, and am sending this to see whether the release team would even consider this. Have you discussed this with the gcc maintainers? What's their opinion on the idea, in terms of feasibility and supportability? Haven't yet, but I'll start a conversation. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CANTw=moyxkwflj4+xpyyo_+wpurs3ovtxlpyf4guan+xkus...@mail.gmail.com
Bug#763278: wheezy-pu: gcc-4.9/4.9.1-14~deb7u1
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 quantify soon? In order to continue providing security updates for chromium in wheezy, I would like to propose a gcc wheezy-pu. I haven't tried to get this working yet, and am sending this to see whether the release team would even consider this. Have you discussed this with the gcc maintainers? What's their opinion on the idea, in terms of feasibility and supportability? 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. Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1412100625.13798.2.ca...@jacala.jungle.funky-badger.org
Processed: Re: Bug#763278: wheezy-pu: gcc-4.9/4.9.1-14~deb7u1
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 UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b763278.14121006352571.transcr...@bugs.debian.org
Bug#763278: wheezy-pu: gcc-4.9/4.9.1-14~deb7u1
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 up to date chromium. In order to continue providing security updates for chromium in wheezy, I would like to propose a gcc wheezy-pu. I haven't tried to get this working yet, and am sending this to see whether the release team would even consider this. The alternative is to drop chromium security support for wheezy way too soon. I'm proposing gcc 4.9 to hedge against future upstream compiler requirements, but gcc 4.8 would also be an option. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CANTw=MMZ=5frqktmpdjnfz9wv45jy0nh+dm8mzwp-gns955...@mail.gmail.com
