Syspatch can't fetch 7.1's patches.

[Zielonykid123]

So, I got a http 404 error everytime i run syspatch on OpenBSD 7.1 GENERIC, installurl is tries to fetch patches from https://cdn.openbsd.org/pub/OpenBSD/syspatch/7.1/, however there is no such directory, there is 7.1-no/. What to do?

[comet--berkeley]

Originally Posted by Zielonykid123

So, I got a http 404 error everytime i run syspatch on OpenBSD 7.1 GENERIC, installurl is tries to fetch patches from https://cdn.openbsd.org/pub/OpenBSD/syspatch/7.1/, however there is no such directory, there is 7.1-no/. What to do?

The first patch was a good patch but it broke syspatch. The patch was retracted by renaming the syspatch directory to 7.1_no

The errata link will contain information when syspatch is fixed again:

OpenBSD 7.1 Errata

[Zielonykid123]

Originally Posted by comet--berkeley

The errata link will contain information when syspatch is fixed again:
OpenBSD 7.1 Errata

I need to wait? linker runs every startup and tries to relink my kernel which is already relinked (It's GENERIC 7.1). I don't know if this is related to the syspatch issue but it may be. I can create a new thread about it.. Thanks.

[jggimi]

The answer from the Project is ... for now... either install the patch from source or wait. The provided syspatch was in error and a replacement has not yet been published.

Kernel relink at boot has been the standard action for the OS for several years. It's a security feature.

[jggimi]

Originally Posted by jggimi

Kernel relink at boot has been the standard action for the OS for several years. It's a security feature.

This feature was announced in 2017 with OpenBSD 6.2:

Originally Posted by 6.2 Release Announcement

Kernel Address Randomized Link (KARL), a new "link-kit" allows the .o files of the kernel to be relinked in a random order, creating a unique kernel for each boot.

[jggimi]

The OpenBSD Project has just corrected the syspatch:


http://www.openbsd.org/errata71.html