. erlang-etap-0.3.4-14.fc24. erlang-etap-0.3.4-15.fc25. erlang-etap-0.3.4-16.fc26 .
Feb 17, 2017
. erlang-etap-0.3.4-15.fc24 Old package: erlang-etap-0.3.4-14.fc23 . 0ad-0.0.26b-alpha-unix-data.tar.xz
A:
The reason is that the binary was created on a different architecture than the one that you are attempting to install on.
In this case, you can run the architecture you are installing on the same system as the source, or run a wrapper script around dnf/yum that lets you build a binary on the architecture you are installing on, and then install the binary. I do not know how to do this in yum, but you can use dnf for this, you just need to create a file in /etc/dnf.d/ in which you run this:
[universe]
# Uncomment the first line to enable Universe (if you are on a
# Red Hat based distro you do not have to do this because it is
# already enabled)
enabled=1
# To add repos (there are quite a few more that you might want to add,
# check out
# This is the most important to add, since it is a little tricky.
# What you need to do is add a line that says something like:
# [epel]
# name=Epel
# baseurl=
# architecture=arm64
# epel_mirror=mirror.cs.umn.edu
# enabled=1
# when adding the Universe repos.
[universe.us.rpmfusion.org-2]
name=RPM Fusion 2 (armv5)
#baseurl= be359ba680
Related links: