-
Notifications
You must be signed in to change notification settings - Fork 843
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
Update to version 64 #332
Comments
Will you publish binaries? |
With a few patches I was able to build this version. Sadly bug with crashpad is still there. |
Because #215 yields Server Error 500 (again), I'm letting everyone know that a failed attempt at bringing back Windows support is in 94ee1be. As the commit states, it fails to link the final binaries with over 600 unresolved externals. I suspect the breakage may be in I've lost access to the Windows machine I was using, and interest in trying to find the root problem. If anyone wants to finish off what I started, please do so. |
Pretty unfortunate, I was looking forward to it, I guess it can't be helped. |
64.0.3282.168-1 is out with Debian 9 binaries. I know Ubuntu 17.10 builds (but I don't have binaries), and |
64.0.3282.186-1 is out. I'm still building Debian 9 binaries. |
I'll open a PR with build for macos then |
It was brought to my attention that the download links for Debian 9 version 64.0.3282.186-1 were broken. They're fixed now. |
Development has ceased on 64 since PRs were merged for 65. See #352 |
This issue tracks the upgrade progress to Chromium 64, and related discussion.
Here are the steps necessary towards the first release in the upgrade process (in approximate order):
After the initial release is published, this issue will remain open for general discussions about upgrading platforms that are not working in this new version. Specific issues should be posted in a separate issue.
The text was updated successfully, but these errors were encountered: