At 10:27 AM +0400 5/20/07, Ruslan Ermilov wrote:
It sometimes happens when the date/time are not being set properly, so that the tools are mistakenly rebuilt again at an inappropriate time when in the foreign environment of the target -- the problem is usually understood better when building for another CPU architecture and hitting it. I think this was an inappropriate commit to make, unless the problem can be reproduced. I have upgraded several i386's and amd64's without a problem.
Is there any way we could detect the clock-skew problem? This keeps coming up, year-after-year, for many different people, including very experienced developers. And when it does come up, it is either: (1) totally safe, and thus unnoticed, or (2) screws up someone in the middle of some major upgrade, thus causing great angst and gnashing of teeth. It would be nice if we could come up with a reliable check for the problem. -- Garance Alistair Drosehn = [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Institute; Troy, NY; USA _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "[EMAIL PROTECTED]"
