Search Criteria
Package Details: lib32-x265 1:4.0-5
Package Actions
Git Clone URL: | https://aur.archlinux.org/lib32-x265.git (read-only, click to copy) |
---|---|
Package Base: | lib32-x265 |
Description: | Open Source H265/HEVC video encoder. 32bit libraries. |
Upstream URL: | https://bitbucket.org/multicoreware/x265_git |
Licenses: | GPL |
Provides: | libx265.so |
Submitter: | llde |
Maintainer: | unit73e |
Last Packager: | unit73e |
Votes: | 12 |
Popularity: | 0.083454 |
First Submitted: | 2017-08-24 18:30 (UTC) |
Last Updated: | 2025-04-22 21:36 (UTC) |
Dependencies (6)
- lib32-gcc-libs (lib32-gcc-libs-gitAUR, lib32-gccrs-libs-gitAUR, lib32-gcc-libs-snapshotAUR)
- lib32-libnumaAUR
- x265 (x265-gitAUR, x265-mod-patman-gitAUR)
- cmake (cmake-gitAUR, cmake3AUR) (make)
- git (git-gitAUR, git-glAUR) (make)
- nasm (nasm-gitAUR) (make)
Required by (19)
- avidemux-core-git (requires libx265.so)
- avidemux-qt5-git (requires libx265.so)
- avidemux-qt6-git (requires libx265.so)
- emby-server-beta (requires libx265.so)
- ffmpeg-ffplayout (requires libx265.so)
- ffmpeg-headless (requires libx265.so)
- ffmpeg-libfdk_aac (requires libx265.so)
- ffmpeg-nvcodec-11-1-git (requires libx265.so)
- ffmpeg2.8 (requires libx265.so)
- ffmpeg6.1 (requires libx265.so)
- lib32-ffmpeg
- lib32-gst-libav (make)
- lib32-gst-plugins-bad
- lib32-gst-plugins-bad (make)
- lib32-gst-plugins-bad-git
- lib32-gst-plugins-bad-libs (make)
- lib32-gst-plugins-ugly (make)
- lib32-libheif (make)
- lib32-libheif (optional)
Latest Comments
1 2 3 4 5 Next › Last »
AmbassadorDave commented on 2025-04-23 22:05 (UTC)
@unit73e thank you kindly, the package installed just fine with your fix applied!
unit73e commented on 2025-04-22 21:40 (UTC)
@AmbassadorDave confirmed and fixed. just adding the
--no-commit
to cherry pick solves the problem.No. They can use the old binary. It's the same thing, this update just fixes the cmake4 problems.
@vitaliikuzhdin having checked the documentation a higher version with same epoch, wins. it's in pacman(8) manual. as you mentioned the epoch cannot go back anymore, it will stay 1 forever. At least until I or someone else messes up again and becomes 2.
AmbassadorDave commented on 2025-04-22 21:13 (UTC) (edited on 2025-04-22 21:13 (UTC) by AmbassadorDave)
Quite appreciative of your efforts, unit73e on maintaining this package, thank you. In updating to this latest version, I received a failure due to git requesting user.email & user.name which the system auto-detect was unable to populate:
I do have github credentials, yet have never needed to set them system-wide before. Others using this package may not have them at all. Are they now required to install/update lib32-x265?
vitaliikuzhdin commented on 2025-04-20 21:53 (UTC)
@unit73e, I just noticed we are building from a git repo, which allows for a cleaner solution. I edited my message just a minute before you replied, so you probably didn't see it. If you want, you can update the PKGBUILD to use
git cherry-pick
without updating thepkgrel
, but it's just cosmetic at this point.Also, it doesn't hurt, but there is no need to increase the
pkgrel
when you increase theepoch
.Thank you for your very quick responses.
unit73e commented on 2025-04-20 21:53 (UTC)
@vitaliikuzhdin ok lets make it cleaner with a cherry pick and use `${url} instead of $url. Final version, I think.
unit73e commented on 2025-04-20 21:45 (UTC)
@vitaliikuzhdin yes cmake3 was still there. Need to pay more attention, good catch.
Now it should work with cmake4, and it's also a little bit more clean with a url variable and all options are in their own line. I think this is it. Btw I left it with
source+=
just because it was slightly prettier than a giant line, but with a variable it's ok.vitaliikuzhdin commented on 2025-04-20 21:29 (UTC) (edited on 2025-04-20 21:43 (UTC) by vitaliikuzhdin)
@unit73e, you need to add
epoch=1
to ensure everyone updates. Do not remove it with the next version; it can only be increased.Also, the current PKGBUILD is still mistakenly using
cmake3
; you have probably forgotten to change that back.Additionally, I somehow missed the fact that we are building from a git repo. In this case, it is probably easier not to add the patch to the sources and just use something like this:
unit73e commented on 2025-04-20 21:23 (UTC)
@sl1pkn07 fixed. now it's 4.0-2. Unfortunately that means whoever updated to 4.1 needs to downgrade manually. Thanks for noticing, I forgot to undo my update version experiment.
@vitaliikuzhdin your suggestion was clever and worked very well. It's compatible with cmake4 now.
unit73e commented on 2025-04-20 21:12 (UTC)
@sl1pkn07 because I messed up. I'll fix it with cmake4 if possible.
1 2 3 4 5 Next › Last »