Arch Linux

AGT

Member

From: Null Void

Registered: 2012-10-27

Posts: 59

Website

Solved: AUR/x265-10bit Conflict with the Official x265 During Upgrades

Hello.

I installed x265-10bit from the AUR, but during some 'pacman -Syu' upgrades, there is a conflict:

resolving dependencies...
looking for conflicting packages...
:: x265 and x265-10bit are in conflict. Remove x265-10bit? [y/N] n
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: x265 and x265-10bit are in conflict

I use 'pacman -Syudd' to ignore the dependency requirements.

I notice that x265-10bit has provides=('x265'), and I even added provides=('x265' 'libx265.so') as user hdrn commented on the AUR page, but the conflict is still there.
Shouldn't the 'provides' resolve this conflict, and not require pacman to make x265 a dependency? I assume that other packages need x265 (because if I remember correctly, I also removed x265, initially, by ignoring dependencies), and I expect that x265-10bit virtually provides that package.

How can I make pacman consider that x265 is installed?

And a side question: what is the difference between x265-10bit and x265-hg from the AUR?

Thank you!

Last edited by AGT (2015-06-18 21:31:55)

Soukyuu

Member

Registered: 2014-04-08

Posts: 854

Re: Solved: AUR/x265-10bit Conflict with the Official x265 During Upgrades

I think what happens is that a "provides" in itself is not enough. If a package requires a specific version of x265, it will fail because "provides" doesn't specify the version. Look here

---

[ Arch x86_64 | linux | Framework 13 | AMD Ryzen™ 5 7640U | 32GB RAM | KDE Plasma Wayland ]

AGT

Member

From: Null Void

Registered: 2012-10-27

Posts: 59

Website

Re: Solved: AUR/x265-10bit Conflict with the Official x265 During Upgrades

It says that x265-10bit depends on x265:
I find that rather strange.
It seems that there are no (other) packages which depend on x265.

> whoneeds x265
Packages that depend on [x265]
comm: file 2 is not in sorted order
  x265-10bit

> pactree -r x265
x265-10bit provides x265

I also noticed that the PKGBUILD for x265-10bit contains '_pkgname=x265'. What is '_pkgname' used for, versus 'pkgname'?

I did check the wiki before, but I didn't find anything explicit mentioning dependency requirements: does 'provides' make it the same as if packages which are listed in this array are installed?

Thaks you.

Last edited by AGT (2015-06-18 19:36:31)

Soukyuu

Member

Registered: 2014-04-08

Posts: 854

Re: Solved: AUR/x265-10bit Conflict with the Official x265 During Upgrades

It does not say that x265-10bit depends on x265 in the PKGBUILD. Only that it conflicts with it, which is a given, because it provides x265.
I don't know what the "whoneeds" command is, nor which package it is from. But attempting to install that package gives me

error: failed to prepare transaction (could not satisfy dependencies)
:: ffmpeg: requires libx265.so=59-64

So there you have it - ffmpeg requires a specific version and x265-10bit doesn't provide it - at least on my system. If ffmpeg is one of the packages you're updating, you could try installing ffmpeg-git

As for your side question: x265-hg is a mercury based package, just like -git is a git based package.

edit: also, try using pacman -Qi x265, this also tells me that ffmpeg depends on it:

pacman -Qi x265
Name           : x265
Version        : 1.7-1
Description    : Open Source H265/HEVC video encoder
Architecture   : x86_64
URL            : https://bitbucket.org/multicoreware/x265
Licenses       : GPL
Groups         : None
Provides       : libx265.so=59-64
Depends On     : gcc-libs
Optional Deps  : None
Required By    : ffmpeg
Optional For   : None
Conflicts With : None
Replaces       : None
Installed Size :   3.86 MiB
Packager       : Bartłomiej Piotrowski <bpiotrowski@archlinux.org>
Build Date     : So 07 Jun 2015 12:16:51 CEST
Install Date   : Mo 08 Jun 2015 19:33:17 CEST
Install Reason : Installed as a dependency for another package
Install Script : No
Validated By   : Signature

Last edited by Soukyuu (2015-06-18 19:50:32)

---

[ Arch x86_64 | linux | Framework 13 | AMD Ryzen™ 5 7640U | 32GB RAM | KDE Plasma Wayland ]

AGT

Member

From: Null Void

Registered: 2012-10-27

Posts: 59

Website

Re: Solved: AUR/x265-10bit Conflict with the Official x265 During Upgrades

pacman shows that there are no packages which need x265-10bit:

> pacman -Qi x265-10bit
...
Required By    : None
...

I'm installing x265 and removing x265-10bit to see if x265 is needed instead.

whoneeds is provided by pkgtools to list packages dependent on an installed one: Arch Wiki / pacman # Querying Package Databases.

Last edited by AGT (2015-06-19 01:49:50)

AGT

Member

From: Null Void

Registered: 2012-10-27

Posts: 59

Website

Re: Solved: AUR/x265-10bit Conflict with the Official x265 During Upgrades

I replaced AUR/x265-10bit by x265, and:

> pacman -Qi x265
...
Required By    : ffmpeg
...

...as you said. I guess that was the problem: ffmpeg needed x265.
I am planning on using a custom x265 package (with a high bit support) from now on.

Thank you for your help!

AGT

Member

From: Null Void

Registered: 2012-10-27

Posts: 59

Website

Re: Solved: AUR/x265-10bit Conflict with the Official x265 During Upgrades

But wouldn't that mean that provides doesn't do what it should: have pacman consider that the packages listed in that array are installed?
That is what provides should do, in my opinion.
The wiki says "packages that the software provides the features of". I assume that it also means that those packages are considered to be installed, because, otherwise, a package cannot provide its features without being installed.
I would like to have pacman consider these provides packages as being installed.
Unless my system was malfunctioning, and pacman is already doing this, but not on my system...

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 21,754

Re: Solved: AUR/x265-10bit Conflict with the Official x265 During Upgrades

I think you'll only need libx265.so in the provides line without the libx265, since this is what the actual file is that is being searched for by ffmpeg's requires line. The AUR pkg is orphaned so it hasn't been updated to conform this, if you have a vested interest for high bit support you can consider taking the package over, and updating its version (currently 1.6 and the arch package is at 1.7) and I think the 1.7 version discrepancy might be the root issue here

Last edited by V1del (2015-06-19 10:32:33)

dwidmann

Member

From: Gordonsville, Virginia, US

Registered: 2009-05-27

Posts: 60

Re: Solved: AUR/x265-10bit Conflict with the Official x265 During Upgrades

The only difference between the 8-bit and 10-bit build should be whether or not you specify "-DHIGH_BIT_DEPTH=1" option to cmake before you build. Just add this to the PKGBUILD from ABS and you should be okay.

---

"I refuse to be part of a society that encourages the rampant abuse of its own language." ~ BM