Skip to content
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

Closed
6 tasks done
Eloston opened this issue Feb 16, 2018 · 11 comments
Closed
6 tasks done

Update to version 64 #332

Eloston opened this issue Feb 16, 2018 · 11 comments
Milestone

Comments

@Eloston
Copy link
Member

Eloston commented Feb 16, 2018

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):

  • Include new patches from Debian (I am working on this)
  • Include new patches from Inox (I am working on this)
  • Include (or upgrade) patches from Iridium (I am working on this)
  • Update ungoogled-chromium's own patches (I am working on this)
  • Informal testing (e.g. checking for major regressions, testing new features)
  • Publish new release and binaries

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.

@Eloston Eloston added this to the 64.x.x.x milestone Feb 16, 2018
@Eloston Eloston mentioned this issue Feb 16, 2018
6 tasks
@Eloston
Copy link
Member Author

Eloston commented Feb 18, 2018

Status update: develop builds on Debian Stretch. 89776f7 should be working even though I didn't make a build with #333 yet.

@onabi
Copy link

onabi commented Feb 18, 2018

Will you publish binaries?

@Eloston
Copy link
Member Author

Eloston commented Feb 19, 2018

@onabi Yes, I will publish Debian binaries when they're ready. I haven't built with #333 yet.

@tectiv3
Copy link
Contributor

tectiv3 commented Feb 19, 2018

With a few patches I was able to build this version. Sadly bug with crashpad is still there.
Created PR: #334

@Eloston
Copy link
Member Author

Eloston commented Feb 20, 2018

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 windows-fix-building-without-safebrowsing.patch, since I was trying to make changes to that patch before I stopped.

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.

@onabi
Copy link

onabi commented Feb 20, 2018

Pretty unfortunate, I was looking forward to it, I guess it can't be helped.

@Eloston
Copy link
Member Author

Eloston commented Feb 22, 2018

64.0.3282.168-1 is out with Debian 9 binaries. I know Ubuntu 17.10 builds (but I don't have binaries), and linux_portable base bundle builds as well.

@Eloston
Copy link
Member Author

Eloston commented Mar 2, 2018

64.0.3282.186-1 is out. I'm still building Debian 9 binaries.

@tectiv3
Copy link
Contributor

tectiv3 commented Mar 2, 2018

I'll open a PR with build for macos then

@Eloston
Copy link
Member Author

Eloston commented Mar 10, 2018

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.

@Eloston
Copy link
Member Author

Eloston commented Mar 12, 2018

Development has ceased on 64 since PRs were merged for 65. See #352

@Eloston Eloston closed this as completed Mar 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants