-
Notifications
You must be signed in to change notification settings - Fork 199
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
Pip package dependency issue, qtfaststart won't install #1716
Comments
FYI: Commenting out the qtfaststart package from the requirements.txt did resolve my issue with getting SMA to run because the other packages successfully installed. But that doesn't resolve it long term and is only a workaround. My output format is mkv, so it's not used in my configuration, but I would imagine it would be a problem for others doing a new installation... |
This appears to be a duplicate of mdhiggins/sma-mod#17 (comment) but probably better suited here since it impacts any installation not just SMA-mod This appears to be related to this issue here For now I will force pip version 24.0 across the containers to address this, should be propagating out now |
Are you going to update the requirements file to specify the version? This would be for those that are doing a git pull of the repo and installing via the requirements.txt file. Thanks! |
It’s not a requirements file issue. It’s the pip version. You would have to have pip installed already to even act on a requirements file and I don’t think you can modify the pip version while it’s actively installing a requirements file |
Okay, thanks for the explanation. |
Fortunately it looks like they’re actively committing changes to fix the issue as of this morning so hopefully this will just be a transient 24.1 bug that gets quickly resolved |
This was resolved upstream. Thx! |
Went ahead and removed the version 24.0 force then so we can continue to be on the latest version of pip |
Describe the bug
This is not a bug with SMA, but a problem with package dependency. qtfaststart won't install, when looking online it seems that it's a very old package and likely unsupported... so the likely chance of a fix seems to be very low... I am posting this because I'm hoping you can at least validate that there is a problem installing the legacy package. If it is reproducible, it might be time to consider deprecating it?
Command or context you are trying to run
pip3 install -r /usr/local/sma/setup/requirements.txt
Log files
System Information
Expected behavior
Install required packages, because the one package is unable to install, all required packages fail to install using the requirements.txt file
Additional context
Just looking for a confirmation that it is broken and if there is any guidance that could help resolve it
The text was updated successfully, but these errors were encountered: