paru icon indicating copy to clipboard operation
paru copied to clipboard

paru failes to install AUR package which is successfully installed with yay

Open lem0nify opened this issue 9 months ago • 0 comments

Affected Version

paru v2.0.4 - libalpm v15.0.0

Description

I'm not sure it is bug or not, because my understanding of versioning may be incorrect. But it is still a problem that paru fails to install some packages which yay installs successfully, I think. Anyway correct me if I'm wrong.

Specifically, I'm trying to install shadps4-git. There is a dependency with epoch in its PKGBUILD:

'vulkan-headers>=1:1.4.305'

paru says:

:: Resolving dependencies...
error: could not find all required packages:
    vulkan-headers>=1:1.4.305 (wanted by: shadps4-git)

paru -Ss vulkan-headers currently lists the following packages:

extra/vulkan-headers 1:1.4.304.1-2 [1.34 MiB 28.56 MiB] [Installed: 1:1.4.303-1] (vulkan-devel)
    Vulkan header files and API registry
aur/vulkan-headers-git 1.4.305.r0.ga03d2f6-1 [+7 ~0.00]
    Vulkan header files
aur/mingw-w64-vulkan-headers 1.4.304-1 [+4 ~0.00]
    Vulkan header files (mingw-w64)

So there is an AUR package vulkan-headers-git with version 1.4.305.r0.ga03d2f6-1 and repo package extra/vulkan-headers with version 1:1.4.304.1-2.

As far as I understand, technically, both package versions are <1:1.4.305: first one – due to lack of epoch, second one – because its patch version 303 is less than required 305, so paru is correct in failing to install this package. Or maybe epoch is not applicable to git packages at all? I don't know.

But yay installs it by first fetching vulkan-headers-git from AUR. Should this be fixed somehow in paru or should I notify the author of the shadps4-git AUR package to fix PKGBUILD?

UPD: No, I guess if he removes epoch from the dependency in the PKGBUILD, then paru will be happy with any version with epoch from the repository, which is incorrect.

lem0nify avatar Mar 01 '25 03:03 lem0nify