On 2020-10-21, Chris Bennett <cpb_m...@bennettconstruction.us> wrote: > On Tue, Oct 20, 2020 at 08:26:05PM -0400, Brennan Vincent wrote: >> Updated yesterday from 6.7 to a snapshot, and now: >> >> $ doas pkg_add -u > > doas pkg_add -u -Dsnap > > You need to do some things different once you change to -current > snapshots. > Might also have to wait for -current packages to match the -current > snapshot sometimes.
-Dsnap does nothing for most of the year. The only thing it's useful for is pointing to the snapshots directory whdn you're running a kernel with no -beta/-current suffix (i.e. a release, or snapshot in the short period in the run-up to release). >> quirks-3.458 signed on 2020-10-18T13:56:14Z This shows that it is indeed looking at a snapshot directory not release. >> Can't update spidermonkey-60.9.0v1->spidermonkey78-78.3.1v1: no update found >> for spidermonkey-60.9.0v1 >> Can't install polkit-0.116p1->0.118: can't resolve spidermonkey78-78.3.1v1 >> >> Is this expected soon after updating? Do I just need to wait for some >> inconsistency in the pkg repo to be resolved? This could either be: - a bug in some port - a package source that does not have a consistent set of files from one build (can happen when a mirror is updating) First thing to do if this happens is check file dates in the mirror's directory listing and see if they're consistent (no big jump between the a* and z* files).
