Package Details: chromium-snapshot-bin 78.0-1

Git Clone URL: (read-only)
Package Base: chromium-snapshot-bin
Description: The open-source project behind Google Chrome (Latest Snapshot)
Upstream URL:
Keywords: browser web
Licenses: BSD
Provides: chromium
Submitter: Det
Maintainer: mrxx
Last Packager: mrxx
Votes: 498
Popularity: 0.520531
First Submitted: 2015-04-20 12:12
Last Updated: 2019-07-27 13:38

Dependencies (11)

Required by (48)

Sources (12)

Pinned Comments

Det commented on 2017-03-30 10:20

Do not flag this package out-of-date.

It updates automatically on each install.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 ... Next › Last »

RemoteAdmin commented on 2017-06-15 07:52

"makedepends=('lib32-libcups')" must be added to PKGBUILD.

Otherwise chrome won't be able to print the current version and exits with:

"ERROR: pkgver() generated an invalid version: chrome-linux/chrome: error while loading shared libraries: cannot open shared object file: No such file or directory"

glapa commented on 2017-04-10 20:35

Why can't I play videos with this package? Gtk2 is not required anymore on behalf of Gtk3

Det commented on 2017-04-03 13:04

Just the "curl -s .." is enough.

Ferik commented on 2017-04-03 13:02

To easily know the last build, launch this command (every 2/3 hours) in the terminal:

echo $(curl -s "")

and use always this package for updates/install.

Bye :)

Det commented on 2017-03-30 10:21

> jab2870 flagged chromium-snapshot-bin out-of-date on 2017-03-30 for the following reason:
> The dev chanel is now on 59.
> The git repo's latest is now so surely the snapshot should be ahead of that

Have a look at the absolute latest discussion on the comment section...

Det commented on 2017-03-30 10:20

Do not flag this package out-of-date.

It updates automatically on each install.

Det commented on 2017-03-09 20:14

The major version bump in Chromium is time-based and otherwise meaningless. Pacaur will fail with every new snapshot anyway.

Things like firefox-nightly do the major bumps, because the PKGBUILD doesn't automatically handle those. When it does, you get the latest version whenever you chose to update like any VCS package that doesn't do those bumps either.

noxpo commented on 2017-03-09 19:58

@det, sry for wasting your time man, I just didn't understand from what you wrote that pkgver is supposed to change *in PKGBUILD*. If pkgver is in PKGBUILD and .SRCINFO, it could have also been in other places, for what I understood about AUR, which isn't much. I just saw the v. 58 package actually building a v. 59 and thought: that *can't* be right. Honestly just being a dumbass, sry. Would be nice for folks like me if pkgver was updated on major version changes though, doesn't happen too often.

Det commented on 2017-03-09 08:36

@noxpo, _listen_ what I'm telling you, because when you flag my package for a wrong reason after I've just told you otherwise (twice), that's when my patience runs out.

1) The problem is Pacaur, not Pacman. Pacman doesn't know, care or understand .SRCINFO (in fact, makepkg uses the same "pacman -U", which was your clue right there).

2) The pkgver() function is *supposed* to update the pkgver beyond what is shown here. There is a new snapshot of Chromium multiple times every hour. You want both of us to update your version every 10-15 minutes or whenever you wish? This is the 3rd time I'm explaining it to you. Have a look here:

3) Complain to Pacaur, not here. In fact, this is how we do it in Arch: Google the message:

noxpo commented on 2017-03-09 07:09

It's pacaur, not pacaur-git. And it does build chromium-snapshot-bin, it just refuses to install it via pacman. I tried building the old fashioned way with makepkg: works, builds the latest 59.xx.. and also changes pkgver in PKGBUILD to 59.xx..
Flagged this package out-of-date since pkgver in the original PKGBUILD is lagging behind now.