From Newsgroup: muc.lists.freebsd.ports
Context (shown from after the oddity happened):
# uname -apKU
FreeBSD 7950X3D-ZFS 16.0-CURRENT FreeBSD 16.0-CURRENT
main-n291147-0c89a55a5d63 GENERIC-NODEBUG amd64 amd64 1600031 1600031
JAILNAME VERSION OSVERSION ARCH METHOD
TIMESTAMP PATH
release14-amd64 14.5-RELEASE-p3 1405000 amd64 ftp-archive 2026-11-13 17:02:34 /usr/local/poudriere/jails/release14-amd64
Note: My analogous aarch64 context gets the same oddity.
I have a script that updates a set of poudriere(-devel) jails in
sequence. Sometimes only some of them have actual updates.
In the below my expectation is that there was no actual update: it was
already at 14.5-RELEASE-p3 from prior activity.
# poudriere jail -jrelease14-amd64 -u
[00:00:00] Upgrading using ftp-archive
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for 14.5-RELEASE from update2.freebsd.org...
done.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.
The following files are affected by updates. No changes have
been downloaded, however, because the files have been modified
locally:
/etc/ssl/certs/36c6b318.0
/etc/ssl/certs/422cf4bf.0
/etc/ssl/certs/9cd9d94b.0
/etc/ssl/certs/faf4fe6b.0
/etc/ssl/untrusted/14bc7599.0
/etc/ssl/untrusted/3dbee7d3.0
/etc/ssl/untrusted/3ed72a2f.0
/etc/ssl/untrusted/b548496f.0
/etc/ssl/untrusted/e36a6752.0
/etc/ssl/untrusted/eb784c64.0
No updates needed to update system to 14.5-RELEASE-p3.
14.5-RELEASE-p3
[00:00:07] Recording filesystem state for clean... done
It does not read as if the files are simply already up to date.
--
===
Mark Millard
marklmi at yahoo.com
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to
news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2