Issue 22379 - cvs rdiff does not work
Summary: cvs rdiff does not work
Status: CLOSED FIXED
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: Upgrade (show other issues)
Version: current
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: jobin1
QA Contact: issues@www
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-11-12 14:35 UTC by Martin Hollmichel
Modified: 2003-12-06 14:52 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Martin Hollmichel 2003-11-12 14:35:44 UTC 
cvs rdiff does not work, please see issue 3021 for reference
Comment 1 jobin1 2003-11-12 17:37:02 UTC 
Opened internal staging issue pcn 24010
Comment 2 jobin1 2003-11-13 01:36:37 UTC 
The underlying absolute path changes from SC 1.1.3 to 2.6.x.  This is 
hidden from CVS client operations by the use of symbolic links.  But 
for r* commands, the user must specify the new absolute, non-symlinks 
path.  The new real path is "/shared/data/ccvs/repository"
Comment 3 Martin Hollmichel 2003-11-13 07:17:27 UTC 
mh->hr: how is the impact to our tooling ?
Comment 4 jens-heiner.rechtien 2003-11-13 11:19:34 UTC 
The change in the path will break things again for all developers.
I'll have to change tools for that. I would have to educate all the
developers to extend their .cvspass. Why can't we have r-commands
which work like supposed? The workarounds for this long standing
problems have already caused man weeks in lost time.
Comment 5 stx123 2003-11-13 11:27:09 UTC 
Please note, that the issue is in state resolved/fixed.
I would recommend to reopen, if you think that a chnage of the new
behaviour is needed.
Comment 6 Martin Hollmichel 2003-11-13 16:05:03 UTC 
reopen
Comment 7 jobin1 2003-11-14 21:13:15 UTC 
We would like to further understand the impact of this change.  

Setting up the old absolute path would create a non-standard, 
unsupported use of CVS for this version of our product. A future 
version of our product will provide absolute path name flexibility, 
but for now the absolute path name is as specified.

Do all users use r* commands?  Or are the tools modified once and 
disseminated to the developers?  To what degree is this an annoyance 
or a major problem?
Comment 8 Martin Hollmichel 2003-11-16 10:26:23 UTC 
the rdiff command is used by almost all users on regular basis. the
rdiff command provideds analysis possibilities in our child work space
scenario we implemented upon cvs.

the current server implementation of ooo cvs does not provide any help
that the standard behavior of cvs has been changed for OOo. Even
worse, the displayed error message doesn't help the user at all.

so we would need to train all users of ooo cvs to add their login to
cvs with this specific r* path and we are also not able to explain,
why collab's implementations of cvs differs from the standard. this is
very error-prone and anoying.
Comment 9 jobin1 2003-11-17 23:56:45 UTC 
Thank you for the feedback.  I have forwarded this information to CN 
engineering.  We are currently evaluating ways to resolve this.
Comment 10 jobin1 2003-11-20 16:50:33 UTC 
We have determined a way to resolve this so the original absolute 
path will work for the 2.6.2 install.  Please confirm on the next OOo 
stage.
Comment 11 Martin Hollmichel 2003-12-02 12:00:42 UTC 
verified on new stage
Comment 12 Martin Hollmichel 2003-12-02 12:09:12 UTC 
closing