* Raúl Sánchez Siles [Tue, Sep 15 2009, 09:23:09PM]: > Hello:
#include <hallo.h> > I had same repositories added some time ago due to ia32-apt-get > installation. Why, oh why? It does work well without that. > Nowadays those repositories are removed from my system (/etc/apt) but > apt-cacher-ng > seems to had catched them and now, automatically expiration fails due to those > repositories still alive somewhere. > > I think apt-cacher-ng should stick to existing/valid repositories > and clean whatever other repositories not used anymore or invalid. Sure. But I can think of many other things that I will never get. In this case some artifical intelligence would be needed to learn from the news pages that the remote stuff has gone forever and is not just a temporarily failure. The best feasible thing I can imagine ATM is some "Expiration diagnostics" button in the web interface where user can mark index files with failure as "dead". Does this sound ok for you? > Checking/Updating debrep/dists/sid/main/binary-amd64/Packages... > <br> > Error while redownloading this file!<br> You said something about ia32, right? This doesn't end up, the problem also appears with amd64 files. You must have some other problem. Please send the contens of /var/cache/apt-cacher-ng/debrep/dists/sid/main/binary-amd64/Packages.bz2.head -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
