hi Stefan,
On Wed, Jul 10, 2002 at 04:31:20PM +0200, Stefan Bellon wrote:
> deb http://mplayer.nmeos.net unstable/
>
> Could some kind soul please tell me how to configure apt-proxy and the
> the local sources.list for those mplayer packages? There must be
> something different in the structure how the files are put on the
> server.
Looks like you found a problem. From apt-proxy.log:
[19707 16:49:18]: wget --timeout=10 --timestamping --no-host-directories
--tries=5 --no-directories -P /var/cache/apt-proxy/mplater/ -O /dev/null
http://mplayer.nmeos.net/unstable
[19707 16:49:19]: wget: --16:49:18-- http://mplayer.nmeos.net/unstable
=> `/dev/null'
Resolving mplayer.nmeos.net... done.
Connecting to mplayer.nmeos.net[212.43.221.91]:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: http://ange.nmeos.net/unstable/ [following]
--16:49:18-- http://ange.nmeos.net/unstable/
=> `/dev/null'
Resolving ange.nmeos.net... done.
Connecting to ange.nmeos.net[212.43.221.91]:80... connected.
HTTP request sent, awaiting response... 404 Not Found
16:49:19 ERROR 404: Not Found.
It seems that the backend does some HTTP redirection which wget does not
like, and apt-proxy thinks the directory unstable does not exist.
I've found a workaround for now.
apt-proxy.conf:
add_backend /mplayer/ $APT_PROXY_CACHE/mplayer/ \
http://mplayer.nmeos.net/
sources.list:
deb http://APTPROXY:9999/mplayer unstable/
Then, create the unstable directory manually:
mkdir -p /var/cache/apt-proxy/mplayer/unstable
chown -R aptproxy /var/cache/apt-proxy/mplayer
That way, apt-proxy will not attempt to check if the unstable directory name
is valid, and it should work.
HTH,
Chris
Attachment:
pgpuEeQpyqIFR.pgp
Description: PGP signature