You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Vespa version 8.334.22 rpm is pointing to non-existing version of packages jllama and onnxruntime
To Reproduce
Steps to reproduce the behavior:
Install Vespa
[root@33a062b3c536 ffuser]# microdnf install -y --nobest vespa-8.334.22
error: Could not depsolve transaction; 1 problem detected:
Problem: package vespa-8.334.22-1.el9.x86_64 from vespa-farfetch-rpm-epel requires vespa-libs = 8.334.22-1.el9, but none of the providers can be installed
- conflicting requests
- nothing provides vespa-jllama = 3.0.0 needed by vespa-libs-8.334.22-1.el9.x86_64 from vespa-farfetch-rpm-epel
- nothing provides vespa-onnxruntime = 1.17.1 needed by vespa-libs-8.334.22-1.el9.x86_64 from vespa-farfetch-rpm-epel
As we can see the only available version is 1.17.3 and not 1.17.1 for onnxruntime and 3.0.1 for jllama
Expected behavior microdnf install -y vespa install Vespa without errors
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
OS: Almalinux
Infrastructure: Docker
Versions: 9.3
Vespa version
8.334.22
The text was updated successfully, but these errors were encountered:
hmusum
changed the title
Unable to install Vespa version 0.334.22, dependencies not found
Unable to install Vespa version 8.334.22, dependencies not found
Apr 29, 2024
Describe the bug
Vespa version 8.334.22 rpm is pointing to non-existing version of packages
jllama
andonnxruntime
To Reproduce
Steps to reproduce the behavior:
onnxruntime
and 3.0.1 forjllama
vespa/dist/vespa.spec
Line 209 in 624c19d
Expected behavior
microdnf install -y vespa
install Vespa without errorsScreenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
Vespa version
8.334.22
The text was updated successfully, but these errors were encountered: