workaround: use a hex key id. i'll upload release 3.0.5 with a fix for this issue in the next days, but that won't make it back into stable: this issue is not important enough.
Thank you!
I’m pretty sure there is a regression here (my backup process was working fine until I upgrade the system to debian 13), and that’s why I’ve declared the issue as important.
But if I’m the only one having the issue, it’s ok for me to apply a pin rule for the package.
