Hey misc, I'm trying to understand the various scenarios that can trigger a package update in 'pkg_add -u'. I thought package updates were triggered only through explicit version bumps, or signature changes. I'm seeing that that isn't always the case however, as shown here:
x1$ pkg_info -S colord ../colord/colord-1.3.5p2.tgz Information for inst:colord-1.3.5p2 Signature: colord-1.3.5p2,6,@consolekit2-1.2.1p9,@dbus-daemon-launch-helper-1.12.20,@dconf-0.36.0p0,@glib2-2.64.6,@lcms2-2.9p0,@polkit-0.118,@sqlite3-3.31.1p0,c.96.0,ffi.1.2,gio-2.0.4200.11,glib-2.0.4201.4,gmodule-2.0.4200.11,gobject-2.0.4200.11,gthread-2.0.4200.11,iconv.7.0,intl.7.0,lcms2.1.2,m.10.1,pcre.3.0,polkit-gobject-1.2.0,pthread.26.1,sqlite3.37.10,z.5.0 Information for file:../colord/colord-1.3.5p2.tgz Signature: colord-1.3.5p2,6,@consolekit2-1.2.1p9,@dbus-daemon-launch-helper-1.12.20,@dconf-0.36.0p0,@glib2-2.64.6,@lcms2-2.9p0,@polkit-0.118,@sqlite3-3.31.1p0,c.96.0,ffi.1.2,gio-2.0.4200.11,glib-2.0.4201.4,gmodule-2.0.4200.11,gobject-2.0.4200.11,gthread-2.0.4200.11,iconv.7.0,intl.7.0,lcms2.1.2,m.10.1,pcre.3.0,polkit-gobject-1.2.0,pthread.26.1,sqlite3.37.10,z.5.0 x1$ pkg_add -un colord quirks-3.471 signed on 2020-10-31T22:51:51Z colord-1.3.5p2->1.3.5p2: ok Running tags: ok --- -colord-1.3.5p2 ------------------- You should also run rm -f /var/db/colord/mapping.db You should also run rm -f /var/db/colord/storage.db In the above example, I've downloaded the colord tarball from my chosen mirror, and compared its signature to my currently installed version. The signatures and version match exactly, however pkg_add still updates the package. Does anyone know what scenario is triggering this update? Thanks, Jeremy
