[p4] Strange sync issue

[Kris Kumler]

p4 sync showed the file(s) as up-to-date.
p4 sync -f brought the file to the head revision.

Reading your other post on shared-machine clients, I could see that as
the issue.
The interesting part there is that of the two machines that were sharing
that client, neither one was synced to the head revision and the issue
only showed itself on one of the machines.

Thanks for the help,
Kris

Weintraub, David wrote:
> What happens if you do a "p4 sync" outside of p4win? Does it update to
> the current revision or the previous one? Does doing a "p4 sync -f"
> update you to the most recent revision? 
> 
> -----Original Message-----
> From: perforce-user-bounces at perforce.com
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Kris Kumler
> Sent: Wednesday, June 07, 2006 2:14 PM
> To: perforce-user at perforce.com
> Subject: [p4] Strange sync issue
> 
> I am currently seeing a strange behavior on one of my development
> systems.  When using p4win, I will select my desired directory in the
> client view and sync to the head revision.
> The output shows no problems with the sync.  All files show that they
> are at the head revision.  However, for some files at least, the
> revision on disk is still the previous version (e.g. Head version is 18,
> and p4win shows having that file revision, but looking at the file on
> disk, even from within p4win using any editor, I see revision 17).
> 
> If I force sync to the head revision in p4win, it does update the files
> as expected.
> 
> Has anyone seen this issue?
> 
> Thanks,
> Kris
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user