Bug#871279: libdolfin2016.2: requires rebuild against GCC 7 and symbols/shlibs bump

2017-08-07 Thread Mattia Rizzolo
On Tue, Aug 08, 2017 at 02:29:48AM +0800, Drew Parsons wrote: > It's been sitting in NEW for a month, so it would have been gcc-6 I > think. But the upload is to experimental. I figure we can ignore > anything in experimental, the symbols will get reset for the new ABI > when we drop it into

Bug#871279: libdolfin2016.2: requires rebuild against GCC 7 and symbols/shlibs bump

2017-08-07 Thread Drew Parsons
On Mon, 2017-08-07 at 17:44 +, Mattia Rizzolo wrote: > > > dolfin 2017.1 is in the NEW queue, so that upgrade will handle this > > bug. > > Is the binary you uploaded built with gcc-7?  Otherwise that would > not fix this bug. It's been sitting in NEW for a month, so it would have been

Bug#871279: libdolfin2016.2: requires rebuild against GCC 7 and symbols/shlibs bump

2017-08-07 Thread Mattia Rizzolo
On Mon, 7 Aug 2017, 6:57 p.m. Drew Parsons, wrote: > > - If your package is about to be renamed due to an upstream SONAME > bump, > > you do not need to add any special symbols handling. > > > > > dolfin 2017.1 is in the NEW queue, so that upgrade will handle this > bug. >

Bug#871279: libdolfin2016.2: requires rebuild against GCC 7 and symbols/shlibs bump

2017-08-07 Thread Drew Parsons
On Mon, 07 Aug 2017 15:47:15 +0100 jcowg...@debian.org wrote: > Package: libdolfin2016.2 > Version: 2016.2.0-5 >  > It appears that your package provides an external symbol that is > affected by the recent name mangling changes in GCC 7. See: >

Bug#871279: libdolfin2016.2: requires rebuild against GCC 7 and symbols/shlibs bump

2017-08-07 Thread jcowgill
Package: libdolfin2016.2 Version: 2016.2.0-5 Severity: serious Tags: sid buster User: debian-...@lists.debian.org Usertags: gcc-7-op-mangling Hi, It appears that your package provides an external symbol that is affected by the recent name mangling changes in GCC 7. See: