On Thu, Sep 10, 2009 at 04:26:50PM -0400, Daniel Richard G. wrote: > On Thu, 2009 Sep 10 11:43+0100, Mark Hindley wrote: > > > > > > Could you try this patch and see if it is fixed for you. > > > > Sorry, that was incomplete. You will also need this: > > I'm still seeing some "uninitialized value" warnings, as well as a new > flock() warning cropping up in spades. Here's what error.log has after > several "apt-get update" cycles:
I thought I had worked out a locking error that was causing this, but obviously not. Could you remove these last patches and turn on debugging and send the error.log so I can try to see why $cached_file is not getting initialised. As you say, it is easy to set the default value as a workaround, but I can't see why it is not being set with the current code. Must be missing something > > $ cut -d: -f4- error.log | sort | uniq -c 235 Header output delayed > whilst getting Content-Length 42 Use of uninitialized value > $cache_status in concatenation (.) or string at apt-cacher2 line 1053. > 8057 flock() on closed filehandle $exlock at apt-cacher-lib.pl line > 326. > > (Wouldn't it make sense for the "Header output delayed" bit to be a > debug message, by the way?) Yes. Mark -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
