Bug 2329061 - wasmedge: rebuild against llvm 18
Summary: wasmedge: rebuild against llvm 18
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: wasmedge
Version: epel9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Carl George 🤠
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-11-26 23:02 UTC by Carl George 🤠
Modified: 2024-12-05 02:02 UTC (History)
2 users (show)

Fixed In Version: wasmedge-0.14.0-2.el8 wasmedge-0.14.0-2.el9
Clone Of:
Environment:
Last Closed: 2024-12-05 00:31:51 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Carl George 🤠 2024-11-26 23:02:16 UTC
Description of problem:
In EPEL 8 and EPEL 9, wasmedge is linked against libLLVM-17.so.  The latest version of llvm-libs provides libLLVM-18.so.  To avoid installation problems, wasmedge needs to be rebuilt.


Version-Release number of selected component (if applicable):
wasmedge-0.14.0-1.el8
wasmedge-0.14.0-1.el9


How reproducible:
always


Steps to Reproduce:
1. dnf install llvm-libs wasmedge


Actual results:
Error: 
 Problem: cannot install both llvm-libs-18.1.8-3.el9.x86_64 from rhel-9-for-x86_64-appstream-rpms and llvm-libs-17.0.6-5.el9.x86_64 from rhel-9-for-x86_64-appstream-rpms
  - package wasmedge-0.14.0-1.el9.x86_64 from epel requires libLLVM-17.so()(64bit), but none of the providers can be installed
  - package wasmedge-0.14.0-1.el9.x86_64 from epel requires libLLVM-17.so(LLVM_17)(64bit), but none of the providers can be installed
  - cannot install the best candidate for the job
  - conflicting requests


Expected results:
successful installation of wasmedge with the latest llvm-libs


Additional info:
This is actually installable on RHEL 8 because llvm-compat-libs (17) is present and parallel installable with llvm-libs (18), but it would still be best to link against the latest soname.  It does not appear that RHEL 9 has the compat package.

Comment 1 Fedora Update System 2024-11-26 23:26:33 UTC
FEDORA-EPEL-2024-81c62b0832 (wasmedge-0.14.0-2.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-81c62b0832

Comment 2 Fedora Update System 2024-11-26 23:26:34 UTC
FEDORA-EPEL-2024-f8c70c454f (wasmedge-0.14.0-2.el8) has been submitted as an update to Fedora EPEL 8.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-f8c70c454f

Comment 3 Fedora Update System 2024-11-27 02:42:05 UTC
FEDORA-EPEL-2024-f8c70c454f has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-f8c70c454f

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 4 Fedora Update System 2024-11-27 03:27:35 UTC
FEDORA-EPEL-2024-81c62b0832 has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-81c62b0832

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2024-12-05 00:31:51 UTC
FEDORA-EPEL-2024-f8c70c454f (wasmedge-0.14.0-2.el8) has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 6 Fedora Update System 2024-12-05 02:02:21 UTC
FEDORA-EPEL-2024-81c62b0832 (wasmedge-0.14.0-2.el9) has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.