Bug#836370: transition: shibboleth

[wferi@niif.hu (Ferenc Wágner)]

Emilio Pozuelo Monfort <pochu@debian.org> writes:

> On 03/09/16 15:58, Ferenc Wágner wrote:
>
>> I'm finished with the uploads.  Xmltooling, opensaml2 and shibboleth-sp2
>> all built on the testing architectures.  Please trigger rebuilds of
>> shibboleth-resolver and moonshot-gss-eap
>
> Scheduled.

Thanks.  They looks mostly good on the transition trackers.  The build
logs don't explain the "bad" shibboleth-resolver states on amd64 and
i386 (to me), I hope it's just some transient.

>> (possibly also opensaml2 on powerpcspe, if you handle ports).
>
> That failed to build. A binnmu makes no sense. Perhaps you meant a
> give back? Why do you think that would help?

Yes, the powerpcspe and sh4 builds should be tried again.  They failed
because they somehow overtook the new xmltooling builds and thus met a
pre-C++11 libxmltooling.

Do you think there's anything else to do (but wait for testing
migration) with this transition?  I don't understand why opensaml2 and
shibboleth-sp2 are "partial" on all arches except the hurd, could you
please give me a hint?  It's the first time I look at such tables...
-- 
Thanks,
Feri