Package Details: ffmpeg-compat-54 1.2.12-3

Git Clone URL: (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:
Licenses: GPL
Submitter: Muflone
Maintainer: Muflone
Last Packager: Muflone
Votes: 88
Popularity: 0.89
First Submitted: 2014-10-04 21:43
Last Updated: 2018-08-25 22:32

Required by (64)

Sources (7)

Latest Comments

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

Muflone commented on 2016-10-29 15:18

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

phraktal commented on 2016-10-25 15:06

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

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

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

Ok. That's what I did and it didn't help
$ gpg --keyserver --recv-keys FCF986EA15E6E293A5644F10B4322F04D67658D8

gpg: key B4322F04D67658D8: "FFmpeg release signing key <>" 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

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

Even after
gpg --keyserver --recv-keys FCF986EA15E6E293A5644F10B4322F04D67658D8
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?

pirinto commented on 2016-10-19 05:40

If you get pgp verification errors. Import the correct gpg key.

See comment from
" saiyuki commented on 2016-02-27 16:04

believe i got the package to correctly build; wasn't able to pass gpg verification check got stopped at the ffmpeg package none of the dependencies stopped me. You can solve the issue by importing the gpg key prior to installing. with gpg --keyserver --recv-keys FCF986EA15E6E293A5644F10B4322F04D67658D8

then you should be able to install the package via yaourt or just building it via source package or however you do ."

Muflone commented on 2016-03-20 02:31

This package has a freetype2 dependency. It *COULD* work also with others freetype2 packages as long they use the same code hierarchy of freetype2.

I won't patch this package to handle the wrong hierarchy of freetype2-ubuntu.
Please ask the freetype2-ubuntu maintainer to apply the fix in order to result compatible with the official freetype2 package.

Haron_Prime commented on 2016-03-17 20:46


ERROR: freetype2 not found

But freetype2-ubuntu installed

temporary solution:
# cd /usr/include/freetype2 && mkdir freetype && cd freetype && ln -s ../freetype.h