Bug#929318: unblock: papi/5.7.0+dfsg-1
On 18/06/2019 23.05, Paul Gevers wrote:
> Hi pcp maintainers,
>
> On 16-06-2019 14:59, Jonathan Wiltshire wrote:
>> On Sun, Jun 09, 2019 at 11:00:10PM +0200, Andreas Beckmann wrote:
>>> The transition from libpapi5 to libpapi5.7 will require only a single
>>> binNMU: eztrace.
>>
>> Scheduled and will monitor.
>
> We are trying to do a very late transition of papi. However, this is
> blocked by pcp. The current version of pcp in unstable doesn't qualify
> to be unblocked for buster as it is a new release. Can you please revert
> pcp to the version currently in buster (with the +really upstream
> version mechanism)? Otherwise, we'll have to remove pcp to enable papi
> to migrate. If we won't do that, papi will be removed (and thus pcp as
> well).
pcp was completely off my radar since it has (silently) dropped all papi
dependencies in unstable.
I'll do a 0-day NMU of pcp on Thursday (36 hours from now) unless we
heard from Nathan till then.
Just thinking ... lazy removal of libpapi5 from testing does not work,
since libpapi5.7 breaks it, and pcp-dev probably depends transitively on
both ... so a soureful tpu upload (since binNMUs in tpu are currently
problematic) does not work either if papi does not migrate ...
Andreas
Reply to: