deps: bump restic/restic from 0.17.2 to 0.17.3 in /config/ansible/roles/ferrarimarco_home_lab_node/files/config/restic in the home-lab-workloads group across 1 directory

[dependabot]

Bumps the home-lab-workloads group with 1 update in the /config/ansible/roles/ferrarimarco_home_lab_node/files/config/restic directory: restic/restic.

Updates restic/restic from 0.17.2 to 0.17.3

Release notes

Sourced from restic/restic's releases.

restic 0.17.3

Changelog for restic 0.17.3 (2024-11-08)

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

Summary

• Fix #4971: Fix unusable mount on macOS Sonoma
• Fix #5003: Fix metadata errors during backup of removable disks on Windows
• Fix #5101: Do not retry load/list operation if SFTP connection is broken
• Fix #5107: Fix metadata error on Windows for backups using VSS
• Enh #5096: Allow prune --dry-run without lock

Details

• Bugfix #4971: Fix unusable mount on macOS Sonoma

  On macOS Sonoma when using FUSE-T, it was not possible to access files in a mounted repository. This issue is now resolved.

  #4971 #5048

• Bugfix #5003: Fix metadata errors during backup of removable disks on Windows

  Since restic 0.17.0, backing up removable disks on Windows could report errors with retrieving metadata like shown below.

  error: incomplete metadata for d:\filename: get named security info failed with: Access is denied.
  

  This has now been fixed.

  #5003 #5123 https://forum.restic.net/t/backing-up-a-folder-from-a-veracrypt-volume-brings-up-errors-since-restic-v17-0/8444

• Bugfix #5101: Do not retry load/list operation if SFTP connection is broken

  When using restic with the SFTP backend, backend operations that load a file or list files were retried even if the SFTP connection was broken. This has now been fixed.

  #5101 https://forum.restic.net/t/restic-hanging-on-backup/8559

• Bugfix #5107: Fix metadata error on Windows for backups using VSS

  Since restic 0.17.2, when creating a backup on Windows using --use-fs-snapshot, restic would report an error like the following:

  error: incomplete metadata for C:\: get EA failed while opening file handle for path \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopyXX\, with: The process cannot access the file because it is being used by another process.
  

... (truncated)

Changelog

Sourced from restic/restic's changelog.

Changelog for restic 0.17.3 (2024-11-08)

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

Summary

• Fix #4971: Fix unusable mount on macOS Sonoma
• Fix #5003: Fix metadata errors during backup of removable disks on Windows
• Fix #5101: Do not retry load/list operation if SFTP connection is broken
• Fix #5107: Fix metadata error on Windows for backups using VSS
• Enh #5096: Allow prune --dry-run without lock

Details

• Bugfix #4971: Fix unusable mount on macOS Sonoma

  On macOS Sonoma when using FUSE-T, it was not possible to access files in a mounted repository. This issue is now resolved.

  restic/restic#4971 restic/restic#5048

• Bugfix #5003: Fix metadata errors during backup of removable disks on Windows

  Since restic 0.17.0, backing up removable disks on Windows could report errors with retrieving metadata like shown below.

  error: incomplete metadata for d:\filename: get named security info failed with: Access is denied.
  

  This has now been fixed.

  restic/restic#5003 restic/restic#5123 https://forum.restic.net/t/backing-up-a-folder-from-a-veracrypt-volume-brings-up-errors-since-restic-v17-0/8444

• Bugfix #5101: Do not retry load/list operation if SFTP connection is broken

  When using restic with the SFTP backend, backend operations that load a file or list files were retried even if the SFTP connection was broken. This has now been fixed.

  restic/restic#5101 https://forum.restic.net/t/restic-hanging-on-backup/8559

• Bugfix #5107: Fix metadata error on Windows for backups using VSS

  Since restic 0.17.2, when creating a backup on Windows using --use-fs-snapshot, restic would report an error like the following:

... (truncated)

Commits

• bc64921 Add version for 0.17.3
• 633883b Generate CHANGELOG.md for 0.17.3
• 8348024 Prepare changelog for 0.17.3
• c3f5748 Merge pull request #5126 from restic/polish-changelogs
• 06ba4af doc: Polish changelogs before release
• fb4d9b3 Merge pull request #5125 from restic/patch-release-cherrypicks
• 7bfe3d9 fs: fallback to low privilege security descriptors on access denied
• d46525a fix double printf usage
• 3800eac prepare-release: improve handling of release from non-master branch
• 75f317e sftp: check for broken connection in Load/List operation
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions