I don't know the specifics of how the Debian people and processes handle binNMU updates. Generically, APT does update the timestamps on files when it updates a package, but the timestamp is preserved by the packaging process (so you get whatever timestamp was on the file when the Debian maintainers/automation packaged it). I.e. it's standard that files installed by APT do not have a modification time matching the time of install. I'm just mentioning that in case it sheds any light on things, as it's behaviour that might not be expected/obvious (but is actually a good thing normally, and very much a traditional/standard thing that timestamps are preserved in various native Unix/Linux file archive formats).
There are a couple of options for dpkg(1) which you might want to look at, if you've not already done so. I suspect that the verify option might have found this for you, possibly.
There are a couple of options for dpkg(1) which you might want to look at, if you've not already done so. I suspect that the verify option might have found this for you, possibly.
Code:
murph@raspberrypi:~ $ dpkg --helpUsage: dpkg [<option>...] <command>Commands:… -V|--verify [<package>...] Verify the integrity of package(s). -C|--audit [<package>...] Check for broken package(s).…Statistics: Posted by Murph9000 — Sat Sep 21, 2024 12:47 am