Re: VMS server testing needed (fwd)

2001-04-12 Thread Hrvoje Niksic

"L. Cranswick" [EMAIL PROTECTED] writes:

 Really silly question.  When getting either 1.6 or the latest
 CVS down via CVS  ---

   Where is the .configure script?

It's not included because it's an auto-generated file.  Info and
`.gmo' files are not in the CVS for similar reasons.

As you've gathered by now, running `make -f Makefile.cvs' (or simply
`autoconf') will generate configure.  This however means that you need
to have `autoconf' installed, but CVS sources are expected to be used
by developers who have such stuff.  And Autoconf comes with most Linux
distributions anyway so it's not such a big deal.



Re: VMS server testing needed - RESULT -d output

2001-04-12 Thread Hrvoje Niksic

"L. Cranswick" [EMAIL PROTECTED] writes:

  # download everything under the anonymous tree.
  wget -r ftp://HOST/
 
 bash-2.03$ ./wgetapr01cvs -r -d ftp://ftp.cc.uniud.it/
 
 
 DEBUG output created by Wget 1.7-dev on irix6.5.
[...]
 file name: '.WWW_BROWSABLE;2'
 Name: '.WWW_BROWSABLE'
 File
 second token: '0'
 day: '  7'
 date parsed
 /MM/DD HH:MM:SS - 1995/12/07 16:29:00
 Timestamp: 821032140
 confusing VMS permissions, skipping line

Lachlan, thanks for testing this.  It seems that Jan's VMS parser has
problems with this server's output.  On my system Wget even dumps
core.

Now that I have the address of a system to test, I'll take a look at
the parser and see if I can fix it.



VMS server testing needed

2001-04-11 Thread Hrvoje Niksic

Jan and I made some changes to FTP code to fix several long-standing
bugs with recursive retrieval and CWD.  I tested it with Unix FTP
servers, but the VMS part might be broken.

Could someone with access to a VMS FTP server please try to compile
the latest CVS sources and see if recursive retrieval works?  You
don't need to DL gigabytes of data; you just need to see whether Wget
issues the correct CWD commands to the server.

The interesting cases are:

# download everything under the anonymous tree.
wget -r ftp://HOST/

# download everything under anonumous-root/DIR.
wget -r ftp://HOST/DIR/

# download everything under USER's home directory.
wget -r ftp://USER:PASSWORD@HOST/

# download everything under ~USER/DIR.
wget -r ftp://USER:PASSWORD@HOST/DIR/

# the same, but specified in a different way.
wget -r ftp://USER:PASSWORD@HOST//path/to/users/home/DIR/

# (attempt to) download the whole Unix system directory tree
wget -r ftp://USER:PASSWORD@HOST//

Needless to say, not all of these need be present.  In fact, your
report will be interesting even with only one of them.  The above is
just a list of different setups that exhibited problems at some point.
(The above all work for me with Unix FTP servers.)

If the test case doesn't work (e.g. Wget CWD's into an obviously wrong
directory), please send the `-d' output along with the report.