Update dependency restic/restic to v0.15.1

This MR contains the following updates:

Package	Type	Update	Change
restic/restic	ironbank-github	patch	v0.15.0 -> v0.15.1

---

Release Notes

restic/restic

v0.15.1: restic 0.15.1

Compare Source

We're very pleased to present you restic 0.15.1! This is just a small bugfix release, fixing some issues that arose after 0.15.0 was published.

restic is distributed as a standalone binary: download the correct file for your operating system and architecture, extract the file and just run it. If you run into any issues, please report them at the GitHub issue tracker or visit the forum. If you already have restic >= 0.9.4, you can use restic self-update to get the latest version in a secure way.

The binaries released with each restic version are reproducible, which means that you can reproduce a byte identical version from the source code for that release. Instructions on how to do that in the Developer Documentation.

Changelog for restic 0.15.1 (2023-01-30)

The following sections list the changes in restic 0.15.1 relevant to restic users. The changes are ordered by importance.

Summary

• Fix #​3750: Remove b2_download_file_by_name: 404 warning from B2 backend
• Fix #​4147: Make prune --quiet not print progress bar
• Fix #​4163: Make self-update --output work with new filename on Windows
• Fix #​4167: Add missing ETA in backup progress bar
• Enh #​4143: Ignore empty lock files

Details

• Bugfix #​3750: Remove b2_download_file_by_name: 404 warning from B2 backend

  In some cases the B2 backend could print b2_download_file_by_name: 404: : b2.b2err warnings. These are only debug messages and can be safely ignored.

  Restic now uses an updated library for accessing B2, which removes the warning.

  #​3750 #​4144 #​4146

• Bugfix #​4147: Make prune --quiet not print progress bar

  A regression in restic 0.15.0 caused prune --quiet to show a progress bar while deciding how to process each pack files. This has now been fixed.

  #​4147 #​4153

• Bugfix #​4163: Make self-update --output work with new filename on Windows

  Since restic 0.14.0 the self-update command did not work when a custom output filename was specified via the --output option. This has now been fixed.

  As a workaround, either use an older restic version to run the self-update or create an empty file with the output filename before updating e.g. using CMD:

  type nul > new-file.exe restic self-update --output new-file.exe

  #​4163 https://forum.restic.net/t/self-update-windows-started-failing-after-release-of-0-15/5836

• Bugfix #​4167: Add missing ETA in backup progress bar

  A regression in restic 0.15.0 caused the ETA to be missing from the progress bar displayed by the backup command. This has now been fixed.

  #​4167

• Enhancement #​4143: Ignore empty lock files

  With restic 0.15.0 the checks for stale locks became much stricter than before. In particular, empty or unreadable locks were no longer silently ignored. This made restic to complain with Load(<lock/1234567812>, 0, 0) returned error, retrying after 552.330144ms: load(<lock/1234567812>): invalid data returned and fail in the end.

  The error message is now clarified and the implementation changed to ignore empty lock files which are sometimes created as the result of a failed uploads on some backends.

  Please note that unreadable lock files still have to cleaned up manually. To do so, you can run restic unlock --remove-all which removes all existing lock files. But first make sure that no other restic process is currently using the repository.

  #​4143 #​4152

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this MR and you won't be reminded about this update again.

---

• If you want to rebase/retry this MR, check this box

---

This MR has been generated by Renovate Bot.