Scott Robison
2011-03-15 20:00:45 UTC
So, I have a subversion repository that I've been using for about 18
months for personal stuff I work on at home and a parallel trac
installation. It has served me well, but I figured I should try out a
dvcs since the world is moving that way. Having been a fan of SQLite
for years I discovered fossil and liked what I read (integrated bug
tracking & wiki) and wanted to give it a shot.
I downloaded a fossil binary for Windows, created an empty repository,
played around with it for a bit, liked it well enough to take the next
step of importing my subversion repository and see how that worked.
After searching for a while, I found a way to import my svn repository
into fossil. svnadmin dump followed by svn-dump-fast-import followed
by fossil import --git. It 'worked' in that I had a fossil repository
after all was said in done. I ran fossil ui, looked at the timeline of
20 most recent items, so far so good. Next I clicked on 200 entries
and got an APPCRASH from Windows 7. "fossil.exe has stopped working"
with the typical check/close/debug options.
I fear that my problem is probably likely due to the very different
models between svn & fossil (or maybe a less than perfect conversion
utility). My svn repo resembles:
\repo
\trunk
\projects
\vendor
\third-party-libraries
\vendor
\third-party-libraryies
\tag-1
\tag-2
\tag-3
\current
Is there a better way to do what I'm trying to do, or should I give up
on the 'ideal' of keeping my subversion history in the new fossil
repository? Also: is it practical to try to maintain multiple projects
in a single repository as I'm trying to do, or should I give that up
and go for a single repo per project?
Thanks for any suggestions & guidance. I really want to like fossil
but am having 'growing pains' or 'migration pains'.
SDR
months for personal stuff I work on at home and a parallel trac
installation. It has served me well, but I figured I should try out a
dvcs since the world is moving that way. Having been a fan of SQLite
for years I discovered fossil and liked what I read (integrated bug
tracking & wiki) and wanted to give it a shot.
I downloaded a fossil binary for Windows, created an empty repository,
played around with it for a bit, liked it well enough to take the next
step of importing my subversion repository and see how that worked.
After searching for a while, I found a way to import my svn repository
into fossil. svnadmin dump followed by svn-dump-fast-import followed
by fossil import --git. It 'worked' in that I had a fossil repository
after all was said in done. I ran fossil ui, looked at the timeline of
20 most recent items, so far so good. Next I clicked on 200 entries
and got an APPCRASH from Windows 7. "fossil.exe has stopped working"
with the typical check/close/debug options.
I fear that my problem is probably likely due to the very different
models between svn & fossil (or maybe a less than perfect conversion
utility). My svn repo resembles:
\repo
\trunk
\projects
\vendor
\third-party-libraries
\vendor
\third-party-libraryies
\tag-1
\tag-2
\tag-3
\current
Is there a better way to do what I'm trying to do, or should I give up
on the 'ideal' of keeping my subversion history in the new fossil
repository? Also: is it practical to try to maintain multiple projects
in a single repository as I'm trying to do, or should I give that up
and go for a single repo per project?
Thanks for any suggestions & guidance. I really want to like fossil
but am having 'growing pains' or 'migration pains'.
SDR