1. KOHA_IMAGE=main-bookworm ktd up 2. prove xt/perltidy.t 3. leave running for like a minute, it passes, don't bother with full run 4. KOHA_IMAGE=main-trixie ktd up 5. prove xt/perltidy.t 6. failures quickly pile up D12: perltidy --version This is perltidy, v20230309 dpkg -l | grep tidy 20230309-1~koha3 (ours) D13: perltidy --version This is perltidy, v20250105 dpkg -l | grep tidy 20250105-1 So in KTD, the D13 image doesn't ship our perltidy so it uses Debian's which is more recent. And might use some different default that aren't covered by our current config. I guess it would be better to complete the config so that both version of perltidy output the same code, right? Rather than making the D13 image ship an old version of perltidy which would postpone the root issue.
Also, it makes the qa script fail if working on Debian 13
(In reply to Victor Grousset/tuxayo from comment #0) > So in KTD, the D13 image doesn't ship our perltidy so it uses Debian's which > is more recent. And might use some different default that aren't covered by > our current config. I guess it would be better to complete the config so > that both version of perltidy output the same code, right? Yes, that is what needs to be done.