Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at

Bug 1763831

Summary: revert incorrect arm64 <-> aarch64 mapping
Product: [Fedora] Fedora Reporter: Peter Robinson <pbrobinson>
Component: rpmAssignee: Packaging Maintenance Team <packaging-team-maint>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 31CC: awilliam, gmarr, igor.raits, jcm, mattdm, mjw, packaging-team-maint, pasik, pbrobinson, pmatilai, pmoravco, robatino, satellitgo, vmukhame
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: AcceptedFreezeException
Fixed In Version: rpm-4.15.0-6.fc31 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-24 17:10:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 245418, 1644939, 1644940    

Description Peter Robinson 2019-10-21 17:25:34 UTC
We explicitly don't want this in Fedora. rpm uses "uname -m" and we explicitly decided that arm64 would be kept out.

We want this reverted [1] before GA because teams install vanilla installer and never update it, as well as it being on live images and Arm images from the duration of the release. As documented in the upstream PR [2] the commit was for one company and their use of alien in a different distribution. We need to revert this to ensure no support issues for the lifetime of F-31 and any ongoing that may happen until a workable compromise can be agreed upon upstream. The arm64.rpm packages wouldn't be useable on el7/el8 or other Fedora releases which also adds to the support issues.

some what related to rhbz 1691430 



Comment 1 Fedora Blocker Bugs Application 2019-10-21 17:26:27 UTC
Proposed as a Blocker for 31-final by Fedora user pbrobinson using the blocker tracking app because:

 Support issues on a primary architecture

Comment 2 Fedora Update System 2019-10-21 18:13:11 UTC
FEDORA-2019-b674cf1e25 has been submitted as an update to Fedora 31.

Comment 3 Geoffrey Marr 2019-10-21 18:57:20 UTC
Discussed during the 2019-10-21 blocker review meeting: [0]

The decision to delay the classification of this bug as a blocker and to classify this bug as an "AcceptedFreezeException" was made as we accept pbrobinson's contention as ARM lead that this is undesired functionality that we don't want shipped in F31 as it may create a support burden. There is no clear rationale for blocker status but we leave the possibility open for further review at go/no-go meeting depending on how things go this week.


Comment 4 Jon Masters 2019-10-22 13:30:43 UTC
This must not be allowed to ship in Fedora or it will become a permanent problem requiring continual effort to undo.

Comment 5 Jon Masters 2019-10-22 13:40:18 UTC
Here's the comment I added to the upstream issue, for context:

Let me be very, very clear:

The name of the 64-bit Arm architecture state in which 64-bit binaries are executed is - and always has been - "aarch64". There was never an "arm64", nor does it exist. The name "arm64" is also an explicit violation of Arm's trademark policy.

When Arm first created the 64-bit Arm architecture, they explicitly and proactively asked that we (and everyone else) use the name "aarch64" to describe it so that it would not contain a trademarked name, and because it was their architecture to name since they invented it in the first place and did the initial enablement work for toolchains and other prerequisite components for bringup.

There were two categories of responses to this polite and reasonable request:

Those who listened and collaborated to adopt the name of the architecture
Those who did not listen and chose the name "arm64" for other reasons

The name of the architecture is - and always has been - "aarch64". The name "arm64" is not a valid name and it should not be perpetuated simply because some chose to use it instead.

Comment 6 Matthew Miller 2019-10-23 13:49:37 UTC
I sure do wish this had been addressed earlier. However, here we are now.

The rationale from Peter and additional support from Jon are both quite strong. 

I don't think we can ship like this.

If we need to, let's consider pulling the aarch64 images from the GA release and putting them out as an update the following week.

Comment 7 Adam Williamson 2019-10-23 14:50:56 UTC
The change is in the current release candidate, so we should be fine. It'd be good if Peter/Jon can confirm it's as expected:

Comment 8 Peter Robinson 2019-10-23 15:02:25 UTC
(In reply to Adam Williamson from comment #7)
> The change is in the current release candidate, so we should be fine. It'd
> be good if Peter/Jon can confirm it's as expected:

Working to confirm both this and the other blocker ATM

Comment 9 Fedora Update System 2019-10-23 15:44:10 UTC
rpm-4.15.0-5.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report.
See for
instructions on how to install test updates.
You can provide feedback for this update here:

Comment 10 Fedora Update System 2019-10-23 20:27:51 UTC
FEDORA-2019-fec5c2fbb8 has been submitted as an update to Fedora 31.

Comment 11 Fedora Update System 2019-10-24 17:10:00 UTC
rpm-4.15.0-6.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.