Uploaded image for project: 'Subversion'
  1. Subversion
  2. SVN-1744

cvs2svn gives wrong >300 second commit warnings

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: all
    • Fix Version/s: cvs2svn-1.0
    • Component/s: tools
    • Labels:
      None

      Description

      From my mail to Mike just now:
      
      Have you noticed that we're getting "RESYNC" messages a lot more often than one
      would expect, and also we're seeing this warning
      
         Warning: commit spans more than 300 seconds
      
      a lot more often than we ought, too?
      
      Now we've got proof... I have a repository with one RCS file, a.txt, and here is
      *all* the revision metadata for that file:
      
         1.1
         date     2004.02.12.22.51.17;  author kfogel;  state Exp;
         branches 1.1.1.1;
         next     ;
         
         1.1.1.1
         date     2004.02.12.22.51.17;  author kfogel;  state Exp;
         branches ;
         next     ;
      
      Clearly, all that's ever happened to a.txt is that it got imported, right?  The
      timestamps are even completely the same.  Yet converting this repository gets
      the "commit spans more than 300 seconds" warning!
      
         $ cvs2svn.py --skip-cleanup --create -s svnrepos cvsrepos
         [...]
         ----- pass 1 -----
         cvsrepos/proj/a.txt,v
         RESYNC: 'proj/a.txt,v' (1.1) :        \
           old time='Thu Feb 12 16:51:17 2004' \
           new time='Thu Feb 12 16:51:16 2004'
         ----- pass 2 -----
         RESYNC: 'proj/a.txt,v' (1.1) :        \
           old time='Thu Feb 12 16:51:16 2004' \
           new time='Thu Feb 12 16:51:16 2004'
         ----- pass 3 -----
         ----- pass 4 -----
         creating repos 'svnrepos'
         committing: Sat Jan 10 07:37:04 2004, over 2884452 seconds
         Warning: commit spans more than 300 seconds
             adding or changing 1.1 : 'trunk/proj/a.txt'
             new revision: 1
         committing: Sat Jan 10 07:37:04 2004, over 2884453 seconds
         Warning: commit spans more than 300 seconds
         [...]
        $ 
      
      Now, that just *can't* be right.  How can a repository with only one file have
      any commits spanning more than 300 seconds? :-)
      

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              kfogel Karl Fogel
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: