Bug 2055732 - boinc-client not available for aarch64 in EPEL
Summary: boinc-client not available for aarch64 in EPEL
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: boinc-client
Version: epel8
Hardware: aarch64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Germano Massullo (Thetra)
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-17 15:28 UTC by c.stackpole
Modified: 2022-02-27 04:08 UTC (History)
3 users (show)

Fixed In Version: boinc-client-7.16.11-9.el8
Clone Of:
Environment:
Last Closed: 2022-02-27 04:08:13 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description c.stackpole 2022-02-17 15:28:17 UTC
Description of problem:
boinc-client is not available on aarch64 systems. Per the following commit it is because webkit2gtk3 is missing:
https://src.fedoraproject.org/rpms/boinc-client/c/ce665e0e2c6d13c9648694568f80998a7c5e43e2?branch=rawhide

However, I see that as available now in appstream.

$ dnf info webkit2gtk3
Available Packages
Name         : webkit2gtk3
Version      : 2.32.3
Release      : 2.el8
Architecture : aarch64
Size         : 15 M
Source       : webkit2gtk3-2.32.3-2.el8.src.rpm
Repository   : appstream
Summary      : GTK Web content engine library
URL          : http://www.webkitgtk.org/
License      : LGPLv2
Description  : WebKitGTK is the port of the portable web rendering engine WebKit to the
             : GTK platform.
             : 
             : This package contains WebKit2 based WebKitGTK for GTK 3.
$ dnf search webkit2gtk3
== Name Exactly Matched: webkit2gtk3 ==
webkit2gtk3.aarch64 : GTK Web content engine library
== Name & Summary Matched: webkit2gtk3 ==
webkit2gtk3-devel.aarch64 : Development files for webkit2gtk3
webkit2gtk3-jsc.aarch64 : JavaScript engine from webkit2gtk3
webkit2gtk3-jsc-devel.aarch64 : Development files for JavaScript engine from webkit2gtk3
$

Is there still a reason to not include boinc-client? Or can this limitation be removed?

How reproducible:
Always

Steps to Reproduce:
1. dnf search boinc

Actual results:
On a aarch64 EL8 system with EPEL -
$ sudo dnf search boinc
== Name & Summary Matched: boinc ==
boinc-tui.aarch64 : Fullscreen Text Mode Manager For BOINC Client
$

Expected results:
On a x86_64 EL8 system with EPEL - 
$ sudo dnf search boinc
== Name & Summary Matched: boinc ==
boinc-client.x86_64 : The BOINC client
boinc-client-devel.x86_64 : Development files for boinc-client
boinc-client-doc.noarch : Documentation files for boinc-client
boinc-client-static.x86_64 : Static libraries for boinc-client
boinc-manager.x86_64 : GUI to control and monitor boinc-client
boinc-tui.x86_64 : Fullscreen Text Mode Manager For BOINC Client
$


Additional info:

Comment 1 c.stackpole 2022-02-17 16:29:15 UTC
I can confirm. Pulled the src.rpm for boinc-client, extracted with rpmbuild, edited the SPEC to remove aarch64 from the exclude list, and ran `rpmbuild -ba boinc-client.spec`. After installing all the devel dependencies it built just fine and I'm running the boinc-client now on aarch64.

I do not see a reason for why aarch64 is still excluded from the build architecture for boinc-client.

Can someone please confirm my findings, and then remove the exclude?

Thanks!

Comment 2 Fedora Update System 2022-02-18 08:56:47 UTC
FEDORA-EPEL-2022-8f6b47abcf has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-8f6b47abcf

Comment 3 Fedora Update System 2022-02-19 02:40:18 UTC
FEDORA-EPEL-2022-8f6b47abcf 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-2022-8f6b47abcf

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

Comment 4 Fedora Update System 2022-02-27 04:08:13 UTC
FEDORA-EPEL-2022-8f6b47abcf has been pushed to the Fedora EPEL 8 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.