Package: apt-proxy
Version: 1.9.29
Severity: normal

apt-proxy is really neat, but it doesn't support the full range of URIs
available in sources.list; for instance:

  deb ssh://[EMAIL PROTECTED]/. sarge main

In my day job we support several remote networks operated by distinct
organisations, and provide packages that either have redistribution
restrictions or contain canned configurations including site-specific
information that we want to ensure is not disclosed inappropriately;
using ssh URIs like this (in conjunction with key-based authentication
and a chrooted user environment) would enable us to maintain remote,
per-site repositories in a secure and convenient way.

In most other regards, apt-proxy would work very well for us; but its
failure to support the full range of backends available to 'direct' apt
is, for us, an unfortunate shortcoming.

Sorry I have no patch, but my Python is essentially non-existent and a
quick look suggests that this is not a 'quick fix' issue.

Thanks for what is in other respects a great tool,


John Pearson.

-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.12.6-xen
Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1)

Versions of packages apt-proxy depends on:
ii  bzip2                      1.0.2-7       high-quality block-sorting file co
ii  debconf                    1.4.30.13     Debian configuration management sy
ii  logrotate                  3.7-5         Log rotation utility
ii  python                     2.3.5-2       An interactive high-level object-o
ii  python-apt                 0.5.10        Python interface to libapt-pkg
ii  python-bsddb3              3.3.0-6       Python interface to libdb3
ii  python-twisted             1.3.0-8       Event-based framework for internet
ii  python2.3                  2.3.5-3sarge1 An interactive high-level object-o

-- debconf information:
* apt-proxy/upgrading-v2:
* apt-proxy/upgrading-v2-result:


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to