The reason it doesn't inspire confidence is that this error occurs during normal operation.
Sometime this error indicates a problem of grabbing an inconsistent set of files from a
round-robin type situation. Yes, the system has saved me from data corruption, theoretically.
Realistically, it is an embarassment that these inconsistencies are encounterable in normal
configurations. For example, chosing a host such as http.us.debian.org will often result in
data inconsistency during updates. Why is this advertised as a viable mirror selection if it
does not work reliably?
Sometimes, however, this error indicates a "problem" such as not bothering to run update for a
few weeks and the key has expired. Once this error indicated that the key had expired before
the new key was even made available, and so the web of trust simply did not extend from one
administration key to the next. Every user of debian testing encountered this during one
Perhaps you begin to see the problem? This thing pops up all the time to suggest a problem
which is not caused by incorectly signed or unsigned files. How will you identify a real
security issue in the noise?