Hi,
I have:
MASTER_SITE_OVERRIDE= \
        ftp://ftp2.fr.netbsd.org/pub/NetBSD/packages/distfiles/${DIST_SUBDIR} \
        ftp://ftp.fr.netbsd.org/pub/NetBSD/packages/distfiles/${DIST_SUBDIR}

in my /etc/mk.conf. This works fine as long as DIST_SUBDIR is not set.
When DIST_SUBDIR is set (e.g. for teTeX-bin) it omits the '/':
===>  Validating dependencies for teTeX-bin-1.0.6
>> teTeX-src-1.0.6.tar.gz doesn't seem to exist on this system.
>> Attempting to fetch teTeX-src-1.0.6.tar.gz from ftp://ftp2.fr.netbsd.org/pub/NetBSD/packages/distfiles/teTeX.
Connected to antioche.antioche.eu.org.
[...]
230 Guest login ok, access restrictions apply.
Remote system type is UNIX.
Using binary mode to transfer files.
200 Type set to I.
250 CWD command successful.
250 CWD command successful.
250 CWD command successful.
250 CWD command successful.
local: teTeXteTeX-src-1.0.6.tar.gz remote: teTeXteTeX-src-1.0.6.tar.gz
500 'EPSV': command not understood.
227 Entering Passive Mode (132,227,74,11,205,229)
550 teTeXteTeX-src-1.0.6.tar.gz: No such file or directory.

If I change /etc/mk.conf to:
MASTER_SITE_OVERRIDE= \
        ftp://ftp2.fr.netbsd.org/pub/NetBSD/packages/distfiles/${DIST_SUBDIR}/ \
        ftp://ftp.fr.netbsd.org/pub/NetBSD/packages/distfiles/${DIST_SUBDIR}/

then when DIST_SUBDIR is not set we'll have '//' before the file name
which seems to confuse the ftp server:
===>  Validating dependencies for bison-1.28
>> bison-1.28.tar.gz doesn't seem to exist on this system.
>> Attempting to fetch bison-1.28.tar.gz from ftp://ftp2.fr.netbsd.org/pub/NetBSD/packages/distfiles//.
Connected to antioche.antioche.eu.org.
[...]
230 Guest login ok, access restrictions apply.
Remote system type is UNIX.
Using binary mode to transfer files.
200 Type set to I.
250 CWD command successful.
250 CWD command successful.
250 CWD command successful.
250 CWD command successful.
500 'CWD ': command not understood.
CWD command not recognized, trying XCWD.
500 'XCWD ': command not understood.

ftp: The `CWD ' command (without a directory), which is required by
     RFC 1738 to support the empty directory in the URL pathname (`//'),
     conflicts with the server's conformance to RFC 959.
     Try the same URL without the `//' in the URL pathname.

221 Goodbye.

Any idea on how to solve this ? I think this setup worked properly some time
ago but I'm can't certify it.

--
Manuel Bouyer, LIP6, Universite Paris VI.           Manuel.Bouyer@lip6.fr
--