unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Sebastian P. Luque" <spluque@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: ange-FTP and Windows NT servers
Date: Thu, 05 Jul 2007 12:23:20 -0500	[thread overview]
Message-ID: <87sl82ydbr.fsf@patagonia.sebmags.homelinux.org> (raw)

Hi,

Trying to access the following Windows NT ftp server through
tramp/ange-FTP fails:

/anonymous@win-builder.r-project.org:/

http://win-builder.r-project.org has a brief explanation for connecting,
which says we should connect with passive ftp in binary mode (I don't
understand what this means).  The following appears in *Messages*:

Listing /anonymous@win-builder.r-project.org:/...done
Doing CD... [44 times]
 nonexistent.

and I can't get any further with debug-on-error set to t.  I can interact
with that directory from a browser (konqueror) at
ftp://win-builder.r-project.org without problems.  I'm told that the
problem seems to be that ange-FTP doesn't understand Windows NT directory
listing format.  Logging in from the shell gives:

---<---------------cut here---------------start-------------->---
$ ftp win-builder.r-project.org
Connected to win-builder.r-project.org.
220-Microsoft FTP Service
220 Welcome on CRANwinGuest
Name (win-builder.r-project.org:sluque): anonymous
331 Anonymous access allowed, send identity (e-mail name) as password.
Password:
230-Before uploading source packages to R-release, R-patched or R-devel, please read
    http://129.217.207.166/index.htm
    Disclaimer
    * You are using this service on your own risk!
    * We do not guarantee privacy of the uploaded
    files or data in any way: Names of uploaded
    packages are always listable by everybody.
    After the compilation process we try to hide
    the binary package as well as the logs using
    randomly chosen directory names.
    Nevertheless, everybody who knows or guesses
    those names can download the.
    * Although virus checking is performed on the
    compiled binary packages, we do not guarantee
    that files made available for download are
    free of malware (such as viruses or trojans).
    * The results of R CMD check are returned from
    a particular given system with a particular
    setup and might not be reproducible on other
    systems. Hence we do not guarantee for the
    results of R CMD check.
230 Anonymous user logged in.
Remote system type is Windows_NT.
ftp> dir
200 PORT command successful.
150 Opening ASCII mode data connection for /bin/ls.
04-16-07  03:41PM       <DIR>          R-devel
12-22-06  11:21AM                  869 ReadMe.txt
07-02-07  08:18PM       <DIR>          R-release
226 Transfer complete.
ftp> bye
221 Goodbye from CRANwinGuest
---<---------------cut here---------------end---------------->---

Hopefully someone with experience on ange-FTP can provide some suggestions
as to what may be going on.  Thanks.


Cheers,

-- 
Seb

             reply	other threads:[~2007-07-05 17:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-05 17:23 Sebastian P. Luque [this message]
2007-07-05 18:05 ` ange-FTP and Windows NT servers Lennart Borgman (gmail)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sl82ydbr.fsf@patagonia.sebmags.homelinux.org \
    --to=spluque@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).