search

ungoogled-software / ungoogled-chromium

Google Chromium, sans integration with Google
BSD 3-Clause "New" or "Revised" License
20.86k stars 846 forks source link

Update to version 62 #262

Closed Eloston closed 6 years ago

Eloston commented 7 years ago

This issue tracks the upgrade progress to Chromium 62, 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.

ghost commented 7 years ago

Go guys go!

Was cool seeing your little discussion in the last thread. Was starting to look like this project was having people come together as a team. Would be kinda cool to see a sort of UGC-Inox merge if that's possible.

I just know that I like seeing the collaboration and discussion.

Not sure what to think of Iridium. They're not meeting their deadlines or giving any comment. Think they might've dropped it. Hope you can continue to implement their changes anyway.

Will definitely keep using it on Linux, but fingers crossed for a Windows build.

Either way, definitely referencing it as a good browser on my own personal site (a place where I reference lots of helpful tools and security/privacy stuff, which I'm revamping now).

nyancat18 commented 7 years ago

@92847586

https://p.teknik.io/Raw/lQLWD

nyancat18 commented 7 years ago

@92847586 i've making something just like this as near to this ideal as is possible

because iridium has some unuseful patches, that try to harden webrtc, i dont need it because i've removed it, some crappy changes pings from google to their site and unuseful talks to unexistent files at chromium tree

and @eloston ungooggled chromium has the same trouble for ug isnt bad, but for me its bad, as i take the chromium raw source lol

@Eloston has some death flags, that i've removed it.

but i've gave some classic mitigation tricks for normal chromium, for cancel any leak

death flag, you use it, you wait your 3.4 hours and when says LINK CHROME......FAILLL

https://crbug.com/767185

https://github.com/nyancat18/inox-patchset

shak3800 commented 7 years ago

Are there any updates of UG new version ? Or we have to wait when Iridum updates their browser to get the patches?

Eloston commented 7 years ago

@shak3800 It's coming, but slowly. I am not certain when I can release a new version.

nyancat18 commented 7 years ago

@eloston feel free to use my wip (i've adapted your paches)

your patches are 40xx..

dimqua commented 7 years ago

Why do you use patches from Debian project, what their main purpose? Are they enhance privacy even further?

Eloston commented 7 years ago

@dimqua They're mostly patches to integrate with Debian better, such as patches to use system libraries. There are also a few very minor tweaks, a couple of which are privacy related.

dimqua commented 7 years ago

They're mostly patches to integrate with Debian better

Why not to drop their support in this case?

Eloston commented 7 years ago

@dimqua Because I use Debian.

Eloston commented 7 years ago

Since 62 came out, focus has shifted onto it. Partial work has been done already, but I'm currently waiting for Debian to release a new version in order to continue.

Calinou commented 7 years ago

There are also a few very minor tweaks, a couple of which are privacy related.

Just a note, one of the included Debian patches implements mouse wheel scrolling in the tab list (scrolling the mouse wheel while having the mouse cursor on the tab list will cycle between tabs). This is a useful feature for some people, but it's hardcoded and cannot be disabled once it's compiled in.

However, this feature cannot be implemented with an extension, it has to be done in the Chromium core.

Eloston commented 7 years ago

@Calinou Can you show me which patch? In all of the time that I've dealt with Debian's Chromium package, I have never come across such patch.

khalibadelni commented 7 years ago

Iridium 61.0.0 is released. when we will expect the new version of ungoogled chromium? btw last stable chrome version now is 62.0.3202.62

Eloston commented 7 years ago

@khalibadelni https://github.com/Eloston/ungoogled-chromium/issues/262#issuecomment-338043924. I cannot guarentee that I will finish updating to 62 in a timely manner once Debian updates. You can view more details about development in https://github.com/Eloston/ungoogled-chromium/commits/develop.

@Calinou My previous message came out harsher than I intended; my apologies. Are you able to recall where you saw the change you mentioned? It's just for curiosity's sake.

LeFroid commented 7 years ago

@Eloston I worked on an update for chromium 62.0.3202.62 today and it seems to be running without any regressions so far on my machine. I've posted the patches at the following URL: https://pastebin.com/SYfuyUCb

Eloston commented 7 years ago

@LeFroid Awesome. I'll merge your patch after I merge in Debian changes.

LeFroid commented 7 years ago

Updated my patch for 62.0.3202.75 : https://pastebin.com/wdtyDVnd

leedoyle commented 7 years ago

Are there going to be 32-bit binaries for Linux?

sergeevabc commented 7 years ago

The story of updating Chromium Ungoogled reminds me of Duke Nukem Forever development.

Eloston commented 7 years ago

@leedoyle Not from me personally. It depends on what other people contribute.

@sergeevabc Hmm... might as well prefix "62" with "3" before I forget then.

Eloston commented 7 years ago

Debian released Chromium 62.0.3202.75-1. If nothing comes up, I plan to resume work next weekend.

LeFroid commented 7 years ago

@Eloston Updated my patchset for 62.0.3202.89 : https://pastebin.com/CnB8ux0c

Eloston commented 7 years ago

I'm writing this message from 91a96717f6e5a2b1ee191c0c94dd8eb6aef8fe92, and the tip of develop is being built right now. I don't think anything I've committed since my last build will break anything, so everyone is welcome to try it out.

avently commented 7 years ago

@Eloston builds fine on Arch except problem mentioned here: https://github.com/Eloston/ungoogled-chromium/issues/266#issuecomment-337654506 Built with icudat from source (just exlcuded it from cleaning_list)

phaoost commented 7 years ago

Hello,

is there any chance to get pre-built binaries?

On 26 November 2017 at 03:10, Eloston notifications@github.com wrote:

I'm writing this message from 91a9671 https://github.com/Eloston/ungoogled-chromium/commit/91a96717f6e5a2b1ee191c0c94dd8eb6aef8fe92, and the tip of develop is being built right now. I don't think anything I've committed since my last build will break anything, so everyone is welcome to try it out.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Eloston/ungoogled-chromium/issues/262#issuecomment-346959903, or mute the thread https://github.com/notifications/unsubscribe-auth/AA5xJ2LBLLasAEzowVNJrtcuRwQxrNhhks5s6GYJgaJpZM4PZ3PJ .

-- Regards, Yevgeny

Eloston commented 7 years ago

Just published 62.0.3202.94-1 with Debian 9.0 (stretch) binaries. Please consult the Wiki for current platform support.

EDIT: Please note of the changes in the first comment: https://github.com/Eloston/ungoogled-chromium/issues/262#issue-258240886. This will be the format used in future issues like these.

chew-z commented 7 years ago

This release is great progress. Is it possible to obtaing macOS binaries?

Eloston commented 6 years ago

Development on 62 has ceased in favor of 63.

sergeevabc commented 6 years ago

Regular rescheduling and lack of support across more popular platforms led me to think @Eloston came in with a bang, but went out with a whimper, i.e. he is out of his depth. Hence, I unsubscribe and move on.

Eloston commented 6 years ago

@sergeevabc ungoogled-chromium has always been developed in bursts with long gaps between, because it's just a side project. If you're expecting more consistent and ongoing development, then most Chromium projects like these will probably disappoint you.

Platform support is lacking because it takes a lot of tedious work; it's time-consuming and not interesting. Not to mention the learning curve involved (see #235).

chew-z commented 6 years ago

Releases for most platforms are stuck on version 55 or 58. It might have been important privacy project pity it is Debian-only.

Eloston commented 6 years ago

@chew-z @sergeevabc I believe it's unfair to group Linux with macOS or Windows.

On Linux, updating the build configuration and patches on one distribution essentially updates support across all other Linux distributions. The only major problems after that are distribution-specific changes to link against system libraries or work with the toolchain provided by the distro, which are already solved in the distribution's Chromium package (if it exists). ungoogled-chromium is just being generous by allowing modified versions of these distro-specific build scripts to be included for the ease of the user. Since not everyone can maintain such a script for their own distro, I plan to implement linux_portable so it can work across a variety of distros and compilers.

On macOS and Windows, I use the same build configuration and patches as I do on Linux, aside for changes specific to Linux. Even then, this configuration contains many deviations from the official build process or processes used elsewhere, so there ends up being many problems no one else has run into. These issues are generally not straight-forward, so they require experimentation and/or thorough investigation to solve (which is very* time-consuming). A subset of them require extensions to ungoogled-chromium's custom build system to automate, especially on Windows (otherwise there will be a lot of manual labor).

@sergeevabc, you specifically pointed out Windows support in your comment. Windows deviates more from Linux than macOS does (in the toolchain and system APIs), so I suspect there will be quite a significant effort to get it updated.

Footnotes: * This is mostly because I and the others I work with lack knowledge of how Chromium is built at the level it is failing. None of it is conceptually difficult.