On 2022/04/04 20:37, Steve Fairhead wrote: > On 04/04/2022 13:10, owner-m...@openbsd.org wrote: > > sysupgrade only copes with what look like release versions (no version > > suffix, upgrades to release+0.1 with no arguments, or snapshot with -s) > > or snapshots (-current or -beta suffix, by default -current upgrades > > to release+0.1 or -beta upgrades to release, or snapshot with -s). > > > > It doesn't handle -stable, and it doesn't handle going from the current > > situation which is "it's still snapshots rather than release but there's > > no suffix" to the forthcoming release. > > I've now upgraded a couple of systems from 6.8 -stable, using "sysupgrade > -r", through 6.9 and then 7.0 (rebuilding and rebooting after patches). They > seem fine. Any gotchas with this?
Ah looking at what that does, it does look alright as a way to handle -stable with just flags rather than patching the script. > To put it another way, what is the recommended way of upgrading a production > system with patches applied (so -stable)? On an arch where syspatches are available (amd64, i386, arm64), the method that would normally be recommended these days would be to use syspatches rather than compiling -stable.
