From jd_hardcastle at yahoo.com Thu Dec 13 05:25:22 2007 From: jd_hardcastle at yahoo.com (Jon Hardcastle) Date: Thu Dec 13 05:25:52 2007 Subject: Calling all migrators! Message-ID: <59590.3924.qm@web51303.mail.re2.yahoo.com> Hello, I have an issue that I hoping I get some with from a fellow migrator! I have successfully migrated my repository, and copied over the latest version of all files so it is current and all gaps 'plugged' But now I have an issue. I have promised that all non-source/plain-text files will sport the 'needs-lock' property. i can not for the life of me work out how I can apply this across the entire repository but only to certain extensions of files.. Can anyone help? Rather annoyingly I have set up auto-props but that only works on new files.. it doesn't set it on existing files. Please any pointers gratefully received! ----------------------- N: Jon Hardcastle E: Jon@eHardcastle.com 'The writing is on the wall...' ----------------------- From eugen_eugen at gmx.de Thu Dec 13 07:14:57 2007 From: eugen_eugen at gmx.de (Jewgenij Moldawski) Date: Thu Dec 13 07:15:05 2007 Subject: A question about vss2svn Message-ID: <20071213121457.269200@gmx.net> Hi! I've found the site http://www.pumacode.org/projects/vss2svn and be glad that there it's! I'm going to migrate a VSS database with a couple of files and directories that had been "branched". Will the vss2svn be creating the corresponding branches (in fact directories) in subversion during it runs? Thanks! -- Psssst! Schon vom neuen GMX MultiMessenger geh?rt? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger From gillius-ml at gillius.org Thu Dec 13 08:26:16 2007 From: gillius-ml at gillius.org (Jason Winnebeck) Date: Thu Dec 13 08:26:24 2007 Subject: Calling all migrators! In-Reply-To: <59590.3924.qm@web51303.mail.re2.yahoo.com> References: <59590.3924.qm@web51303.mail.re2.yahoo.com> Message-ID: <476132F8.6020606@gillius.org> There is a script to do this: http://svn.collab.net/viewvc/svn/trunk/contrib/client-side/svn_apply_autoprops.py?view=log Also there is an auto-props setting when you convert using vss2svn, which will set the properties retroactively over all of the history. If you have migrated but haven't gone live yet, you could use that functionality. Jason Jon Hardcastle wrote: > Hello, > > I have an issue that I hoping I get some with from a > fellow migrator! > > I have successfully migrated my repository, and copied > over the latest version of all files so it is current > and all gaps 'plugged' > > But now I have an issue. I have promised that all > non-source/plain-text files will sport the > 'needs-lock' property. > > i can not for the life of me work out how I can apply > this across the entire repository but only to certain > extensions of files.. > > Can anyone help? Rather annoyingly I have set up > auto-props but that only works on new files.. it > doesn't set it on existing files. > > Please any pointers gratefully received! > > ----------------------- > N: Jon Hardcastle > E: Jon@eHardcastle.com > 'The writing is on the wall...' > ----------------------- > > _______________________________________________ > 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 Thu Dec 13 08:28:46 2007 From: gillius-ml at gillius.org (Jason Winnebeck) Date: Thu Dec 13 08:28:53 2007 Subject: A question about vss2svn In-Reply-To: <20071213121457.269200@gmx.net> References: <20071213121457.269200@gmx.net> Message-ID: <4761338E.4030106@gillius.org> My understanding is that it doesn't. I think branches and shares are viewed as completely separate files that are just modified in lock-step. I'm not sure you could map it properly, because VSS is file-based, so you branch files. You don't name branches, if I recall correctly, so SVN wouldn't have a way of naming the branch directory anyway. Jason Jewgenij Moldawski wrote: > Hi! > > I've found the site http://www.pumacode.org/projects/vss2svn and be glad that there it's! > > I'm going to migrate a VSS database with a couple of files and directories that had been "branched". Will the vss2svn be creating the corresponding branches (in fact directories) in subversion during it runs? > > Thanks! > > From toby at etjohnson.us Thu Dec 13 09:29:39 2007 From: toby at etjohnson.us (Toby Johnson) Date: Thu Dec 13 09:29:41 2007 Subject: A question about vss2svn In-Reply-To: <20071213121457.269200@gmx.net> References: <20071213121457.269200@gmx.net> Message-ID: <476141D3.6070000@etjohnson.us> Jewgenij Moldawski wrote: > Hi! > > I've found the site http://www.pumacode.org/projects/vss2svn and be glad that there it's! > > I'm going to migrate a VSS database with a couple of files and directories that had been "branched". Will the vss2svn be creating the corresponding branches (in fact directories) in subversion during it runs? > A branch in VSS is mapped to a copy in Subversion, so yes that "should" be supported. From toby at etjohnson.us Thu Dec 13 09:31:46 2007 From: toby at etjohnson.us (Toby Johnson) Date: Thu Dec 13 09:31:48 2007 Subject: A question about vss2svn In-Reply-To: <4761338E.4030106@gillius.org> References: <20071213121457.269200@gmx.net> <4761338E.4030106@gillius.org> Message-ID: <47614252.5020706@etjohnson.us> Jason Winnebeck wrote: > My understanding is that it doesn't. I think branches and shares are > viewed as completely separate files that are just modified in lock-step. > > I'm not sure you could map it properly, because VSS is file-based, so > you branch files. You don't name branches, if I recall correctly, so > SVN wouldn't have a way of naming the branch directory anyway. I don't honestly remember whether VSS branches files or directories or both but we do try to support branches. You don't name the branch itself, but when you branch you in effect make a copy of it in a 2nd location, so that's what we do in vss2svn. toby From jd_hardcastle at yahoo.com Thu Dec 13 10:36:35 2007 From: jd_hardcastle at yahoo.com (Jon Hardcastle) Date: Thu Dec 13 10:37:17 2007 Subject: Calling all migrators! In-Reply-To: <476132F8.6020606@gillius.org> Message-ID: <778381.47148.qm@web51310.mail.re2.yahoo.com> Fantastic. that python script is the dogs nads! Cheers! --- Jason Winnebeck wrote: > There is a script to do this: > > http://svn.collab.net/viewvc/svn/trunk/contrib/client-side/svn_apply_autoprops.py?view=log > > Also there is an auto-props setting when you convert > using vss2svn, which will > set the properties retroactively over all of the > history. If you have migrated > but haven't gone live yet, you could use that > functionality. > > Jason > > Jon Hardcastle wrote: > > Hello, > > > > I have an issue that I hoping I get some with from > a > > fellow migrator! > > > > I have successfully migrated my repository, and > copied > > over the latest version of all files so it is > current > > and all gaps 'plugged' > > > > But now I have an issue. I have promised that all > > non-source/plain-text files will sport the > > 'needs-lock' property. > > > > i can not for the life of me work out how I can > apply > > this across the entire repository but only to > certain > > extensions of files.. > > > > Can anyone help? Rather annoyingly I have set up > > auto-props but that only works on new files.. it > > doesn't set it on existing files. > > > > Please any pointers gratefully received! > > > > ----------------------- > > N: Jon Hardcastle > > E: Jon@eHardcastle.com > > 'The writing is on the wall...' > > ----------------------- > > > > _______________________________________________ > > 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 > > > ----------------------- N: Jon Hardcastle E: Jon@eHardcastle.com 'The writing is on the wall...' ----------------------- From toby at etjohnson.us Thu Dec 13 10:50:08 2007 From: toby at etjohnson.us (Toby Johnson) Date: Thu Dec 13 10:50:11 2007 Subject: Calling all migrators! In-Reply-To: <778381.47148.qm@web51310.mail.re2.yahoo.com> References: <778381.47148.qm@web51310.mail.re2.yahoo.com> Message-ID: <476154B0.7000504@etjohnson.us> Jon Hardcastle wrote: > Fantastic. that python script is the dogs nads! > Hmm, is that considered a good thing? From jd_hardcastle at yahoo.com Thu Dec 13 11:12:46 2007 From: jd_hardcastle at yahoo.com (Jon Hardcastle) Date: Thu Dec 13 11:12:52 2007 Subject: Calling all migrators! In-Reply-To: <476154B0.7000504@etjohnson.us> Message-ID: <313496.47989.qm@web51302.mail.re2.yahoo.com> --- Toby Johnson wrote: > Jon Hardcastle wrote: > > Fantastic. that python script is the dogs nads! > > > Hmm, is that considered a good thing? > No, it is considered a VERY good thing.. :) ----------------------- N: Jon Hardcastle E: Jon@eHardcastle.com 'The writing is on the wall...' ----------------------- From hyugaricdeau at gmail.com Mon Dec 31 15:42:43 2007 From: hyugaricdeau at gmail.com (Erik Bray) Date: Mon Dec 31 15:42:48 2007 Subject: Fwd: Memory error Message-ID: Jason Winnebeck wrote: > Maybe it does something silly like assume sizeof(int) = 4 bytes? I don't know, > on modern compilers was the decision made that int should become 8 bytes (64 > bits wide)? I know that size of pointers would have to change, but if it is > trying to do IO based on pointer sizes that would be really out there. > > Jason > > David Blaikie wrote: > > my mistake - ssphys has the problem... > > > > On Nov 30, 2007 4:15 PM, David Blaikie > > wrote: > > > > eek. This is the same error I was going to bring up next - the > > error I got when migrating a small database! Looks like I'm out of > > luck, then! > > > > Anyone have any idea why this should be so? Why should vss2svn have > > trouble on 64? > > > > David I actually ran into this problem a while ago and never remembered to post my solution. It's pretty much as you say--in SSTypes.h, unsigned longs are being used as members in some structs, breaking things, due to the assumption that they'll be 32-bits wide. I just changed the typedef for "ulong" at the top of the file to be an unsigned int, recompiled, and it worked fine. Erik