Bug 1748276

Summary: Rebase flatpak to 1.4.x
Product: Red Hat Enterprise Linux 8 Reporter: Jiri Koten <jkoten>
Component: flatpakAssignee: David King <dking>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: high    
Version: 8.2CC: alexl, david, jatin1812, klember, mclasen, mkrajnak, tpelka
Target Milestone: betaKeywords: Rebase
Target Release: 8.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: flatpak-1.4.3-1.el8 Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Story Points: ---
Clone Of:
: 1753591 (view as bug list) Environment:
Last Closed: 2020-04-28 16:10:29 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: 1760817    
Bug Blocks: 1748290, 1748296, 1753591, 1753613, 1754051    

Description Jiri Koten 2019-09-03 09:26:48 UTC
We should update the flatpak in RHEL8 (1.0.6) to the current stable series 1.4.x

The major changes since the 1.2.x is the improved I/O use for system-installed applications, and the new format for pre-configured remotes.

Comment 1 Kalev Lember 2019-09-19 11:05:12 UTC
It would be good to bump this up to RHEL 8.1.1. The new flatpak version has important fixes that are needed for new flatpak runtimes that are getting deployed to flathub just now.

Comment 2 Alexander Larsson 2019-09-19 11:11:47 UTC
One important feature we want (that landed in 1.4.2) is the support for extra_data for runtime extensions (previously it was for apps only). The main usecase for this is the openh264 extension which contains the cisco-blessed openh264 decoder. We need that to use extra_data for legal (patent grant) reasons.

We're actually interested in using this particular extension for the fedora runtime too, so that e.g. a fedora-based firefox flatpak can support h264 videos.

Comment 3 Kalev Lember 2019-09-19 11:59:59 UTC
After some more irc discussion with alex and mclasen, there's a fair bit of urgency for getting the fixes out. Here's a new plan:

1) Do a Z stream update for both RHEL 7 and 8, shipping flatpak 1.0.9 (Alex Larsson is doing a 1.0.9 release just for RHEL with targeted backports).

If it's necessary (if 1.0.x version updates aren't at all allowed in Z stream), we can just "fake" the 1.0.9 version (there's a server side check that makes sure the client is at least version 1.0.9) and backport the patches. I'd much prefer doing an update to 1.0.9 in Z though to make things easier and less error prone.

2) Rebase to 1.4.x for RHEL 8.1.1

Comment 4 Tomas Pelka 2019-09-19 12:13:33 UTC
(In reply to Kalev Lember from comment #3)
> After some more irc discussion with alex and mclasen, there's a fair bit of
> urgency for getting the fixes out. Here's a new plan:
> 
> 1) Do a Z stream update for both RHEL 7 and 8, shipping flatpak 1.0.9 (Alex
> Larsson is doing a 1.0.9 release just for RHEL with targeted backports).
> 
> If it's necessary (if 1.0.x version updates aren't at all allowed in Z
> stream), we can just "fake" the 1.0.9 version (there's a server side check
> that makes sure the client is at least version 1.0.9) and backport the
> patches. I'd much prefer doing an update to 1.0.9 in Z though to make things
> easier and less error prone.
> 
> 2) Rebase to 1.4.x for RHEL 8.1.1

-> 8.2.0 just FYI

Comment 8 Tomas Pelka 2020-02-11 19:18:21 UTC
*** Bug 1777003 has been marked as a duplicate of this bug. ***

Comment 10 errata-xmlrpc 2020-04-28 16:10:29 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2020:1767