sysupgrade fails with "FAILED" when "verifying sets"?

Hi All,

Today sysupgrade failed for me, but I'm not sure why? Here's the output:
> # sysupgrade -s -n
> Fetching from http://ftp.fau.de/pub/OpenBSD/snapshots/amd64/
> SHA256.sig 100% |***********************************************************************************************************************************************| 2144 00:00
> Signature Verified
> Verifying old sets.
> base72.tgz 100% |***********************************************************************************************************************************************| 332 MB 00:28
> bsd 100% |***********************************************************************************************************************************************| 22470 KB 00:02
> bsd.mp 100% |***********************************************************************************************************************************************| 22578 KB 00:02
> bsd.rd 100% |***********************************************************************************************************************************************| 4546 KB 00:01
> comp72.tgz 100% |***********************************************************************************************************************************************| 75019 KB 00:07
> game72.tgz 100% |***********************************************************************************************************************************************| 2745 KB 00:00
> man72.tgz 100% |***********************************************************************************************************************************************| 7610 KB 00:01
> xbase72.tgz 100% |***********************************************************************************************************************************************| 52860 KB 00:05
> xfont72.tgz 100% |***********************************************************************************************************************************************| 22967 KB 00:02
> xserv72.tgz 100% |***********************************************************************************************************************************************| 14815 KB 00:02
> xshare72.tgz 100% |***********************************************************************************************************************************************| 4573 KB 00:01
> Verifying sets.
> (SHA256) base72.tgz: FAILED
> (SHA256) bsd: FAILED
> (SHA256) bsd.mp: FAILED
> (SHA256) bsd.rd: FAILED
> (SHA256) comp72.tgz: FAILED
> (SHA256) game72.tgz: FAILED
> (SHA256) man72.tgz: FAILED
> (SHA256) xbase72.tgz: FAILED
> (SHA256) xfont72.tgz: FAILED
> (SHA256) xserv72.tgz: FAILED
> (SHA256) xshare72.tgz: FAILED

I see that the sha256 digests/checksums in "SHA256" differ from those of
the downloaded files:
> mjoelnir:_sysupgrade 12.12 13:02:53 [$?==1]# grep bsd.rd SHA256
> SHA256 (bsd.rd) = 9065a190be5eaf047c1c0ece2517712e21964c17f39bebe3420aba2372c054ad
> mjoelnir:_sysupgrade 12.12 13:03:15 # sha256 bsd.rd
> SHA256 (bsd.rd) = 84ce928ccf6d71ebe5e7673aa198e424a9fdaf409d64723ba6dc8cd9333d9388

I don't know if that's the problem though ...

I have never really used signify before, but this command from the man
page also generates an error:
> mjoelnir:_sysupgrade 12.12 13:03:30 # signify -C -p /etc/signify/openbsd-73-base.pub -x SHA256
> signify: invalid comment in SHA256; must start with 'untrusted comment: '

That file starts like this:
> mjoelnir:_sysupgrade 12.12 13:05:09 # head SHA256
> SHA256 (BOOTIA32.EFI) = e05572dc89a5c2c1ac53962cbf6fecda01dad0d4330d95a27e2d645a63b92d6e
> SHA256 (BOOTX64.EFI) = c9cf5ec60caba47c4b4ad0dc37dc88409ff9b5adb38814de1e35496759c2eed8
> SHA256 (BUILDINFO) = 4d0249887ed7db9e9f336556c33a7e66024e08aeb5643f517b98c0815917529b
> ...

Any suggestions?

Cheers,
Robb.