badsig error on update from private ppa due to 0-byte Release file
Bug #836419 reported by
Martin Pool
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
High
|
Unassigned | ||
Bug Description
I'm running apt-get update on a machine with access to the canonical-
W: GPG error: https:/
This might be related to bug 807303 or bug 485151.
In /var/lib/apt/lists I see
-rw-r--r-- 1 root root 0 2011-08-29 09:03 private-
and updating again does not update that file.
Analysis
========
archivepublisher writes files non-atomically, possibly combined with custom apache validator settings.
Revision history for this message
| Martin Pool (mbp) wrote | #1 |
| summary: |
- badsig error on update from private ppa + badsig error on update from private ppa due to 0-byte Release file |
Revision history for this message
| William Grant (wgrant) wrote | #2 |
| Changed in launchpad: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| description: | updated |
| tags: | added: easy |
To post a comment you must log in.
some debugging in apt:
- this is over https so there should be no proxy in the way
- it is getting a 200 response for the gpg file with the correct size (316 bytes)
- it's sending a conditional request for the Release file:
User-Agent: Debian APT-CURL/1.0 (0.8.16~
Host: private-
Accept: */*
If-Modified-Since: Sun, 28 Aug 2011 23:03:31 GMT
Cache-Control: max-age=0
... and getting a not-modified response.
deleting the 0-byte file from my cache gets things unjammed.
So, I'm not sure:
* if, perhaps as part of bug 807303, Launchpad is ever disconnected before serving the files, things could be getting stuck here
* conversely perhaps it's a bug in apt that it's caching a failed download, or not using a stronger cache validator