Hi Felix,
I took the liberty of updating restic to version 0.12 because I needed to use the rewritten prune feature to clean up a repository that was left unattended for too long. For this, I also had to update the golang-github-cenkalti-backoff package to version 4.1.0, which you updated in git but never got uploaded.
- restic (well, the point of this exercise is to get to 0.12)
- golang-github-xenolf-lego
So, it seems to me that in order to have restic 0.12 in unstable, we'd need 3 uploads. All of these packages have autopkgtests and would TTBOMU pass the soft freeze policy.
Any thoughts/concerns?
--
regards,
Reinhard