[Debian-med-packaging] Bug#1036743: Bug#1036743: kleborate: debsums reports modified files after apt-get upgrade && apt-get dist-upgrade

[Andreas Beckmann]

On 25/05/2023 14.42, Andreas Tille wrote:
> Am Thu, May 25, 2023 at 10:34:10AM +0200 schrieb Étienne Mollier:
>>
>> Installation of kleborate from sid and testing shown no issues.
>> Installation of kleborate from bullseye on bullseye is okay too.
> 
> Good.  Maybe we should reflect in BTS that this bug is not relevant for
> bookworm?

It is relevant for bookworm, it's just not happening in the upgrade 
tests on piuparts.d.o (because that does no 2-step upgrades)

In the failing test kleborate got upgraded during 'apt-get upgrade' 
while ncbi-blast+ only got upgraded during the subsequent 'apt-get 
dist-upgrade'. So the kleborate.postinst from bookworm was actually 
running makeblastdb from bullseye, creating files in the "older" format.
Are these "old format" files still correctly usable after the 
dist-upgrade has been performed? Or would that need some kind of trigger 
mechanism to regenerate these files with the newer makeblastdb version?

>> I haven't checked closely yet, but I suspect the .ndb and .ntf
>> should be removed from the .deb and rely entirely on mkaeblastdb
>> to produce the files.  Looking that up…
> 
> Without checking this seems to be a sensible assumption.

Yes. Either the file is created at build time or at installation time. 
Doing both does not look like a sensible idea to me.
(And it didn't produce identical files, otherwise I wouldn't have 
noticed this bug)

Andreas