Re: git-p4 issue

[Vitor Antunes <vitor.hda@gmail.com>]

Hi Pete and Michael,

Pete Wyckoff <pw <at> padd.com> writes:

> 
> michael.horowitz <at> ieee.org wrote on Fri, 15 Apr 2011 16:39 -0400:
> > I am sure that is a common mistake people make, but not in this case.
> > I have been using it successfully for a while now, it just suddenly
> > stopped working, not sure what changed.  I am not seeing anything on
> > remotes/p4/master either, and I was originally doing rebase and went
> > back to sync so I could run "--verbose" and see if it was even
> > downloading those changes.  I can clearly see it says it is
> > downloading them, but then they just don't end up in git.

I've seen similar behavior when branch detection is enabled. Could it be that
the new changelists are not being imported because they are under a folder that
is not part of the path provided to git-p4 sync (or automatically detected by
it) during the original import? That would explain why --verbose shows the
changelists being downloaded but then they are not imported.

You said that if you clone the depot again you see the new changes. Could you
please confirm if "depot_paths" value is the same in git-log of both git repos?

> > Since I don't see an error message about it failing to sync, I am at a
> > loss to figure out why it says it succeeded, but it didn't.  Could
> > there be one step in the code that is not catching an error condition?
> >  I am not all that familiar with Python, but if someone could point me
> > where to put some debug messages, I can do some testing.
> 
> It would say something if it failed.  If git-p4 says it brought
> in changes, they would appear at the top of p4/master, or another
> branch in remotes/p4 if you use git-p4's auto-branch feature.
> 
> Do "git branch -av".  You should see remotes/p4/master with the
> latest p4 change.
> 
> It is possible to create a branch "p4/master" that is not
> remotes/p4/master and possibly cause confusion.  "tree -a
> .git/refs" to see all your branches.
> 
> You can try "git fsck" to see if something is terribly wrong.
> Or nose around .git, see if there are some recently-created
> objects and use "git cat-file -p" to look at them.
> 
> If you are willing to tar up your .git and leave it somewhere,
> I can take a look too.
> 
> 		-- Pete


Vitor