Please test, merge, and sign packages again if everything looks good testing-wise, with:
./ppa -r pirogue-3rd-party
(Just to be on the safe side, in case some users are lagging behind and still didn't get the new pirogue-archive-keyring package, I'm not updating Packages* and Release* files on my own.)
Note: Since 16.5.4 FTBFS'd on my bookworm host, I've upgraded all QEMU packages from bookworm to bookworm-backports, and that fixed the segfaults/internal compiler errors I was getting with cc during the arm64 crossbuild. All packages up to and including 16.5.2 were built using the bookworm QEMU packages. All packages starting with 16.5.3 were built using the bookworm-backports QEMU packages (that particular version was rebuilt to have another data point after the upgrade).
Please test, merge, and sign packages again if everything looks good testing-wise, with:
(Just to be on the safe side, in case some users are lagging behind and still didn't get the new
pirogue-archive-keyringpackage, I'm not updatingPackages*andRelease*files on my own.)Note: Since 16.5.4 FTBFS'd on my
bookwormhost, I've upgraded all QEMU packages frombookwormtobookworm-backports, and that fixed the segfaults/internal compiler errors I was getting withccduring thearm64crossbuild. All packages up to and including 16.5.2 were built using thebookwormQEMU packages. All packages starting with 16.5.3 were built using thebookworm-backportsQEMU packages (that particular version was rebuilt to have another data point after the upgrade).