As it is common for archive packages to be compressed with bzip2 (tar.bz2) the flatpak-builder RPM package should depend on bzip2. This would help prevent painful debugging of build errors and make it "Just Work"™ in more situations. Example affected build spec: https://github.com/KDE/flatpak-kde-applications/blob/c7b34f2d19cf4a951fda7d1900094ccfdff050b8/org.kde.krita.json#L32
Created attachment 1255554 [details] Require bzip2 for flatpak-builder I am new to RPMs coming from the DEB world but I believe this would solve the issue. Note: flatpak-builder does not call "bzip2" itself bit uses "tar -j".
Thanks for the patch. I had already prepared a patch which was a bit more complete (bumping the release number and adding a changelog entry) but the Requires change was sound. The Rawhide build is done, and builds for stable releases will follow soon.
flatpak-0.8.3-3.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-87896dfb59
flatpak-0.8.3-3.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2017-bc7abf175b
flatpak-0.8.3-3.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-bc7abf175b
flatpak-0.8.3-3.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-87896dfb59
flatpak-0.8.3-3.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.
flatpak-0.8.3-3.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.