Date: Sat, 04 Jul 2026 02:21:43 +0000 From: bugzilla-noreply@freebsd.org To: pkg@FreeBSD.org Subject: [Bug 296467] pkg upgrade installs unrelated, unnecessary other packages Message-ID: <bug-296467-32340-4l1zbswBQF@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-296467-32340@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=296467 --- Comment #4 from wbe@psr.com --- I'm sorry if I confused you. The system uses freebsd-update. It is not pkgbase'ified. The "pkg upgrade -f" is done after all the "freebsd-update install"s and reboots have been done, to upgrade all the pkg ports (e.g., X windows). > So multiple file adjustments as long as pkg 2.6.2 is in use. 2.6.2?? As I said in Comment 2, the system currently runs 2.7.5. > The following 2 definitions conflict by, overall, using both quarterly and > latest in the command that you typed: Since the repositories have different names, pkg has been happily updating from both, sees the later version in /latest, and uses that. > If you want FreeBSD-ports to be based on latest, I do. >then in a /usr/local/etc/pkg/repos/*.conf file, have: > > FreeBSD-ports: { > url: "pkg+https://pkg.FreeBSD.org/${ABI}/latest", > } That looks like the better approach. I probably need some way to remove pkg's repository information for "FreeBSD", though, or will "pkg update" discard information for repositories no longer mentioned in any of the .conf files? > It looks like you will need to pkg delete the packages that are in FreeBSD > and then remove that definition before then putting to use FreeBSD-ports (at > least if you follow modern naming conventions). I'll note that pkg delete > does not support -rFreeBSD as an option, even in 2.7.5 . I'm not sure what you mean, but I'm not going to uninstall hundreds of currently installed pkgs, unless it's some sort of single command reinstall-like operation. The FreeBSD /latest repo itself is (I think) larger than the FreeBSD-ports /quarterly repo in terms of number of entries. What about using rm to delete the relevant "FreeBSD" files? Here's what's under /var/db/pkg/ at the moment: # ls -F /var/db/pkg FreeBSD.meta repo-FreeBSD.sqlite-journal local.sqlite repos/ repo-FreeBSD.sqlite vuln.xml # ls -F /var/db/pkg/repos/ FreeBSD/ FreeBSD-ports/ FreeBSD-kmods/ FreeBSD-ports-kmods/ Would deleting /var/db/pkg/*FreeBSD* and the directory /var/db/pkg/FreeBSD/ work? The name local.sqlite suggests there might be references to "FreeBSD" in there somewhere that need to be cleaned up, too. While doing all this would bring things more up-to-date, and the strategy of "fix known issues first, then see if it solves the unknown ones" is a time-honored strategy, I don't yet see how this will fix the original problem (unless the problem is something only in the FreeBSD repo data, which, I suspect, will turn out to be identical to the FreeBSD-ports /latest repo data). -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-296467-32340-4l1zbswBQF>