Bug: attachement save error
In the file bin/upload there is a misspelling (twice):
oopssaveerrr --> oopssaveerr
When I solved this problem I got:
Topic save error
During save of file Wap.WapLinks an error was found by the version control
system. Please notify your TWikibeta administrator.
/opt/local/GNU/bin/rcs -x,v -q -i -t-none -kb
/app/web/twiki/current/pub/Wap/WapLinks/lucatext.pdf,v 2>&1 1>/dev/null
rcs error: unknown option: -kb
rcs usage: rcs -{ae}logins -Afile -{blu}[rev] -cstring -{iLU}
-{nNs}name[:rev] -orange -t[file] -Vn file ...
rcs aborted
Go back in your browser and save your changes locally.
RCS option configuration will be done in TWiki.cfg but I don't know
what
-kb means.
Test case
Fix record
Corrected spelling to
oopssaveerr.
Environment
| TWiki version: |
twiki20010803 |
| TWiki plugins: |
- |
| Server OS: |
Solaris 5.7 |
| Web server: |
Apache |
| Perl version: |
5.004_04 |
| Client OS: |
HP-UX 10.20 |
| Web Browser: |
Netscape 4.76 |
--
BeatJucker - 21 Aug 2001
Fixed the spelling, in
TWikiAlphaRelease.
I can't reproduce the unknown option -kb rcs error.
Man on rcs on Debian Linux brings this for -kb:
- -b[rev]
- Set the default branch to rev. If rev is omitted, the default branch is reset to the (dynamically) highest branch on the trunk.
Question to
JohnTalintyre: What does this switch do? May be just -k is enough?
--
PeterThoeny - 21 Aug 2001
Here's an extract from the
co manpage (note that
rcs man page refers to this):
Generate a binary image of the old keyword string. This acts like -ko, except it performs all working file input and output in binary mode. This makes little difference on Posix and Unix hosts, but on DOS-like hosts one should use rcs -i -kb to initialize an
RCS file intended to be used for binary files. Also, on all hosts, rcsmerge(1) normally refuses to merge files when -kb is in effect.
Odd this doesn't work in your version of
RCS, the current GNU version certainly includes this, earlier
RCSs did not include support for binary files. TWiki considers a file to be binary if it's not in TWiki.cfg
$attachAsciiPath entry. I've ammended
TWikiReleaseSpring2001UpgradeNotes with this information.
I've rejected the bug on the basis of working
RCS being readily available. However, it would be good to have the option of not using
RCS for attachments histories as an alternative.
--
JohnTalintyre - 23 Aug 2001