#include <hallo.h>
* Johan Daine [Sat, Mar 04 2006, 08:18:47AM]:
> Hi everyone,
>
> I am making some tests with apt-proxy.
> apt-proxy is working perfectly. I have been purging gpm, removing the
> 2006/03/04 08:16 CET [-] [apt_pkg] No Packages files available for
> security backend
> 2006/03/04 08:16 CET [-] [apt_pkg] No Packages files available for
> debian-non-US backend
> 2006/03/04 08:16 CET [-] [import] libconfigfile-perl_1.2.1_all.deb
> skipped - no suitable backend found
> </cut>
> and so on...
> Any clue to solve this problem?
> Thanks in advance.
apt-proxy is poorly documented WRT error messages. I guess this happens
because it needs Packages files from the backend directories to get the
paths of that files. No packages files -> no path data -> no clue where
to store the files (to have correct url) -> apt-proxy confusion.
Solution: update the Packages files by running "apt-get update" on
clients, so apt-proxy would need to download them at least once.
(self-add...) I am maintainer of apt-cacher and the current version
will let you import anything, but may deliver wrong files later. The
next version will track the files in a similar way that apt-proxy does.
Eduard.
--
Emperor Cartagia: [to Londo Mollari] The trouble with being infallible is that
you have to deal with everyone else making mistakes.
-- Quotes from Babylon 5 --
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
