On 03/08/16 02:02, Peter Colberg wrote: > Dear Debian Release Team, > > twinkle has been marked for autoremoval from testing on 2016-08-27 due > to this FTBFS. Building ucommon with GCC 6 instead of GCC 5 yields > slight differences in the list of visible symbols. > > How should this bug be dealt with? Is it not simply a matter of > waiting for GCC 6 to become default, uploading ucommon with an > updated symbols file and an ABI bump (if needed), and submitting > binNMUs for dependent packages?
Yes. > If so, can this bug be downgraded to severity important until then? No. Just ping the bug to restart the timer if that becomes necessary (e.g. that date gets closer and GCC 6 is not the default yet). Cheers, Emilio
