Package Details: chromium-pepper-flash-dev 21.0.0.232-1

Git Clone URL: https://aur.archlinux.org/chromium-pepper-flash-dev.git (read-only)
Package Base: chromium-pepper-flash-dev
Description: Google Chrome's Pepper Flash plugin for Chromium (Dev Channel)
Upstream URL: http://www.google.com/chrome
Licenses: custom:chrome
Conflicts: chromium-pepper-flash, chromium-pepper-flash-stable
Provides: chromium-pepper-flash
Submitter: Ner0
Maintainer: sl1pkn07
Last Packager: sl1pkn07
Votes: 257
Popularity: 3.425103
First Submitted: 2014-01-22 06:53
Last Updated: 2016-04-27 15:02

Dependencies (1)

Required by (6)

Sources (2)

Latest Comments

hotaru commented on 2015-05-06 21:55

==> Validating source files with sha1sums...
eula_text.html ... FAILED
google-chrome-unstable-44.0.2391.0-1.x86_64.rpm ... Passed
==> ERROR: One or more files did not pass the validity check!
==> ERROR: Makepkg was unable to build chromium-pepper-flash-dev.

Det commented on 2015-04-20 10:01

Yeah, but you need to notify people of the newer version (because it's not a VCS package), so that they don't have to look for it themselves. Like it is now.

sl1pkn07 commented on 2015-04-14 20:44

@det the pkgbuild update automagic if reinstall the package

Det commented on 2015-03-17 02:40

@orflman, well, that doesn't make much sense, because how would you go on about _finding out_ the URL for the newer release? At least now you _can_ just skip the md5sums.

md5sums=('SKIP') in the PKGBUILD itself doesn't make much sense either, because this isn't a _VCS_ package. It's software with clear, distinct, separate releases that all should be verified and notifying users through the change in pkgver, just like with any other package.

orlfman commented on 2015-03-04 20:31

yeah since this is dev version it should be set to SKIP for md5 checks. its always going to be updated randomly.

only stable should have a md5 check since that's meant for people wanting the most stable, safest version.

or at least link the source to a static dev version that's only updated when the maintainer switches it to a newer dev version if you really want md5 check.

georgnix commented on 2015-02-21 15:02

@sl1pkn07: Um, what's the point of checking the hashsum of the downloaded file against the hashsum *in a downloaded file*. You could just as well do md5sums=('SKIP') or am I missing something?

georgnix commented on 2015-02-21 15:00

@sl1pkn07: Um, what's the point of checking the hashsum of the downloaded file against the hashsum *in the downloaded file*. You could just as well do md5sums=('SKIP') or am I missing something?

sl1pkn07 commented on 2014-12-10 07:22

please test this pkgbuild
http://sl1pkn07.wtf/paste/view/69030a9f
(need a pepper.install and LICENSE.txt from this package)

this pkgbuild
- gets SHA1 sum automatic from official RPM repository (like YUM)
- gets plugin version automatic from a manifest.json include in the pepperplugin folder
- no need manual intervention if exist a new version, only need reinstall this package when the release is out

greetings

Arkranur commented on 2014-10-11 10:55

Guys, you don't need to find the updated hashes always.

If you trust the source, you can just change the hash to SKIP, say

md5sums=('SKIP')

or

md5sums=(SKIP)

and makepkg will skip the hash check

mediocregopher commented on 2014-10-10 14:42

Newest md5 hashes to use are:
]
38b58579bdc3b43b5fd2631c5bce845f for i386
de2eb3d54e128520ee06adebd3d26350 for amd64

Also note that even if the deb being pulled from is updated the version number on this package does not, so if things start not working after a chromium update you should re-sync this package as well (and you'll have to find out the new hashes).

All comments