On Tue, 23 Jan 2018 at 4:12 pm, O. Hartmann <ohartmann_at_walstatt.org> wrote: > For a client I tried PkgBase and followed the procedures recommended (first > build the OS from /usr/src/, installworld/kernel, then proceed with pkg > update > -r FreeBSD-base and pkg install -g 'FreeBSD-*'. > > This doesn't work for any update I try to apply. Since the target host is > a two > years old Intel NUC based on some Broadwell snail CPU, building world and > kernel is performed on another, much more potent host. > > In the first place, when performing a "pkg upgrade", the system complains > about > mismatching OSVERSION, 1200055 forthe running system, and 1200056 for the > packages to be updated. When setting env OSVERSION=1200056, pkg (not > pkg-static!) complains about revision numbers (the long date trailing the > package's name), for instance the newest one is > > FreeBSD-hast-12.0.s20180123050738.txz > > contained within the repository to be used for the update, but installed is > something older, like FreeBSD-hast-12.0.s20171103114456.txz. > > When trying pkg-static, I get a crash of pkg-static, segmentation fault is > its > death-cause. > > How am I supposed to update a base system via PkgBase? > > Kind regards, > > oh > > p.s. sorry for the lack of data, the box in question is on a remote site > without net. > > _______________________________________________ > freebsd-current_at_freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org" This issue was discussed on the FreeBSD-current mailing list. A workaround has been provided there, but a proper fix is still to be developed: https://lists.freebsd.org/pipermail/freebsd-current/2018-January/068153.html Workaround: # pkg -o OSVERSION=1200056 upgrade Regards, Ben > -- -- From: Benjamin Woods woodsb02_at_gmail.comReceived on Tue Jan 23 2018 - 21:34:27 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:14 UTC