Package: <apt-proxy> Version: <1.9.35-0.1> I have used apt-proxy running on a "sarge" box for some time both for sarge and etch files, including building ISO disc images using jigdo, but I am now finding that boxes running etch are unable to get the Release.gpg file, and then ignore everything else. I have tried upgrading the box running apt-proxy from sarge to etch, and also installing a new copy of etch and apt-proxy on to another box. The file is fetched and updated, and I can find it in the normal position not in etch/main etch/contrib or etch/non-free but as /var/cache/apt-proxy/debian/etch/Release.gpg so I suspect that apt-proxy is not looking in the correct place in the local cache. However the error message shown by aptitude does not correspond to this, so even when I am using aptitude on a box that is running apt-proxy I see
http://127.0.0.1:9999 etch Release.gpg Error: could not connect to 127.0.0.1:9999 (127.0.0.1). - connect (111 Connection refused) I have not found any port access restrictions from any local box, all etch boxes are fully updated, and the two running apt-proxy are using Debian etch GNU/Linux kernel 2.6.18-3-686 Am I doing something wrong? Thanks for all the hard work. -- Chris Bell -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
