I had difficulties reproducing the issue with piuparts, but I manage to reproduce the problem as I suspected, with the following upgrade path, most likely because of the inconsistent makeblastdb version between the one used for building kleborate in bookworm and the one "refreshed" during postinst by the one available in bullseye:
1. kleborate from bullseye - ncbi-blast+ from bullseye dpkg --verify raises no complaints 2. kleborate from bookworm - ncbi-blast+ from bullseye dpkg --verify starts complaining here! 3. kleborate from bookworm - ncbi-blast+ from bookworm dpkg --verify still complains! Upgrading on top of that with a package that only relies on postinst script (and prerm to manually cleanup the artifacts): 4. kleborate fixed - ncbi-blast+ from bookworm dpkg --verify raises no complaints The prerm change is important to ensure there are no leftovers during package removal and purge. The following upgrade path is also fixed: 2. kleborate fixed - ncbi-blast+ from bullseye dpkg --verify raises no complaints 3. kleborate fixed - ncbi-blast+ from bookworm dpkg --verify still raises no complaints I just pushed my changes on salsa and will upload shorly if CI tests do not raise anything else outstanding I would have missed otherwise. Have a nice day, :) -- Étienne Mollier <emoll...@emlwks999.eu> Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/3, please excuse my verbosity.
signature.asc
Description: PGP signature