Incorrect error message if versioned dependency from repository not satisfied

[homocomputeris]

Pikaur v1.3.0.3
Pacman v5.1.1 - libalpm v11.0.

Is there an option in Pikaur to get deps for an AUR package from the official repos?

Attached log:

pikaur -S python-numba
LC_ALL=en_US pikaur -S python-numba
Reading repository package databases...
Reading local package database...
Resolving AUR dependencies...
:: error: Dependencies missing for python-llvmlite
:: warning: Following package cannot be found in AUR:
    llvm    

[actionless]

that's because python-llvmlite require llvm 6 but in repos is llvm7 but error message is indeed not correct

[homocomputeris]

OK, I see, thanks. Formally, though, it seems to be able to resolve the dependency with versions above 6 too:

llvm<6.1.0 (llvm-assert, llvm-pypy-stm, llvm-polly-svn, llvm39, llvm-svn, clang-trunk, llvm38)
llvm>=6.0.0 (llvm-assert, llvm-pypy-stm, llvm-polly-svn, llvm39, llvm-svn, clang-trunk, llvm38)

[actionless]

?

llvm38: Provides: llvm=3.8.1-5

[homocomputeris]

Oops, sorry. It needs LLVM above 6, but below 6.1.

[actionless]

but also AUR search for "Provides" field is not implemented in AUR API: https://github.com/actionless/pikaur/issues/53

[actionless]

is that still reproduciable with any other packages?

i think now the message should be:

$ pikaur -P
Reading local package database...
Resolving AUR dependencies...
Reading repository package databases...
:: error: Can't resolve dependencies for AUR package 'mypkgname':
Version mismatch:
mypkgname depends on: 'llvm-libs>=4.0.0,llvm-libs<5.1.0'
 found in 'PackageSource.REPO': '9.0.1-1'

[homocomputeris]

Well, it resolves deps from AUR:

$ LC_ALL=en_US pikaur -S python-numba
[sudo] password for nik: 
Reading repository package databases...
Reading local package database...
Resolving AUR dependencies...

:: New dependencies will be installed from repository:
 cmake (for llvm8-libs, llvm8)                    -> 3.16.5-1
 ninja (for llvm8-libs, llvm8)                    -> 1.10.0-1
 python-babel (for python-sphinx)                 -> 2.8.0-4
 python-commonmark (for python-recommonmark)      -> 0.9.1-1
 python-docutils (for python-commonmark, python-sphinx, python-recommonmark)    -> 0.14-4
 python-future (for python-commonmark)            -> 0.18.2-2
 python-imagesize (for python-sphinx)             -> 1.2.0-1
 python-pytz (for python-babel)                   -> 2019.3-3
 python-recommonmark (for llvm8-libs, llvm8)      -> 0.6.0.194.48f9d1a-2
 python-snowballstemmer (for python-sphinx)       -> 2.0.0-3
 python-sphinx (for python-recommonmark, llvm8-libs, llvm8)    -> 2.4.4-1
 python-sphinx-alabaster-theme (for python-sphinx)    -> 0.7.12-3
 python-sphinxcontrib-applehelp (for python-sphinx)    -> 1.0.2-1
 python-sphinxcontrib-devhelp (for python-sphinx)    -> 1.0.2-1
 python-sphinxcontrib-htmlhelp (for python-sphinx)    -> 1.0.3-1
 python-sphinxcontrib-jsmath (for python-sphinx)    -> 1.0.1-4
 python-sphinxcontrib-qthelp (for python-sphinx)    -> 1.0.3-1
 python-sphinxcontrib-serializinghtml (for python-sphinx)    -> 1.1.4-1
 rhash (for cmake)                                -> 1.3.9-1

:: AUR package will be installed:
 python-numba                                     -> 0.48.0-1

:: New dependencies will be installed from AUR:
 llvm8 (for python-llvmlite)                      -> 8.0.1-2
 llvm8-libs (for llvm8, python-llvmlite)          -> 8.0.1-2
 python-llvmlite (for python-numba)               -> 0.31.0-1

:: Proceed with installation? [Y/n] 
:: [v]iew package details   [m]anually select packages

Repos now have LLVM 9.

[deraffe]

Stumbled upon this while trying to build linphone-desktop while not all of the dependencies have been updated.

One of the (many) dependencies is belle-sip, which is currently at 4.4.13-1 in the AUR. This depends on bctoolbox=4.4.13, but the bctoolbox in the community repo has already been updated to 4.4.21-1, so it fails with:

:: error: Can't resolve dependencies for AUR package 'belle-sip':
Version mismatch:
belle-sip depends on: 'bctoolbox=4.4.13'
 found in 'PackageSource.REPO': '4.4.21-1'

~Not even building an old version of bctoolbox and installing it locally seems to work around this.~ That actually works when you install the correct version – which isn't easy, because lime has been updated to yet another path release that requires yet another version of bctoolbox. /o\

[actionless]

@deraffe 1) that's expected behavior 2) and not related to the issue above