Hi
why is splitted? this is arch, no ubuntu
greetings
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.015167 |
First Submitted: | 2013-05-18 04:43 (UTC) |
Last Updated: | 2024-09-27 17:48 (UTC) |
« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 15 16 .. 21 Next › Last »
Hi
why is splitted? this is arch, no ubuntu
greetings
@oxalin I'm on Manjaro, so I think that is the issue. I had to match the 64 bit packages that were installed. Once those get updated it shouldn't be an issue anymore.
@inverimus : I don't have any problem building with the x265 3.4 and aom 2.0. Without any log of your build process, I would be tempted to think that your system's arch packages (64 bit) were not updated to the same versions as your multilib packages (32 bit). Could you make sure both 32 amd 64 bit packages are at the same version before building lib32-ffmpeg packages?
Everything from packages_*'s depends must also be on makedepends, otherwise makepkg -s
doesn't see all dependencies.
You don't need to add extra depends or a global depends, just expose them in makedepends.
This still fails to build for me without manually reverting lib32-x265 to version 3.3. Not sure if anything can be done about that.
EDIT: Also had to downgrade lib32-aom to v1.0.0-errata1-avif.
From ArchWiki (https://wiki.archlinux.org/index.php/PKGBUILD#Dependencies) "depends An array of packages that must be installed for the software to build and run. Dependencies defined inside the package() function are only required to run the software."
I'll need to move some dependencies outside of the package so they can be grabbed by "makepkg -s".
About lib32-x264: I had news from the ex-maintainer. It seems they were flagged as orphane almost a year ago. He has no explanation on why the package would have been deleted. I took the ownership and the package is now available once again.
@DDoSolitary : is the error limited to lib32-ffmpeg or both? Maybe some dependencies (or all) need to be in the general section of PKGBUILD to be honored? I'll have a look at it.
As a follow up on the deletion of lib32-x264, I haven't heard back from the previous maintainer. So I'm considering reverting the package's deletion. I'm not sure if there is an official way of doing it (I'll ask on the mailing list).
I'm unable to build this package with makepkg -s -r
in a clean environment. (In my case the missing lib32-x264 package isn't an issue for now because I've built it and uploaded it to my personal repo before)
Error message:
ERROR: gmp not found
It seems that the dependencies specified in the split package functions won't be installed automatically by makepkg -s
. I'm not sure about what's the correct way of fixing this, but probably adding required build-time dependencies to makedepends will work.
lib32-x264 dependency: I'm investigating why the package was deleted. There is no trace in aur-requests mailing list that could explain its deletion. I contacted the maintainer earlier today. I'll let you know as soon as possible. If needed, I'll recreate lib32-x264 package and maintain it.
@programegg : that's annoying. I'll see what is going on with it. Last commit (when accessing its git repository) was June 6th 2020. I was able to retrieve the PKGBUILD if for any reason we need to recreate it.
That being said, this could be because the package is being moved elsewhere (multilib). So I'll wait a bit and come back later.
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