-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Add release-fedora to build fedora compatible RPM #5281
Conversation
8749c17
to
f7e5813
Compare
f7e5813
to
bac6e22
Compare
7364a27
to
81651ed
Compare
2e8f91e
to
69b8bc7
Compare
69b8bc7
to
abb50f3
Compare
Is this fixes will land on master? Thanks for insomnia! ❤️ |
3579891
to
e11da85
Compare
6d7dc8e
to
8c09307
Compare
By the way, I tried the artifact from here: https://github.com/Kong/insomnia/actions/runs/3481857586 I still see the SSL connect error followed by a crash. |
8c09307
to
bcf60ee
Compare
Hi @azzamsa @leonardehrenfried , while we don't have a more definitive solution, in order to unblock you in the meantime, I've compiled an experimental build on my fork which you can download and use: https://github.com/filfreire/insomnia/releases/tag/fedora-experiment%408ae4fe71 Contains changes up to 8ae4fe71 and was built using: #5281 Please let me know if you have any issues with it. |
@filfreire I just upgraded all of my dependencies and re-installed the build you provided. I can now indeed use insomnia again! Thank you for this. This will be good enough for me for a while. |
a010b61
to
83f5cbc
Compare
5378869
to
1aa7995
Compare
71a919e
to
5aeb0fb
Compare
5aeb0fb
to
3ddd65d
Compare
SEE UPDATE 23 January 2023
In this PR we add another job
to the release-publish,release-fedora
where we build Insomnia.rpm
withbuildDependenciesFromSource
setting from within a fedora 36 container.This helps provide a working workaround build that solves the issue folks are running into for #5088.
When we do builds with
buildDependenciesFromSource
set totrue
from within a Fedora 36 environment, we no longer get the SSL crash:TL;DR: Exploration to try and provide some sort of workaround for #5088