1.) broken timestamps:
see http://www.pumacode.org/projects/vss2svn/ticket/5
2.) destroyed projects
see http://www.pumacode.org/projects/vss2svn/ticket/36
___
vss2svn-users mailing list
Project homepage:
http://www.pumacode.org/projects/vss2svn/
Currently I can see two problems with your database:
1.) broken timestamps:
This will result in the addition of files out of order. Since we will
add files to projects that weren't created yet, we do not have a correct
name and therefor we will fail adding the file, e.g. see the first actions:
Sorry, yes, I did try this and it failed as the following:
* adding path : VR/VR inc/com_intel.h ...svnadmin: File not found:
revision 1822, path '/Ecis/inc/com_intel.h'
The file com_intel.h exists in other locations in the repository, but not in
the specified location at the specified time.
The only thing that I'd really like to retain are the labels, which is why
it would be great to get the ssphys.exe version of vss2svn working. I was
looking at the ss.exe-based version however, and I could easily modify that
script to mimic the current status of the archive and generate the lab
ace the '/' with another valid character). Just a thought. :-)
Tbanks again for all of your assistance with this. I really appreciate it.
jward.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dirk
Sent: Tuesday, June 06, 2006 4:03 AM
To: Vs
I do know, however (as you probably do as well), that Visual SourceSafe can
easily be affected if the date / time of the client PCs is not correct at
the time of a particular action. So, if they made changes to the DB and the
client PC had an incorrect date, then you've effectively made a mess
essage-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dirk
Sent: Monday, June 05, 2006 8:21 PM
To: Vss2Svn Users
Subject: Re: pin_handler: another file history issue
> ACBA shows the same problem, while YBBA seems to be ok.
>
> We need to push it a little furthe
ACBA shows the same problem, while YBBA seems to be ok.
We need to push it a little further, can you look at BCBA,
CCBA, ...?
Or can you send me your PhysicalAction.txt in a private mail?
It seems that you have a lot of broken timestamps in your archive. It is
not only a s
onday, June 05, 2006 7:29 PM
To: Vss2Svn Users
Subject: Re: pin_handler: another file history issue
I havn't tested the new 2006. So I don't know. I would use what comes
with the database you have, and I expect that this is 2005
Dirk
[EMAIL PROTECTED] schrieb:
> My IT department wa
ich I use to analyze the DB?
jward.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dirk
Sent: Monday, June 05, 2006 7:00 PM
To: Vss2Svn Users
Subject: Re: pin_handler: another file history issue
What kind of information would you require t
Vss2Svn Users
Subject: Re: pin_handler: another file history issue
> What kind of information would you require to help track down this
problem?
>
Have you tried to run analyze? Probably this will solve the error by
destroying all orphaned files ;-)
Dirk
__
What kind of information would you require to help track down this problem?
Have you tried to run analyze? Probably this will solve the error by
destroying all orphaned files ;-)
Dirk
___
vss2svn-users mailing list
Project homepage:
http://www.pu
Now the interesting part:
ZBBA is the source of all and was created on 881667180. But it was
added to the KIAA at 850977216, actually before it's creation???
Strange, ...
Can you give me a grep for KIAA in PhysicalAction.txt? Or the result
of "ssphys info data/k/kiaa"?
Di
Ok, let' try it:
ZBBA ist the source of all activities. It was created at the
timestamp "881667180" and had 23 modifications. Later it was branched
into CBCA and DBCA
CBCA again had 3 more commits.
DBCA had also a few more commits, and was shared into the projects
/ * /Ec
I expect this is the same problem that Dukhat reported just a 3 hours
before your message. But in order to help it is always good to do the
following:
1.) look into your partially generated repository and see whether you
can find the problematic file anywhere. Esp in your case look into the
l
I'm currently trying to do a VSS -> Subversion conversion, and because of
that, I've been watching the pin_handler version over the past couple and
the rapid progress that is being made on this branch of vss2svn. With each
iteration, I'm getting a bit closer to being able to fully import my
databas
16 matches
Mail list logo
