applied: [PATCH proxmox{,-backup} v4 0/5] fix #6990: server: drop verify state on push & pull job

[Thomas Lamprecht <t.lamprecht@proxmox.com>]

On Thu, 15 Oct 2026 14:16:54 +0200, Jakob Klocker wrote:
> When syncing a snapshot to another datastore, the source's verify_state
> is currently carried over to the target. This reports the target
> snapshot as verified even though its stored copy was never checked
> there. Since verify jobs skip snapshots that already carry a
> verify_state, the target's copy can't be verified again.
> 
> Chunks are checksummed in memory while being transferred, but a verify
> serves a different purpose: confirming the write to the (external)
> target actually succeeded.
> 
> [...]

Applied, thanks!

I folded a few changes into patch 4/5, namely:
- the target's own verify state is now also dropped when an archive got
  re-synced, as the old result does not cover the rewritten data
- the "nothing changed" fast path compares the manifests ignoring the
  verify state, as otherwise a verified source could never match its
  stripped target copy again, so every pull re-hashed all archives and
  rewrote, and for S3 re-uploaded, the manifest
- the manifest is written through the shared replace_file helper

[proxmox] applied to git/proxmox.git (master)
[1/5] pbs-api-types: implement Hash and Borrow<str> for BackupArchiveName
      commit: f00b1061ba7e19f620e1ad1f7b0003b4c46d5097

[proxmox-backup] applied to git/proxmox-backup.git (master)
[2/5] server: pull: run blocking file operations on the blocking pool
      commit: b98c63f34d8ccecb78ec8737df9e5b760dc75ff3
[3/5] pbs-datastore: pass expected files to cleanup_unreferenced_files
      commit: 908ba15753aedb9822bcfed6e217cb1acc9cd1c2
[4/5] fix #6990: server: drop verify state on non-decrypt pull job
      commit: 7241811f7ed6224fa02294053b0953b9453ed417
[5/5] fix #6990: server: drop verify state on push job
      commit: bae3060140198d7cdbb3dc37ac08d8356fabf577