Package Details: chromium-snapshot-bin 88.0-1

Git Clone URL: (read-only, click to copy)
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.126275
First Submitted: 2015-04-20 12:12
Last Updated: 2020-10-05 22:23

Dependencies (11)

Required by (72)

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 9 ... Next › Last »

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.

Det commented on 2017-03-08 13:24

Is that the -git version? Either way it's broken, as through the pkgver() function is how all the VCS packages (Git, SVN, etc.) update the pkgver, as well as these nightlies.

.SRCINFO is synced with mksrcinfo (community/pkgbuild-introspection) and I really can't see why should pacaur start caring about it during build, especially as much as to abort it.

noxpo commented on 2017-03-08 13:11

The error seems to come from pacaur, sry. After buikding the package archive, it says:

:: chromium-snapshot-bin package(s) failed to install. Check .SRCINFO for mismatching data with PKGBUILD.

pkgver is 58.xx.. in .SRCINFO and 59.xx.. in PKGBUILD. The actual package archive has the version from PKGBUILD. Installing it with pacman -U works. The header of .SRCINFO is:

# Generated by mksrcinfo v8
# Thu Feb 2 13:26:13 UTC 2017

Det commented on 2017-03-08 07:55

Pacman doesn't care about the .SRCINFO, which in fact is in sync until you update with the pkgver().

What's the error?

noxpo commented on 2017-03-07 18:58

pacman throws an error because .SRCINFO und PKGBUILD are not in sync. Probably due to two different package versions (58 vs 59).

Det commented on 2017-01-29 16:48

Something was done about the lib lookup a while back so that even replacing the bundled FFmpeg libs with Chrome's own didn't bring back H.264 (related?:

So if you want a bleeding edge H.264 "Chromium", that's

Pontorez commented on 2017-01-29 16:35

Does anyone know is there a way to enable H.264 video codec in chromium snapshot? page says that this browser doesn't supports MSE & H.264 codecs so I can't view live streams at YouTube using chromium snapshot.