|
OpenBSD Installation and Upgrading Installing and upgrading OpenBSD. |
|
Thread Tools | Display Modes |
|
|||
OpenBSD 7.1 bad patch 71-001_wifi ?
After upgrading to OpenBSD 7.1 earlier today I ran syspatch and
updated the system using patch 71-001_wifi. But later now when I run syspatch -c I get this error: #syspatch -c syspatch: Error retrieving https://cdn.openbsd.org/pub/OpenBSD/...64/SHA256.sig: 404 Not Found It seems odd and I looked at the directory, https://cdn.openbsd.org/pub/OpenBSD/syspatch/ and the 7.1 patch directory is gone!. It has been renamed to 7.1-no thus triggering the SHA256.sig 404 error...
__________________
When you see a good move, look for a better one. --Lasker |
|
|||
Quote:
Earlier I tried to revert the patch with syspatch -r and that failed, so I reverted it manually: Code:
#tar -C / -xvf /var/syspatch/71-001_wifi/rollback.tgz #/usr/libexec/reorder_kernel
__________________
When you see a good move, look for a better one. --Lasker Last edited by comet--berkeley; 23rd April 2022 at 02:39 AM. Reason: rename rollbackotgz to rollback.tgz |
|
|||
Thanks jggimi, comet--berkeley
I applied it also and will keep an eye on this thread and @misc hoping a fix eventually comes out. If nothing comes out before the next patch (if any), I will follow what comet--berkeley did. But, does anyone know if comet--berkeley's instructions fix will correct syspatch(8) too ? At least I am having no issues
__________________
[t]csh(1) - "An elegant shell, for a more... civilized age." - Paraphrasing Star Wars (tvtropes.org) Last edited by jmccue; 23rd April 2022 at 02:23 AM. Reason: fixed |
|
|||
jggimi is correct. The patch does not need to be removed.
Quote:
Quote:
Re: Sprurios errors from syspatch -c Quote:
__________________
When you see a good move, look for a better one. --Lasker |
|
||||
The Project will be publishing a fix for those of us who installed the patch via syspatch(8). One of my -release systems is affected, so I'll be following their guidance when published.The Project's guidance might be the same. But it could be different. I'm going to wait and see. I would recover my one affected system by restoring from backup, if I was concerned. But I'm not concerned. The only thing impacted by the broken syspatch that has been withdrawn is that it broke syspatch(8).
|
|
|||
The "bad" patch is now good again
__________________
When you see a good move, look for a better one. --Lasker |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
LibreSSL - Patch Burden Increases for OpenBSD Developers | shep | News | 1 | 18th January 2021 11:25 AM |
5.9 amd64 kernel panic after 004_mbuf.patch.sig patch | shep | OpenBSD General | 0 | 2nd May 2016 04:34 PM |
Patch for OpenBSD 5.6 httpd(8) | J65nko | OpenBSD General | 12 | 7th January 2015 12:49 PM |
Patch 007 | hitest | OpenBSD Security | 3 | 7th June 2014 05:17 PM |
Patch question | Mr-Biscuit | Off-Topic | 6 | 4th May 2010 07:47 PM |