Package Details: libavutil-52 2.3.6-4

Git Clone URL: https://aur.archlinux.org/libavutil-52.git (read-only, click to copy)
Package Base: libavutil-52
Description: Compatibility package for ffmpeg to provide versions 52 of libavutil not anymore provided by the ffmpeg package
Upstream URL: http://ffmpeg.org/
Licenses: GPL
Provides: libavutil.so
Submitter: Muflone
Maintainer: Muflone
Last Packager: Muflone
Votes: 75
Popularity: 0.000000
First Submitted: 2014-10-04 18:23 (UTC)
Last Updated: 2023-05-07 20:57 (UTC)

Dependencies (20)

Required by (67)

Sources (2)

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

evamvid commented on 2018-07-01 14:35 (UTC)

gpg --search-keys B4322F04D67658D8 returns gpg: data source: https://193.164.133.100:443 (1) FFmpeg release signing key ffmpeg-devel@ffmpeg.org 2048 bit RSA key B4322F04D67658D8, created: 2011-04-26

but trying to rebuild after that still returns the same

ffmpeg-2.3.6.tar.bz2 ... FAILED (unknown public key B4322F04D67658D8) ==> ERROR: One or more PGP signatures could not be verified! ==> ERROR: Makepkg was unable to build libavutil-52. ==> Restart building libavutil-52 ? [y/N]

elecuba commented on 2018-03-31 04:31 (UTC)

gpg --search-keys B4322F04D67658D8

Works!!

Thanks julienrat

elecuba commented on 2018-03-31 04:31 (UTC)

gpg --search-keys B4322F04D67658D8

Works!!

Thanks julienrat

julienrat commented on 2017-04-07 18:37 (UTC)

GPG error just type gpg --search-keys B4322F04D67658D8 solved compilation for me

Muflone commented on 2017-03-05 20:03 (UTC)

Rebuild in a clean root. Just tried again and compiles fine, unflagging out-of-date

debbio commented on 2017-01-30 10:56 (UTC)

Still impossible to compile it

firekage commented on 2016-12-27 10:33 (UTC)

Could not build. Verifying source file signatures with gpg... ffmpeg-2.3.6.tar.bz2 ... FAILED (unknown public key B4322F04D67658D8) ==> ERROR: One or more PGP signatures could not be verified! ==> ERROR: Makepkg was unable to build libavutil-52. ==> Restart building libavutil-52 ? [y/N] Tried to add key, tried to sign it - still cant do.

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

@naraesk the keys is not a random one, is the same key you can find in the PKGBUILD. If that key matches then the source file can be validated with the key itself to guarantee authenticity.

naraesk commented on 2016-10-20 21:00 (UTC)

How does the signing adds security if I have to import a key from a random comment from aur? :)

rjuarezp commented on 2016-10-18 16:22 (UTC)

I solved the problem with: gpg --keyserver pgp.mit.edu --recv-keys FCF986EA15E6E293A5644F10B4322F04D67658D8 Then you can import the key and you don't get the error anymore... I hope it helps...

« First ‹ Previous 1 2 3 Next › Last »