Package Details: ungoogled-chromium 75.0.3770.80-1

Git Clone URL: https://aur.archlinux.org/ungoogled-chromium.git (read-only)
Package Base: ungoogled-chromium
Description: A lightweight approach to removing Google web service dependency
Upstream URL: https://github.com/Eloston/ungoogled-chromium
Keywords: blink browser privacy web
Licenses: BSD
Conflicts: chromium
Provides: chromium
Submitter: ilikenwf
Maintainer: seppia
Last Packager: seppia
Votes: 96
Popularity: 4.456769
First Submitted: 2016-12-19 08:08
Last Updated: 2019-06-18 14:16

Dependencies (53)

Required by (47)

Sources (4)

Pinned Comments

seppia commented on 2019-04-07 18:31

There have been made some changes in ungoogled-chromium and there now is a separate git repository handling archlinux packaging and building. There are some concerns about the decisions that must be done reguarding the versioning scheme in paritcular. You could read about it in details here https://github.com/ungoogled-software/ungoogled-chromium-archlinux/issues/1 . I've always followed upstream versioning because that was ideal, also for AUR PKGBUILD, but now, as already stated, some concerns have been risen. I'm honestly a bit confused and it's not very clear to me which solution would be better to adopt. I would like to know your opinion in merit, what this community thinks about it and I encourage and very much appreciate any direct involvement from anyone interested on github repo and issue.

seppia commented on 2018-12-12 21:34

Please do NOT flag this package as out of date in relation to official chromium releases.

This is NOT Google Chromium and new releases come after additional work of the ungoogled-chromium contributors, so they may not be ready, nor available for days or even weeks after a new version of official chromium is released.

Please refer to https://github.com/Eloston/ungoogled-chromium/tags for ungoogled-chromium releases. Use those and please flag this package as out of date only if a newer release is present there. I will update the PKGBUILD as soon as I can every time a new release comes out.

Thanks

Latest Comments

1 2 3 4 5 6 ... Next › Last »

lunainvictum commented on 2019-06-24 07:25

Please update the PKGBUILD to latest commit https://github.com/ungoogled-software/ungoogled-chromium-archlinux/commits/master (or https://github.com/Eloston/ungoogled-chromium/commits/master)

Actually a build is not possible because of few bugs.

Reden commented on 2019-06-21 20:56

seppia, do you know what did exactly happen to the -bin version? JstKddng made a repository for -bin packaging, but I would like to know what did happen to the -bin main AUR package.

solnce commented on 2019-06-21 20:24

This won't build for me. I have set ninja to -j3. Log is shown here: https://pastebin.com/6zwS9hmJ

g99 commented on 2019-06-21 11:10

build may well break then use https://github.com/Eloston/ungoogled-chromium/issues/784

PKGBUILD build op:

ninja -j 3 -l 3 -C out/Default chrome chrome_sandbox chromedriver

limit to 3 threads or less when ninja screws up.

aNewDay commented on 2019-06-20 14:59

ERROR at //third_party/protobuf/proto_library.gni:369:15: Only source, header, and object files belong in the sources of a static_library. //out/Default/pyproto/google_apis/gcm/protocol/mcs_pb2.py is not one of the valid types. sources = get_target_outputs(":$action_name") ^--------------------------------- See //google_apis/gcm/BUILD.gn:78:1: whence it was called. proto_library("proto") { ^----------------------- See //BUILD.gn:86:7: which caused the file to be included. "//google_apis/gcm:gcm_unit_tests", ^--------------------------------- ==> ERROR: A failure occurred in build(). Aborting... Error making: ungoogled-chromium

seppia commented on 2019-06-18 14:47

I'm sorry for my two month absence, I should keep up updating now. For changes details please refer to https://github.com/ungoogled-software/ungoogled-chromium-archlinux/issues/1

seppia commented on 2019-04-07 18:31

There have been made some changes in ungoogled-chromium and there now is a separate git repository handling archlinux packaging and building. There are some concerns about the decisions that must be done reguarding the versioning scheme in paritcular. You could read about it in details here https://github.com/ungoogled-software/ungoogled-chromium-archlinux/issues/1 . I've always followed upstream versioning because that was ideal, also for AUR PKGBUILD, but now, as already stated, some concerns have been risen. I'm honestly a bit confused and it's not very clear to me which solution would be better to adopt. I would like to know your opinion in merit, what this community thinks about it and I encourage and very much appreciate any direct involvement from anyone interested on github repo and issue.

TheGoliath commented on 2019-04-02 19:33

As @Scrumplex has already pointed out, this package needs the $pkgbuild variable changed. Because this isn't the official chromium package and therefore the $pkgbuild definition isn't used as it may have meant to be

Cheers

Scrumplex commented on 2019-04-01 18:48

The PKGBUILD creates the symlink at usr/bin/chromedriver pointing to /usr/lib/$pkgname/chromedriver, which should actually be /usr/lib/chromium/chromedriver like the other links.1

Scrumplex commented on 2019-03-26 16:40

@rodneyck One quick DuckDuckGo search reveals, that it is for multi factor authentication with hardware. https://askubuntu.com/questions/844090/what-is-cryptotokenextension-in-chromium-extensions