Package Details: ffmpeg-compat-54 1.2.12-5

Git Clone URL: https://aur.archlinux.org/ffmpeg-compat-54.git (read-only, click to copy)
Package Base: ffmpeg-compat-54
Description: Compatibility package for ffmpeg to provide versions 54 of libavcodec, libavdevice and libavformat, not anymore provided by the ffmpeg package
Upstream URL: http://ffmpeg.org/
Licenses: GPL-3.0-only
Provides: libavcodec.so, libavdevice.so, libavformat.so
Submitter: Muflone
Maintainer: Muflone
Last Packager: Muflone
Votes: 87
Popularity: 0.000000
First Submitted: 2014-10-04 21:43 (UTC)
Last Updated: 2024-09-22 23:46 (UTC)

Required by (130)

Sources (10)

Latest Comments

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

Muflone commented on 2017-04-09 11:50 (UTC)

@4javier fixed shasum, thank you for reporting.

4javier commented on 2017-04-09 10:24 (UTC)

@Muflone, you should update the shasum for the patch file. This works 1e4a01ed62db525607f9d0c708ef7889474222f9ae31aac057c5bb67edf7e38f

carlzoo commented on 2017-04-09 06:29 (UTC)

I'm getting an error with the sha256sum for the patch: :: Proceed with installation? [Y/n] y :: Retrieving package(s)... :: ffmpeg-compat-54 build files are up-to-date -- skipping :: libavutil-52 build files are up-to-date -- skipping :: Checking libavutil-52 integrity... ==> Making package: libavutil-52 2.3.6-3 (Sun Apr 9 02:19:47 EDT 2017) ==> Retrieving sources... -> Found ffmpeg-2.3.6.tar.bz2 -> Found ffmpeg-2.3.6.tar.bz2.asc ==> Validating source files with sha256sums... ffmpeg-2.3.6.tar.bz2 ... Passed ffmpeg-2.3.6.tar.bz2.asc ... Skipped ==> Verifying source file signatures with gpg... ffmpeg-2.3.6.tar.bz2 ... Passed :: Checking ffmpeg-compat-54 integrity... ==> Making package: ffmpeg-compat-54 1.2.12-1 (Sun Apr 9 02:19:54 EDT 2017) ==> Retrieving sources... -> Found ffmpeg-1.2.12.tar.bz2 -> Found ffmpeg-1.2.12.tar.bz2.asc -> Found libvpx_VP8E_UPD_ENTROPY.patch ==> Validating source files with sha256sums... ffmpeg-1.2.12.tar.bz2 ... Passed ffmpeg-1.2.12.tar.bz2.asc ... Skipped libvpx_VP8E_UPD_ENTROPY.patch ... FAILED ==> ERROR: One or more files did not pass the validity check! :: failed to verify ffmpeg-compat-54 integrity

Muflone commented on 2016-10-29 15:18 (UTC)

@phraktal read the previous comments. You have to import the gpg key

phraktal commented on 2016-10-25 15:06 (UTC)

Does this package works for anyone ? I've tried to follow the discussion below, but I'm unable to make this work: ==> Making package: ffmpeg-compat-54 1.2.12-1 (Tue Oct 25 11:00:31 EDT 2016) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found ffmpeg-1.2.12.tar.bz2 -> Found ffmpeg-1.2.12.tar.bz2.asc -> Found libvpx_VP8E_UPD_ENTROPY.patch ==> Validating source files with sha256sums... ffmpeg-1.2.12.tar.bz2 ... Passed ffmpeg-1.2.12.tar.bz2.asc ... Skipped libvpx_VP8E_UPD_ENTROPY.patch ... Passed ==> Verifying source file signatures with gpg... ffmpeg-1.2.12.tar.bz2 ... FAILED (unknown public key B4322F04D67658D8) ==> ERROR: One or more PGP signatures could not be verified!

ZeroBit commented on 2016-10-22 11:34 (UTC) (edited on 2016-10-22 11:53 (UTC) by ZeroBit)

@Muflone Thank you. You were right. I re-created the trustdb and it worked fine. Thank you again! $ gpg --verify ffmpeg-1.2.12.tar.bz2.asc gpg: assuming signed data in 'ffmpeg-1.2.12.tar.bz2' gpg: Signature made Thu Feb 12 2015 16:47:48 EET gpg: using RSA key B4322F04D67658D8 gpg: lookup_hashtable failed: Unknown system error gpg: trustdb: searching trust record failed: Unknown system error gpg: Error: The trustdb is corrupted. gpg: You may try to re-create the trustdb using the commands: gpg: cd ~/.gnupg gpg: gpg --export-ownertrust > otrust.tmp gpg: rm trustdb.gpg gpg: gpg --import-ownertrust < otrust.tmp gpg: If that does not work, please consult the manual

Muflone commented on 2016-10-22 10:20 (UTC)

@ZeroBit I've just tried with a clean new user, using yaourt and before importing the key I had your same errors. After importing the key with gpg the error has gone. I suppose that your download is corrupt and you have to delete it and start again. If the error persists move where your PKGBUILD is and execute: gpg --verify ffmpeg-1.2.12.tar.bz2.asc

ZeroBit commented on 2016-10-21 08:21 (UTC)

Ok. That's what I did and it didn't help $ gpg --keyserver pgp.mit.edu --recv-keys FCF986EA15E6E293A5644F10B4322F04D67658D8 gpg: key B4322F04D67658D8: "FFmpeg release signing key <ffmpeg-devel@ffmpeg.org>" not changed gpg: Total number processed: 1 gpg: unchanged: 1 $ yaourt -S ffmpeg-compat-54 ... => Verifying source file signatures with gpg... ffmpeg-1.2.12.tar.bz2 ... FAILED ==> ERROR: One or more PGP signatures could not be verified! ==> ERROR: Makepkg was unable to build ffmpeg-compat-54. What should I do?

Muflone commented on 2016-10-20 22:58 (UTC)

pacman-key is not related in any way with makepkg. It adds keys for pacman, hence to the root user, not your regular user. If you want to import the key for this source file you have to use gpg like @pirinto wrote before.

ZeroBit commented on 2016-10-20 19:58 (UTC)

Even after gpg --keyserver pgp.mit.edu --recv-keys FCF986EA15E6E293A5644F10B4322F04D67658D8 and pacman-key -r FCF986EA15E6E293A5644F10B4322F04D67658D8 pacman-key --refresh-keys I have the following error: ==> Verifying source file signatures with gpg... ffmpeg-1.2.12.tar.bz2 ... FAILED ==> ERROR: One or more PGP signatures could not be verified! ==> ERROR: Makepkg was unable to build ffmpeg-compat-54. What to do?