Upgrades that result in no change to the version level

Go to: [ bottom of page ] [ top of archives ] [ this month ]

From: Graham Perrin <grahamperrin_at_gmail.com>
Date: Sun, 20 Oct 2024 05:25:56 UTC

When an upgrade to a set of packages results in no change to the version 
level, what's the likeliest explanation?

For example,

FreeBSD 15.0-CURRENT main-n273049-366d6a424e1f GENERIC-NODEBUG

– before and after the set below.

FreeBSD-clibs upgraded: 15.snap20241015182318 -> 15.snap20241018235309
FreeBSD-clibs-dbg upgraded: 15.snap20241015182318 -> 15.snap20241018235309
FreeBSD-runtime upgraded: 15.snap20241018205121 -> 15.snap20241018235309
FreeBSD-utilities upgraded: 15.snap20241018215924 -> 15.snap20241018235309
FreeBSD-clibs-dev upgraded: 15.snap20241018173754 -> 15.snap20241018235309
FreeBSD-tests upgraded: 15.snap20241018162843 -> 15.snap20241018235309
FreeBSD-src upgraded: 15.snap20241018215924 -> 15.snap20241019045901
FreeBSD-tests-dbg upgraded: 15.snap20241016165033 -> 15.snap20241018235309
FreeBSD-runtime-man upgraded: 15.snap20241018125255 -> 
15.snap20241019010212
FreeBSD-clibs-dev-lib32 upgraded: 15.snap20241015182318 -> 
15.snap20241018235309
FreeBSD-runtime-dbg upgraded: 15.snap20241018205121 -> 
15.snap20241018235309
FreeBSD-utilities-man upgraded: 15.snap20241018090701 -> 
15.snap20241019045901
FreeBSD-utilities-dbg upgraded: 15.snap20241018215924 -> 
15.snap20241018235309
FreeBSD-clibs-dbg-lib32 upgraded: 15.snap20241015182318 -> 
15.snap20241018235309
FreeBSD-clibs-lib32 upgraded: 15.snap20241015182318 -> 
15.snap20241018235309