Package Details: ungoogled-chromium-bin 136.0.7103.59-1

Git Clone URL: https://aur.archlinux.org/ungoogled-chromium-bin.git (read-only, click to copy)
Package Base: ungoogled-chromium-bin
Description: A lightweight approach to removing Google web service dependency
Upstream URL: https://github.com/ungoogled-software/ungoogled-chromium
Keywords: blink browser privacy web
Licenses: BSD
Conflicts: chromedriver, chromium
Provides: chromedriver, chromium
Submitter: networkException
Maintainer: networkException
Last Packager: networkException
Votes: 115
Popularity: 10.68
First Submitted: 2022-08-27 13:16 (UTC)
Last Updated: 2025-05-04 21:11 (UTC)

Dependencies (35)

Required by (133)

Sources (1)

Pinned Comments

networkException commented on 2025-05-02 13:41 (UTC)

Hello everyone, there's always a lot of confusion when ungoogled-chromium doesn't start because of a system dependency it can't find.

This issue is inherent to Arch Linux package management, there's no mechanism that tracks required rebuilds. Maintainers are expected to push manual pkgrel bumps once a rebuild is required. The chromium package can somewhat easily handle this, they can also update the package in testing first.

People's comments here or on GitHub are how I notice that a rebuild is required, I try to push an update quickly then. Sadly a full rebuild currently takes over 24 hours on GitHub Actions and I'm not exactly maintaining open source software as my dayjob either, so this can take a while.

There's no solution for this really, other than adopting the package into the official repository maybe (I cannot do that). Note that for Manjaro users even a rebuild might not be enough as there can always be mismatches in what system library versions are available.

networkException commented on 2022-09-20 17:36 (UTC)

Please note that normally it's not required to flag this package as out of date. I usually tag releases in the main ungoogled-chromium repository and update the arch packaging right afterwards.

If the package hasn't updated after an ungoogled-chromium release GitHub Actions might still be building or the ungoogled-chromium patchset got updated for non Linux platforms only to match their upstream release cycle

Latest Comments

« First ‹ Previous 1 .. 8 9 10 11 12 13

intrnl commented on 2022-09-11 03:46 (UTC)

Browser crashes without libavif and jsoncpp installed.

foutrelis commented on 2022-08-28 14:18 (UTC)

I want to believe we're pragmatic enough to not see any difference between repackaging either pkg.tar.zst or aur.tar.zst. Previously expressed opinions on the matter appear to be about the existence of a -bin package in general (and not the technicalities of the repackaged binaries).

Arguments about the existence of a -bin package aside, I'd say you should feel free to switch to pkg.tar.zst as the source.

networkException commented on 2022-08-28 11:19 (UTC)

Previously the package got removed because "the AUR is not intended to provide an index for PKGBUILDs that repackage the build package originally created by another PKGBUILD". I asked on the mainling list and removing makepkg metadata files seemed to be most compliant with not repackaging the pkg.tar.zst.

If I can be sure that the package wont get removed packaging the pkg.tar.zst is better of course.

foutrelis commented on 2022-08-28 04:01 (UTC)

Please ensure the downloaded tarball gets a unique name, otherwise the first version someone installs will keep getting packaged (or will fail the checksum).

Since you're the upstream maintainer as well, may I suggest not generating the aur.tar.zst artifact and instead downloading and repackaging the .pkg.tar.zst one? This would avoid unnecessary duplication in your releases on GitHub and you'd also get a unique source filename for the AUR package.

« First ‹ Previous 1 .. 8 9 10 11 12 13