dotSoftwaredotDevelopmentdotCustomersdotAbout us
PushOk logoblank
bullet Home
bullet My software
bullet Support
bullet My payments
bullet My info
bullet Subscriptions
bullet Voting
bullet Contact us
fast linksFast Links
news&eventsnews and events

2012-12-21 
Major update of SVN SCC plug-in - versions 1.7.2 are finaly released

2012-12-21 
Major update of SVNCOM version 1.7.2 are finaly released

Lightweight embedded Node.js database with MongoDB API.

Ticket

Search go
PushOk Logo blank
leftTicketright

renaming files with cvsnt does not always work properly

( CVSSCC )
Type: Public Status:Closed Created: 17 May 07 05:00 Updated: 22 May 07 05:00
--> Igor Pushkov (admin)  at 22 May 07 05:00 writes

I'm sorry, however our experiments shows that renaming functionality of CVS
NT is very unstable and can be considered only as experimental. File
renames some how worked, folder renaming on repeating renames (same file
several times) cause unpredictable results.
I do believe that you better address this issue to CVS NT developers, who
unfortunatelly doesn't release any _really usefule_ code more than one
year.
Renaming functionality pretty well work with Subversion for which is also
exist our plug-in.
--> Prof. Dr. E. Neuburger Versich Ferdinand Helmer (user)  at 18 May 07 05:00 writes

Dear all,

a little update/supplement to the above message:

1.) Compression seems to work now
2.) The key feature to "make" the server create the .directory_xxx file
where the renaming information is stored is to perform the "addtitional"
commit as described before. This commit has to be on the project and not on
any specifi file. (as described above)
3.) Getting old versions with old filenames e.g. using tags/branches does
not work reliably. Although it sometimes seems to work, very often you
still get new filenames with correct old contents. (the "mixed" state
described above)

We would really like to hear your experience with the renaming feature and
if such behaviour is known and if a solution/workaround exists.

all the best,

Ferdinand Helmer
inst. Prof. Neuburger & Partner
--> Prof. Dr. E. Neuburger Versich Ferdinand Helmer (user)  at 17 May 07 05:00 writes

Hello,

using pushok for cvsnt and also a cvsnt server on a fedora core 5 machine:

this is what we are trying to do:

1. We start with a VS 2005 project containing some source files.
2. Then we want to rename some of them, so we first create a branch caled
"VORUM" on the project to mark the state before renaming
3. Then we rename the files in Visual Studio (and maybe afterwards also
edit/change and commit them again)
4. Then we do a "clean" checkout of the whole project from within VS2005
(head revision) to some other place and correctly see the renamed files
5. Then we do a "clean" checkout of the project but request the branch
"VORUM"

-> Unfortunately we do not get the old filenames back, instead we get a
"mixed" state, new filenames (wrong) but correct content according to the
branch "VORUM"

Another observation: Regardless of the server-side setting, using
compression when renaming seems to break things completely, so not even
step 4 works.

To analyze the problem, we intercepted the calls from the pushok client to
the cvsnt binary by writing a "proxy" application that dumps the commands
and return codes and passes them on to the cvsnt binary.

This is the "log" for the above procedure up to step 3 (with compression):

Command: C:\temp\cvs_orig.exe "-z" "5" "-r" "status" "-l"
"ReadMe_um.txt" returned value: 0
Command: C:\temp\cvs_orig.exe "-z" "5" "-r" "editors"
"cvs_test29.vcproj.vspscc" "cvs_test29.vcproj" returned value: 0
Command: C:\temp\cvs_orig.exe "-z" "5" "-r" "edit"
"cvs_test29.vcproj.vspscc" "cvs_test29.vcproj" returned value: 0
Command: C:\temp\cvs_orig.exe "-z" "5" "-r" "rename" "ReadMe.txt"
"ReadMe_um.txt" returned value: 0
Command: C:\temp\cvs_orig.exe "-z" "5" "-r" "update" "-c"
"ReadMe_um.txt" returned value: 0
Command: C:\temp\cvs_orig.exe "-z" "5" "-r" "commit" "-m" ""
"ReadMe_um.txt" returned value: 0
Command: C:\temp\cvs_orig.exe "-z" "5" "-r" "editors" "ReadMe_um.txt"
returned value: 0
Command: C:\temp\cvs_orig.exe "-z" "5" "-r" "edit" "ReadMe_um.txt"
returned value: 0

However, although we do not really fully understand it, we are able to
perform the whole procedure from the command-line directly, just doing one
thing differently. Instead of doing:

Command: C:\temp\cvs_orig.exe "-z" "5" "-r" "rename" "ReadMe.txt"
"ReadMe_um.txt" returned value: 0
Command: C:\temp\cvs_orig.exe "-z" "5" "-r" "update" "-c"
"ReadMe_um.txt" returned value: 0
Command: C:\temp\cvs_orig.exe "-z" "5" "-r" "commit" "-m" ""
"ReadMe_um.txt" returned value: 0

We insert another commit of the whole project directly after renaming.

Command: C:\temp\cvs_orig.exe "-z" "5" "-r" "rename" "ReadMe.txt"
"ReadMe_um.txt" returned value: 0
Command: C:\temp\cvs_orig.exe -z 5 -r commit -m "renamed" returned value:
0
Command: C:\temp\cvs_orig.exe "-z" "5" "-r" "update" "-c"
"ReadMe_um.txt" returned value: 0
Command: C:\temp\cvs_orig.exe "-z" "5" "-r" "commit" "-m" ""
"ReadMe_um.txt" returned value: 0


This seems to fix the "branch" problem, however it is only a workaround and
the compression problem remains and we still need to manually edit the
.vcproj files.

Is this a known issue?

Is there another easy way to achieve what we are trying to do?

Any help is appreciated.

Yours sincerely,

Ferdinand Helmer
Inst. Prof Neuburger & Partner
Rate this ticket:
Not useful at all
Partially useful
Useful
Very useful



You are 9789355 visitor since 20 Jan 2003.
624 visitors today and 1 online right now.
blank left to top right blank

© Copyright by PushOk Software, 2003-2024, webmaster@pushok.com