So long as the target repository allows for access via HTTP then simply specify is as such in /etc/apt-proxy/apt-proxy-v2.conf. My problem was I had ftp:// URIs in there, so went through the chain:
aptitude
|
v
apt HTTP method (necessary because that's how apt-proxy works)
|
HTTP
v
apt-proxy
|
FTP (might be necessary if some repository is FTP only)
v
repository
And of course because aptitude was being told to use HTTP it did, and
the HTTP method translates ~ to %7e, which apt-proxy then doesn't
translate back on using an FTP method.
Final solution, given some repositories may be FTP only? Make
apt-proxy check for %escapes and translate back if about to use FTP to
actually fetch a file. At least for this obvious case of %7e -> ~ anyway.
This will, of course, affect rsync and any other non-HTTP method in
apt-proxy as well.
-Ath
--
- Athanasius = Athanasius(at)miggy.org / http://www.miggy.org/
Finger athan(at)fysh.org for PGP key
"And it's me who is my enemy. Me who beats me up.
Me who makes the monsters. Me who strips my confidence." Paula Cole - ME
signature.asc
Description: Digital signature
