On Mon, Mar 24, 2008 at 04:29:47 +0000, Nick Boyce wrote:
Just wondering whether anyone here understands the cause of the "BADSIG"
error from "aptitude update"
I'm inclined to agree with you about our proxy having a caching problem,
and I like your suggestion of using 'wget' to flush the proxy's cache
before the 'aptitude update'. It seems odd however, that such a problem
could exist (big company, commercial web proxy), and be solvable by just
repeating the download.
I will try the investigations you suggest :
The next time when the problem appears, make a backup copy of
and check if the file has changed after you rerun "apt-get update"
Well here's a funny thing - I've added some debug code to our overnight
"aptitude update" script to save the above signature file *and* the
signed file itself whenever the BADSIG error occurs, both before and
after the rerun ... and on every occasion I find that *before* the rerun
(i.e. immediately after the BADSIG) the 'Release' file is missing
altogether ... no wonder the signature fails to verify. Here's what the
script saved over the last few days :
[The code creates a couple of folders in ~root called
"nick-aptupdate-debug-YYYYMMDD-HHMM-[before|after], and saves the two
files into the relevant folders]
On Thu, Apr 10, 2008 at 03:34:12AM +0000, Nick Boyce <firstname.lastname@example.org> was heard to say:
> I wrote:
> > Two further inferences are :
>> (1) the aptitude code isn't checking the exit status from 'wget' (I
>> assume it uses wget).
>> (2) the wget operation is in fact asynchronous, and by the time I rerun
>> - 5 seconds later - the wget for 'Release' has by then completed. This
>> is just a wild guess, and may be way off-target.
> Now I think about it a bit more I realise aptitude almost certainly
> *isn't* using wget ... the proxy specification is in apt.conf, not
> .wgetrc. Must be own code ....
Yes, in methods/http.cc. The code that manages the overall download
process is in apt-pkg/acquire*.cc.
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact email@example.com