From hyugaricdeau at gmail.com Mon Oct 1 12:54:39 2007 From: hyugaricdeau at gmail.com (Erik Bray) Date: Mon Oct 1 12:54:44 2007 Subject: [PATCH] Tiny hash dereference warning in revision 324 Message-ID: Hello, When running vss2svn.pl from trunk with Perl 5.8.7, the following warning is printed: Using a hash as a reference is deprecated at /usr/local/share/perl/5.8.7/Vss2Svn/Dumpfile.pm line 798 Of course, this still works, but being that it's deprecated (and somewhat confusing) syntax, it should be changed at some point. Thanks, Erik Index: script/Vss2Svn/Dumpfile.pm =================================================================== --- script/Vss2Svn/Dumpfile.pm (revision 324) +++ script/Vss2Svn/Dumpfile.pm (working copy) @@ -775,7 +775,7 @@ if (defined $self->{auto_props}) { %tmpProps = $self->{auto_props}->get_props ($node->{path}); } - my $eolStyle = %tmpProps->{'svn:eol-style'}; + my $eolStyle = $tmpProps{'svn:eol-style'}; my $isNative = (defined $eolStyle && $eolStyle eq 'native') ? 1 : 0; my $string = $node->get_headers(); From toby at etjohnson.us Mon Oct 1 23:48:28 2007 From: toby at etjohnson.us (Toby Johnson) Date: Mon Oct 1 23:48:35 2007 Subject: [PATCH] Tiny hash dereference warning in revision 324 In-Reply-To: References: Message-ID: <4701BF8C.8050400@etjohnson.us> Erik Bray wrote: > Hello, > When running vss2svn.pl from trunk with Perl 5.8.7, the following > warning is printed: > Using a hash as a reference is deprecated at > /usr/local/share/perl/5.8.7/Vss2Svn/Dumpfile.pm line 798 > > Of course, this still works, but being that it's deprecated (and > somewhat confusing) syntax, it should be changed at some point. > Thanks Erik, I've committed in r325. toby From david.beddoe at gmail.com Wed Oct 10 10:44:14 2007 From: david.beddoe at gmail.com (David Blinker) Date: Wed Oct 10 10:44:23 2007 Subject: Memory error Message-ID: Hi, I am attempting to migrate a modest project from VSS to SVN. - Our VSS database DATA folder is approximately 40GB in size. - I am using DESTROY to strip away all but the target project (overnight), - then ANALYZE (at least 20 hours) - and vss2svn.pl to convert. However, vss2svn.pl terminates with one of 2 errors: 1. file corrupted, cannot continue or 2. memory error: "The instruction at "0x28085bc1" referenced memory at "0x000000004". The memory could not be "written"." (This last error occurs during "STARTING CACHE FOR PhysicalAction") Can you help me understand what's going on here and what I might do? Also, can you explain why VSS has so many corruptions (reams and reams from ANALYZE) and yet never corrupts the source? Our developers have never reported any source corruption. David -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.pumacode.org/pipermail/vss2svn-users-lists.pumacode.org/attachments/20071010/2f6f75c4/attachment.html From gillius-ml at gillius.org Wed Oct 10 14:59:13 2007 From: gillius-ml at gillius.org (Jason Winnebeck) Date: Wed Oct 10 14:59:25 2007 Subject: Memory error In-Reply-To: References: Message-ID: <470D2101.20005@gillius.org> VSS corrupts often. However, the latest version of the source it does well with. What corrupts are the history records and the versions you pull out of history and I have seen this first hand on many instances. The analyze tool really is finding data that is lost, so VSS is a horrible tool to manage this (hence the benefits of SVN). I wonder if the error comes from ssphys.exe, as I thought when Perl programs fail they give an "exception"-like print. Also I noticed when you DESTROY (delete permanently), it doesn't actually remove anything from VSS. vss2svn actually recovers that. Just an interesting side note. You might need to convert and use filters to get just the data you need. Jason David Blinker wrote: > Hi, I am attempting to migrate a modest project from VSS to SVN. > > > * Our VSS database DATA folder is approximately 40GB in size. > * I am using DESTROY to strip away all but the target project > (overnight), > * then ANALYZE (at least 20 hours) > * and vss2svn.pl to convert. > > > However, vss2svn.pl terminates with one of 2 errors: > > 1. file corrupted, cannot continue or > 2. memory error: "The instruction at "0x28085bc1" referenced memory > at "0x000000004". The memory could not be "written"." (This > last error occurs during "STARTING CACHE FOR PhysicalAction") > > > > Can you help me understand what's going on here and what I might do? > > Also, can you explain why VSS has so many corruptions (reams and reams > from ANALYZE) and yet never corrupts the source? Our developers have > never reported any source corruption. > > David > > > > ------------------------------------------------------------------------ > > _______________________________________________ > 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 From gillius-ml at gillius.org Wed Oct 10 17:26:18 2007 From: gillius-ml at gillius.org (Jason Winnebeck) Date: Wed Oct 10 17:26:34 2007 Subject: Fwd: Memory error In-Reply-To: References: <470D2101.20005@gillius.org> <85ADF0B17B14A64A973404FBC0162F7B06FAD05F@NYC-EXCLS2.dc1.doubleclick.corp> Message-ID: <470D437A.9040403@gillius.org> Well I ran the tool sometime back so you will have to see if it has any filtering options. I believe the "official" story is to export everything then use svnadmin dump and filter that using the standard SVN ways. It was not recommended in the documentation, but I have done a partial backup and restore and exported just those projects. The documentation as I said warns against it but it worked for me. If the project is small you could try that. The checkins really need to be completely separate -- if there is any code sharing then you are going to run into problems. It probably worked for me because the directories I exported never referenced each other, separate groups with separate accounts in separate programming languages never touched the other folders. Jason David Blaikie wrote: > Yes, the error does appear to be coming from ssphys.exe. > > Hm, then should I not be using DESTROY? It seems that converting the > whole 40GB database would be a bear, likely to fail. Do you have any > suggestions on how to proceed? I was hoping if I isolated a small, > young project I could convert that. > > When the perl script (responding to ssphys) tells me that a file is > corrupt, would it work to skip that file? > > I'm actually at wits' end here - not frustrated, just flummoxed. Any > hints, ideas or avenues of exploration much appreciated! > > thanks > > David > > -----Original Message----- > From: vss2svn-users-bounces@lists.pumacode.org > > [mailto:vss2svn-users-bounces@lists.pumacode.org > ] On Behalf Of Jason > Winnebeck > Sent: Wednesday, October 10, 2007 2:59 PM > To: dbb14@columbia.edu ; Vss2Svn Users > Subject: Re: Memory error > > VSS corrupts often. However, the latest version of the source it does > well with. What corrupts are the history records and the versions you > pull out of history and I have seen this first hand on many instances. > The analyze tool really is finding data that is lost, so VSS is a > horrible tool to manage this (hence the benefits of SVN). > > I wonder if the error comes from ssphys.exe, as I thought when Perl > programs fail they give an "exception"-like print. > > Also I noticed when you DESTROY (delete permanently), it doesn't > actually remove anything from VSS. vss2svn actually recovers that. Just > an interesting side note. You might need to convert and use filters to > get just the data you need. > > Jason > > David Blinker wrote: > > Hi, I am attempting to migrate a modest project from VSS to SVN. > > > > > > * Our VSS database DATA folder is approximately 40GB in size. > > * I am using DESTROY to strip away all but the target project > > (overnight), > > * then ANALYZE (at least 20 hours) > > * and vss2svn.pl to convert. > > > > > > However, vss2svn.pl terminates with one of 2 errors: > > > > 1. file corrupted, cannot continue or > > 2. memory error: "The instruction at "0x28085bc1" referenced > memory > > at "0x000000004". The memory could not be "written"." (This > > last error occurs during "STARTING CACHE FOR PhysicalAction") > > > > > > > > Can you help me understand what's going on here and what I might do? > > > > Also, can you explain why VSS has so many corruptions (reams and reams > > > from ANALYZE) and yet never corrupts the source? Our developers have > > never reported any source corruption. > > > > David > > > > > > > > ---------------------------------------------------------------------- > > -- > > > > _______________________________________________ > > vss2svn-users mailing list > > Project homepage: > > http://www.pumacode.org/projects/vss2svn/ > > Subscribe/Unsubscribe/Admin: > > http://lists.pumacode.org/mailman/listinfo/vss2svn-users-lists.pumacod > > e.org Mailing list web interface (with searchable > archives): > > http://dir.gmane.org/gmane.comp.version-control.subversion.vss2svn.use > > r > > _______________________________________________ > 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 > From dbb14 at columbia.edu Wed Oct 10 17:42:00 2007 From: dbb14 at columbia.edu (David Blaikie) Date: Wed Oct 10 17:42:09 2007 Subject: Fwd: Memory error In-Reply-To: <470D437A.9040403@gillius.org> References: <470D2101.20005@gillius.org> <85ADF0B17B14A64A973404FBC0162F7B06FAD05F@NYC-EXCLS2.dc1.doubleclick.corp> <470D437A.9040403@gillius.org> Message-ID: Jason, thanks a lot for your knowledgeshare. I will try a few different things and see what might work. Perhaps I'll try to run the script on the whole 40GB. Does 40GB sound like an inordinately massive project? I've seen messages on this list saying that 10GB is large. If we've been building this thing up over the last 5 years, am I facing a Holy Grail - type situation? thanks again David On 10/10/07, Jason Winnebeck wrote: > > Well I ran the tool sometime back so you will have to see if it has any > filtering options. I believe the "official" story is to export everything > then > use svnadmin dump and filter that using the standard SVN ways. It was not > recommended in the documentation, but I have done a partial backup and > restore > and exported just those projects. The documentation as I said warns > against it > but it worked for me. If the project is small you could try that. The > checkins > really need to be completely separate -- if there is any code sharing then > you > are going to run into problems. It probably worked for me because the > directories I exported never referenced each other, separate groups with > separate accounts in separate programming languages never touched the > other > folders. > > Jason > > David Blaikie wrote: > > Yes, the error does appear to be coming from ssphys.exe. > > > > Hm, then should I not be using DESTROY? It seems that converting the > > whole 40GB database would be a bear, likely to fail. Do you have any > > suggestions on how to proceed? I was hoping if I isolated a small, > > young project I could convert that. > > > > When the perl script (responding to ssphys) tells me that a file is > > corrupt, would it work to skip that file? > > > > I'm actually at wits' end here - not frustrated, just flummoxed. Any > > hints, ideas or avenues of exploration much appreciated! > > > > thanks > > > > David > > > > -----Original Message----- > > From: vss2svn-users-bounces@lists.pumacode.org > > > > [mailto:vss2svn-users-bounces@lists.pumacode.org > > ] On Behalf Of Jason > > Winnebeck > > Sent: Wednesday, October 10, 2007 2:59 PM > > To: dbb14@columbia.edu ; Vss2Svn Users > > Subject: Re: Memory error > > > > VSS corrupts often. However, the latest version of the source it does > > well with. What corrupts are the history records and the versions you > > pull out of history and I have seen this first hand on many instances. > > The analyze tool really is finding data that is lost, so VSS is a > > horrible tool to manage this (hence the benefits of SVN). > > > > I wonder if the error comes from ssphys.exe, as I thought when Perl > > programs fail they give an "exception"-like print. > > > > Also I noticed when you DESTROY (delete permanently), it doesn't > > actually remove anything from VSS. vss2svn actually recovers that. Just > > an interesting side note. You might need to convert and use filters to > > get just the data you need. > > > > Jason > > > > David Blinker wrote: > > > Hi, I am attempting to migrate a modest project from VSS to SVN. > > > > > > > > > * Our VSS database DATA folder is approximately 40GB in size. > > > * I am using DESTROY to strip away all but the target project > > > (overnight), > > > * then ANALYZE (at least 20 hours) > > > * and vss2svn.pl to convert. > > > > > > > > > However, vss2svn.pl terminates with one of 2 errors: > > > > > > 1. file corrupted, cannot continue or > > > 2. memory error: "The instruction at "0x28085bc1" referenced > > memory > > > at "0x000000004". The memory could not be "written"." (This > > > last error occurs during "STARTING CACHE FOR PhysicalAction") > > > > > > > > > > > > Can you help me understand what's going on here and what I might do? > > > > > > Also, can you explain why VSS has so many corruptions (reams and > reams > > > > > from ANALYZE) and yet never corrupts the source? Our developers have > > > never reported any source corruption. > > > > > > David > > > > > > > > > > > > > ---------------------------------------------------------------------- > > > -- > > > > > > _______________________________________________ > > > vss2svn-users mailing list > > > Project homepage: > > > http://www.pumacode.org/projects/vss2svn/ > > > Subscribe/Unsubscribe/Admin: > > > > http://lists.pumacode.org/mailman/listinfo/vss2svn-users-lists.pumacod > > > e.org Mailing list web interface (with searchable > > archives): > > > > http://dir.gmane.org/gmane.comp.version-control.subversion.vss2svn.use > > > r > > > > _______________________________________________ > > 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 > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.pumacode.org/pipermail/vss2svn-users-lists.pumacode.org/attachments/20071010/79ebc4ae/attachment.html From gillius-ml at gillius.org Wed Oct 10 18:25:43 2007 From: gillius-ml at gillius.org (Jason Winnebeck) Date: Wed Oct 10 18:25:58 2007 Subject: Fwd: Memory error In-Reply-To: References: <470D2101.20005@gillius.org> <85ADF0B17B14A64A973404FBC0162F7B06FAD05F@NYC-EXCLS2.dc1.doubleclick.corp> <470D437A.9040403@gillius.org> Message-ID: <470D5167.8000200@gillius.org> David, if you want to keep the topic on the list remember to continue to include vss2svn users e-mail. 40GB sounds huge to me. I hear people speak of repositories that large, and I don't know how it gets that way. Probably because we only use it to do source code. I converted a repository some months ago that represented 5 years of development of a team of 1-5 developers. The converted SVN repository (1.3, not 1.4 style) is 200MB. I considered that large. I don't think I would envy having to deal with a 40GB job. I noticed that when I ran the script on Linux it ran many times faster than on Windows (hours to minutes). When I ran the vss2svn script on a Linux RAM disk, the process went from many minutes to a few minutes. The conversion process and the subsequent svnadmin load are extremely I/O intensive and make lots of small writes. I suggest you use whatever is the fastest storage media you can. In fact, if you have more than one HD on a server, I suggest hosting VSS on one and vss2svn output on the other and reversing that to minimize the switching of reads and writes, which kills HDs. I noticed when I was doing partition resizing with gparted to move file systems around it was going to take an entire DAY to move the partition on the drive to another location, but it took 15 minutes to move it from disk A to disk B then from B back to A in a different location. Sequential reads vs random reads make or break this. If you make the process fast enough, perhaps if you have to convert the whole thing it won't be so bad. Extra memory or disks help. Jason David Blaikie wrote: > Jason, thanks a lot for your knowledgeshare. I will try a few different > things and see what might work. Perhaps I'll try to run the script on > the whole 40GB. Does 40GB sound like an inordinately massive project? > I've seen messages on this list saying that 10GB is large. If we've > been building this thing up over the last 5 years, am I facing a Holy > Grail - type situation? > > thanks again > > David From dbb14 at columbia.edu Wed Oct 10 18:32:19 2007 From: dbb14 at columbia.edu (David Blaikie) Date: Wed Oct 10 18:32:24 2007 Subject: Fwd: Memory error In-Reply-To: <470D5167.8000200@gillius.org> References: <470D2101.20005@gillius.org> <85ADF0B17B14A64A973404FBC0162F7B06FAD05F@NYC-EXCLS2.dc1.doubleclick.corp> <470D437A.9040403@gillius.org> <470D5167.8000200@gillius.org> Message-ID: thanks, my last note was meant just to thank you, but then a question slipped in... ; ) I would _love_ to run the conversion on Linux, which I'm sure you're right is much faster. Is it possible then to just copy the VSS repo to a Linux box and get a Linux version of ssphys.exe? Would ssphys have to be compiled from source? Is any part of this documented somewhere? thanks again for your time here David On 10/10/07, Jason Winnebeck wrote: > > David, if you want to keep the topic on the list remember to continue to > include vss2svn users e-mail. > > 40GB sounds huge to me. I hear people speak of repositories that large, > and I > don't know how it gets that way. Probably because we only use it to do > source > code. I converted a repository some months ago that represented 5 years of > development of a team of 1-5 developers. The converted SVN repository (1.3 > , > not 1.4 style) is 200MB. I considered that large. I don't think I would > envy > having to deal with a 40GB job. > > I noticed that when I ran the script on Linux it ran many times faster > than on > Windows (hours to minutes). When I ran the vss2svn script on a Linux RAM > disk, > the process went from many minutes to a few minutes. The conversion > process > and the subsequent svnadmin load are extremely I/O intensive and make lots > of > small writes. I suggest you use whatever is the fastest storage media you > can. > In fact, if you have more than one HD on a server, I suggest hosting VSS > on > one and vss2svn output on the other and reversing that to minimize the > switching of reads and writes, which kills HDs. I noticed when I was doing > partition resizing with gparted to move file systems around it was going > to > take an entire DAY to move the partition on the drive to another location, > but > it took 15 minutes to move it from disk A to disk B then from B back to A > in a > different location. Sequential reads vs random reads make or break this. > > If you make the process fast enough, perhaps if you have to convert the > whole > thing it won't be so bad. Extra memory or disks help. > > Jason > > David Blaikie wrote: > > Jason, thanks a lot for your knowledgeshare. I will try a few different > > things and see what might work. Perhaps I'll try to run the script on > > the whole 40GB. Does 40GB sound like an inordinately massive project? > > I've seen messages on this list saying that 10GB is large. If we've > > been building this thing up over the last 5 years, am I facing a Holy > > Grail - type situation? > > > > thanks again > > > > David > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.pumacode.org/pipermail/vss2svn-users-lists.pumacode.org/attachments/20071010/27ebaf2b/attachment.html From gillius-ml at gillius.org Wed Oct 10 18:40:21 2007 From: gillius-ml at gillius.org (Jason Winnebeck) Date: Wed Oct 10 18:40:32 2007 Subject: Fwd: Memory error In-Reply-To: References: <470D2101.20005@gillius.org> <85ADF0B17B14A64A973404FBC0162F7B06FAD05F@NYC-EXCLS2.dc1.doubleclick.corp> <470D437A.9040403@gillius.org> <470D5167.8000200@gillius.org> Message-ID: <470D54D5.90904@gillius.org> Yes I copied the VSS repo over. ssphys is what reads it. However, there is no prebuilt. I might be able to send you a copy, but what I had to do is compile vss2svn completely from source. There are instructions on the wiki on how to do this. Since the version I built, there are probably patches that have been checked into its source. If you aren't already, I really do suggest the latest version in the code repository. Last I looked the stable version is something over a year old -- the development version is actually better and more stable than the "stable" release, if this is still the case. The vss2svn developers might chime in at this point? Jason David Blaikie wrote: > thanks, my last note was meant just to thank you, but then a question > slipped in... ; ) > > I would _love_ to run the conversion on Linux, which I'm sure you're > right is much faster. Is it possible then to just copy the VSS repo to > a Linux box and get a Linux version of ssphys.exe? Would ssphys have to > be compiled from source? Is any part of this documented somewhere? > > thanks again for your time here > > David From axissixa at yahoo.fr Thu Oct 18 05:07:45 2007 From: axissixa at yahoo.fr (hector gustave) Date: Thu Oct 18 05:07:53 2007 Subject: Restore VSS2SVN (vss2svn-nightly-20071002.zip) Message-ID: <468695.98319.qm@web23404.mail.ird.yahoo.com> Hello at all, I try to convert my database VSS to SVN (It's not original on this mailing list :) ). I used Analyse 6 for fix my vss database. I ran vss2svn(vss2svn-nightly-20071002.zip) with success and i have my dump file. But when i use my dump file for svn restore, the process stop and i have this error after few minutes. <<< D?but d'une nouvelle transaction bas?e sur la r?vision 7006 * ajout de : orphaned/_BAAAAAAA/GCOS/CP.E/GLOBAL-BAT/2pca81.c ...COPIED... fait. * ajout de : orphaned/_BAAAAAAA/GCOS/CP.D/GLOBAL-BAT/2pca81.c ...svnadmin: Pas de r?vision 7006 (not revision 7006) I had this error yet with vss2svn-nightly-20070803.zip version but at revision 5790. My data base is heavy 3.7GB 178.648 files and 132 folders. My svnadmin version is 1.4.4 (r25188) I can't tell more... Someone can help me ? Thanx a lot. Axis --------------------------------- Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.pumacode.org/pipermail/vss2svn-users-lists.pumacode.org/attachments/20071018/6daa7ae5/attachment.html From vss2svn at nogga.de Fri Oct 19 10:51:10 2007 From: vss2svn at nogga.de (Dirk) Date: Fri Oct 19 10:54:36 2007 Subject: Restore VSS2SVN (vss2svn-nightly-20071002.zip) In-Reply-To: <468695.98319.qm@web23404.mail.ird.yahoo.com> References: <468695.98319.qm@web23404.mail.ird.yahoo.com> Message-ID: <4718C45E.3000503@nogga.de> hello gustave, did you use any specific archive / restore activities on your database. This is still a problem in the converter since it will mess up the timestamps. I'm very busy in the moment, but I could try to have a look into your problem. If you send me the content of your temporary folder for the conversion I will try my very best to have a look at it. Best regards Dirk hector gustave schrieb: > Hello at all, > > I try to convert my database VSS to SVN (It's not original on this > mailing list :) ). > I used Analyse 6 for fix my vss database. > I ran vss2svn(vss2svn-nightly-20071002.zip) with success and i have my > dump file. > But when i use my dump file for svn restore, the process stop and i > have this error after few minutes. > > <<< D?but d'une nouvelle transaction bas?e sur la r?vision 7006 > * ajout de : orphaned/_BAAAAAAA/GCOS/CP.E/GLOBAL-BAT/2pca81.c > ...COPIED... > fait. > * ajout de : orphaned/_BAAAAAAA/GCOS/CP.D/GLOBAL-BAT/2pca81.c > ...svnadmin: > Pas de r?vision 7006 (not revision 7006) > > I had this error yet with vss2svn-nightly-20070803.zip version but at > revision 5790. > My data base is heavy 3.7GB 178.648 files and 132 folders. > > My svnadmin version is 1.4.4 (r25188) > > I can't tell more... > > Someone can help me ? > > Thanx a lot. > > Axis > > ------------------------------------------------------------------------ > Ne gardez plus qu'une seule adresse mail ! Copiez vos mails > vers Yahoo! Mail > ------------------------------------------------------------------------ > > _______________________________________________ > 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 From brucetwilson at gmail.com Mon Oct 22 13:23:50 2007 From: brucetwilson at gmail.com (Bruce Wilson) Date: Mon Oct 22 13:24:05 2007 Subject: Index of errors? Message-ID: <471CDCA6.8020408@toomuchblue.com> I'm finally getting serious about migrating from VSS to SVN. My new repository is up and live, now it's time for the messy work. My first test (using 0.11 Alpha 1) produced an alarming-looking list of errors. I know not to panic, but I'd like to see what I can do to improve on the situation before I do my final. I looked around the Wiki for any index as to what each error means, how serious it is, and what (if anything) can be done to correct or compensate. I came up empty. This seems like a very useful thing to have, and if I could obtain some of this information, I'd be happy to turn this into one or more Wiki pages for future reference. I'd also read that trunk may be more "stable" than 0.11 Alpha 1. Is there a good way to get a binary of trunk? (Again, seems like this would be a good thing to update on the site.) Thanks for all your (volunteer) help. From dbb14 at columbia.edu Mon Oct 22 15:48:16 2007 From: dbb14 at columbia.edu (David Blaikie) Date: Mon Oct 22 15:48:25 2007 Subject: Fwd: Memory error In-Reply-To: <470D54D5.90904@gillius.org> References: <470D2101.20005@gillius.org> <85ADF0B17B14A64A973404FBC0162F7B06FAD05F@NYC-EXCLS2.dc1.doubleclick.corp> <470D437A.9040403@gillius.org> <470D5167.8000200@gillius.org> <470D54D5.90904@gillius.org> Message-ID: Hi I just wanted to check back in and say that I'm planning to do as you suggest to build the script on Linux and take advantage of the speed improvement. When I have more experiences I'll let you know further what's going on. thanks David On 10/10/07, Jason Winnebeck wrote: > > Yes I copied the VSS repo over. ssphys is what reads it. However, there is > no > prebuilt. I might be able to send you a copy, but what I had to do is > compile > vss2svn completely from source. There are instructions on the wiki on how > to > do this. Since the version I built, there are probably patches that have > been > checked into its source. > > If you aren't already, I really do suggest the latest version in the code > repository. Last I looked the stable version is something over a year old > -- > the development version is actually better and more stable than the > "stable" > release, if this is still the case. > > The vss2svn developers might chime in at this point? > > Jason > > David Blaikie wrote: > > thanks, my last note was meant just to thank you, but then a question > > slipped in... ; ) > > > > I would _love_ to run the conversion on Linux, which I'm sure you're > > right is much faster. Is it possible then to just copy the VSS repo to > > a Linux box and get a Linux version of ssphys.exe? Would ssphys have to > > be compiled from source? Is any part of this documented somewhere? > > > > thanks again for your time here > > > > David > > _______________________________________________ > 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 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.pumacode.org/pipermail/vss2svn-users-lists.pumacode.org/attachments/20071022/6e527ea1/attachment.html From brucetwilson at gmail.com Wed Oct 31 18:29:11 2007 From: brucetwilson at gmail.com (Bruce Wilson) Date: Wed Oct 31 18:29:22 2007 Subject: vss2svn-users Digest, Vol 19, Issue 7 In-Reply-To: <20071023160005.E0B3015B6A4@cp.thetahost.com> References: <20071023160005.E0B3015B6A4@cp.thetahost.com> Message-ID: <472901B7.4090802@toomuchblue.com> Wow, I didn't realize this question would bring such a hush on the list. :-) Anybody there? > > Subject: > Index of errors? > Date: > Mon, 22 Oct 2007 12:23:50 -0500 > > > I'm finally getting serious about migrating from VSS to SVN. My new > repository is up and live, now it's time for the messy work. > > My first test (using 0.11 Alpha 1) produced an alarming-looking list > of errors. I know not to panic, but I'd like to see what I can do to > improve on the situation before I do my final. > > I looked around the Wiki for any index as to what each error means, > how serious it is, and what (if anything) can be done to correct or > compensate. I came up empty. This seems like a very useful thing to > have, and if I could obtain some of this information, I'd be happy to > turn this into one or more Wiki pages for future reference. > > I'd also read that trunk may be more "stable" than 0.11 Alpha 1. Is > there a good way to get a binary of trunk? (Again, seems like this > would be a good thing to update on the site.) > > Thanks for all your (volunteer) help. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.pumacode.org/pipermail/vss2svn-users-lists.pumacode.org/attachments/20071031/df351958/attachment.html From snowell at validatedsoftware.com Wed Oct 31 18:54:32 2007 From: snowell at validatedsoftware.com (Scott Nowell) Date: Wed Oct 31 18:52:25 2007 Subject: vss2svn-users Digest, Vol 19, Issue 7 In-Reply-To: <472901B7.4090802@toomuchblue.com> Message-ID: <284525B9F252A445BC26E6DDC34B21710D9E13@vsc-server.ValidatedSoftware.local> Ok, I'll play. I hate to see that no one answered yet. Certainly not the expert, but here goes. I would recommend getting the most recent nightly build. It will have many bugs fixed. Unfortunately I think you have to build it yourself. There is an SVN archive and you have to down load active perl and some functions for it (I think). I managed to do it without too many tries, so it couldn't be too hard. I'm not a perl user but a muddled through. Make absolutely sure you have run the analyze and repair on your VSS database. None the less you are likely to wind up with some strange results. Some of names and versions get real strange due to differences between unix and windows file and path naming conventions. I wound up with quite a few invalid path names. Honestly can't remember how I fixed all that. I may have edited some of the names in the intermediate file. I seem to remember reading on this list that most of those bugs have been fixed, so maybe you won't have that problem. Now that I've typed this, maybe the experts will post the real answers. Good luck though. Scott ________________________________ From: vss2svn-users-bounces@lists.pumacode.org [mailto:vss2svn-users-bounces@lists.pumacode.org] On Behalf Of Bruce Wilson Sent: Wednesday, October 31, 2007 4:29 PM To: vss2svn-users@lists.pumacode.org Subject: Re: vss2svn-users Digest, Vol 19, Issue 7 Wow, I didn't realize this question would bring such a hush on the list. :-) Anybody there? Subject: Index of errors? Date: Mon, 22 Oct 2007 12:23:50 -0500 I'm finally getting serious about migrating from VSS to SVN. My new repository is up and live, now it's time for the messy work. My first test (using 0.11 Alpha 1) produced an alarming-looking list of errors. I know not to panic, but I'd like to see what I can do to improve on the situation before I do my final. I looked around the Wiki for any index as to what each error means, how serious it is, and what (if anything) can be done to correct or compensate. I came up empty. This seems like a very useful thing to have, and if I could obtain some of this information, I'd be happy to turn this into one or more Wiki pages for future reference. I'd also read that trunk may be more "stable" than 0.11 Alpha 1. Is there a good way to get a binary of trunk? (Again, seems like this would be a good thing to update on the site.) Thanks for all your (volunteer) help. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.pumacode.org/pipermail/vss2svn-users-lists.pumacode.org/attachments/20071031/b37270c2/attachment.html