This should make it a little bit easier to read. The (native) build
inputs and options now have a consistent order, defaultDependencies and
yasm aren't required anymore, and this adds some brief comments.
Note: The third_party/node/linux/node-linux-x64/bin/node change causes
rebuilds.
(cherry picked from commit 4a5b36725919c002751228515d518f23772f988e)
Note: I've only tested this with llvmPackages_git but it should work
with llvmPackages_13 as well.
fieldtrial_testing_like_official_build was renamed to
disable_fieldtrial_testing_config:
https://github.com/chromium/chromium/commit/486e9d58c0980be0d50054064e0b7d79446de071
(cherry picked from commit 1e372f40047912013568d731208655bd9dab526c)
https://gitlab.com/gitlab-org/gitaly/-/commit/e7f8fe4f6759669c24b2fd216beaab4a477c5b3d
changed the binary name to always end with its module version. This
makes sure gitaly's internal version references are set to the package
version and renames the binary, postfixing it with the package
version.
(cherry picked from commit d14e9188d1cd88f1b530bf860638c2de27486a6d)
This doesn't cause any rebuilds because we use a set but should make it
a bit easier to understand what's going on. This also moves two flags
that where incorrectly in "optionalAttrs pulseSupport" (enabled by
default) out of there.
The native client deprecation is stated here:
https://developer.chrome.com/docs/native-client/
(cherry picked from commit 555c3afaf2b17af6ad06ae82b545ca06e252bcd1)
Our system FFmpeg version is too outdated and Snappy causes a linking
failure (I didn't have time to investigate yet). Hopefully we can revert
this before the stable release of M93.
(cherry picked from commit bd22d2425cb7f14b1f98f7432e6ad38208609adb)
This wasn't done in 97570d30c7f to allow reusing chromiumBeta builds
(without having to perform any changes) in the meantime.
(cherry picked from commit 9ac31885527059cfc150343e576216e712408d1b)
I'm having trouble building bluez on a CentOS 7.9 builder.
Turns out that the test-mesh-crypto test depends on the following Linux
kernel configuration items:
CONFIG_CRYPTO_[USER|USER_API|USER_API_AEAD|USER_API_HASH|AES|CCM|AEAD|CMAC]
and will fail if run wih an incompatible kernel with the following error
message:
...
IVindex = 12345678
NetworkNonce = 00800000011201000012345678
00800000011201000012345678 => PASS
PrivacyRandom = 000000000012345678b5e5bfdacbaf6c
000000000012345678fffd034b50057e => FAIL
FAIL unit/test-mesh-crypto (exit status: 1)
I found the same bug reported on Gentoo https://bugs.gentoo.org/704190.
Their fix is to only run the test if the kernel options are available,
which we don't want to do for build reproducibility.
Instead we just want to skip the test unconditionally. As it's simpler
to completely override the test instead of patching the build system, we
opt for doing just that.
(cherry picked from commit 05c517698dcf6a989e364863cf5e7f6f548dd50a)
Michael Weiss