Index | Thread | Search

From:
Stuart Henderson <stu@spacehopper.org>
Subject:
Re: CVS: cvs.openbsd.org: ports
To:
David Higgs <higgsd@gmail.com>
Cc:
ports@openbsd.org
Date:
Sat, 22 Nov 2025 19:59:04 +0000

Download raw body.

Thread
On 2025/11/22 09:30, David Higgs wrote:
> On Sat, Nov 22, 2025 at 5:52 AM Stuart Henderson <stu@spacehopper.org> wrote:
> 
> > You would either need to move the 3.6 database to a machine where 3.6
> > can
> > still run and follow the dump/restore steps in the pkg-readme for unifi,
> > or clean and restore from .unf backup.
> 
> I removed unifi and the old mongodb, cleaned up, reinstalled unifi
> (which installed a new mongodb), and loaded from backup.  Everything
> is happy again though I don't quite understand why mongodb was never
> updated.

it wasn't possible to automatically update from 36 to 44 because it
needed dump/restore

> > pkg_add -u only updates packages when there was a change. these ones
> > don't include binaries and the relevant ports have been untouched for
> > some time, so there's been no need to update them.
> 
> Cool. I figured that there'd be an upgrade because some portion of the
> manifest had changed, e.g. old signify keys?

it needs a package signature change (pkg_info -S) or a higher version
in the pkgname. no point updating the on-disk copy just because
basically the same package was signed with a different key.

> I force-upgraded them anyways

no need to do that, but it doesn't matter if you do.