Package Details: chromium-pepper-flash-dev 22.0.0.209-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: 259
Popularity: 1.572713
First Submitted: 2014-01-22 06:53
Last Updated: 2016-07-15 16:36

Dependencies (1)

Required by (8)

Sources (2)

Latest Comments

sl1pkn07 commented on 2016-07-18 04:34

ask to your AUR helper bugtracker(?)

hendry commented on 2016-07-18 01:33

Hmmm, this looks a bit dodgy http://s.natalian.org/2016-07-18/1468805564_1140x1380.png

sl1pkn07 commented on 2016-05-26 19:20

packed with makepkg and install througth yaourt without problems here

tested packed/install only with yaourt, also zero problems

greetings

thx1138 commented on 2016-05-26 18:56

==> Finished making: chromium-pepper-flash-dev 22.0.0.168-1 (Thu May 26 12:44:22 MDT 2016)
==> Cleaning up...
:: Installing chromium-pepper-flash-dev package(s)...
:: chromium-pepper-flash-dev package(s) failed to install. Check .SRCINFO for mismatching data with PKGBUILD.

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?

All comments