[p4] updgrading from 2006.1 to 2007.3

[McKenna, Robert]

Perforce changed the binary repository file naming convention from
1.<revision>.gz to 1.<change #>.gz, where change number may be the
submitted change number or the original change number in the case of
submitting a numbered changelist. That could give you a problem if you
have any scripts that work directly with versioned files, such as a hot
backup.

Rob McKenna

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Looney, James B
(N-ULA)
Sent: Thursday, February 07, 2008 8:35 AM
To: Buster; perforce-user at perforce.com
Subject: Re: [p4] updgrading from 2006.1 to 2007.3


We're about to do something similar tonight.  2006.2 -> 2007.3.  But
I've already tried the update on a backup server to check things out and
had no issues.  If I come up with something, I'll let you know.

> -----Original Message-----
> From: perforce-user-bounces at perforce.com 
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Buster
> Sent: Thursday, February 07, 2008 7:56 AM
> To: perforce-user at perforce.com
> Subject: [p4] updgrading from 2006.1 to 2007.3
> 
> Hello,
> 
> I am starting a project to upgrade our p4d from 2006.1 to 2007.3 on a 
> FreeBSD server.  Anyone had any trouble with that?
> 
> Anything watch out for?
> 
> Thanks,
> 
> Andrew 
> _______________________________________________
> 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