Date: Sun, 23 Mar 2025 14:56:21 +0000 From: Graham Perrin <grahamperrin@gmail.com> To: freebsd-pkgbase@freebsd.org Cc: FreeBSD-CURRENT <freebsd-current@freebsd.org> Subject: Re: pkgbase major version upgrades Message-ID: <3eaa04e7-f091-4c5b-9999-42d9228ff8e6@gmail.com> In-Reply-To: <5e86f828-d86e-4f7c-abe1-e0f6d7cec6f0@gmail.com> References: <5e86f828-d86e-4f7c-abe1-e0f6d7cec6f0@gmail.com>
index | next in thread | previous in thread | raw e-mail
On 28/12/2024 10:17, Graham Perrin wrote: > Someone might like to update <https://wiki.freebsd.org/PkgBase#major>, > where the current example is 11 to 12. > > :x86:64 was recently a cause of confusion for someone (not me); and so > on. > > Ideally, verify the validity of the updated section with: > > - a pkgbase upgrade from 14.1 to 14.2, followed by 14.2 to 15.0-CURRENT > > – including attention to non-root user account passwords and group > memberships that exist in the 14.1 environment. > > Thanks Updated. Then and now: <https://wiki.freebsd.org/action/recall/PkgBase?action=recall&rev=114#major>; <https://wiki.freebsd.org/action/recall/PkgBase?action=recall&rev=126#major>; The currently given pkg-static command differs, from the previous, only in the ABI – FreeBSD:15:amd64. More eyes on this, please. Proceeding (y) with the command can significantly break systems, in more ways than one. I'm aware of at least two methods that should minimise, or negate, the risk of breakage. I'd like other testers to share their thoughts on how to avoid breakage, before I share my own; before another update to this subsection of the wiki. Thankshelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3eaa04e7-f091-4c5b-9999-42d9228ff8e6>