-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revert build from source #104
base: master
Are you sure you want to change the base?
Conversation
Started test build 173571 |
Build 173571 failed |
Revert changes made on PR flathub#85 that broke flathubbot updates (flathub#102 and flathub#103)
ed4a243
to
cb9ccd1
Compare
Started test build 173575 |
Build 173575 successful
|
I'm all for a simpler update process but how do we support aarch64 when the upstream doesn't provide a binary? |
@hexchain Building from source would require a manual update of I tried to create a flatpak build step to generate So my conclusion is that there is no way to support aarch64 builds without upstream support, unless there is someone available to manually update Maybe opening an issue upstream and request aarch64 binaries for new releases could be a more viable way of solving this. |
Also, maybe using Github Actions to create an updated version of |
Indeed, that tool is not supposed to be run inside flatpak builds (see here). A bigger problem is that tool cannot handle some corner cases in this project (e.g. dependency on git repo in Meanwhile I'll open an issue in the upstream repo to ask for aarch64 binary support. |
Revert changes made on PR #85 that broke flathubbot updates (see #102 and #103)