Comment 12 for bug 11259

We could just delete any partial downloaded signature file in partial/ before
trying to fetch a new one.

I'm unsure if this is enough to work-around broken caches as apt will move the a
Release.gpg file in lists/ into lists/partial before it starts the fetching.

If a file is found in partial, apt will send a HTTP range request with the
missing range and a If-Range: header with the mtime of the file. Apt also sends
a "Cache-Control: max-age=0" by default for index files (such as Release.gpg).
This should force the cache to revalidate it's entry. So in theory even for old
files in partial/ a cache should return the correct file.

Did you problems go away complettely after you removed the Release.gpg file from
the partial directory? If so, I think we should apply the workaround to removed
any Release.gpg files in partial/ before trying to fetch the new ones.

thanks,
 Michael