"reporting bugs to the effect that a no-change update should finish
instantly."
By definition, if the on-disk copy is corrupt, there is an change-update
available.
The algorithm for update should look like this:
- does the local copy exist? No -> update available
- is the local copy valid (checks
I was picturing scenario (1); if there are updates or the checksum on
the existing doesn't match, download the index.
apt has trained users to "apt update" before doing anything else, so
this would be okay.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
The problem with deferring the situation to the clean command is that
the system appears to be working properly with no problem, and the user
will have to _guess_ that cleanup is required.
Running md5sum on the packages is not expensive:
ubuntu@T00-tx2b:/var/lib/apt/lists$ time md5sum
ports.
Filesystem is ext4
ubuntu@T00-tx2b:~$ mount
/dev/mmcblk0p1 on / type ext4 (rw,relatime,data=ordered)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1809174
Title:
apt doesn't detect file corrupt
Public bug reported:
The Problem
==
/var/lib/apt/lists contains the repository index caches or similar; I'm
not sure what the correct apt-terminology is.
I've installed Chrome on my laptop, so I have:
smacdonald@L247:/var/lib/
Putting ~/bin at the end of the path increases security. That is enough
to end the argument.
If the user wants to override system tools, then they can just as easily
rearrange their path to have ~/bin at the beginning. In fact, that's
congruence: a user savvy enough to install their own tools to ~
