Package: pcp
Version: 5.2.1-1
Severity: serious
Tags: patch

The recent 5.2.1-1 upload made a dependency change to pcp:

 Package: pcp 
-Depends: ${shlibs:Depends}, ${misc:Depends}, gawk, procps, libpcp-pmda-perl, 
python3-pcp, python3, libpcp-web1
+Depends: ${shlibs:Depends}, ${misc:Depends}, gawk, procps, libpcp-pmda-perl, 
python3-pcp, python3, bpftrace (>= 0.9.2), libpcp-web1

But the "bpftrace" package only exists on a few architectures [1]. This is what
makes the package uninstallable and prevents testing migration [2].

Please fix
that at least by restricting the architectures, like so:

  Depends: ${shlibs:Depends}, ${misc:Depends}, gawk, procps, libpcp-pmda-perl, 
python3-pcp, python3, bpftrace (>= 0.9.2) [amd64 arm64 ppc64 ppc64el], 
libpcp-web1

Preferably you would also drop it to Recommends:, as hopefully bpftrace isn't
an absolute requirement for running PCP? I.e.

  Depends: ${shlibs:Depends}, ${misc:Depends}, gawk, procps, libpcp-pmda-perl, 
python3-pcp, python3, libpcp-web1
  Recommends: bpftrace (>= 0.9.2)

Thanks!

Martin

[1] https://packages.debian.org/sid/bpftrace
[2] https://tracker.debian.org/pkg/pcp

Attachment: signature.asc
Description: PGP signature

Reply via email to