--disable-maintenance-service fails to build
Categories
(Toolkit :: Application Update, defect)
Tracking
()
People
(Reporter: alexboy94, Assigned: bytesized)
References
(Regression)
Details
(Keywords: regression, Whiteboard: [fidedi-ope])
Attachments
(2 files, 2 obsolete files)
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
2.06 KB,
patch
|
RyanVM
:
approval-mozilla-esr91+
|
Details | Diff | Splinter Review |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Firefox/91.0 Waterfox/91.0a1
Steps to reproduce:
Build mozilla-central with mingw-w64 or standard toolchain targetting Windows and ac_add_options --disable-maintenance-service.
Actual results:
toolkit/mozapps/update/updater/updater.cpp:3436:13: error: use of undeclared identifier 'IsSecureUpdateStatusSucceeded'
8:21.41 if (IsSecureUpdateStatusSucceeded(updateStatusSucceeded) &&
8:21.41 ^
8:21.41 1 error generated.
Expected results:
Build should complete.
It appears that IsSecureUpdateStatusSucceeded is only declared when MOZ_MAINTENANCE_SERVICE is, here.
in Bug 1658711, the guards wrapping the if block in MOZ_MAINTENANCE_SERVICE were removed.
| Reporter | ||
Updated•4 years ago
|
Updated•4 years ago
|
Comment 1•4 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Toolkit::Application Update' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Updated•4 years ago
|
Comment 2•4 years ago
|
||
Alex: I'd review a patch to wrap the block in MOZ_MAINTENANCE_SERVICE, if you want to supply one.
| Reporter | ||
Comment 3•4 years ago
|
||
Sorry, missed this! Yes, not a problem at all. Currently on holiday but will submit a patch when I’m back 👍
| Assignee | ||
Comment 4•4 years ago
|
||
Setting S4 severity because this is a build problem that does not affect any of our standard releases.
| Reporter | ||
Comment 5•4 years ago
|
||
(In reply to Nick Alexander :nalexander [he/him] from comment #2)
Alex: I'd review a patch to wrap the block in
MOZ_MAINTENANCE_SERVICE, if you want to supply one.
Here's the patch I've used (and haven't noticed any issues with so far).
| Assignee | ||
Updated•4 years ago
|
Comment 6•4 years ago
|
||
This was a regression from Bug 1658711.
Updated•4 years ago
|
Updated•4 years ago
|
Comment 7•4 years ago
|
||
Sorry for the long delay. I've submitted a modified version of this patch to Phab for review.
Comment 8•4 years ago
|
||
Set release status flags based on info from the regressing bug 1658711
Updated•4 years ago
|
Updated•4 years ago
|
| Assignee | ||
Updated•4 years ago
|
Updated•4 years ago
|
| Assignee | ||
Comment 9•4 years ago
|
||
I finally have a moment to take a look at this. It looks to me like the correct thing to do is to make the relevant functions available without MOZ_MAINTENANCE_SERVICE being defined rather than to remove the code using those functions. I should have a patch up shortly.
Updated•4 years ago
|
| Assignee | ||
Comment 10•4 years ago
|
||
Building without support for the maintenance service currently does not work because the definitions of EnvHasValue and IsSecureUpdateStatusSucceeded are ifdef'ed out despite being used. This patch fixes this by including those functions, even if compiling without support for the maintenance service.
Comment 11•4 years ago
|
||
Comment 12•4 years ago
|
||
| bugherder | ||
Comment 13•4 years ago
|
||
Is that something we would benefit from uplifting to beta or can I mark this bug as wontfix for 95?
Comment 14•4 years ago
|
||
(In reply to Pascal Chevrel:pascalc from comment #13)
Is that something we would benefit from uplifting to beta or can I mark this bug as wontfix for 95?
This is fallout from a change in Firefox 81, so I see no reason to uplift. Thanks for checking!
| Reporter | ||
Comment 15•4 years ago
|
||
Would it be possible to have this pulled in to ESR91 as well?
Comment 16•4 years ago
|
||
(In reply to Alex Kontos from comment #15)
Would it be possible to have this pulled in to ESR91 as well?
ESR91 makes more sense than uplift to Beta 94, IMO.
| Assignee | ||
Comment 17•4 years ago
|
||
(In reply to Alex Kontos from comment #15)
Would it be possible to have this pulled in to ESR91 as well?
Hmm. I've spent a little time thinking about this. The user impact seems low to non-existent, depending on how you quantify it. But the risk is also low to non-existent. I think it's reasonable to uplift to ESR.
| Assignee | ||
Comment 18•4 years ago
|
||
Comment on attachment 9248111 [details]
Bug 1728536 - Fix --disable-maintenance-service build capability r=nalexander!
ESR Uplift Approval Request
- If this is not a sec:{high,crit} bug, please state case for ESR consideration: This patch really doesn't affect Firefox users, because we don't build Firefox with this build flag. But not having the patch does make it more difficult for Firefox forks that use this build flag to incorporate upstream changes and build successfully.
- User impact if declined: Build bustage in certain non-default configurations.
- Fix Landed on Version: 96
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): This patch strictly changes
#ifdefs that determine what functions ought to be defined. The changes should only really be relevant when the--disable-maintenance-serviceflag is specified. So this patch should have no effect on official Mozilla builds, which do not use that flag. - String or UUID changes made by this patch: None
Updated•4 years ago
|
Comment 19•4 years ago
|
||
Comment on attachment 9248111 [details]
Bug 1728536 - Fix --disable-maintenance-service build capability r=nalexander!
NPOTB for Firefox, makes life easier for downstream distros. Approved for 91.4esr.
Comment 20•4 years ago
|
||
Comment on attachment 9248111 [details]
Bug 1728536 - Fix --disable-maintenance-service build capability r=nalexander!
Actually this needs rebasing for ESR91.
| Assignee | ||
Comment 21•4 years ago
|
||
ESR Uplift Approval Request
- If this is not a sec:{high,crit} bug, please state case for ESR consideration: This patch really doesn't affect Firefox users, because we don't build Firefox with this build flag. But not having the patch does make it more difficult for Firefox forks that use this build flag to incorporate upstream changes and build successfully.
- User impact if declined: Build bustage in certain non-default configurations.
- Fix Landed on Version: 96
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): This patch strictly changes
#ifdefs that determine what functions ought to be defined. The changes should only really be relevant when the--disable-maintenance-serviceflag is specified. So this patch should have no effect on official Mozilla builds, which do not use that flag. - String or UUID changes made by this patch: None
Comment 22•4 years ago
|
||
Comment on attachment 9250309 [details] [diff] [review]
esr91.patch
Approved for 91.4esr.
Comment 23•4 years ago
|
||
| bugherder uplift | ||
Comment 24•4 years ago
|
||
| bugherder uplift | ||
Description
•