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 bugzilla.redhat.com.

Bug 2000853

Summary: Missing aarch64 flatpaks
Product: [Fedora] Fedora Container Images Reporter: Stanislav Graf <sgraf>
Component: flatpak-build-baseAssignee: Kalev Lember <klember>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: klember, mark, otaylor, pbrobinson
Target Milestone: ---Keywords: Reopened, Tracking
Target Release: ---   
Hardware: aarch64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-11-19 16:05:22 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:
Embargoed:
Bug Depends On:    
Bug Blocks: 245418    

Description Stanislav Graf 2021-09-03 07:51:28 UTC
Description of problem:

Flatpak offers on aarch64 Fedora Workstation flatpaks from fedora registry:
~~~
$ flatpak remote-ls
Name                                  Application ID                           Version                                             Branch       Arch
Dconf Editor                          ca.desrt.dconf-editor                    3.38.3                                              stable       aarch64
..
~~~

but they are not available:
~~~
$ flatpak install org.gnome.Sudoku
Looking for matches…
Found similar ref(s) for ‘org.gnome.Sudoku’ in remote ‘fedora’ (system).
Use this remote? [Y/n]: y
error: The application org.gnome.Sudoku/aarch64/stable requires the runtime org.fedoraproject.Platform/aarch64/f34 which was not found
~~~

Version-Release number of selected component (if applicable):
flatpak-1.10.2-4.fc34.aarch64

How reproducible:
100%

Steps to Reproduce:
1. $ flatpak remote-add --if-not-exists fedora oci+https://registry.fedoraproject.org
2. $ flatpak remote-ls
3. $ flatpak install org.gnome.Sudoku

Actual results:
aarch64 flatpak offered, but not available

Expected results:
aarch64 flatpak offered and available

Additional info:

Comment 1 Kalev Lember 2021-09-03 08:21:48 UTC
We are missing flatpak runtime builds for aarch64. Individual app flatpaks are (super confusingly) already available for aarch64, but they cannot be installed because the runtime is missing.

I'm planning on looking into this soon.

Comment 2 Ben Cotton 2022-05-12 16:53:01 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 3 Ben Cotton 2022-06-08 06:24:51 UTC
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 4 Kalev Lember 2022-11-19 16:05:22 UTC
This was fixed more than a year ago.