Package Details: svtplay-dl 4.101-1

Git Clone URL: https://aur.archlinux.org/svtplay-dl.git (read-only, click to copy)
Package Base: svtplay-dl
Description: Media downloader for play sites (e.g. SVT Play)
Upstream URL: https://github.com/spaam/svtplay-dl
Licenses: MIT
Submitter: swearchnick
Maintainer: swearchnick
Last Packager: swearchnick
Votes: 16
Popularity: 0.028101
First Submitted: 2014-04-27 08:43 (UTC)
Last Updated: 2024-10-26 07:35 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

bezerk commented on 2021-02-24 17:50 (UTC)

==> Making package: svtplay-dl 3.0-2 (ons 24 feb 2021 18:48:46) ==> Retrieving sources... -> Found 3.0.tar.gz ==> Validating source files with sha256sums... 3.0.tar.gz ... FAILED ==> ERROR: One or more files did not pass the validity check!

PKGBUILD: sha256sums=('c864473e69bc7db5f68c1393cbbb024ba66b8d92e2a5494e50e78d46d80bae8f') WHILE $ sha256sum .cache/yay/svtplay-dl/3.0.tar.gz 6770538cb53644d54bd202c719b7af8857c13a77188f1ed0b2b491d34c70c493

swearchnick commented on 2021-02-22 05:50 (UTC)

@Mkornby Thank you, updated.

Mkornby commented on 2021-02-21 15:57 (UTC)

3.0-1 does not pass the validity check

newk commented on 2021-02-14 13:26 (UTC)

I had no issues with the validity check here. I just upgraded to 2.9-2

niclasc commented on 2021-02-14 11:11 (UTC)

svtplay-dl-2.9-2 does not pass the validity check.

swearchnick commented on 2021-02-12 06:06 (UTC)

@nicolito: Thank you, updated. Can someone answer me why this is changing? The checksum is correct at the time the PKGBUILD is uploaded.

nicolito commented on 2021-02-11 11:36 (UTC)

2.9-1 does not pass validity check. sha256 should be 39cd333912f8e9a7010d8ad44fce0df7dcad4920aa4662c9543905bad799f975

swearchnick commented on 2021-01-02 08:49 (UTC)

@niclasc It works now, can not reproduce failed validity check. Make sure you make a clean build and try also without an aur helper.

niclasc commented on 2021-01-01 15:48 (UTC) (edited on 2021-01-01 15:48 (UTC) by niclasc)

2.8-3 does not pass the validity check.

swearchnick commented on 2020-12-30 07:50 (UTC)

@newk Thank you, it's fixed now.