Chromium maintenance #213862
Labels
5. scope: tracking
Long-lived issue tracking long-term fixes or multiple sub-problems
Comments
|
The M110 (chromiumBeta) patch phase currently fails with the following error (easy to fix, we just need to adapt the build expressions to some upstream changes): |
primeos
added a commit
to primeos/nixpkgs
that referenced
this issue
Jan 31, 2023
Upstream dropped use_system_libwayland and related build arguments [0]. The deprecation is tracked in [1]. As a result, we must now build with third_party/wayland instead of wayland from the system (or complex patches would be required). This fixes [2]. [0]: https://source.chromium.org/chromium/chromium/src/+/1c3c8db518f78cb2d08a3990e5280e324c4a6e99 [1]: https://bugs.chromium.org/p/chromium/issues/detail?id=1385736 [2]: NixOS#213862 (comment)
|
TODOs for M110:
|
|
Next issue (expected / we already got this in the past when building with the bundled wayland): |
|
Have been trying to get it to work on a local build, and it seems the flag that would be necessary/an easy solution would be to make use of systemffi, as was added in this commit (v107): |
primeos
added a commit
to primeos/nixpkgs
that referenced
this issue
Feb 6, 2023
This change (dynamically linking against libffi from Nixpkgs) is required since we switched to third_party/wayland instead of linking against Wayland from Nixpkgs (26aadca). See also f9d9864 and d932886 for more details. We could alternatively provide libffi_pic.a for static linking but due to our immutable dependency model / pure builds the dynamic linking shouldn't cause any issues. This fixes the build error shown in [0]. [0]: NixOS#213862 (comment)
|
@DavidCromp yes, thanks :) We already discovered this issue and possible solutions in the past but I decided to stick with using Wayland from Nixpkgs back then. I already fixed it locally but forgot / didn't get around to submit the change. |
|
The build and VM test both pass now :) I also just start a build of M111 / chromeDev to see if there's more work left (which would be a good challenge for new/additional maintainers as there's enough time to fix those issues - unlike M110 which will be released tomorrow). |
primeos
added a commit
to primeos/nixpkgs
that referenced
this issue
Feb 7, 2023
Upstream dropped use_system_libwayland and related build arguments [0]. The deprecation is tracked in [1]. As a result, we must now build with third_party/wayland instead of wayland from the system (or complex patches would be required). This fixes [2]. [0]: https://source.chromium.org/chromium/chromium/src/+/1c3c8db518f78cb2d08a3990e5280e324c4a6e99 [1]: https://bugs.chromium.org/p/chromium/issues/detail?id=1385736 [2]: NixOS#213862 (comment) (cherry picked from commit 26aadca)
primeos
added a commit
to primeos/nixpkgs
that referenced
this issue
Feb 7, 2023
This change (dynamically linking against libffi from Nixpkgs) is required since we switched to third_party/wayland instead of linking against Wayland from Nixpkgs (26aadca). See also f9d9864 and d932886 for more details. We could alternatively provide libffi_pic.a for static linking but due to our immutable dependency model / pure builds the dynamic linking shouldn't cause any issues. This fixes the build error shown in [0]. [0]: NixOS#213862 (comment) (cherry picked from commit 06eb99f)
gador
pushed a commit
to gador/nixpkgs
that referenced
this issue
Feb 13, 2023
This change (dynamically linking against libffi from Nixpkgs) is required since we switched to third_party/wayland instead of linking against Wayland from Nixpkgs (26aadca). See also f9d9864 and d932886 for more details. We could alternatively provide libffi_pic.a for static linking but due to our immutable dependency model / pure builds the dynamic linking shouldn't cause any issues. This fixes the build error shown in [0]. [0]: NixOS#213862 (comment)
|
chromiumDev (113.0.5638) is broken again: Maybe LLVM 15 is already too "old" to build M113 but I haven't looked into it yet. |
This was referenced Mar 11, 2023
|
Compiler bug in LLVM <= 15. Requires LLVM 16 or higher (unreleased). See also llvm/llvm-project#48582. |
Nice. I have started a llvm16 branch (https://github.com/nixos/nixpkgs/tree/llvm16) that's still very wipy. |
|
Thanks a lot @RaitoBezarius and @lorenz! :) |
|
M114 seems to require |
|
But we do have libevdev in nixpkgs, right? |
primeos
added a commit
to primeos/nixpkgs
that referenced
this issue
May 10, 2023
The configuration phase was failing with "No package 'libevdev' found". See [0] for the full output. The build phase is still failing and we probably need to use a patch to avoid requiring a newer, unreleased LLVM version. [0]: NixOS#213862 (comment)
|
Yes, that issue is luckily trivial to fix but I expected additional issues so I didn't commit the fix right away. But I've included it in 5267a34 now. Anyway, unfortunately it's worse than I thought as it looks like the build scripts aren't compatible with LLVM 16 anymore and LLVM 17 definitely won't be out when M114 releases. I guess we'll have to patch the source code or rather build scripts (either by reverting the commit that introduced the problematic changes (preferred, if it's a dedicated commit) or by writing a custom patch. I'm getting the following error now: Does someone have the time and motivation to investigate? Maybe there's already an upstream "bug" report with useful information/discussion or patches from other packagers. |
|
We don't care about this flag, I'd personally just revert https://chromium-review.googlesource.com/c/chromium/src/+/4470209, which should be fairly self-contained and maintainable. But longer term I think we need to come to terms with the fact that Chromium pins their own LLVM toolchain which is close to master and does not guarantee compatibility with anything else (especially if it is older). Considering the amount of QA and other things they do to it it might make sense to just package their toolchain. |
|
I've sent a message to the distributions list to try to get a cross-distro perspective on this. |
primeos
added a commit
to primeos/nixpkgs
that referenced
this issue
May 30, 2023
This reverts a small commit [0] that adds the flag "-disable-auto-upgrade-debug-info" as it requires an unreleased LLVM version or the build will fail with the following error message: ``` ld.lld: error: -mllvm: ld.lld: Unknown command line argument '-disable-auto-upgrade-debug-info'. Try: '/nix/store/bx494s1r30zwa7zdsyg72sjryy0k0pyg-llvm-binutils-16.0.1/bin/ld.lld --help' ld.lld: Did you mean '--disable-auto-paired-vec-st'? clang++: error: linker command failed with exit code 1 (use -v to see invocation) ``` See [1] for a full example output. Thanks to Lorenz Brun for the analysis/help [2]. [0]: chromium/chromium@5496976 [1]: NixOS#213862 (comment) [2]: NixOS#213862 (comment)
12 tasks
primeos
added a commit
to primeos/nixpkgs
that referenced
this issue
May 31, 2023
This reverts a small commit [0] that adds the flag "-disable-auto-upgrade-debug-info" as it requires an unreleased LLVM version or the build will fail with the following error message: ``` ld.lld: error: -mllvm: ld.lld: Unknown command line argument '-disable-auto-upgrade-debug-info'. Try: '/nix/store/bx494s1r30zwa7zdsyg72sjryy0k0pyg-llvm-binutils-16.0.1/bin/ld.lld --help' ld.lld: Did you mean '--disable-auto-paired-vec-st'? clang++: error: linker command failed with exit code 1 (use -v to see invocation) ``` See [1] for a full example output. Thanks to Lorenz Brun for the analysis/help [2]. [0]: chromium/chromium@5496976 [1]: NixOS#213862 (comment) [2]: NixOS#213862 (comment) (cherry picked from commit 16f87c4)
primeos
added a commit
to primeos/nixpkgs
that referenced
this issue
May 31, 2023
The configuration phase was failing with "No package 'libevdev' found". See [0] for the full output. The build phase is still failing and we probably need to use a patch to avoid requiring a newer, unreleased LLVM version. [0]: NixOS#213862 (comment) (cherry picked from commit 5267a34)
primeos
added a commit
to primeos/nixpkgs
that referenced
this issue
May 31, 2023
This reverts a small commit [0] that adds the flag "-disable-auto-upgrade-debug-info" as it requires an unreleased LLVM version or the build will fail with the following error message: ``` ld.lld: error: -mllvm: ld.lld: Unknown command line argument '-disable-auto-upgrade-debug-info'. Try: '/nix/store/bx494s1r30zwa7zdsyg72sjryy0k0pyg-llvm-binutils-16.0.1/bin/ld.lld --help' ld.lld: Did you mean '--disable-auto-paired-vec-st'? clang++: error: linker command failed with exit code 1 (use -v to see invocation) ``` See [1] for a full example output. Thanks to Lorenz Brun for the analysis/help [2]. [0]: chromium/chromium@5496976 [1]: NixOS#213862 (comment) [2]: NixOS#213862 (comment) (cherry picked from commit 16f87c4)
qjoly
added a commit
to qjoly/nixpkgs
that referenced
this issue
Jun 1, 2023
terraform-providers.infoblox: 2.3.0 -> 2.4.0 terraform-providers.pagerduty: 2.14.5 -> 2.14.6 terraform-providers.scaleway: 2.19.0 -> 2.20.0 build(deps): bump cachix/install-nix-action from 20 to 21 Bumps [cachix/install-nix-action](https://github.com/cachix/install-nix-action) from 20 to 21. - [Release notes](https://github.com/cachix/install-nix-action/releases) - [Commits](cachix/install-nix-action@v20...v21) --- updated-dependencies: - dependency-name: cachix/install-nix-action dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]> powershell: drop openssl_1_1 zinit: 3.7 -> 3.11.0 picard: Fix inputs Add qt5.qtwayland - for the wrapper. Put most qt5 inputs in `buildInputs` - not `nativeBuildInputs`. Remove `fetchpatch` unused argument. prom2json: 1.3.2 -> 1.3.3 httplib: 0.12.3 -> 0.12.4 credhub-cli: 2.9.15 -> 2.9.16 rust-analyzer-unwrapped: 2023-05-22 -> 2023-05-29 goflow2: 1.3.3 -> 1.3.4 webhook: 2.8.0 -> 2.8.1 vtm: 0.9.9k -> 0.9.9l linux_xanmod: 6.1.29 -> 6.1.30 pdal: 2.4.3 -> 2.5.4 powershell: 7.3.2 -> 7.3.4 cloudflared: 2023.5.0 -> 2023.5.1 pqrs: 0.2.2 -> 0.3.1 signalbackup-tools: 20230523 -> 20230528-1 clickhouse-backup: 2.2.6 -> 2.2.7 amazon-ecr-credential-helper: 0.7.0 -> 0.7.1 flacon: 11.0.0 -> 11.1.0 plumed: 2.8.2 -> 2.9.0 limitcpu: 2.9 -> 3.0 frp: 0.48.0 -> 0.49.0 minio-client: 2023-05-18T16-59-00Z -> 2023-05-26T23-31-54Z netbird-ui: 0.20.3 -> 0.20.5 dagger: 0.5.3 -> 0.6.0 re-flex: 3.3.2 -> 3.3.3 pacparser: 1.4.1 -> 1.4.2 clj-kondo: 2023.05.18 -> 2023.05.26 flrig: 1.4.8 -> 2.0.0 router: 1.18.1 -> 1.19.0 theforceengine: 1.09.100 -> 1.09.200 lhasa: 0.3.1 -> 0.4.0 guile-opengl: 0.1.0 -> 0.2.0 shotman: 0.4.1 -> 0.4.3 pleroma: 2.5.1 -> 2.5.2 Security update, fixes a critical bug in the media proxy. The crypt dependency was removed, dropping the libxcrypt-legacy workaround \0/. Full changelog there: https://git.pleroma.social/pleroma/pleroma/-/releases/v2.5.2 buildGoModule: format Co-authored-by: Yueh-Shun Li <[email protected]> memcached: 1.6.19 -> 1.6.20 krill: 0.12.3 -> 0.13.0 calico-pod2daemon: 3.25.1 -> 3.26.0 python311Packages.django-rest-registration: 0.7.3 -> 0.8.2 buildkite-agent: 3.46.1 -> 3.47.0 invidious: unstable-2023-05-08 -> 2023-05-25 eksctl: 0.142.0 -> 0.143.0 python310Packages.azure-containerregistry: 1.0.0 -> 1.1.0 python310Packages.azure-containerregistry: update disabled - add format - add missing input prometheus-node-exporter: 1.5.0 -> 1.6.0 prometheus-pushgateway: 1.5.1 -> 1.6.0 supabase-cli: 1.64.2 -> 1.64.8 gopsuinfo: 0.1.3 -> 0.1.4 clamav: 1.0.1 -> 1.1.0 keama: init at 4.4.3-P1 rathole: 0.4.7 -> 0.4.8 rl-2305: alpha version for 23.05 This is an alpha version worked out by the release managers. Co-Authored-By: Martin Weinelt <[email protected]> doc: clarify that meta.timeout is only for Hydra I read this and expected it to be a timeout that was always applied when building the derivation, but it's actually a Hydra-specific thing. python3.pkgs.glean-sdk: unvendor lmdb asnmap: 1.0.3 -> 1.0.4 gpg-tui: 0.9.5 -> 0.9.6 catnip: init at 1.8.0 https://github.com/noriah/catnip ddnet: 17.0 -> 17.0.1 https://ddnet.org/downloads/#17.0.1 ddnet: 17.0.1 -> 17.0.2 https://ddnet.org/downloads/#17.0.2 lightning-loop: 0.23.0-beta -> 0.24.1-beta mongodb-compass: 1.36.4 -> 1.37.0 maddy: 0.6.3 -> 0.7.0 Diff: foxcpp/maddy@v0.6.3...v0.7.0 nixos/maddy: change secrets option to accept a list of paths flirc: lock readline to 6.x version as required libreoffice-still: 7.4.6.2 -> 7.4.7.2 libreoffice-fresh: 7.5.2.2 -> 7.5.4.1 snagboot: init at 1.0 Signed-off-by: Otavio Salvador <[email protected]> nixos/vmalert: init xfce.xfce4-session: 4.18.2 -> 4.18.3 https://gitlab.xfce.org/xfce/xfce4-session/-/compare/xfce4-session-4.18.2...xfce4-session-4.18.3 grype: 0.62.1 -> 0.62.2 Diff: anchore/grype@refs/tags/v0.62.1...v0.62.2 Changelog: https://github.com/anchore/grype/releases/tag/v0.62.2 flyctl: 0.1.18 -> 0.1.20 python3Packages.langchain: 0.0.183 -> 0.0.184 Diff: langchain-ai/langchain@refs/tags/v0.0.183...v0.0.184 Changelog: https://github.com/hwchase17/langchain/releases/tag/v0.0.184 ockam: 0.87.0 -> 0.88.0 openssl_1_1: 1.1.1t -> 1.1.1u https://github.com/openssl/openssl/blob/OpenSSL_1_1_1u/NEWS Fixes: CVE-2023-2650, CVE-2023-0466, CVE-2023-0465, CVE-2023-0464 maintainers: add flemzord moon: init at v1.5.1 oxidized: 0.26.3 -> 0.29.1 (NixOS#234001) This commit updates oxidized, fixes the oxidized-script executable and removes the non existing oxidized-web executable (oxidized-web is just a library for oxidized and does not provide a executable). python310Packages.pydyf: 0.5.0 -> 0.6.0 python310Packages.weasyprint: 58.1 -> 59.0 vencord: 1.1.6 -> 1.2.5 denaro: 2023.2.2 -> 2023.5.0; add updateScript python311Packages.pyzipper: init at 0.3.6 python311Packages.xknxproject: init at 3.1.0 python311Packages.aioairzone-cloud: init at 0.1.6 bun: 0.6.3 -> 0.6.5 nixVersions.nix_2_15: 2.15.0 -> 2.15.1 hyprwm: update packages hyprland: 0.25.0 -> 0.26.0 hyprpaper: 0.2.0 -> 0.4.0 hyprpicker: 0.1.0 -> 0.1.1 xdg-desktop-portal-hyprland: 0.3.1 -> 0.4.0 python311Packages.dvc-data: 0.52.0 -> 0.53.0 Diff: iterative/dvc-data@refs/tags/0.52.0...0.53.0 Changelog: https://github.com/iterative/dvc-data/releases/tag/0.53.0 cameradar: Mark as broken qmidiarp: 0.6.7 -> 0.7.0 erdtree: 3.0.0 -> 3.0.1 Diff: solidiquis/erdtree@v3.0.0...v3.0.1 Changelog: https://github.com/solidiquis/erdtree/releases/tag/v3.0.1 haruna: 0.10.3 -> 0.11.0 python3Packages.mautrix: 0.19.14 -> 0.19.16 Diff: mautrix/python@refs/tags/v0.19.14...v0.19.16 Changelog: https://github.com/mautrix/python/releases/tag/v0.19.16 mautrix-telegram: 0.13.0 -> 0.14.0 Diff: mautrix/telegram@refs/tags/v0.13.0...v0.14.0 python311Packages.meshtastic: 2.1.6 -> 2.1.7 Diff: meshtastic/python@refs/tags/2.1.6...2.1.7 Changelog: https://github.com/meshtastic/python/releases/tag/2.1.7 python311Packages.aliyun-python-sdk-kms: 2.16.0 -> 2.16.1 Changelog: https://github.com/aliyun/aliyun-openapi-python-sdk/blob/master/aliyun-python-sdk-kms/ChangeLog.txt python311Packages.types-requests: 2.31.0.0 -> 2.31.0.1 chromiumBeta: 114.0.5735.35 -> 114.0.5735.45 chromiumDev: 115.0.5773.4 -> 115.0.5790.3 runme: 1.2.1 -> 1.2.2 Diff: stateful/runme@v1.2.1...v1.2.2 Changelog: https://github.com/stateful/runme/releases/tag/vv1.2.2 linux: 4.14.315 -> 4.14.316 linux: 4.19.283 -> 4.19.284 linux: 5.10.180 -> 5.10.181 linux: 5.15.113 -> 5.15.114 linux: 5.4.243 -> 5.4.244 linux: 6.1.30 -> 6.1.31 linux: 6.3.4 -> 6.3.5 linux-rt_5_15: 5.15.111-rt63 -> 5.15.113-rt64 linux_latest-libre: 19299 -> 19308 linux/hardened/patches/4.14: 4.14.314-hardened1 -> 4.14.315-hardened1 linux/hardened/patches/4.19: 4.19.282-hardened1 -> 4.19.283-hardened1 linux/hardened/patches/5.10: 5.10.179-hardened1 -> 5.10.180-hardened1 linux/hardened/patches/5.15: 5.15.111-hardened1 -> 5.15.112-hardened1 linux/hardened/patches/5.4: 5.4.242-hardened1 -> 5.4.243-hardened1 linux/hardened/patches/6.1: 6.1.28-hardened1 -> 6.1.29-hardened1 rbdoom-3-bfg: 1.5.0 -> 1.5.1 python311Packages.tplink-omada-client: 1.2.5 -> 1.3.0 Changelog: https://github.com/MarkGodwin/tplink-omada-api/releases/tag/release%2Fv1.3.0 python310Packages.types-deprecated: init at 1.2.9.2 python311Packages.pyquil: 3.5.0 -> 3.5.2 Diff: rigetti/pyquil@refs/tags/v3.5.0...v3.5.2 Changelog: https://github.com/rigetti/pyquil/blob/v3.5.2/CHANGELOG.md python311Packages.intake-parquet: 0.2.3 -> 0.3.0 Diff: intake/intake-parquet@0.2.3...0.3.0 python310Packages.intake: 0.6.8 -> 0.7.0 Diff: intake/intake@refs/tags/0.6.8...0.7.0 Changelog: https://github.com/intake/intake/blob/0.7.0/docs/source/changelog.rst python311Packages.peaqevcore: 15.3.1 -> 18.0.6 Changelog: https://github.com/elden1337/peaqev-core/releases/tag/18.0.6 bearer: fix version bearer: add version test httpdump: 20210126-d2e0dea -> unstable-2023-05-07 python311Packages.python-roborock: 0.18.6 -> 0.18.9 Diff: Python-roborock/python-roborock@refs/tags/v0.18.6...v0.18.9 Changelog: https://github.com/humbertogontijo/python-roborock/blob/v0.18.9/CHANGELOG.md python311Packages.python-roborock: add input for darwin python311Packages.zeroconf: 0.62.0 -> 0.63.0 Diff: python-zeroconf/python-zeroconf@refs/tags/0.62.0...0.63.0 Changelog: https://github.com/python-zeroconf/python-zeroconf/releases/tag/0.63.0 python311Packages.sentry-sdk: 1.21.1 -> 1.24.0 Diff: getsentry/sentry-python@refs/tags/1.21.1...1.24.0 Changelog: https://github.com/getsentry/sentry-python/blob/1.24.0/CHANGELOG.md laminar: 1.2 → 1.3 gh: 2.29.0 -> 2.30.0 Diff: cli/cli@v2.29.0...v2.30.0 Changelog: https://github.com/cli/cli/releases/tag/v2.30.0 chromiumBeta: Fix the build with LLVM 16 by reverting a commit This reverts a small commit [0] that adds the flag "-disable-auto-upgrade-debug-info" as it requires an unreleased LLVM version or the build will fail with the following error message: ``` ld.lld: error: -mllvm: ld.lld: Unknown command line argument '-disable-auto-upgrade-debug-info'. Try: '/nix/store/bx494s1r30zwa7zdsyg72sjryy0k0pyg-llvm-binutils-16.0.1/bin/ld.lld --help' ld.lld: Did you mean '--disable-auto-paired-vec-st'? clang++: error: linker command failed with exit code 1 (use -v to see invocation) ``` See [1] for a full example output. Thanks to Lorenz Brun for the analysis/help [2]. [0]: chromium/chromium@5496976 [1]: NixOS#213862 (comment) [2]: NixOS#213862 (comment) automatic-timezoned: 1.0.92 -> 1.0.93 python311Packages.aioesphomeapi: 13.7.5 -> 13.9.0 Diff: esphome/aioesphomeapi@refs/tags/v13.7.5...v13.9.0 Changelog: https://github.com/esphome/aioesphomeapi/releases/tag/v13.9.0 checkov: 2.3.261 -> 2.3.264 Diff: bridgecrewio/checkov@refs/tags/2.3.261...2.3.264 Changelog: https://github.com/bridgecrewio/checkov/releases/tag/2.3.264 jackett: 0.21.34 -> 0.21.88 helix: switch back to release tarball erlang_odbc_javac: 25.3.2 -> 25.3.2.1 yuzu: mainline 1437 -> 1452, early access 3596 -> 3621 rustypaste: 0.9.1 -> 0.10.0 Diff: orhun/rustypaste@v0.9.1...v0.10.0 Changelog: https://github.com/orhun/rustypaste/blob/v0.10.0/CHANGELOG.md dontgo403: 0.9.1 -> 0.9.3 libcyaml: 1.4.0 -> 1.4.1 shell_gpt: 0.9.0 -> 0.9.1 ledger-live-desktop: 2.58.0->2.60.0 ledger-live-desktop: 2.58.0->2.60.0 ocamlPackages.ocplib-endian: fix for OCaml 5.0 ocamlPackages.lwt: fix for OCaml 5.0 ocamlPackages.iter: 1.6 → 1.7 alt-ergo: 2.4.2 → 2.4.3 terraform-providers.akamai: 3.6.0 -> 4.0.0 terraform-providers.cloudflare: 4.6.0 -> 4.7.0 terraform-providers.google: 4.66.0 -> 4.67.0 terraform-providers.google-beta: 4.66.0 -> 4.67.0 terraform-providers.newrelic: 3.23.0 -> 3.24.0 terraform-providers.pagerduty: 2.14.6 -> 2.15.0 terraform-providers.snowflake: 0.64.0 -> 0.65.0 ruby: fix typo cocoapods: 1.12.0 -> 1.12.1 Updated using pkgs/development/tools/cocoapods/update python310Packages.openstacksdk: 1.1.0 -> 1.2.0 python3Packages.edk2-pytool-library: 0.15.0 -> 0.15.1 Diff: tianocore/edk2-pytool-library@v0.15.0...v0.15.1 Changelog: https://github.com/tianocore/edk2-pytool-library/releases/tag/v0.15.1 python310Packages.archinfo: 9.2.52 -> 9.2.53 python310Packages.ailment: 9.2.52 -> 9.2.53 python310Packages.pyvex: 9.2.52 -> 9.2.53 python310Packages.claripy: 9.2.52 -> 9.2.53 python310Packages.cle: 9.2.52 -> 9.2.53 python310Packages.angr: 9.2.52 -> 9.2.53 python311Packages.asysocks: 0.2.5 -> 0.2.7 Changelog: https://github.com/skelsec/asysocks/releases/tag/0.2.7 python311Packages.minikerberos: 0.4.0 -> 0.4.1 Changelog: https://github.com/skelsec/minikerberos/releases/tag/0.4.1 python311Packages.asyauth: 0.0.13 -> 0.0.14 Changelog: https://github.com/skelsec/asyauth/releases/tag/0.0.14 python311Packages.aiosmb: 0.4.4 -> 0.4.6 Changelog: https://github.com/skelsec/aiosmb/releases/tag/0.4.6 python311Packages.aiowinreg: 0.0.9 -> 0.0.10 Diff: skelsec/aiowinreg@refs/tags/0.0.9...0.0.10 Changelog: https://github.com/skelsec/aiowinreg/releases/tag/0.0.10 python311Packages.msldap: 0.4.7 -> 0.5.5 Changelog: https://github.com/skelsec/msldap/releases/tag/0.5.5 python311Packages.aesedb: 0.1.3 -> 0.1.4 Diff: skelsec/aesedb@refs/tags/0.1.3...0.1.4 Changelog: https://github.com/skelsec/aesedb/releases/tag/0.1.4 python311Packages.pypykatz: 0.6.6 -> 0.6.8 Changelog: https://github.com/skelsec/pypykatz/releases/tag/0.6.8 sleek: init at 0.3.0 blueberry: add missing libnotify ref: NixOS#234833 postgresql11JitPackages.pgroonga: 3.0.1 -> 3.0.3 postgresqlPackages.pgroonga: 3.0.3 -> 3.0.5 https://github.com/pgroonga/pgroonga/releases/tag/3.0.5 postgresqlPackages.pgroonga: add changelog to meta python310Packages.tubeup: 28.5.2023 -> 2023.5.29 Changelog: https://github.com/bibanon/tubeup/releases/tag/2023.5.29 python310Packages.ibm-cloud-sdk-core: 3.16.5 -> 3.16.6
|
It seems like M115 introduces some initial Rust support (https://security.googleblog.com/2023/01/supporting-use-of-rust-in-chromium.html, https://bugs.chromium.org/p/chromium/issues/detail?id=1292038): This could be quite challenging for Nixpkgs - depending on how well Google handles it (since scripts like Does someone have time and motivation to look into this? @lorenz huge thanks for your analysis in #213862 (comment) btw. I've credited you in primeos@16f87c4 - hope that's fine (I can also add you as co-author next time, if you want - alternatively you can of course also make a PR next time 😉). |
|
I read the new GN specs and plumbed in the nixpkgs Rust compiler. From a look at Chromium's upstream packaging they do not use a patched Rust, so this should be fine (as fine as not using their bespoke LLVM is). Build is still running, but didn't fail during GN phase. I'll send a PR once it finished building. |
|
115 built successfully, I'll submit a patch this evening or tomorrow. |
|
I'm debugging the build of electron 28 / chromium 120.x currently. One of the patches no longer applies. |
|
patch for building chromium 120 with llvm 16 is in #271677, please review (built a chromium 120 beta on x86_64-linux and electron 28 on aarch64-linux) |
tomodachi94
added
the
5. scope: tracking
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Just an experiment / meta issue to track Chromium build failures, for coordination, etc (it'll be a bit noisy).
Chromium-specific documentation: https://github.com/NixOS/nixpkgs/blob/master/pkgs/applications/networking/browsers/chromium/README.md
cc #197609
The text was updated successfully, but these errors were encountered: