You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I installed Muzika from the latest x86_64 CI build, the remote devel-origin with the URL https://vixalien.github.io/muzika/repo was automatically added. But doing a flatpak update, I got the following error:
No such ref 'app/com.vixalien.muzika.Devel/x86_64/master' in remote devel-origin
I discovered that the x86_64 build indeed isn't part of the Flatpak repository deployed to GitHub pages. This seems to be a regression that happened between run 10 (commit 4682fc2) and 11 (commit 30ef140) of the pages-build-deployment action. I'm not very familiar with the way GitHub actions work, so unfortunately I can't tell you the cause of the problem.
PS: You seem to have leaked a revocation certificate for the remote's PGP key in e70229a. You might want to create a new key before using this one long-term.
The text was updated successfully, but these errors were encountered:
Thanks. Probably the best solution atm, so at least flatpak doesn't error out anymore.
Would it help if I tried to figure out the problem with Flatter when I have some time on my hands, or should I just wait for the v1 release on Flathub?
When I installed Muzika from the latest x86_64 CI build, the remote
devel-origin
with the URL https://vixalien.github.io/muzika/repo was automatically added. But doing aflatpak update
, I got the following error:I discovered that the x86_64 build indeed isn't part of the Flatpak repository deployed to GitHub pages. This seems to be a regression that happened between run 10 (commit 4682fc2) and 11 (commit 30ef140) of the
pages-build-deployment
action. I'm not very familiar with the way GitHub actions work, so unfortunately I can't tell you the cause of the problem.PS: You seem to have leaked a revocation certificate for the remote's PGP key in e70229a. You might want to create a new key before using this one long-term.
The text was updated successfully, but these errors were encountered: