Piotr Jasiukajtis <estseg at gmail.com> writes: > On Wed, Jul 1, 2009 at 9:55 PM, James Carlson<carlsonj at workingcode.com> > wrote: >> John Beck wrote: >>> >>> Yes. ?That means that a file is found in the proto area but is not found >>> in any package prototype. ?The two common reasons for hitting this are: >>> 1. You are adding a new file and forgot to update packaging. ?The fix >>> ? for this is to update your packaging. >>> 2. A file was deleted and you did an incremental build and your proto >>> ? area still has it. ?The fixes for this are either do a clobber build >>> ? or manually delete each such file from your proto area. >>> >>> These all look familiar as recent instances of case #2. >> >> A third common reason is using closed binaries that are out of sync (either >> too new or too old) compared to the sources in use. ?I agree with jbeck that >> this is probably #2, but the third does happen sometimes. > I am pretty sure it's #3 in my case but I was wondering why it takes > so long to update the closed bins.
It looks like something went wrong, or was changed without announcement. The nightly closed bins I just downloaded are timestamped June 10th, so it seems clear something went very wrong. The current/ directory looks no better. The nightly-bins should be updated nightly, the current/ directory (I believe) weekly, and the build directory as the builds are delivered to RE. Any deviation from this is, I think, a bug. The current situation seems pretty clearly a bug. -- Rich
