-
-
Notifications
You must be signed in to change notification settings - Fork 862
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
Some flatpak fixing #5510
Some flatpak fixing #5510
Conversation
Looks the flatpak build is broken for a while. |
@SoftFever possibly that open cascade isn't being downloaded during the flatpak build |
@SoftFever no wait, it's running out of space again |
Does that also equate to the error I'm getting: |
@cochcoder yes |
though, to be more specific, the |
I see, could it be a issue where the flatpak isn't deleting enough stuff for its second, and so on, runs? |
It's possibly the CCACHE. |
Hopefully its that, it would suck if it means no more ~20 minute builds, but its much better to have a flatpak rather than nothing. Currently having a flapak version is the only way for me, and others, to run Orca Slicer reliably. |
Yeah coch, I really, really, really don't like the appimage. I just wish I had more time to work on this. |
You've already done incredible work so far with the initial support. Even if this doesn't get worked on for a while, at least the majority, and I imagine the hardest, part is done. |
This should be good now that caching is disabled. THOUGH, this means that the flatpak will take significantly longer to build. |
@SoftFever Changes:
|
...A few more changes, apparently: @SoftFever
|
@cochcoder upstream change |
Even to upload to GitHub actions as an artifact? |
No, that should just be in the CI job. |
Strange, maybe they're using the same name... Edit: Seems that's it |
i'm trying to build it in fedora silverblue 40 and encountering this error error: metadata-generation-failed _× Encountered error while generating package metadata. note: This is an issue with the package mentioned above, not pip. i'm really new to this things so i probably did something wrong, if not hope that helps |
@AlessioMagni make sure you're using this branch and building with it. I applied a fix for that in here. |
Thought that I would put this out there in case this information is helpful in the future. When I enable caching I find that it gets stuck on adding printer covers in ~20 mins and then silently crashes before saying it succeeded with no artifact. |
@SoftFever bump |
I've done a few builds recently and found that the flatpak build was consistently getting this error and stopping:
|
You'll need to ctrl-f "error:" for the first indication of an error. |
deps/wxWidgets/wxWidgets.cmake
Outdated
@@ -26,6 +26,7 @@ orcaslicer_add_cmake_project( | |||
wxWidgets | |||
GIT_REPOSITORY "https://github.com/SoftFever/Orca-deps-wxWidgets" | |||
GIT_SHALLOW ON | |||
GIT_TAG a675dbe8fd07cb5c982cdab7b93cffc9d9f05f22 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to specify this since the a675dbe8fd07cb5c982cdab7b93cffc9d9f05f22 is the latest commit in master branch?
@@ -144,7 +160,7 @@ modules: | |||
sources: | |||
- type: git | |||
url: https://github.com/SoftFever/Orca-deps-wxWidgets | |||
branch: master | |||
commit: a675dbe8fd07cb5c982cdab7b93cffc9d9f05f22 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to specify this since the a675dbe8fd07cb5c982cdab7b93cffc9d9f05f22 is the latest commit in master branch?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, because they should always be the same and never mismatch during building both the appimage and flatpak. Really, it's a sanity check because of CI restrictions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Isn't it the same if we use last master branch without pining the commit?
in case we made changes in https://github.com/SoftFever/Orca-deps-wxWidgets in the future, we don't have to modify multiple places to update it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While it would normally, one of the things that a flathub upload would very likely require is dependency locking per release version. If a flatpak only bug is discovered, then you want to fix it without any unexpected or unneeded updates. Since this is the only dependency that has to be synchronized in a different way compared to all the other ones (due to CI size constraints), I figured this is the least intrusive method to this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If a flatpak only bug is discovered, then you want to fix it without any unexpected or unneeded updates.
This is actually the opposite for third-party cases in my experience. It's better to avoid pointing to different commits for different build systems. The reason I'm asking to remove the commit tag is that the Orca-deps-wxWidgets repository is specifically created for OrcaSlicer. Any build break errors caused by the changes made in that repo should be promptly caught by the CI/CD pipeline.
If Flatpak points to an old commit, it will miss that check. The worst-case scenario is however that it may result in different behaviors compared to other platforms due to different versions of wxWidgets being used, which would be a nightmare to troubleshoot.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alright, then you may revert both tagged parts.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've reverted both tagged parts.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for the slow response.
Was a bit busy in the past two weeks.
Looks good, thank you so much!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good
Thank you so much for the continuous effort to bring Flatpak to life!
This reverts commit 6579549.
@powpingdone |
This reverts commit e29cba2.
This reverts commit e29cba2.
This is a smaller PR to attempt to address future flathub reviews. As of May 30, 1700 CST, I haven't filed the issue to flathub yet, but it will happen in the future. This is just heading off future issues.