Skip to content
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

Fedora 35 on top of Python 3.10 #231

Closed
1 task
fridex opened this issue Jan 20, 2022 · 13 comments
Closed
1 task

Fedora 35 on top of Python 3.10 #231

fridex opened this issue Jan 20, 2022 · 13 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@fridex
Copy link
Contributor

fridex commented Jan 20, 2022

Is your feature request related to a problem? Please describe.

See sclorg/s2i-python-container#486 - we could plug solver-fedora-35-py310 and start ingestion.

  • update Python packages packaged as RPMs for Fedora 35
@fridex fridex added kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/...` label and requires one. labels Jan 20, 2022
@goern
Copy link
Member

goern commented Jan 20, 2022

I think this might be a good opportunity to show different advises, based on latest -> f35-py310 or security -> ubi8-py39 wdyt?

/priority important-soon
/triage accepted

@sesheta sesheta added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on. labels Jan 20, 2022
@harshad16 harshad16 removed the needs-triage Indicates an issue or PR lacks a `triage/...` label and requires one. label Feb 1, 2022
@fridex
Copy link
Contributor Author

fridex commented Feb 1, 2022

@fridex
Copy link
Contributor Author

fridex commented Feb 3, 2022

https://bodhi.fedoraproject.org/updates/FEDORA-CONTAINER-2022-84cdd058eb

It looks like the container image is now stable. We could install fedora-35-py310 solver and trigger ingestion. I'm not 100% sure if Python 3.10 parsing from the solver name will be correct in our tooling - worth checking.

@fridex
Copy link
Contributor Author

fridex commented Feb 3, 2022

I'm not 100% sure if Python 3.10 parsing from the solver name will be correct in our tooling - worth checking.

It is wrong:

>>> from thoth.common import OpenShift
>>> OpenShift.parse_python_solver_name("solver-fedora-35-py310")
{'os_name': 'fedora', 'os_version': '35', 'python_version': '3.1.0'}

@fridex
Copy link
Contributor Author

fridex commented Mar 1, 2022

/sig stack-guidance
/priority important-soon

@sesheta sesheta added the sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance. label Mar 1, 2022
@Gregory-Pereira
Copy link
Member

/assign

@codificat
Copy link
Member

@codificat
Copy link
Member

/lifecycle active

@sesheta sesheta added the lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. label Mar 15, 2022
@Gregory-Pereira
Copy link
Member

With respect to #235 that created the f35-py310 solver, the tagged image in quay.io is showing with a critical vulnerability in the scan (see scan). It appears that the vulnerability lies with pip. What should be done about this?

@Gregory-Pereira
Copy link
Member

Can we close this issue, or is there more that needs to be done here?

@fridex
Copy link
Contributor Author

fridex commented Mar 29, 2022

It might be a good idea to generate prescriptions for packages packaged as RPMs in Fedora 35 (also might be worth to document this). See thoth-station/thoth-application#1803 (comment) and this issue should state code on how to do that thoth-station/adviser#1961 (might require changes to conform to the current prescriptions structure and thoth-station/prescriptions#59).

BTW it sounds like we could turn on ingestion in stage env?

@codificat
Copy link
Member

BTW it sounds like we could turn on ingestion in stage env?

Tracking that in thoth-station/thoth-application#2479

@harshad16
Copy link
Member

This seems to be done.
closing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

6 participants