On 31/08/16 12:00, Sebastiaan Couwenberg wrote:
> On 08/31/16 11:30, Sebastiaan Couwenberg wrote:
>> On 08/31/16 00:41, Emilio Pozuelo Monfort wrote:
>>> On 28/08/16 18:13, Sebastiaan Couwenberg wrote:
>>>> On 08/25/16 19:17, Sebastiaan Couwenberg wrote:
>>>>> On 08/25/16 17:33, Sebastiaan Couwenberg wrote:
>>>>>> Several packages unfortunately fail to build, some due to unrelated
>>>>>> issues to the new protobuf packages. Bugs still need to be filed for
>>>>>> those that weren't sid-ony due to RC bugs already.
>>>>>
>>>>> The bugreports have been filed, and ones specific to protobuf 3.0.0
>>>>> have
>>>>> been usertagged for easy access:
>>>>>
>>>>> https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=protobuf-3.0.0;[email protected]
>>>>>
>>>>>
>>>>>
>>>>
>>>> Release Team, can you schedule binNMUs for the packages that rebuilt OK?
>>>
>>> Scheduled.
>>
>> Thanks, can you also nmu libphonenumber (7.1.0-4), it builds
>> successfully with the changes from protobuf (3.0.0-6).
>>
>> And mosh (1.2.6-1) which I mistakenly marked as NOT-NEEDED which should
>> have been mozc which was already rebuilt via a maintainer upload.

Both scheduled.

> Just for the record, osmium rebuilds are failing because most tests segfault 
> by
> having two version of libdap installed. Caused by the uncoordinated transition
> triggered with the upload of libdap (3.18.0-1) to unstable. gdal needs to be
> rebuilt with the new libdap to fix the issue affecting the osmium package. 
> First
> the libdap build failures on several release architectures need to be fixed.

OK. Looks like libdap is already fixed. I'll look at its binnmus later.

Cheers,
Emilio

Reply via email to