There seem to be quite a few failed CVS updates at the moment for some of the non-Apache repositories. As these (by definition, I suppose) are for dependencies relied on by other projects, these failures can have a big knock-on effect.
Would it be possible to treat CVS errors as non-fatal? This would have the same effect as if there had been no changes in CVS. The build should allowed to continue on that basis that it might depend on something else that _had_ changed. The problem would need to be flagged against the individual project. Other projects would still be able to be built against the latest "available" sources, for at least some sense of available. Just a thought. -- Sebastian Bazley --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
