Bug#442189: broken manifests

[Joey Korkames <joey@kidfixit.com>]

Hello Eugene,

Thanks for checking on this. I doubled back through a couple of things in my 
chroot creation process since Vincent's procedure sounds just as exotic as 
mine...I suspect we are outliers.

I found that removing my site's mini-dinstall managed apt repos from 
sources.list fixed the problem. I'm going to migrate that repo to reprepro 
and see if it creates cleaner manifests. 

I stopped using the apt-proxy program and switched to a homegrown and 
stateless deb-cacher (http://www.ruby-forum.com/topic/153856), so I don't 
think it's a stalling http proxy/server that is causing it.

I have to gear up for lenny anyways, so I can try testing the newwer 
apt-get with the broken manifests too - maybe the error handling will be 
better and I'll see exactly what gzip is barfing on. 

-joey