On 2017-06-22, tomr <[email protected]> wrote: > > > On 06/21/17 20:17, Bryan Linton wrote: >> Upgrading to a snapshot and seeing if that makes any difference >> would be a simple way to see if anything in -current has fixed the >> issue you're seeing too. > > I thought "upgrading to a snapshot" was not recommended, with either > "installing a snapshot" or "upgrading to a more recent snapshot" being okay. > > https://www.openbsd.org/faq/current.html says "You should always use a > snapshot as the starting point for running -current." > > But as it goes on to say "Upgrading by compiling your own source code is > not supported" - without mentioning release -> snapshot, maybe I've read > that over-cautiously. > > Clarification appreciated! > > t > >
These warnings mean something like: "don't move straight from a release or an older snapshot directly to building new code from source (whether that's -current or a newer release)". If there is much of a gap between the version you're running and the version you want to move to, boot the install kernel from a recent snapshot and 'u'pgrade to that, then boot and upgrade all packages (pkg_add -u). If you are looking to see if something has been fixed in recent code, just moving to a snapshot is usually enough. Snaps are built often. If you want to build all or part of the base system from source (e.g. to test a diff, add some debug code, or test a fix which has been committed *very* recently), install a recent snapshot first, then try building.
