But PCP is going to be autoremoved from testing on 3 Jan 2025. I do not want
that to happen, and if the bpftrace issue does get resolved in the future I can
re-instate the Build-Depends: for PCP.
It is only one (small) part of PCP that depends in bpftrace and the existing
configure-and-build mechanisms will build and package PCP even if the bpftrace
component is not available (strictly speaking bpftrace is not used in the PCP
build and should never have been in PCP's Build-Depends).
The autoremoval email I recieved says this:
pcp 7.0.5-1 is marked for autoremoval from testing on 2026-01-03
It (build-)depends on packages with these RC bugs:
1120134: bpftrace: fails to migrate to testing for too long
As I understand it, although PCP is the victim here, the only thing I can do to
prevent the autoremoval of PCP from testing is to break the build-dependency on
bpftrace ... if there is some other way to avoid the autoremoval of PCP, please
tell me how.
