On Wed, Feb 04, 2015 at 09:38:17PM +0100, Paul van der Vlis wrote: > Op 04-02-15 om 15:40 schreef Michael Gilbert: > > On Mon, Feb 2, 2015 at 11:46 AM, Paul van der Vlis wrote: > >> I think it's a good idea to do a backport of the build-system after > >> freeze-time of testing. Then we know what the new build-environment is > >> for the coming release. > >> > >> I can understand that Michael does not have the time and motivation for > >> such a backport, Chromium will take much time. But maybe others have. > > > > The backports team expects backporters to have demonstrated competence > > with the packages that they're planning to upload. Anyone considering > > this should first get involved with the package maintenance teams > > first and help with a few unstable uploads. > > I understand. Good thing. But maybe the normal packagers could think > about a backport. Or to help with it. > > >> And there will be more packages with this problem, e.g. Iceweasel and > >> Icedove. > > > > There are unlikely to be any other packages facing the build > > environment problem during wheezy's lifetime, so it's quite likely not > > worth the effort. > > In the past, Iceweasel and Icedove never had a year security support > after a new release.
I'm curious to know where that's coming from. Iceweasel and Icedove have always received security support, even if that means upgrading to a new version. Mike -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
