|
List Info
Thread: Some Comments
|
|
| Some Comments |
 
Mexico |
2007-05-24 15:15:00 |
I've recently tried to convert a VSS repository to
Subversion.
We have all our projects in a single VSS repository (one per
folder).
So I first tried to convert the whole repository and use
filtering to
only insert entries related to the project I wanted to
convert. (method
recommended in the Wiki)
This project had shares that were deleted and various files
ended in the
orphaned folder. So when I tried to svndumpfilter for only
the project
folder I was getting errors when svn was trying to copy from
orphaned
back to the project folder.(missing file error)
So I thought I would include the orphaned folder but then
again ran into
trouble because orphaned was trying to copy some files to
another
project that was not included in the filter....
To solve that I ended up searching for all copy operations
from orphaned
to my project folder and with that created a big include
that would
include all the subfolders that were needed by a svn
copy/move operation
( orphaned/YYYYAAA ..etc)
After doing that svndumpfilter managed to create a file. I
inserted that
file into SVN and tried to compare and realized that some
files were
missing (actually whole folders too)
I searched the dumpfile and realized that those missing
files and
missing folders were in the orphaned folder and were never
moved to the
project folder....
At that point I was about to give up and insert a latest
copy into SVN
(effectively losing all history) and then tried to do a
backup of the
project restored that backup into a fresh new VSS repository
and ran the
conversion again (actually this time I used the latest
nightly). At the
end I inserted the content of the dump file and the project
folder was
not even there. The whole project was in orphaned. But I
just
moved/renamed and then compared. Only very few files were
missing.
Those missing files were all files that were created and
never modified
(i.e. no history) so I added those missing files manually
and ended up
with a complete SVN repository with full history.
I am not sure if the backup/restore is better than
svndumpfilter but it
surely is a lot easier/faster. The first try was made using
the
recommended alpha version while the second was made using
the latest
nightly so maybe the latest nightly would have managed to
move missing
files from orphaned on its own using the original repository
but who
knows...
Anyway hats off to the developers, that project folder was
the worst so
I guess if vss2svn managed to convert this one it should be
able to
convert all others.....
_______________________________________________
vss2svn-users mailing list
Project homepage:
http://www.
pumacode.org/projects/vss2svn/
Subscribe/Unsubscribe/Admin:
http://lists.pumacode.org/mailman/lis
tinfo/vss2svn-users-lists.pumacode.org
Mailing list web interface (with searchable archives):
http://dir.gmane.org/gmane.comp.version-c
ontrol.subversion.vss2svn.user
|
|
| Re: Some Comments |
 
United States |
2007-05-24 16:27:20 |
|
An interesting experience.
Unfortunately I'm now about to abort
my efforts with vss2svn. After finding and fixing a problem that prevented
the dumpfile from being loaded into subversion, a comparison of the HEAD
revision of the Subversion database against a fresh "Get Latest"
from VSS showed hundreds of different and/or missing files. There were
many many orphaned directories, and no doubt the missing files were buried
in there somewhere, but I don't have time to look for all of them. I don't
know why some of the files would be different, though. What would concern
me the most, however, is that if the HEAD revision does not match, can
I be sure about the history that I am painstakingly trying to preserve
?
So, I agree, vss2svn is a great tool.
However, methinks our VSS database is perhaps so corrupt that it was too
hard a task to convert it.
Dave
This e-mail message and any attachments
may contain confidential, proprietary or non-public information. This information
is intended solely for the designated recipient(s). If an addressing or
transmission error has misdirected this e-mail, please notify the sender
immediately and destroy this e-mail. Any review, dissemination, use or
reliance upon this information by unintended recipients is prohibited.
Any opinions expressed in this e-mail are those of the author personally.
Guillaume Gros <guillaume scio.com.mx>
Sent by: vss2svn-users-bounceslists.pumacode.org
25-May-2007 06:15 AM
Please respond to
Vss2Svn Users <vss2svn-userslists.pumacode.org>; |
|
To
| vss2svn-userslists.pumacode.org
|
cc
|
|
|
Subject
Some Comments | | |
| |
I've recently tried to convert a VSS repository to
Subversion.
We have all our projects in a single VSS repository (one per folder).
So I first tried to convert the whole repository and use filtering to
only insert entries related to the project I wanted to convert. (method
recommended in the Wiki)
This project had shares that were deleted and various files ended in the
orphaned folder. So when I tried to svndumpfilter for only the project
folder I was getting errors when svn was trying to copy from orphaned
back to the project folder.(missing file error)
So I thought I would include the orphaned folder but then again ran into
trouble because orphaned was trying to copy some files to another
project that was not included in the filter....
To solve that I ended up searching for all copy operations from orphaned
to my project folder and with that created a big include that would
include all the subfolders that were needed by a svn copy/move operation
( orphaned/YYYYAAA ..etc)
After doing that svndumpfilter managed to create a file. I inserted that
file into SVN and tried to compare and realized that some files were
missing (actually whole folders too)
I searched the dumpfile and realized that those missing files and
missing folders were in the orphaned folder and were never moved to the
project folder....
At that point I was about to give up and insert a latest copy into SVN
(effectively losing all history) and then tried to do a backup of the
project restored that backup into a fresh new VSS repository and ran the
conversion again (actually this time I used the latest nightly). At the
end I inserted the content of the dump file and the project folder was
not even there. The whole project was in orphaned. But I just
moved/renamed and then compared. Only very few files were missing.
Those missing files were all files that were created and never modified
(i.e. no history) so I added those missing files manually and ended up
with a complete SVN repository with full history.
I am not sure if the backup/restore is better than svndumpfilter but it
surely is a lot easier/faster. The first try was made using the
recommended alpha version while the second was made using the latest
nightly so maybe the latest nightly would have managed to move missing
files from orphaned on its own using the original repository but who
knows...
Anyway hats off to the developers, that project folder was the worst so
I guess if vss2svn managed to convert this one it should be able to
convert all others.....
_______________________________________________
vss2svn-users mailing list
Project homepage:
http://www.pumacode.org/projects/vss2svn/
Subscribe/Unsubscribe/Admin:
http://lists.pumacode.org/mailman/listinfo/vss2svn-users-lists.pumacode.org
Mailing list web interface (with searchable archives):
http://dir.gmane.org/gmane.comp.version-control.subversion.vss2svn.user
|
[1-2]
|
|
|
about | contact Other archives ( Real Estate discussion Medical topics )
|