I suspect that the exact causes of this have shifted over time. The two
relevant cases in precise (at least assuming that my test case is
sufficient) seem to be:
InRelease renamed to Release despite signature failure
IndexDiff files moved to /var/lib/apt/lists/ despite parse failure
The latter is easily fixed by reordering pkgAcqDiffIndex::Done, I guess,
but I'm puzzled by the former. In pkgAcqMetaIndex::Failed it appears to
be deliberate:
/* Always move the meta index, even if gpgv failed. This ensures
* that PackageFile objects are correctly filled in */
So if an HTTP proxy returns some junk for anything you ask for,
including an InRelease file that wouldn't exist if we were actually
talking to the real archive, we'll save that as Release? This seems
bizarre. Can we deal with the problem alluded to in that comment some
other way?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/24061
Title:
GPG error with apt-get/aptitude/update-manager behind proxy (BADSIG
40976EAF437D05B5)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/24061/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
