-
Notifications
You must be signed in to change notification settings - Fork 22
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
Generate RPM with packit and maybe copr ? #853
Comments
There is supposed to be a way to hook things together so that github commits can trigger rpm generation. |
So the basic problem is that whenever I build an RPM on rhel8 (most important target os atm) many dependencies are missing, So far redhat environments have always been missing many dependencies (except fedora39, built experimentally in #740 ... with the issue740_hatchling branch, but that does not work at all with python3.6 ... which is on redhat 8. |
following the comment from https://discuss.python.org/u/webknjaz in the python packaging thread mentioned in the initial post of this issue ... looked into packit.dev, which seems to use https://copr.fedorainfracloud.org/ ... which requires a fedora account... ok, then I look into creating a package in copr, but which wants me to use tito... https://github.com/rpm-software-management/tito... that's as far as I've gotten so far. |
https://devguide.python.org/versions/ note that python on redhat8 and ubuntu18 are deprecated... so security situation is a bit unclear. |
so far, have merged a .spec file... which is a step along the way to any of these. |
based on advice here:
https://discuss.python.org/t/tool-to-build-a-rpm-package-backed-by-pep-517/4020/16
led to looking at https://packit.dev, and now created a copr ( https://copr.fedorainfracloud.org/coprs/bitgrazer/MetPX-sr3/ )
project? ... should figure out how to build RPM's automagically based on github commits... automate rpm generation.
The text was updated successfully, but these errors were encountered: