Comment 7 for bug 2008212

So this change/fix actually seems to inadvertently fix #2007311. All along I thought it was a problem with upstream cache being broken, but I could definitely see it being plausible that phased updates could cause this same weird behavior.

Anyone who writes anything that depends on apt-check may be in for nasty surprises when apt-check breaks and returns bad data instead of predictably formatted pairs of integers.

Example:
 /usr/lib/update-notifier/apt-check
E: Unknown Error: '<class 'KeyError'>' ("The cache has no package named 'libxmlb2:amd64'")

/usr/lib/update-notifier/apt-check --human-readable
E: Unknown Error: '<class 'KeyError'>' ("The cache has no package named 'libxmlb2:amd64'")