-
Notifications
You must be signed in to change notification settings - Fork 174
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
Cannot create build environment in Fedora 37 #294
Comments
As of January 23rd, 2023, the issue with Fedora 37 still persists. |
apyrgio
added a commit
that referenced
this issue
Feb 6, 2023
Run CI tests for Fedora 37 environments, now that we no longer require PySide2 as a dev dependency. Fixes #294
apyrgio
added a commit
that referenced
this issue
Feb 7, 2023
Run CI tests for Fedora 37 environments, now that we no longer require PySide2 as a dev dependency. Fixes #294
apyrgio
added a commit
that referenced
this issue
Feb 7, 2023
Run CI tests for Fedora 37 environments, now that we no longer require PySide2 as a dev dependency. Fixes #294
apyrgio
added a commit
that referenced
this issue
Feb 7, 2023
Run CI tests for Fedora 37 environments, now that we no longer require PySide2 as a dev dependency. Fixes #294
apyrgio
added a commit
that referenced
this issue
Feb 7, 2023
Run CI tests for Fedora 37 environments, now that we no longer require PySide2 as a dev dependency. Fixes #294
apyrgio
added a commit
that referenced
this issue
Feb 7, 2023
Run CI tests for Fedora 37 environments, now that we no longer require PySide2 as a dev dependency. Fixes #294
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As is, we can't currently create a build environment for Fedora 37 because:
This means that we can't create a build environment, by running
poetry install
and installing PySide2 from PyPI.Interestingly, the Fedora maintainers have managed to make PySide2 run on Fedora 37, meaning that end users who install Dangerzone will simply download PySide2 from the official repos, and not get affected.
Still, this impacts development, and its one more push for #164
Originally posted by @apyrgio in #263 (comment)
The text was updated successfully, but these errors were encountered: