Package Details: chromium-widevine 1:4.10.2891.0-1

Git Clone URL: https://aur.archlinux.org/chromium-widevine.git (read-only, click to copy)
Package Base: chromium-widevine
Description: A browser plugin designed for the viewing of premium video content
Upstream URL: https://www.widevine.com/
Keywords: amazon chrome netflix prime webengine
Licenses: custom
Submitter: Scimmia
Maintainer: envolution
Last Packager: envolution
Votes: 419
Popularity: 0.009002
First Submitted: 2015-04-17 05:05 (UTC)
Last Updated: 2025-04-21 04:58 (UTC)

Latest Comments

« First ‹ Previous 1 .. 23 24 25 26 27 28 29 30 31 32 33 .. 37 Next › Last »

TheStochasticMan commented on 2016-02-17 04:23 (UTC)

This doesn't seem to be working for me. Is there anything I need to do other than simply installing this patch?

aaschmid commented on 2016-02-03 19:53 (UTC) (edited on 2016-02-03 19:57 (UTC) by aaschmid)

Yes, you are right, that helped. Didn't do any intended force update but it obviously was my fault. Removed the comment. Sorry for the effort!

foutrelis commented on 2016-02-03 19:53 (UTC) (edited on 2016-02-03 19:53 (UTC) by foutrelis)

@aaschmid Sounds like you force upgraded chromium and then updated chromium-widevine which would end up removing chromium's libwidevinecdmadapter.so. You need to remove this plugin, reinstall chromium and finally install chromium-widevine again.

Det commented on 2016-01-21 23:37 (UTC) (edited on 2016-01-21 23:37 (UTC) by Det)

E: Nope, nevermind.

Scimmia commented on 2016-01-21 21:07 (UTC)

1:1.4.8.824-2 available. Remember update it BEFORE updating to chromium 48.0.2564.82

Scimmia commented on 2016-01-21 18:58 (UTC)

While we were in Chromium 47, the downgrade didn't matter that much. I was hoping they'd go back to 1.4.8.865 for Chrome 48 and we'd be able to avoid the epoch. That didn't happen and the Chrome 48 package needs to be newer than any of the Chrome 47 packages.

txus commented on 2016-01-21 17:17 (UTC)

But that was a month and a half ago, and applied to chromium ver. 47, AFAIR, which is going to get obsoleted quite soon, right?

Scimmia commented on 2016-01-21 17:05 (UTC)

epoch was necessary because the pkgver went backwards.

txus commented on 2016-01-21 17:02 (UTC)

Why the epoch change and not just a pkgrel bump? Even if this was in an actual repo and not in AUR, where in theory you build your own packages and the version is basically a commodity, you just did a change to the "build" result without changing the version, which is what pkgrel is for. I would recommend reverting the epoch line! For more information, see here: https://wiki.archlinux.org/index.php/PKGBUILD#Version

« First ‹ Previous 1 .. 23 24 25 26 27 28 29 30 31 32 33 .. 37 Next › Last »