Closed
Bug 362514
Opened 18 years ago
Closed 18 years ago
"official build" detection code doesn't work, treats all builds as "official"
Categories
(Toolkit :: Safe Browsing, defect)
Toolkit
Safe Browsing
Tracking
()
RESOLVED
FIXED
People
(Reporter: Gavin, Assigned: Gavin)
References
Details
Attachments
(1 file)
890 bytes,
patch
|
benjamin
:
review+
|
Details | Diff | Splinter Review |
The code added in bug 344897 to use different URLs/IDs for "official" builds doesn't actually work, at least not on my Windows build. "$(origin BUILD_OFFICIAL)_$(origin MOZILLA_OFFICIAL)" is always "file_file", regardless of whether the build had MOZILLA_OFFICIAL or BUILD_OFFICIAL defined. I'm guessing this is because it's unconditionally set at http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/config/autoconf.mk.in&rev=3.413#544 . This has the result of treating all builds as "official".
Comment 1•18 years ago
|
||
Why are we using $(origin) instead of just testing MOZILLA_OFFICIAL?
Assignee | ||
Comment 2•18 years ago
|
||
This is the same code I used for bug 362460.
Updated•18 years ago
|
Attachment #247199 -
Flags: review?(benjamin) → review+
Assignee | ||
Comment 3•18 years ago
|
||
mozilla/browser/components/safebrowsing/Makefile.in 1.6
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Comment 4•18 years ago
|
||
I had heard a report of this, but it was never confirmed. I just stole this code from http://lxr.mozilla.org/mozilla1.8/source/config/Makefile.in#161, since this was originally written on the 1.8 branch; is this method of build officialness detection no longer valid on the trunk, or was it never valid anywhere?
Assignee | ||
Comment 5•18 years ago
|
||
(In reply to comment #4) > I just stole this code from > http://lxr.mozilla.org/mozilla1.8/source/config/Makefile.in#161, since this was > originally written on the 1.8 branch; is this method of build officialness > detection no longer valid on the trunk, or was it never valid anywhere? It looks like it was always broken, but that it didn't matter until the first patch from bug 324690 landed. The second patch from bug 324690 made exactly the same change as the patch from this bug to fix it.
Updated•10 years ago
|
Product: Firefox → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•