Description of problem: I'm currently trying to convert a locally self-built rpm into a self-built flatpak application. We would like to publish this self-built flatpak app via a self-hosted flatpak service. Question #1: Might such an idea currently be possible to be implemented? Currently it is already possible for me to built a patched version of the clang-tools-extra rpm. I start with the following source rpm https://mirror.23m.com/fedora/linux/updates/35/Everything/source/tree/Packages/c/clang-13.0.0-3.fc35.src.rpm I changed the spec file to include the necessary patch. I build the multiple binary rpms of the source rpm inside a dockerized container triggered via a gitlab-ci runner. The built rpms are uploaded to an instance of a JFrog Artifactory service. Theoretically the built rpms might come thus from a ftp server at this point. Up until here everything works. Now I would like to build a flatpak application in a further dockerized container. I would like to follow more or less the description given in: http://janberan.tech/2021/02/rpm2flatpak/ But it seems that the commands used are only using rpms available in the fedora repo. The commands given in this description look like they are very fedora centric and depending on the fedora infrastructure. Question #2: Do you know of any better description to setup the infrastructure needed for my plan? Question #3: It looks like the command used in the referenced description from above 'fedmod rpm2flatpak clang-tools-extra' only works with rpms in the fedora repo. What am i supposed to do here to reference my self-built rpms? Version-Release number of selected component (if applicable): see above How reproducible: see above Steps to Reproduce: see above Actual results: see above Expected results: see above Additional info: see above
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. 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 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13. Fedora Linux 35 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.