Bug 23740 - [Backport request] flatpak-1.0.0 on Mageia 6
Summary: [Backport request] flatpak-1.0.0 on Mageia 6
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: Backports (show other bugs)
Version: 6
Hardware: All Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: Neal Gompa
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-20 21:59 CEST by Sébastien Morin
Modified: 2019-07-01 19:49 CEST (History)
1 user (show)

See Also:
Source RPM: flatpak-1.0.0-1.mga7.x86_64.rpm
CVE:
Status comment:


Attachments

Description Sébastien Morin 2018-10-20 21:59:58 CEST
Description of problem:

flatpak-0.10.3-1.mga6 doesn't allow to install several apps from flathub. It would be very nice if a backport of flatpak-1.0.0-1.mga7.x86_64.rpm could be packaged for Mga6.

Examples:
 1. kdenlive
$ flatpak install flathub org.kde.kdenlive
error: app/org.kde.kdenlive/x86_64/stable needs a later flatpak version (0.11.4)

 2. OpenShot
$ flatpak install flathub org.openshot.OpenShot
error: app/org.openshot.OpenShot/x86_64/stable needs a later flatpak version (0.11.4)

 3. Shotcut
$ flatpak install flathub org.shotcut.Shotcut
error: app/org.shotcut.Shotcut/x86_64/stable needs a later flatpak version (0.11.4)


Thank you!
Sébastien Morin 2018-10-20 22:00:31 CEST

Version: Cauldron => 6

Comment 1 Marja Van Waes 2018-10-21 21:38:19 CEST
Assigning to the registered flatpak maintainer.

CC: (none) => marja11
Assignee: bugsquad => ngompa13

Comment 2 Neal Gompa 2018-10-28 03:47:58 CET
It sounds like this qualifies as something we should ship as a regular update (as opposed to a backport).

At least the flatpak libraries look like they are ABI compatible, so it might be possible without rebuilding gnome-software and plasma-discover, but I'll have to investigate a bit...
Comment 3 Sébastien Morin 2018-10-28 20:04:00 CET
This sounds like excellent news! Thank you Neal!
Comment 4 Sébastien Morin 2019-07-01 19:49:24 CEST
flatpak 1.4.1 is available in the current Mageia 7, so I guess this can now be closed.

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.