From nobody Sun Jun 21 14:50:41 2026 X-Original-To: freebsd-pkgbase@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4gjvQl5gYcz6h7P5 for ; Sun, 21 Jun 2026 14:50:55 +0000 (UTC) (envelope-from matias@pizarro.net) Received: from mail04.docbase.net (mail04.docbase.net [IPv6:2a01:4f8:1c1b:1324::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail04.docbase.net", Issuer "YR1" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4gjvQk1141z40jj for ; Sun, 21 Jun 2026 14:50:53 +0000 (UTC) (envelope-from matias@pizarro.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=pizarro.net header.s=dkim header.b=r8xG7ipI; dmarc=pass (policy=quarantine) header.from=pizarro.net; spf=pass (mx1.freebsd.org: domain of matias@pizarro.net designates 2a01:4f8:1c1b:1324::1 as permitted sender) smtp.mailfrom=matias@pizarro.net Received: from [127.0.0.1] (localhost [127.0.0.1]) by localhost (Mailerdaemon) with ESMTPSA id 1B1C7E8438; Sun, 21 Jun 2026 16:50:43 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pizarro.net; s=dkim; t=1782053444; h=from:subject:date:message-id:to:mime-version:content-type: content-transfer-encoding:in-reply-to:references; bh=wNGJ1u1lPdUJfNIEOhuCczCEIQR81wBanVRA0MzTuR4=; b=r8xG7ipIAZJDZjA2rTg2NkTBhvln2iolvSWsG5yf6yCyQ3HkOuuW4kwkE7QmP8IEC3FkeL jNJBOKbKmSxUb/rzhzokTLmP94n2qrgXipR1fj3ylxlLTA0evnOuD0uAgtRZMjs+zpDOPA Y+kwAZ1v5QM6A1HEZWv2+61i19kDwRj5/7hHp3JZXWL2pVXermkZ4T91zNENZgyxIgyqPQ Zm7MeYr5QXNutmqXBMEqfHifjRbOm6FRhzPiR/1Ee/Ysjiqb5hNLQE6Z+ftF0lWubMkrKD WtwqoyUSk0G/eP8sFcvvxjTOGqYSDXKnU9co0rskIJEd0kpohrFRUMk0XCcrHQ== Date: Sun, 21 Jun 2026 16:50:41 +0200 From: Matias Pizarro To: freebsd-pkgbase@freebsd.org, freebsd-pkgbase@FreeBSD.org Subject: Re: Moving to pkg-based in 15.1 ... User-Agent: Thunderbird for Android In-Reply-To: <86a4sot2l4.fsf@ltc.des.dev> References: <86a4sot2l4.fsf@ltc.des.dev> Message-ID: <439B3749-A366-446E-B54C-3E4098F4CE72@pizarro.net> List-Id: Packaging the FreeBSD base system List-Archive: https://lists.freebsd.org/archives/freebsd-pkgbase List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-pkgbase@FreeBSD.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=----VENH4CQ2S6KYJ5ZG0Y6ZMN95F5FB66 Content-Transfer-Encoding: 7bit X-Last-TLS-Session-Version: TLSv1.3 X-Spamd-Result: default: False [-1.48 / 15.00]; FORGED_MUA_THUNDERBIRD_MSGID_UNKNOWN(2.50)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.991]; DMARC_POLICY_ALLOW(-0.50)[pizarro.net,quarantine]; R_DKIM_ALLOW(-0.20)[pizarro.net:s=dkim]; R_SPF_ALLOW(-0.20)[+ip6:2a01:4f8:1c1b:1324::1]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; XM_UA_NO_VERSION(0.01)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/32, country:DE]; RCVD_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; MID_RHS_MATCH_FROM(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; RECEIVED_HELO_LOCALHOST(0.00)[]; RCVD_TLS_ALL(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; MLMMJ_DEST(0.00)[freebsd-pkgbase@freebsd.org]; DKIM_TRACE(0.00)[pizarro.net:+] X-Spamd-Bar: - X-Rspamd-Queue-Id: 4gjvQk1141z40jj ------VENH4CQ2S6KYJ5ZG0Y6ZMN95F5FB66 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Indeed, it has never been that simple and robust=2E You can also follow thi= s guide: https://www=2Efreebsd=2Eorg/releases/15=2E1R/installation/#upgrade-pkg On 21 June 2026 16:01:11 CEST, "Dag-Erling Sm=C3=B8rgrav" wrote: >Mike writes: >> Now, as I understand the pkgbase system, it has gotten a bit more >> complex=2E > >On the contrary=2E=2E=2E > >> I no longer see that easy ability to update from one patch level to >> the current patch level within the installed version=2E > >To upgrade a pkgbase system, simply run: > > # pkg upgrade > >or, if you want to upgrade _only_ the base system and leave the rest >untouched: > > # pkg upgrade -r FreeBSD-base > >This essentially replaces `freebsd-update fetch` and `freebsd-update >install` in your script, including the intervening prompt, and the rest >will work as before=2E If you want to get fancy, do: > > # pkg upgrade -r FreeBSD-base -Fy > >to download updated packagtes without installing them, then > > # pkg upgrade -r FreeBSD-base > >to prompt the user and install the downloaded packages=2E This will also >avoid a rare situation (very unlikely to occur with pkgbase on a release >branch) where pkg computes an upgrade plan, prompts the user, then >computes a different plan after examining the packages it downloaded and >prompts the user a second time=2E > >A reboot is always recommended, unless you know exactly what was updated >and can manually restart all affected services (or you know that none of >the services that you run are affected)=2E That was always the case=2E > >> https://wiki=2Efreebsd=2Eorg/PkgBase > >This is severely out of date and (like most of the wiki) was always more >of an internal roadmap than any sort of user documentation=2E > >DES >--=20 >Dag-Erling Sm=C3=B8rgrav - des@FreeBSD=2Eorg > ------VENH4CQ2S6KYJ5ZG0Y6ZMN95F5FB66 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Indeed, it has never been that s= imple and robust=2E You can also follow this guide:

https://= www=2Efreebsd=2Eorg/releases/15=2E1R/installation/#upgrade-pkg


On 21 June 2026 16:01= :11 CEST, "Dag-Erling Sm=C3=B8rgrav" <des@FreeBSD=2Eorg> wrote:
= 
Mike <the=2Elists@mgm51=2Ecom> writes:
Now, as I und=
erstand the pkgbase system, it has gotten a bit more
complex=2E

On the contrary=2E=2E=2E

<=
blockquote class=3D"gmail_quote" style=3D"margin-bottom: 1ex; --net-thunder=
bird-android__blockquote-default-border-color: #729fcf;">
=
I no longer see that easy ability to update from one patch level to
the =
current patch level within the installed version=2E
<= div dir=3D"auto">
To upgrade a pkgbase system, simply run:

# = pkg upgrade

or, if you want to upgrade _only_ the base system and le= ave the rest
untouched:

# pkg upgrade -r FreeBSD-base

= This essentially replaces `freebsd-update fetch` and `freebsd-update
ins= tall` in your script, including the intervening prompt, and the rest
wil= l work as before=2E If you want to get fancy, do:

# pkg upgrade= -r FreeBSD-base -Fy

to download updated packagtes without installin= g them, then

# pkg upgrade -r FreeBSD-base

to prompt the = user and install the downloaded packages=2E This will also
avoid a rare= situation (very unlikely to occur with pkgbase on a release
branch) whe= re pkg computes an upgrade plan, prompts the user, then
computes a diffe= rent plan after examining the packages it downloaded and
prompts the use= r a second time=2E

A reboot is always recommended, unless you know e= xactly what was updated
and can manually restart all affected services (= or you know that none of
the services that you run are affected)=2E Tha= t was always the case=2E


This is severely out of date and (like most of the w= iki) was always more
of an internal roadmap than any sort of user docume= ntation=2E

DES
------VENH4CQ2S6KYJ5ZG0Y6ZMN95F5FB66--