Pacman & yaourt/packer library problems? (specific: amarok and x265)

Question

(Sorry for the [RET])
Hello,
First the error:
amarok: error while loading shared libraries: libx265.so.21: cannot open shared object file: No such file or directory
There is /usr/lib/libx265.so, so.1.1 and so.25
pkgfile says that the owner is extra/x265.
I went to ARM and download the package x265 from July (who has libx265.so.21) and then, the error is related to qdbus.
I have completely upgraded everything (Syyu).
If I go to other computer, I can see how amarok is working with libx265.so.21 (but it is true that has no the latest packages, just some of them like amarok).
Question a) (question focused just in repairing amarok)
How to solve this?
- NOTE: Amarok is repaired (needed to compile from sources). But the question below is still open.
Question b) (trying to understand the problem)
It is possible that because I built ffmpeg-full (AUR) and it compiled many libraries, has something unsync with pacman and now pacman says: "hey, everything is up to date", but amarok complains, and it does not matter that I have rebuilt amarok and x265 but the problem persists?. I see (-Si) that amarok depends on ffmpeg.
I would like to know how can I combine multiple libraries at the same time (like x265.so.21 and x265.so.25) but not manually (downloading, moving packages), like: pacman "--parallel-deps" amarok. And everything is done (maybe this is too easy).
Last edited by Zzipo (2014-08-13 18:16:50)

Answer 1

Zzipo wrote:
Thank you for your ideas:
a) Amarok is in the latest build (2.0.8-3) (I did -Syyu to be sure when the problems started). -> Maybe is in this point where the maintainer of Amarok forgot/got busy.
b) I have another PC with the same build version and different mirrors.
Let's suppose the next:
- State 0: I build from sources ffmpeg, that it builds x265 too. I got ffmpeg v2 and x265 v2 (let's suppose).
- State 1: I do (-Syyu) and install from binaries amarok -> it needs ffmpeg and x265, but It finds in the system (although it a newer version than the amarok dependency). It installs correctly. I run it and I get problems because amarok (v5 for example) depends upon ffmpeg v1 and x265 v1.
I think I get what you mean here. You build the source using a PKGBUILD, right? Now, as we are assuming things, let's assume that we are working with the actual archlinux repositories. If there are dependency conflicts in the repositories, this is something to report to the bugtracker as all software in there should work. So, amarok needing ffmpeg v1 while only v2 is in the repository is something that the maintainer needs to look into.
In short: What you describe is not supposed to happen in the actual arch repositories.
Now, if we add in the AUR things become different. With the aur we can get these rather annoying dependency conflicts. The usual way to resolve these is (using your example) to make a seperate package for ffmpeg and x265 version 1 (conveniently named ffmpeg1 and x265_1 for example). The next step is then to make amarok depend on these 2 packages. As mentioned before, for the official repos you can take a look at how things are done with python v3 and python v2. In the AUR there are also numerous examples of older software, like gcc.
Zzipo wrote:I have seen previous times that when I do yaourt ----> It can fetch another package at the same time (like x265.so.21) and  x265.so.25 with pacman. I was just expecting some sort of good approach to deal with this problem.
I assume that this means that they used the trick I just described. Also, the sentence makes me think that you maybe lack a bit of understanding about the workings of the AUR and the build process in general. Did you read the wiki pages about the AUR and makepkg before trying to use the AUR?
Last edited by runical (2014-08-13 20:46:50)