Richard Narron <[email protected]> wrote: > On Fri, 22 Apr 2022, Lyndon Nerenberg (VE7TFX/VE6BBM) wrote: > > > After the 7.1 update syspatch -c started throwing errors due to a > > missing signatures file: > > > > Patch check: > > syspatch: Error retrieving > > http://ftp.openbsd.org/pub/OpenBSD/syspatch/7.1/amd64/SHA256.sig: 404 Not > > Found > > > > The error is valid. To suppress this message it would make sense to drop > > an empty place holder SHA256.sig file whenever a new release comes out. > > > > The error is caused by the wrong directory name. > > The syspatch/7.1 directory was renamed to syspatch/7.1-no > > Rumor has it that the source patch is good but the syspatch is bad, so > someone renamed the syspatch 7.1 directory to prevent its use. > > Has anyone heard anything "official" about this?
The syspatch was accidentally built from the wrong branch, so upon relinking, it results in a kernel which says it is "7.1-stable". To prevent application of syspatches to the wrong type of system, syspatch(8) inspects 'sysctl kern.version'. It checks you have a normal release system (ie. 7.0 or 7.1). Since this patch renamed the system to "7.1-stable", syspatch(8) will refuse to install future patches. And of course the way this check is coded, it won't let you backout the patch which took the system to 7.1-stable.. Simple instructions for getting over this trouble will be coming along before there is a new syspatch 001_wifi is made available. I estimate a week. People who already installed the 001_wifi syspatch aren't harmed by the fix otherwise, but I have stopped distribution of the file to reduce the number of people in this crossed-over state. (Other than this issue, the syspatch itself was good, it fixes wifi association problems on a number of devices, so people who already have it shouldn't take special measures to get rid of it yet, wait for our advice in a week or so). And of course, the syspatch testing procedures will get another step or two to make sure this doesn't happen again.... So just wait.
