On 8/21/26 5:23 PM, Nick Holland wrote:
On 8/21/26 4:54 PM, Sonic wrote:
Getting:
"Downloaded snapshot is older than installed system. Use -f to force downgrade."
When doing sysupgrade -s.
Currently at:
OpenBSD 8.0-beta (GENERIC.MP) #103: Fri Aug 21 11:39:58 MDT 2026
Build date: 1787334687 - Fri Aug 21 17:51:27 UTC 2026

Was an update pulled? Anything to worry about? Should I force a
downgrade or just wait and let it resolve itself?

Thank you.

I'm not claiming my memory is accurate here -- but I think that you get that
same message if you try to sysupgrade to the SAME version.

vvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
That would be wrong!!! <<<
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
I remembered a machine I had that was overdue for an upgrade, so ran it
to -current, and then tried again:
/home/nick $ doas sysupgrade -ks
Fetching from https://openbsd.cs.toronto.edu/pub/OpenBSD/snapshots/amd64/
SHA256.sig   100% |*************************************|  2144       00:00
Signature Verified
Already on latest snapshot.

I'm late to think of this: are you using a cdn?  If running snapshots,
I'm going to suggest NOT doing that -- it is possible the Content Delivery
Network is pulling from a mirror with an older snapshot for your second
upgrade. Pick a well managed mirror that gives you good performance, and run
with that.

Keep in mind, amd64 is probably the fastest OpenBSD platform to build. Looking
through my logs, I see there are often two or three snapshots a day coming
through, and unfortunately, it's something of an asynchronous process.  Not
all mirrors update at the same instant.  CDNs can decide different mirrors are
better at different moments, so you might get one  still downloading the latest
snap (it sounds like sometimes you can get different files off different 
mirrors,
too, which is a whole different bundle of joy).

CDNs work great for releases. Not good for snapshots.

(this is where you say, "I'm not using a CDN" :) )


IF you aren't using a CDN, pull bsd.mp from your favorite mirror and see
what build it is.

Nick.

Reply via email to