[Bug 292810] [15.0-RELEASE-p1] pkg upgrade stays in loop

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

--- Comment #4 from Mark Millard <marklmi26-fbsd@yahoo.com> ---
(In reply to bugzeo from comment #3)

Using just "pkg update" will update FreeBSD-base (15.*
notation) information about the status of upstream
pkgbase packages as well (if FreeBSD-base is an enabled
repository at the time), not just upstream port-package
related information.

Later using "pkg upgrade" will upgrade FreeBSD-base
pkgbase pacakges as well (if FreeBSD-base is an enabled
repository at the time), not just port packages.

It is not clear to me how you intend on the likes of
FreeBSD-ports-kmods so I'll pick one way of handling it
below. Using 15.* repository notation and assuming
pkg 2.7.5 or later is already in place at the start:

# pkg update -rFreeBSD-ports
# pkg bootstrap -f -rFreeBSD-ports
# pkg upgrade -rFreeBSD-ports

avoids having FreeBSD-base and FreeBSD-ports-kmods
involved for both information about the upstream
pkgbase and ports-kmods packages and about upgrading
to what upstream has for those.


Note (assuming pkg boostrap establishes pkg 2.7.5
or later):

The -rFreeBSD-ports options for update (and upgrade) do
not operate as intended in the likes of pkg 2.6.2 ,
unfortunately. The files declaring the repositories
FreeBSD-base and FreeBSD-ports-kmods have to have to
have them disabled first for such an older pkg version
for the pkg update, unfortunately. After the pkg
bootstrap, the pkg upgrade command should work even if
FreeBSD-base and FreeBSD-ports-kmods were first enabled.

(I have assumed not wanting not wanting the pkg update
information for a repository to be updated but then not
used, keeping such information as it was.)

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