24353 - Are Build IDs on CVS-pull builds out of date?

Status: VERIFIED WONTFIX

(SeaMonkey :: Build Config, defect, P3)

Description

[Sean Richardson]

It appears that in at least some circumstances a freshly-built-from-new-cvs-pull
browser will have an out-of-date Build ID, which does not help at all, for
a reader of a bug report. It would be nice to be able to rely on the
Build ID as an identifier no matter who built a binary, or where.

Quoting from bug 23336, "Double paste on single mouse click":
  >--- Additional Comments From [e-mail]  2000-01-19 03:48 ---
  >As I said, I did a COMPLETE rm -r, re-pull, and rebuild on Jan 10.  If CVS
  >was handing out December trees on Jan 10th, then that's what I got.  I also
  >did the same on Jan 14th, and it displayed the very same problem (as well as
  >a 1998* build-id).

It seems very unlikely that the entire tree was from December...more likely
that just the ID has gotten out of sync.

Comment 1

[Jon Granrose]

talking with leaf, the build date is only updated if you are doing an official
build.  to do that you need to set MOZ_BUILD_OFFICIAL=1 (I think that's the
variable, check the makefile).  I've cc'd leaf for any comments, but I don't
think we want to set the build id automatically for all builds.  For
non-official builds or really any builds, the most accurate way to describe the
build is by pull date/time.  Buildid only tells us when it was built, which
doesn't necessarily imply when the source tree was pulled which is what we
really need to know.

resolving wont fix.

Comment 2

[Markus Gerstel]

MOZILLA_OFFICIAL=1
BUILD_OFFICIAL=1

vfy