commit 3c60b37ec37008a582330d6cb42e46bfe675d01d
Author: Ken McDonell <kenj@kenj.id.au>
Date: Sun May 24 17:15:54 2026 +1000
Fix: rpm build broken by Multilib changes in Debian build
Of course it would ... the rpm build reaches back round to use
the package "manifest" files from the Debian build, and some of
these now contain a usr/lib/*/libpcp_... instead of a
usr/lib/libpcp... that the rpm build is expecting.
Rewrite these "manifest" files on the fly during the rpm build.
modified: build/rpm/pcp.spec.in
modified: build/rpm/redhat.spec
commit 9ead848e1ba451bc92adf655d7a8865fcfc868c0
Author: Ken McDonell <kenj@kenj.id.au>
Date: Sun May 24 13:37:57 2026 +1000
Makepkgs & qa/admin/myconfigure: revert dh_auto_configure change
We cannot run dh_auto_configure safely as a drop-in replacement
for ./configure outside the Debian build ecosystem ... will need
to find another way here to make Multilib paths appear for these
scripts when building for Debian-based systems.
commit 14f40296f14829b754b659762a8656787b282684
Author: Ken McDonell <kenj@kenj.id.au>
Date: Sun May 24 12:36:13 2026 +1000
Debian build: fix serious Multilib problem
In commit 704b93c3b I changed from using ./configure to using
dh_auto_configure to address a botch in the build for armhf.
This had the unfortunate side-effect of activating Debian's Multiarch
feature (that we had not previously been using in the build),
which moved *all* of the PCP libraries from /usr/lib to (on bozo)
/usr/lib/x86_64-linux-gnu and this meant the .install files for *all*
the library packages missed their intended library and all of the
libraries "migrated" to the pcp package, as you can see here.
kenj@bozo:~$ dpkg-query -S /usr/lib/x86_64-linux-gnu/libpcp.so
pcp: /usr/lib/x86_64-linux-gnu/libpcp.so
qa/1648 was supposed to detecting this sort of problem, but it requires
lintian to be installed (not in the package-list files) and so in
the QA Farm was _notrun on lots of Debian-based platforms (but I was
distracted with travel and pmUnits changes and didn't notice the 3
failures), and this test is marked _not_in_ci (because lintian takes so
long to run) and was never being run in the github QA action.
First we need to fix the .install files using a * glob for the extra
directory level.
Then, since pcp-7.1.4 has escaped we need the whole Breaks+Replaces
circus for *all* the packages that lost their libraries.
And finally, this explains why
$ sudo make install
recently stopped working in the library source directories, so there
is an additional change in Makepkgs and (more importantly)
qa/admin/myconfigure to use dh_auto_configure in preference to
./configure for Debian-based platforms so a developer's
$ sudo make install
updates libraries in the same place where the package installer has
dumped 'em.
commit fa63a3052c4f28e54a1a3e23c1899da688989702
Author: Nathan Scott <nathans@redhat.com>
Date: Fri May 22 13:07:46 2026 +1000
qa: add pmdards filtering in common.filter
commit 0574edacb5941c0142e9b501708c08650b31bbe8
Author: Nathan Scott <nathans@redhat.com>
Date: Fri May 22 13:07:23 2026 +1000
docs: bump version for next planned release
There are 4 open security issues in bookworm.
You can find information about how to handle these issues in the security team's documentation.
![[bug history graph]](https://qa.debian.org/data/bts/graphs/p/pcp.png){kind=link}