#11 apt-proxy-import: no suitable backend

[Anonymous]

Upon updating to Sarge I wanted to minimize mirror
traffic so I attempted
to install and initialize apt-proxy version 2.

Attempting to run apt-proxy-import -i
/var/cachce/apt/archives gave a permissions error. I
changed the shell in /etc/passwd for aptproxy to be
bash, did: su - aptproxy, and attempted to re-run the
above command.

At this point, I was told that every package was being
skipped due to the inability to find a suitable backend.

After searching the bug data base, it appears that this
problem was reported, then reported fixed more than ten
days ago, but it appears to still be in the apt-proxy
package I installed on 2005 Jun 18.

[Nobody/Anonymous]

Logged In: NO

Email me at john at betelgeuse dot us

Thanks

[Chris E]

Logged In: YES
user_id=24312

This is still a problem as of version 1.9.32 of apt-proxy.

From a brief look at the problem, when 'import_file' in
packages.py is reached, the value of 'paths' returned by:

try:
paths = get_mirror_path(factory, dir+'/'+file)
except SystemError:
log.msg(file + ' skipped - wrong format or
corrupted', 'import')
return

is the empty array.

[Chris E]

Logged In: YES
user_id=24312

Additionally, the other message printed out repeatedly is:

No Packages files available for %s backend

[Nobody/Anonymous]

Logged In: NO

(using apt-proxy 1.9.x (1.9.33-0.1) on debian)
Having digged through the sources of apt-proxy-import, it
seems the import utility relies on packages.db in
/var/cache/apt-proxy/.apt-proxy-import/backend/xxxxx
directories.
On my system these directories are empty until I start
apt-proxy-import. After that there are databases, but they
are empty.
Is it possible, that apt-proxy-import is not up to date with
apt-proxy 2 ?