[ Reason ]
Jody Bruchon, the jdupes author, told me that the hash database feature is
disabled due to a conditional logic error introduced in v1.28.0 during the
major hashdb changes.

The condition was inadvertently written with the opposite logic, completely
disabling the hash database functionality.

[ Impact ]
This does not affect the correctness of jdupes results or pose any data
integrity risk, but causes a significant performance regression, especially
when processing large, unchanging datasets where the hash database provides
substantial performance improvements.

Several Debian packages use jdupes during the package build process.

[ Tests ]
Some manual tests were performed to confirm that the package works fine after
fixing the issue.

[ Risks ]
This is a small and straightforward change provided by upstream, with no
expected risks.

[ Checklist ]
  [x] *all* changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in (old)stable
  [x] the issue is verified as fixed in unstable

[ Changes ]
A small patch provided by upstream was applied. This fix is closing the bug
#1148491.

[ Other info ]
No more info.

I am closing this trixie-pu because we have issues with i386 CI tests.

I will wait for a solution from upstream.

Eriberto

I am reopening this PU.

After talking with upstream and conducting some additional tests on Trixie
i386, I confirm the changes are working fine for jdupes-1.28.0 on all archs,
so they are ready to be applied now.

Sorry for this confusion.

Regards,

Eriberto