Package: lftp
Version: 3.3.2-1
Severity: normal

I installed the latest lftp to avoid the double-free problem (bug
#334059 and several duplicates) but ran into a new bug that didn't
happen with 3.3.1-1 and earlier - when accessing an HTTP host the first
`ls' issued lists nothing, but repeating the `ls' a second time gives
the proper listing.

An example:

[EMAIL PROTECTED]:~$ lftp http://www.google.ca/
cd ok, cwd=/
lftp www.google.ca:/> ls
lftp www.google.ca:/> ls
-rw-r--r--  --  intl/en_ca/images/logo.gif
drwxr-xr-x  --  intl/en/options
-rw-r--r--  --  fr
drwxr-xr-x  --  ads
drwxr-xr-x  --  services
-rw-r--r--  --  intl/en/about.html
lftp www.google.ca:/> exit


`ls' for FTP targets appears to work properly.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.13-ck1
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)

Versions of packages lftp depends on:
ii  libc6                         2.3.5-7    GNU C Library: Shared libraries an
ii  libexpat1                     1.95.8-3   XML parsing C library - runtime li
ii  libgcc1                       1:4.0.2-2  GCC support library
ii  libgcrypt11                   1.2.1-4    LGPL Crypto library - runtime libr
ii  libgnutls12                   1.2.6-1    the GNU TLS library - runtime libr
ii  libgpg-error0                 1.1-4      library for common error values an
ii  libncurses5                   5.5-1      Shared libraries for terminal hand
ii  libreadline5                  5.0-11     GNU readline and history libraries
ii  libtasn1-2                    0.2.13-1   Manage ASN.1 structures (runtime)
ii  netbase                       4.22       Basic TCP/IP networking system
ii  zlib1g                        1:1.2.3-6  compression library - runtime

lftp recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to