Hi Paul, Andreas, Apologies for the slow response - I'm in meetings all week this week and I'm a bit behind as a result.
On Thu, Jun 20, 2019 at 9:17 AM Andreas Beckmann <a...@debian.org> wrote: > > On 18/06/2019 23.05, Paul Gevers wrote: > > pcp was completely off my radar since it has (silently) dropped all papi > dependencies in unstable. The PAPI metrics in PCP have been transitioned to using perfevent - one of the several reasons for this was to help resolve this Debian bug. The best outcome for Debian PCP user base here would be to use the bugfix PCP update that has been in unstable for several weeks now - this provides a clean upgrade path for pmdapapi users, and removes the PCP dependency on PAPI completely. > I'll do a 0-day NMU of pcp on Thursday (36 hours from now) unless we > heard from Nathan till then. If we cannot use the tested, stable, upstream bugfix update provided earlier due to the release constraints, please go ahead and NMU as needed Andreas - thanks. > Just thinking ... lazy removal of libpapi5 from testing does not work, > since libpapi5.7 breaks it, and pcp-dev probably depends transitively on FWIW, the PCP development packages do not depend on any PAPI (and never have) - it is only older versions of the 'pcp' package itself, which contain the pmdapapi binary - now retired to help resolve this issue. cheers. -- Nathan
