Bug 1401215

Summary: Configure flatpak to provide all "stable runtimes" (or at least the org.freedesktop ones or another sane subset) to make install of standard flatpaks easier
Product: [Fedora] Fedora Reporter: ell1e <el>
Component: flatpakAssignee: David King <amigadave>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 25CC: amigadave
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-12 10:56:39 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:

Description ell1e 2016-12-03 14:45:13 UTC 
Description of problem:
Right now, I went through the following steps to install a flatpak:

1. Read the man page and see "install" and try this: flatpak install ./my-flatpak.flatpak
2. I notice it doesn't work. It takes me a while to find out the --bundle option listed at the very bottom of the usage page is needed. (I filed a bug about this here: https://github.com/flatpak/flatpak/issues/429 )
3. I use this which works: flatpak install --bundle ./my-flatpak-flatpak
4. I have no idea what I just installed, so the developer needs to tell me the flatpak app name to run it. (Part of this ticket: https://github.com/flatpak/flatpak/issues/429 )
5. I can finally attempt to run it, and I get this error: error: runtime/org.freedesktop.Platform/x86_64/1.4 not installed

Clearly, http://flatpak.org/runtimes.html gives the impression that this is a stable runtime that can be expected to be used by a lot of flatpak apps. Also, teh whole repository thing is very complicated for most regular users, so it would help a LOT if a simple one-liner install actually WORKED.

To make that happen, all the stable runtimes at http://flatpak.org/runtimes.html have to be actually available per default. Otherwise, everyone trying even simple apps based on one of the most default runtimes is going to run into this problem and will need to try and google around to figure out how to add the necessary runtime to their system.

Can you please therefore change how flatpak is packaged in Fedora to make the default runtimes available right from the start? If this and the flatpak usability issue with the command line switches itself is addressed, maybe users can then finally actually just do the following:

1. flatpak install --bundle ./my-flatpak.flatpak  --> outputs which app was actually installed.
2. flatpak run com.myvendor.myapp

.. which is really how it should work, at least if the devs went through the extra effort to package it with one of the stable runtimes to allow for an easier install.

Version-Release number of selected component (if applicable):
Flatpak 0.6.13



Additional info:
Comment 1 ell1e 2016-12-03 14:51:15 UTC 
I filed an upstream bug here just in case this is not a fedora-specific packaging problem of the flatpak tool: https://github.com/flatpak/flatpak/issues/430
Comment 2 Fedora End Of Life 2017-11-16 18:59:43 UTC 
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 Fedora  'version'
of '25'.

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

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 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, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Comment 3 Fedora End Of Life 2017-12-12 10:56:39 UTC 
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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. If you experience problems, please add a comment to this
bug.

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