I’m waiting until there’s another dom0 update available to confirm this, but when I ran “sudo qubesctl state.sls update.qubes-dom0”, the system was reported as already up-to-date. However, running sudo qubes-dom0-update immediately afterwards returned updates.
I also get some confused output:
ID: update
Function: cmd.run
Name: if qubes-dom0-update --quiet --assumeyes --clean --action=clean expire-cache >/dev/null 2>&1; then
echo “result=True comment=‘Cache cleaned’”
else
echo “result=False comment=‘Could not clean cache’”
fi
Result: True
Comment: Could not clean cache
…
Running the command “qubes-dom0-update --quiet --assumeyes --clean --action=clean expire-cache” from dom0 shows ERROR: the yum version installed in the host VM does not support --downloadonly
Removing “–action=clean expire-cache” seems to fix this.
Maybe the cache failing to clear caused a false report of my system being up-to-date? Or maybe that part is a red herring. But something doesn’t seem right.
I wanted to raise this here as I’m relatively new to Qubes and I’m not 100% sure I’ve not made a mistake.