Bug 1660137

Summary:	oci support issues
Product:	Red Hat Enterprise Linux 7	Reporter:	David King <dking>
Component:	flatpak	Assignee:	David King <dking>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.7	CC:	desktop-qa-list, jkoten, mclasen, mkrajnak, otaylor, tpelka
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	flatpak-1.0.2-3.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1657306
Clones:	1665969 (view as bug list)		Environment:
Last Closed:	2019-08-06 12:42:58 UTC	Type:	---
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:	1657306
Bug Blocks:	1656436, 1665969

Description David King 2018-12-17 15:30:39 UTC

+++ This bug was initially created as a clone of Bug #1657306 +++

I was testing the fedora flatpak repo with rhel8 beta, and right away, i hit the

error: lgetxattr: Permission denied issue

This was recently fixed upstream. We should backport oci fixes for 8.0

--- Additional comment from David King on 2018-12-13 13:15 GMT ---

I am unable to test this patch at the moment, as my RHEL 7.6 system has an old RPM and so errors out when seeing the Recommends tag, and my RHEL 8 system will not authenticate against brew. There are a few more OCI patches that could do with being backported from master, but these should be the minimum that is required.

--- Additional comment from David King on 2018-12-17 15:12:23 GMT ---

I added another backported fix, and triggered a build with the changes.

Comment 4 Martin Krajnak 2019-05-07 12:51:31 UTC

flatpak-libs-1.0.2-7.el7.x86_64
flatpak-1.0.2-7.el7.x86_64

Tested by installing and removing Quadrapassel and Firefox flatpaks from OCI

Comment 6 errata-xmlrpc 2019-08-06 12:42:58 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/RHBA-2019:2080