Bug 604004 - 'man lftp' gives wrong default for xfer:clobber
Summary: 'man lftp' gives wrong default for xfer:clobber
Alias: None
Product: Fedora
Classification: Fedora
Component: lftp
Version: 13
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Jiri Skala
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-06-15 06:39 UTC by Bruce Jerrick
Modified: 2014-11-09 22:33 UTC (History)
3 users (show)

Fixed In Version: lftp-4.0.9-1.fc13
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-06-15 07:47:19 UTC

Attachments (Terms of Use)

Description Bruce Jerrick 2010-06-15 06:39:52 UTC
Description of problem:
/usr/share/doc/lftp-4.0.7/NEWS states (correctly) that xfer:clobber
is off by default now, yet the man page still says "Default is on".
(And since the default has changed, "xfer:clobber" will be showing up
in error messages now, and people will look at the man page and wonder

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. head -3 /usr/share/doc/lftp-4.0.7/NEWS	# right there on top
2. zgrep -A2 "xfer:clobber" /usr/share/man/man1/lftp.1.gz
Actual results:
From Step 1:
    Version 4.0.7 - 2010-04-29
    * make xfer:clobber off by default.
From Step 2:
    .BR xfer:clobber \ (boolean)
    if this setting is off, get commands will not overwrite existing
    files and generate an error instead. Default is on.

Expected results:
Man page should say "Default is off."

Additional info:
It is left as an exercise to show that xfer:clobber is indeed off now
by default.  Hint: Error message is:
    get: license.chm: file already exists and xfer:clobber is unset

Be aware that 'man lftp | grep "xfer:clobber"' will not show anything,
due to embedded overstrike characters.

Comment 1 Fedora Update System 2010-06-15 07:46:25 UTC
lftp-4.0.9-1.fc13 has been submitted as an update for Fedora 13.

Comment 2 Fedora Update System 2010-06-30 15:11:45 UTC
lftp-4.0.9-1.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.

Note You need to log in before you can comment on or make changes to this bug.