Re: [Apt-proxy-users] groking apt-proxy, and "no suitable backend found"

[Chris H. <ha...@de...>]

On Monday 16 May 2005 17:53, Bill Moseley wrote:
> So, if the apt-proxy machine is also a client then there can be two
> copies of the package -- one in /var/cache/apt/archives/ and the other
> in /var/cache/apt-proxy/.  Is this correct?

Yes, correct

> Before installing apt-proxy I would run this via cron:
>
>     apt-get -qq update && \
>     apt-get -qqd dist-upgrade && \
>     apt-get -qq autoclean
>
> That keeps my Packages list up to date and pre-fetches packages, so
> when I do a dist-upgrade the packages are ready to be installed.
>
> So, with using apt-proxy I can use the same method as above to
> pre-fetch packages (via cron during the night), but to avoid storing
> the packages in two locations on the same machine I would use "clean"
> instead of "autoclean".  Then later when I run a dist-upgrade I'll
> fetch the packages from the apt-proxy cache.
>
> Is the above correct?  Is that a typical usage for pre-fetching
> packages?

Yes, that would be fine.

One feature I'd like to do when I have time is to implement the prefetching in 
a-p itself.  We already store last time a client requested each package, so 
it would be possible to automatically download updates of all packages that 
clients have been downloading recently.  Now, I just need some time, or 
someone, to implement it :)

> Next, I can't see to import my existing .deb into the apt-proxy
> cache.  This seems to happen for every package:

I accidentally broke apt-proxy-import and max_versions a while ago. 1.9.30 
fixes this, please upgrade.

Chris