Upgrade failure from 2.2.1 to 2.2.8

Derrick J Brashear shadow at dementia.org
Wed Sep 1 00:27:15 EDT 2004

On Tue, 31 Aug 2004, Ken Murchison wrote:

>> This is a 64 bit platform, I wonder if for some reason it's broken in that 
>> case. Though... I don't see it.
> Right.  I *believe* the changes in question are those between 2.2.1 and 2.2.3 
> (caching additional headers and making a hole for 64-bit quotas), but none of 
> those seem 32-bit specific.  I don't think any of the changes in 2.2.4 to 
> 2.2.8 would cause a problem.

One thing I did notice:
everything is a bit32 * except the bit where the old part of the record 
index record is copied, which is char *. But that shouldn't matter, 
because if pointers are 64 bit it should all be broken, and if not, it 
should all work.

But that's all I see.

Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

More information about the Info-cyrus mailing list