On 05/10/2025 16:50, Mark Millard wrote:
…
I see a mix of:
QUOTE
-U, --no-repo-update
Suppress the automatic update of the local copy of the
repository catalogue from remote. Automatic repository
catalogue updates are only attempted when the effective UID
of the process has write access to the package database.
Otherwise they are silently ignored.
END QUOTE
and:
QUOTE
32 MiB to be downloaded.
END QUOTE
So the repository catalog would not have been updated
for the download if the download had happened?
I had previously combined -F and -y, repeatedly, to fetch all packages.
It's true that proceeding to upgrade (with -U) sometimes results in an
unexpected fetch of more packages, with consequent changes to things
such as the number of packages to be removed. These moving goalposts
have taught me to be extremely wary of -y for upgrades.
In this case, it's _possible_ that I inadvertently allowed a repo update
some time between the -Fy and the installation. (I spent more than a day
attempting to upgrade a single system. Tiredness may have led to
carelessness.)
It leads me to wonder if it ended up in a status of
"can not do as requested overall" but just did not
explicitly report anything about that status.
The nothingness is extraordinary.
I could make a debug run (I do have a VirtualBox snapshot of the
affected guest), but it's not a priority.
Thanks
