The rules are clear.
syspatch only works on against official releases.
We are not going to change this code to handle piece-meal adjustments
and the potential shitshow that could occur.
So you get to run release (and use syspatch), or you are on your own and
probably following -current / snapshots.
There are no other use patterns available.
So you are on your own.
Benjamin Stürz <benni+open...@stuerz.xyz> wrote:
> Hi misc@,
>
> out of curiosity I recently compiled a custom kernel
> and now syspatch(8) fails with:
> syspatch: Unsupported release: 7.3-stable
>
> Taking a short look at /usr/sbin/syspatch reveals the following lines:
> > set -A _KERNV -- $(sysctl -n kern.version |
> > sed 's/^OpenBSD \([1-9][0-9]*\.[0-9]\)\([^ ]*\).*/\1 \2/;q')
> > ((${#_KERNV[*]} > 1)) && err "Unsupported release: ${_KERNV[0]}${_KERNV[1]}"
>
> This tells me that using syspatch(8) is not supported on -stable.
>
> But I actually only run a -stable kernel.
> The userspace is still -release + syspatch.
>
> Do I have to compile the entire userspace too,
> if I want to use a custom kernel?
> Or is there some other way of using a custom kernel
> AND using syspatch for userspace?
>
> PS: I update my /usr/src with:
> $ cvs -qd $CVSROOT up -Pd -rOPENBSD_7_3
>
> PS 2: I compile with
> COPTIMIZE=-O3 -march=native -mtune=native
> and no crashes so far.
>
> I might try -Ofast in the future.
>
> Best regards,
> Benjamin Stürz
>
