On Sat, Nov 30, 2024 at 5:27 PM Stephen Morris <steve.morris.au@xxxxxxxxx> wrote: > > On 30/11/24 23:27, Bob Marčan via users wrote: > [...] > The python way to isolate from the OS is to use the venv machinary. > I'm guessing from your response you are not familiar with it. > > How to build rpm: > > python setup.py bdist_rpm > > The magazines said they had written their tutorials for python 3.12, as that was the most commonly used version of python. But my main question is, because I had issues where required functions for the tutorial weren't in the Fedora version of the package, which in my case was already installed as part of the python install, how do we know before installing a package rpm whether or not it is going to have the needed functions? The way I have dealt with this in the past is, don't use bleeding edge. Download packages that are from the same epoch as the Fedora release you are building for. If you are building something for Fedora 41, which was released October 2024, then download packages and dependencies that were released around that time. If functions are missing, then download an earlier version of the package or dependency and try again. I do the same regularly for Keysmith, especially on Ubuntu. I can't build the latest Keysmith release on Ubuntu. I usually have to checkout an earlier version due to Qt dependencies. Jeff -- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
