[Bug 289414] pkg upgrade without further arguments breaks the system on upgrades

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289414

--- Comment #2 from Graham Perrin <grahamperrin@gmail.com> ---
Please note: 

- <https://www.freshports.org/ports-mgmt/pkg-devel/#history> for pkg-devel, 
  currently 2.2.99.2

- more recent <https://github.com/freebsd/pkg/commits/main/>

- <https://lists.freebsd.org/archives/freebsd-pkg/2025-September/001468.html>
  mentioned an experimental run of pkg 2.3.0. 


> … little Atom board with 4GB RAM and 32GB eMMC flash … 
> (4GB RAM + 2GB swap) …

I'm not familiar with the hardware. 

Pull request <https://github.com/freebsd/freebsd-doc/pull/542> should, I
believe, be followed by another documentation PR for: 

vm.pageout_oom_seq

<https://lists.freebsd.org/archives/freebsd-pkg/2025-September/001466.html>
etc., Mark Millard's technical comments in particular. 


> … lost the list of packages I previously installed, … reconstructed 
> from /var/log/messages. …

There's also the database backup, which might be recent. See 542 above.


> … pkg-static to reinstall all base packages. …

pkgbasify can be more graceful: 

- more discrete (a requirement for all 525 packages would be extraordinary)

- in my experience, better handling of merges in situations such as yours.

Using pkgbasify to repair a broken installation of FreeBSD 14.3-RELEASE: 

- <https://gist.github.com/grahamperrin/9570092c127bd43777961b6f016e75ba>


<https://github.com/FreeBSDFoundation/proj-laptop/issues/83#issuecomment-3265333839>
refers to
<https://lists.freebsd.org/archives/freebsd-pkgbase/2025-August/000625.html>, 

> freebsd-update and pkgbase

----

Last but not least: if this bug 289414 can be a ports-mgmt/pkg issue (not base
system), then maybe the port can be enhanced; for some pkg(8) commands to
respond more cautiously where the value of vm.pageout_oom_seq is less than,
say, 120. 

<https://man.freebsd.org/cgi/man.cgi?query=pkg&sektion=8&manpath=freebsd-ports>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.