New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chromium: 61.0.3163.100 -> 62.0.3202.62 #30603
Conversation
See also #30562. It does not remove the patches though. |
@jtojnar that one fails because it doesn't remove them (there's a warning about unneeded patches). And doesn't seem to follow contribution guidelines. |
Ok, it seems not everything builds fine now... |
@YorikSar if you have a build failure, I recommend retrying with the updated ( If you could also compare and update the patches for I'll try the builds later, when at home. thanks |
@bendlas Thanks, yes, that's my thinking. I'm currently verifying Stable/Beta versions, it takes quite some time to build on my laptop, but so far it seems to be compiling everything just fine. That said, why are you referring to r3 version of that patch? I thought about using r4 instead. And, surely, I'll pull along all the latest patches from Gentoo repo. |
@YorikSar when looking at the |
@bendlas, oh, right. For version 62 everything builds fine with r2 version. It's 63 (dev) version that seems to be tricky. |
a388c63
to
bf6d9f3
Compare
I've uploaded new version of the commit. Dev version still won't build, it raises these error:
I guess I'll need to investigate further. |
Found a bug in Gentoo about this: https://bugs.gentoo.org/633452, leading to this change: https://chromium-review.googlesource.com/c/chromium/src/+/603127 - from the commit message, we could probably try to revert it... |
3d37e86
to
5f35820
Compare
Found a fix for it at https://chromium-review.googlesource.com/c/chromium/src/+/730709 - it seems to be good on review. Now it fails with
Will dig further. |
I've committed your current patch, because it contains security updates: f0a0f02 Leaving the PR open, for further investigations into the |
@bendlas no, they've changed how they build freetype and harfbuzz - it seems it doesn't support using one from system and another from source right now. I'll try to come up with solution tomorrow. |
Unfortunatelly after [0] chromium doesn't support using harfbuzz provided by system while using vendored version of freetype. Disabling usage of separate harfbuzz for now. [0] https://chromium-review.googlesource.com/c/chromium/src/+/696241
5f35820
to
7977c5c
Compare
I've disabled using system harfbuzz for dev version for now. I don't have time to wait for it to be built to finish right now though, but it passed main pain points there. @bendlas Can you also cherry-pick these commits to release-17.09? I'd love to finally see new Chrome on my system (it's funny how to upgrade Chrome in pkgs one has to fight with weirdness of Chromium builds). |
For reference, this was backported to 17.09: 527eb2b |
Please see #30863 for new version bump. |
Motivation for this change
Stable version updated to 62 with various security and other fixes.
Things done
build-use-sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)