From nobody Tue Jun 30 15:06:19 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 4gqRLY0TPrz6kKmd for ; Tue, 30 Jun 2026 15:06:29 +0000 (UTC) (envelope-from ziaee@FreeBSD.org) Received: from mailtransmit04.runbox.com (mailtransmit04.runbox.com [IPv6:2a0c:5a00:149::25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4gqRLX2FsKz3WbR for ; Tue, 30 Jun 2026 15:06:28 +0000 (UTC) (envelope-from ziaee@FreeBSD.org) Authentication-Results: mx1.freebsd.org; none Received: from mailtransmit02.runbox ([10.9.9.162] helo=aibo.runbox.com) by mailtransmit04.runbox.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.93) (envelope-from ) id 1wea2V-003nhP-RL; Tue, 30 Jun 2026 17:06:19 +0200 Received: from [10.9.9.129] (helo=rmmprod07.runbox) by mailtransmit02.runbox with esmtp (Exim 4.86_2) (envelope-from ) id 1wea2V-0004ci-Cl; Tue, 30 Jun 2026 17:06:19 +0200 Received: from mail by rmmprod07.runbox with local (Exim 4.86_2) (envelope-from ) id 1wea2V-0006mp-Ab; Tue, 30 Jun 2026 17:06:19 +0200 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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 Received: from [Authenticated alias (960477)] by runbox.com with http (RMM6); Tue, 30 Jun 2026 15:06:19 GMT From: "Alexander Ziaee" To: "Larry Fahnoe" , "Mark Millard" CC: "vermaden" , "Lexi Winter" , "freebsd-pkgbase" Subject: Re: None of "man freebsd-base" (or "man pkgbase"), "man pkg-upgrade", or "man pkg-install" deal with documenting .pkgsave and/or .pkgnew behavior or how to handle such Date: Tue, 30 Jun 2026 15:06:19 +0000 (UTC) X-RMM-Aliasid: 960477 X-Mailer: RMM6 In-Reply-To: Message-Id: X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:50304, ipnet:2a0c:5a00::/29, country:NO] X-Rspamd-Queue-Id: 4gqRLX2FsKz3WbR X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated On Monday, June 30, 2026, Larry Fahnoe wrote: > On Monday, June 29th, 2026, Mark Millard wrote: >=20 >> I have suggested elsewhere that the last of the output from those >> commands should probably list the counts of each of *.pkgnew and >> *.pkgave such files generated for any where the count is positive. >> That would make a good prompt to go looking --and allow avoiding >> looking when none were generated. >=20 > I would second this comment/suggestion, particularly for those who are > newer or less familiar with FreeBSD update practices. My system admin > experience comes from other platforms (VMS, linux and other unix) so I > have been paying attention to the conversations that are mentioning > the *.pkgnew and *.pkgsave files as they seem a bit less intuitive > than on the other platforms. For some it may be natural to go looking > for these leftover telltales but they may represent important but > neglected potential time-bombs for the less familiar. OpenVMS and Linux do create these files. OpenVMS increments the version (;2 or ;3) or drops a TEMPLATE file. Linux uses .dpkg-dist and .dpkg-old or .rpmnew and .rpmsave. However, it is a not a ticking time bomb, so they do not tell you and you have not noticed. Everyone is using roughly the same three-way merge strategy, we just tell you about the failure case because of our culture which prizes thorough docs. We do not want to make a big deal out of it because it is already causing misunderstanding. Best, Alex