I’ve been putting this off for a long time but since sometime after Jan 13 ‘25, pro security-status keeps insisting that sudo apt updateis overdue:
$ pro security-status
[snip]
The system apt information was updated 439 day(s) ago. Make sure to run
sudo apt update
to get the latest package information from apt.
[snap]
After some digging I found /var/lib/apt/periodic/update-success-stamp, dated Jan 13 ‘25. And it is indeed the one pro checks, because when I move it out of the way, the message becomes:
The system apt cache may be outdated. Make sure to run
sudo apt update
to get the latest package information from apt.
I am not aware of having done any changes to apt’s config, but I may have forgotten about them, so not sure. I vaguely remember that I turned down some unattended upgrade settings. And everything works flawlessly, so I am suspecting that some newer version of apt stopped using that particular timestamp file but pro is still using it. There are four other files in that directory with fresh timestamps:
$ ls -l /var/lib/apt/periodic
total 0
-rw-r--r-- 1 root root 0 Mar 28 11:42 download-upgradeable-stamp
-rw-r--r-- 1 root root 0 Mar 28 11:42 unattended-upgrades-stamp
-rw-r--r-- 1 root root 0 Mar 28 11:42 update-stamp
-rw-r--r-- 1 root root 0 Jan 13 2025 update-success-stamp.bak
-rw-r--r-- 1 root root 0 Mar 28 11:42 upgrade-stamp
So is this a bug in the pro CLI or in apt? Have I inadvertently broken it?