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
On Tue, Jul 12, 2016 at 09:56:12PM +0100, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
>
> On Thu, 2016-06-30 at 22:19 +0200, Moritz Muehlenhoff wrote:
> > +harfbuzz (0.9.35-2+deb8u1) jessie; urgency=medium
> > +
> > + * Backport upstream commit 613e630617074eb9b62b794cc37c9b42a7fb079b
On 26/07/16 01:32, Matthias Maier wrote:
>
> On Mon, Jul 25, 2016, at 16:05 CDT, Emilio Pozuelo Monfort
> wrote:
>
>> What's the bug number?
>
> There is no reported bug so far.
>
>> A binNMU to workaround an ABI break is usually the wrong approach,
>> unless there has been
3 matches
Mail list logo