> the problem did not appear with the previously used versions, which
> were 1.0.49 and 1.0.56.
I just read the diff from 1.0.56 to 1.1.8, and I'm afraid that nothing
immediatedly leapt out.
I think that to make progress on this, I'd need either a recipe to
reproduce the error or a finer identification of the changeset that
caused the change in behaviour.
james anderson <email address hidden> writes:
> the problem did not appear with the previously used versions, which
> were 1.0.49 and 1.0.56.
I just read the diff from 1.0.56 to 1.1.8, and I'm afraid that nothing
immediatedly leapt out.
I think that to make progress on this, I'd need either a recipe to
reproduce the error or a finer identification of the changeset that
caused the change in behaviour.
Christophe