apt-proxy-users

[Apt-proxy-users] Release.gpg is retrieved and updated, but not made available

[Chris B. <chr...@ov...>]

Hello,
   I have been using apt-proxy for some time for installing and updating
Debian software, including building ISO images using jigdo. Aptitude now
reports repeated errors. The first request from aptitude is for the file
Release.gpg and I can see a recently updated file

/var/cache/apt-proxy/debian/dists/etch/Release.gpg

but now all attempts to get it from apt-proxy are answered by a failure to
connect, even when aptitude is running on the same box as apt-proxy. I
suspect that apt-proxy is only searching through

/var/cache/apt-proxy/debian/dists/etch/main/
/var/cache/apt-proxy/debian/dists/etch/contrib/
/var/cache/apt-proxy/debian/dists/etch/non-free/

and not

/var/cache/apt-proxy/debian/dists/etch/

aptitude will then report failure to connect for other requests or just
ignore any other output from apt-proxy and collect from a normal Debian
mirror site instead.
   I did have apt-proxy as the only source listed in /etc/apt/sources.list
and had a few messages about an untusted site but then decided to add some
standard mirror sites just to get regular updates.

   I was running apt-proxy then apt-proxy-v2 on a sarge box, so tried
upgrading that box to etch, and also apt-proxy on a totally new box running
etch, but get the same results, now also from boxes still running aptitude
on sarge.

   Any ideas? It would be good to get this working before etch is officially
released.

-- 
Chris Bell

Re: [Apt-proxy-users] Release.gpg is retrieved and updated,

[Chris B. <chr...@ov...>]

   I am now finding that boxes running Debian sarge are able to download
from the apt-proxy-v2 without complaints. Also, I am able to use jigdo to
build etch ISO images via the apt-proxy-v2 without problems, although jigdo
does run separate checks as it builds.
   All boxes running etch had /etc/apt/sources.list pointing to etch, not
testing. I then noticed that I had the following files, with different
sizes:

/var/cache/apt-proxy/debian/dists/etch/Release.gpg    189 bytes

/var/cache/apt-proxy/debian/dists/testing/Release.gpg 378 bytes

Unfortunately, adding pointers in /etc/apt/sources.list to testing as well
as etch just increased the number of error messages from aptitude.

-- 
Chris Bell

Re: [Apt-proxy-users] Release.gpg is retrieved and updated,

[Chris B. <chr...@ov...>]

On Wed 21 Feb, Chris Bell wrote:
> 
>    All boxes running etch had /etc/apt/sources.list pointing to etch, not
> testing. I then noticed that I had the following files, with different
> sizes:
> 
> /var/cache/apt-proxy/debian/dists/etch/Release.gpg    189 bytes
> 
> /var/cache/apt-proxy/debian/dists/testing/Release.gpg 378 bytes
> 
> Unfortunately, adding pointers in /etc/apt/sources.list to testing as well
> as etch just increased the number of error messages from aptitude.
> 
   The two files above have now been updated by apt-proxy, and they now show
the same file contents. Unfortunately, apt-proxy does not find and supply
them from the cache. I am not a programmer, and am not able to supply a
patch.


-- 
Chris Bell