I REVISED THE CHROMIUM AND CHROME AND SEEMS DOES NTO RESPECT THE FREEDOM OF THE USERS IN ANY CHANCE AFTER A REVIEW OVER THE UNGOOGLED CHROMIUM PROJECT.. https://github.com/ungoogled-software/ungoogled-chromium-debian As LXDE does in the past and today.. it's better that upstream work hand to hand with the debian itselft.. that's reduced the problems of updating things.. in chromium that are a very oftyen updated package... Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Severity: wishlist Owner: Thomas <rt1omas@protonmail.com> * Package name : ungoogled-chromium Version : 84.0.4147.105-1.1 Upstream Author : Eloston <eloston@programmer.net> * URL :https://github.com/Eloston/ungoogled-chromium * License : BSD-3-Clause Programming Lang: Python Description : A lightweight approach to removing Google web service dependency I intend to maintain the package that Piccoro has pointed out here as I use this browser on a daily basis and I believe that it is a better alternative to chromium. Chromium itself is still very dependent on Google web services to operate making this very difficult for those who want to use Chromium without the Google aspect to it. The package currently has a ungoogled-chromium-debian Github link where the original developer has included build files for ungoogled-chromium. I also intend on contacting & assisting the developer in packaging the files for Debian and uploading them to the official Debian archive.The ungoogled-chromium-debian branch contains packages for Debian sid and stable but is sometimes not as up-to-date as the original upstream source. So far, I plan on maintaining the package on my own but if I do need help I hope that I can reach out to the Debian Chromium Team. I require a sponsor - I have found a developer willing to sponsor the uploads.
Please work on the already existing (and patched!) chromium in the archive instead of adding one additional chromium-based browser that then also lacks team power. If you need any additional patches on Debian's chromium that are in ungoogled chromium, make them available in Debian's chromium. The chromium package might be excluded from bookworm when not enough people care about keeping it secure.
Does that mean that Debian's `chromium` is also "ungoogled"? That would admittedly make a lot of sense. I see a directory `ungoogled` in https://sources.debian.org/src/chromium/121.0.6167.160-1/debian/patches/ but it contains a fairly trivial patch that doesn't do what I expect "ungoogled" to mean. If it is indeed, ungoogled, then the package's description should say so, shouldn't it? Currently it just says: Description: web browser Web browser that aims to build a safer, faster, and more stable internet browsing experience. This package contains the web browser component. which doesn't hint at it being ungoogled at all. Stefan
Am 11.02.24 um 16:40 schrieb Stefan Monnier: I guess you expect the rest of the patch set at https://github.com/ungoogled-software/ungoogled-chromium/tree/master/patches/core/ungoogled-chromium to be applied. Please ask for that on the chromium package's bug tracker. That is true, and it is probably not to the extend of ungoogled chromium. I have just said that Debian's chromium is already patched and the package maintainers would probably welcome integrating patches that remove privacy violations.
hi all, The Debian Chromium team is aware of the ungoogled-chromium project and has a list of the patches included in the Debian source: https://salsa.debian.org/chromium-team/chromium/-/blob/master/ungoogled-chromium.md I agree that it would make more sense to work with the Debian Chromium team rather than create a separate "ungoogled-chromium" package. Cheers Boud
Hi, Thanks for filing this tracking bug. I'd encourage anyone who's interested in seeing ungoogled-chromium support in debian move forward, who also has the time & expertise: please help update and sort through the list of ungoogled-chromium patches listed in [2]. I simply haven't had time, as maintaining chromium and then having to do related backports/fixes of llvm-toolchain-* and rustc compilers ends up being a lot. You can use salsa to open a merge request with updates to [2], and then I can handle adding the useful patches to the chromium debian package. Thanks, Andres