Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upWIP: Rebase omaha #25
Conversation
Corrected registry path for UpdateDev for 32-bit process usage
Trivial tyop fix.
Fixed Spelling.
Update DeveloperSetupGuide.md
Fixed markup.
DeveloperSetupGuide.md protobuf version required.
`NTDDI_VERSION` was defined in CPPDEFINES as `DNTDDI_VERSION`. The D prefix would be valid for CPPFLAGS, but not here.
Set WIN_VER to _WIN32_WINNT_WS03 (0x0502) Add missing _WIN32_WINNT define. This targets "Windows XP with Service Pack 2 (SP2)".
Define NTDDI_VERSION correctly
Merge pull request #145 from macqm/master
Use python 27
Update WINVER to Windows 7 value.
Notable changes here include adding support for unpacking CRX files, making "Code Red" more secure by wrapping the payload in a CRX container, and fixing a race condition where the /ua process may hang on shutdown during a program update.
Added libzip 1.3.0 and zlib 1.2.11 to third-party dependencies.
Update DeveloperSetupGuide.md
Set support.brave.com as a help url.
* Remove invalid third_party index and add .gitmodules * Create omaha target * Build stub/standalone installer with tagging
It turns out that enterprise module only needs admin priv. Brave doesn't used it. So it is excluded from build dir list.
Build all(release/debug) can take a long build time.
This is part of the work for issue: brave/brave-browser#2210
When silent tag is added in tag list, "/silent /install" is added to command line by metainstaller. silent tag should be added at last of tag list.
The download-complete/installer-run stats pings weren't being sent when the stub installer was run in admin mode. This was due to us storing the app guid in the registry, as it is written to a different location when running as an admin vs a regular user. Fixed this by fetching app guid from tag instead. In addition, we append the referral code to the tag sent to the installer in order to avoid the same problem with the registry.
We already use the Digicert timestamp server in brave builds but need to also update it here as that might not pass down.
* libzip 1.5.2 from https://libzip.org/download/libzip-1.5.2.tar.xz Unzip the contents of libzip-1.5.2.tar.gz\libzip-1.5.2.tar\libzip-1.5.2\ into the directory third_party\libzip * zlib 1.2.11 from https://zlib.net/zlib-1.2.11.tar.gz Unzip the contents of zlib-1.2.11.tar.gz\zlib-1.2.11.tar\zlib-1.2.11\ into the directory third_party\zlib\v1_2_11
|
Looks like there are a lot of conflicts, but I take it those won't be relevant if we're just going to make this the new master? cc: @mbacchi and @mihaiplesa, just FYI - but assuming you already know this is coming... |
|
I was not aware of this effort. I wonder if we need to coordinate this with the omaha-server rebase as we're behind there too, and have an open issue to rebase but no plan to do it in the near term: brave/devops#1092 |
|
@mbacchi |
Yes, it will not have any problem if this becomes master. |
How does that impact this PR? It seems like we would want to update either both (client and server) or neither, I think. |
|
@emerick yes, both side should be updated. So, this PR should be pended till we can start to debug together on updater client and server. |
simonhong commentedJul 18, 2019
•
edited
Fix brave/brave-browser#5186
I think this branch should become master after renaming current master.
Rebased branch can't be merged onto master.