[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#763278: marked as done (wheezy-pu: gcc-4.9/4.9.1-14~deb7u1)

Your message dated Sat, 31 Jan 2015 17:17:25 -0500
with message-id <CANTw=MOMHSOg+W1OYFGXjZGQhv=jyxzSYZF7rzMMhvsaN5Dfwg@mail.gmail.com>
and subject line Re: Bug#763278: gcc 4.9 wheezy-pu?
has caused the Debian Bug report #763278,
regarding wheezy-pu: gcc-4.9/4.9.1-14~deb7u1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
763278: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763278
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
User: release.debian.org@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

--- End Message ---
--- Begin Message --- 
On Thu, Oct 9, 2014 at 11:01 PM, Michael Gilbert wrote:
> I would like to ask for your opinion about uploading a newer gcc
> version to wheezy?

I am no longer looking into this.

Best wishes,
Mike

--- End Message ---
Reply to: