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. > 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. The reason being that very few packages are security maintained with new upstream versions anyway (iceweasel, mysql as examples), and chromium is the only one known to be willing to entirely break support so quickly. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-security-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CANTw=moohrgckgbnpmgt3cpyv+rhz+4xbietrtzgtifwn2l...@mail.gmail.com
