On 20/01/16 18:14, Martin Michlmayr wrote: > * Daniel Pocock <[email protected]> [2016-01-20 08:31]: >>> Note that only the first error is reported; there might be more. You >>> can find a snapshot of GCC 6 in experimental. To build with GCC 6, >>> you can set CC=gcc-6 CXX=g++-6 explicitly. >> Is it possible to submit reports like this with the output from "make -i >> -k" so that we can see all the errors? This would make it easier for >> people to see the size of the task when triaging the bug. > I'm not sure this is easily possible. I need to think about it. > OTOH, one hope of these bug reports is that maintainers will create a > GCC 6 chroot and test future uploads, so -k wouldn't help with that. >
Some maintainers are probably not fixing issues like this themselves, they are just forwarding the email or BTS link to upstream. If the upstream developer has to set up a chroot then that might slow their response but if we had a way to show them the total size of the problem (is it just 1 error or are there 500 errors) then they might respond more quickly (if it is really just one error) or we might have a better way of understanding that the move to GCC 6 needs to slow down (if many packages have hundreds of errors). Regards, Daniel
