Date: Tue, 16 Feb 2021 15:37:29 -0800 From: Mark Millard <marklmi@yahoo.com> To: Brandon Bergren <bdragon@FreeBSD.org> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: pkg vs uname troubles after upgrade to 14 Message-ID: <224EA9F1-AF1B-4F85-9D0F-3BA990F30814@yahoo.com> In-Reply-To: <5ef34e30-6c65-417a-810e-257fc0864a84@www.fastmail.com> References: <5B780540-0C4A-4438-A550-E88A36EA50F3.ref@yahoo.com> <5B780540-0C4A-4438-A550-E88A36EA50F3@yahoo.com> <5ef34e30-6c65-417a-810e-257fc0864a84@www.fastmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2021-Feb-16, at 11:49, Brandon Bergren <bdragon at FreeBSD.org> wrote: > It looks like there were recently some fixes to release.sh, that just got backported to 13. I wonder if the problem is the packages themselves being misbuilt. > > https://cgit.freebsd.org/src/commit/release?h=releng/13.0&id=4689ab1eab624d1a551a5a8f109383ea18eeba20 release/release.sh and release/tools/arm.subr are not used for self-building ports as far as I know. Steve Kargl's example was: self-built pkg, then portmaster, then used portmaster to build the rest of his ports, and not in/for an arm context. release/release.sh would have to contribute as a side effect of its prior use in some way for that sequence, if I understand right. > > On Tue, Feb 16, 2021, at 12:20 PM, Mark Millard wrote: >> There are other reports of a: >> >> pkg: Warning: Major OS version upgrade detected. Running "pkg >> bootstrap -f" recommended === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?224EA9F1-AF1B-4F85-9D0F-3BA990F30814>