Date: Mon, 29 Jun 2026 08:00:17 -0700 From: Mark Millard <marklmi@yahoo.com> To: Alexander Ziaee <ziaee@FreeBSD.org>, vermaden <vermaden@interia.pl>, Lexi Winter <ivy@freebsd.org>, freebsd-pkgbase <freebsd-pkgbase@freebsd.org> 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 Message-ID: <03d3d0aa-4dd0-4732-a4a8-0aca88b49263@yahoo.com> In-Reply-To: <E1we7RC-0002ry-2u@rmmprod06.runbox> References: <whswxsmftdottbdvxpzb@npvv> <E1we7RC-0002ry-2u@rmmprod06.runbox>
index | next in thread | previous in thread | raw e-mail
On 6/29/26 01:33, Alexander Ziaee wrote: > Hey, > > On 2026-06-29 04:19 -04:00 EDT, "vermaden" <vermaden@interia.pl> wrote: >>> documenting .pkgsave and/or .pkgnew behavior or how to handle such >> >> I gathered some summary here: >> >> https://vermaden.wordpress.com/2026/05/10/freebsd-pkgbase-minor-upgrades/#comment-27442 > > You are always the first to find them! > I saw that and put a bit in pkg(8) manual, and put a thank you in the commit message: > > https://github.com/freebsd/pkg/commit/6895ed1cbcfd1287d382928d28938fb332bf3e61 > > Best, > Alex > QUOTE Vermaden also mentioned pkgtemp, should we mention those too? END QUOTE I've not seen a .pkgtemp.* file in a rather long time. I used to see them on occasion. Once or twice I got a large number of them. I expect that what should be said about them is something like: Please report getting such a file as a problem, with any notes that might seem to be useful background information about the context. QUOTE .It Pa *.pkgnew New file that failed to merge during an update. END QUOTE May be: New file version that failed to merge during an update. Why: A new, distinct file name would not end up with a *.pkgnew status. I'll also note that normally *.pkgnew is from pkg upgrade and normally *.pkgsave is from pkg install. That suggests similar notes in the man pages for those commands. In fact those 2 man pages should each probably suggest looking for such files and dealing with them after executing the command. 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. -- === Mark Millard marklmi at yahoo.comhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?03d3d0aa-4dd0-4732-a4a8-0aca88b49263>