Rob Siemborski wrote:
> On Thu, 28 Aug 2003, Michael Sims wrote:
>
>> Thanks for the quick response and the explanation. Do you think it
>> will be a problem if I continue to use the reconstruct binary from
>> 2.1.14 until the bug is fixed, or should I revert my entire
>> installation to 2.1.14? T
[EMAIL PROTECTED] wrote:
>>> Obviously this broke the case where the cyrus.header file doesn't
>>> exist, which I'm going to throw into bugzilla.
>
> Can you try 'touching' cyrus.{header,cache,index} files so they
> exist, have the correct permissions, but are empty? Older versions of
> reconstruct
> > Obviously this broke the case where the cyrus.header file doesn't
> > exist, which I'm going to throw into bugzilla.
Can you try 'touching' cyrus.{header,cache,index} files so they exist, have
the correct permissions, but are empty? Older versions of reconstruct seemed
to work ok in this case
Rob Siemborski wrote:
> On Thu, 28 Aug 2003, Michael Sims wrote:
>> Is the new version of reconstruct not able to rebuild the cyrus
>> metadata files? Or am I missing something obvious? Any assistance
>> would be very much appreciated...
>
> One of the assumptions that reconstruct is making (inde
