Closed Arcitec closed 3 years ago
Thanks for pointing this out. I don't usually force push over tags on the main repo so I just fixed the SHA in this case. Can you show me where the build is failing so I can check that my change fixed it?
Edit: NVM I see the CI build now.
@borgmanJeremy Oh, I didn't notice that you're part of the official flameshot project. Awesome. Thanks for making a flatpak! And thanks a lot for making the best screenshot utility for linux! :)
And glad you found the CI log. I saw it on the https://github.com/flathub/org.flameshot.Flameshot/commits/master page by clicking on the red "X" at the v0.9.0 commit.
Well, thank you very much for fixing it! Awesome! ❤️
@borgmanJeremy Hi, I noticed that flathub is still on 0.8.5. And I see that it's caused by the latest flatpak commit failing to build:
https://github.com/flathub/org.flameshot.Flameshot/commit/cbf0daacd0e5eaa7245878e60957f40e044bfecd
Try to remove the "commit" rule and build based on release tag instead, since flameshot clearly force-pushes and overwrites their own tags periodically to point at other commits.