Hello, Thanks for the quick reply.Autopkgtests for these architectures have never worked in the past. I believe the package previously benefitted from an unblock related to this particular issue.
The autopkgtests fail because of the default 300s systemd unit startup timeout which is tripped by the slow JVM startup time on those test platforms.
I could upload a modified package which only enables autopkgtests for amd64 and arm64, like I did before with the puppetserver package.
What do you think? -- Jérôme Le 2025-05-05 à 10 h 38, Sebastian Ramacher a écrit :
Control: tags -1 moreinfo On 2025-05-05 10:07:54 -0400, Jérôme Charaoui wrote:Package: release.debian.org Severity: normal User: release.debian.org@packages.debian.org Usertags: unblock Please unblock package puppetdbpuppetdb is in bookworm, so based on that we can grant an exception. However, puppetdb also has failing autopkgtests on armel and riscv64. Please investigate/fix them and remove the moreinfo tag once the issues are resolved.
[ Reason ] PuppetDB was removed from testing in March due to expired x509 certificates among the upstream unit test fixtures. These issues were fixed with the latest upload in unstable, but it missed the soft freeze cutoff by a few days. [ Impact ] Since upstream stopped providing PuppetDB packages for Debian, these packagages have increased significance for the Puppet community. Also, DSA is a user of the PuppetDB package, as far as I know. [ Tests ] The package executes the full suite of unit tests at build time, and autopkgtests are also implemented. [ Risks ] The inclusion of PuppetDB in trixie doesn't carry any risks. [ Checklist ] [x] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [ ] attach debdiff against the package in testing (the package is not yet in testing) [ Other info ] Knowing that we missed the soft freeze deadline for Debian 13, this is a humble request for a freeze exception.