[p4] Perforce 2006.1 - Time to upgrade?

Russell C. Jackson rusty at rcjacksonconsulting.com
Fri Jul 21 15:03:23 PDT 2006


Can you give an example of some of your mappings that it complained about?

Thanks,
Rusty


Karl Elvis MacRae wrote:
> I have to advise against upgrades to 2006.1 if you use any kind of complicated client/branch mappings. 
>
> There's a new feature (they call it a feature, I call it a bug - #89167). 
>
> The undesired effect here is that you can get a combination of a 'legal' client mapping and a 'legal' branch mapping that when combined, produce this error:
>
>     Excessive combinations of wildcard ... in path and maps.   
>
> I upgraded a test instance to 2006.1 after testing all my client mappings for illegal wildcards, and then started getting this error on integs (which I use a lot). 
>
> And per perforce support, there's no way to good way to go look for problems automatically. 
>
> If your client mappings are all simple, you may be ok. But IMO this change can cause a lot of trouble. The intent was good, but what they did was installed a 'fix' that brakes things that work in 2005*. 
>
>
> --Karl
>
>
>
> On Wed, Jul 19, 2006 at 12:35:43PM -0700, Ryan Dooley may have typed these words: 
>   
>>> Maybe this helps you with your upgrade decision:
>>> I just upgraded our test system (a full mirror of the real system) from
>>> 2005.2 to 2006.1. I went very well.
>>> I also did some real life integrations with the test server. Also no
>>> issues so far.
>>>
>>> Any other experiences with the new version?
>>>       
>> Same here... I upgraded our backup system last night to 2006.1 from 2005.1 and 
>> no problems.  After the "p4 verify" the actual upgrade was a breeze and I've not 
>> found any problems with it yet.
>>
>> I'll end up doing our actual primary box this week.
>>     
>
>
>   



More information about the perforce-user mailing list