1.8.0 r55286 error from port outdated

[Bryan Blackburn]

On Sun, Aug 09, 2009 at 04:21:08PM -0500, Ryan Schmidt said:
> 
> On Aug 8, 2009, at 23:17, Adam Mercer wrote:
> 
> >On Sat, Aug 8, 2009 at 21:41, Joshua Root wrote:
> >
> >>Looks like you have a port in one of your indices that has no version
> >>field. I'll commit a check to make action_outdated handle this error
> >>more gracefully.
> >
> >Thanks Josh, that wasn't the actual problem but the fix helped me find
> >it. Turns out the index of one of my local port trees was generated
> >using base 1.7.1 and 1.8.0 was choking on it. Updating the index using
> >1.8.0 and the problem goes away.
> 
> But surely the PortIndex we are distributing with our ports tree
> today is being generated by 1.7.1?

It's been generated by a version from trunk (don't know the precise rev) for
some time, otherwise we wouldn't see the PortIndex.quick updates as well.

Bryan