Package Details: lib32-ffmpeg 2:7.0.1-1

Git Clone URL: https://aur.archlinux.org/lib32-ffmpeg.git (read-only, click to copy)
Package Base: lib32-ffmpeg
Description: Complete solution to record, convert and stream audio and video (32 bit)
Upstream URL: http://ffmpeg.org
Licenses: GPL-3.0-only
Conflicts: lib32-libffmpeg
Provides: libavcodec.so, libavdevice.so, libavfilter.so, libavformat.so, libavutil.so, libpostproc.so, libswresample.so, libswscale.so
Replaces: lib32-libffmpeg
Submitter: lano1106
Maintainer: oxalin
Last Packager: oxalin
Votes: 37
Popularity: 0.041180
First Submitted: 2013-05-18 04:43 (UTC)
Last Updated: 2024-08-03 20:23 (UTC)

Required by (292)

Sources (2)

Pinned Comments

oxalin commented on 2024-04-09 22:05 (UTC)

For those wondering: I intentionally keep this package as close to the native package as possible, to the extent of the available dependencies. FFMPEG package sees a lot of modifications through time and I prefer to follow the changes applied to the native PKGBUILD as much as possible. The more it goes, the more flags are added and the more often we need to cherrypick commits (until a new release comes in).

This means I'll keep the dependencies around even if there is no obvious usecase for them.

Also, since openjpeg2 is still used with the native package, I'll also keep it around. Last thing I read about the JPEG2000 internal decoder was that it was faster, but that it was still introducing errors in the rendering. This probably explains why it is still enable in the native package. I look at it once in a while and things may have evolved since, but a quick checkup didn't bring up any tangible answer.

Now, if someone would like to take the ownership of this package, I would be more than pleased to hand it over. The same goes for any related packages that I maintain mostly for FFMPEG. lib32-libffmpeg and lib32-ffmpeg could be merged back together to simplify its maintenance.

Let me know if this is something you're interested in.

oxalin commented on 2018-02-25 07:37 (UTC) (edited on 2020-05-25 15:55 (UTC) by oxalin)

About GPG, it is up to you to import the missing public key. If you receive an error about it, this is ffmpeg's project public key. Something like the following should do the trick: gpg --recv-keys B4322F04D67658D8

Latest Comments

« First ‹ Previous 1 .. 11 12 13 14 15 16 17 18 19 20 21 Next › Last »

oxalin commented on 2018-03-06 06:04 (UTC)

Thanks for your test. I was about to ask to the lib32-libx264 (and also possibly the libx264) maintainer to have a look on his side. You give me a valid argument.

DarkPhoenixFF4 commented on 2018-03-05 00:12 (UTC)

Just to let you know, the problem seems to be with lib32-libx264, not this package. I removed the dependency on lib32-ffmpeg it had and built it manually with no problems.

oxalin commented on 2018-02-25 09:10 (UTC)

@TemplarGR and @SteelTitanium: well, there was a circular dependency that I read about, but it was from 2014. From your comments, I've been digging again and I found out yesterday that there is a new problem about a circular dependency. I'll investigate it further.

oxalin commented on 2018-02-25 07:37 (UTC) (edited on 2020-05-25 15:55 (UTC) by oxalin)

About GPG, it is up to you to import the missing public key. If you receive an error about it, this is ffmpeg's project public key. Something like the following should do the trick: gpg --recv-keys B4322F04D67658D8

TemplarGR commented on 2018-02-24 12:30 (UTC)

There is an error when trying to build this package, it depends on lib32-libx264, yet lib32-libx264 depends on lib32-ffmpeg. I suppose someone who is just updating any of those 2 shouldn't face any issue, but anyone doing a fresh install will encounter this cyclical dependency. The fun part is that lib32-libx264 no longer shows up when searhing for it here (so i couldn't find its maintainer to ask), yet yaourt and packer find the pkgbuild...

oxalin commented on 2018-02-23 18:52 (UTC)

@SteelTitanium: you "can't". In fact, from what I have read on x264 forum, libx264 (the library itself) doesn't depend on ffmpeg. However, x264 have an optional dependency at build time against ffmpeg. Now, that being said, are you getting an error while trying to install the current package?

SteelT commented on 2018-02-19 23:56 (UTC) (edited on 2018-02-19 23:57 (UTC) by SteelT)

How do you break the dependency cycle, lib32-ffmpeg depends on lib32-libx264 and lib32-libx264 depends on lib32-ffmpeg.

oxalin commented on 2017-12-17 21:22 (UTC)

@unknown78: nothing changed since last version except version number and sha256sum.

The first step executed in the build() step is configure, which can take a moment to process. However, it should move to the next step, which is "make".

Could you restart your system and see if that helps if you didn't try it yet?

unknown78 commented on 2017-12-16 09:11 (UTC)

The last minor update seems to break something. makepkg -si output: LC_ALL=C makepkg ==> Making package: lib32-ffmpeg 1:3.4.1-1 (Sat Dec 16 10:08:16 CET 2017) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Downloading ffmpeg-3.4.1.tar.bz2... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 9938k 100 9938k 0 0 1419k 0 0:00:07 0:00:07 --:--:-- 1637k -> Downloading ffmpeg-3.4.1.tar.bz2.asc... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 473 100 473 0 0 473 0 0:00:01 --:--:-- 0:00:01 5255 ==> Validating source files with sha256sums... ffmpeg-3.4.1.tar.bz2 ... Passed ffmpeg-3.4.1.tar.bz2.asc ... Skipped ==> Verifying source file signatures with gpg... ffmpeg-3.4.1.tar.bz2 ... Passed ==> Extracting sources... -> Extracting ffmpeg-3.4.1.tar.bz2 with bsdtar ==> Starting build()...

and than nothing more happens.

« First ‹ Previous 1 .. 11 12 13 14 15 16 17 18 19 20 21 Next › Last »