-
Notifications
You must be signed in to change notification settings - Fork 209
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
libjpeg-turbo
on pytorch conda channel shadows conda-forge with old version
#1679
Comments
It looks like Would it be possible for the |
cc @seemethere I guess this one is a depency from domains? Who is the most up to date about which version we need here? |
IIUC this is connected to FFmpeg, which is also on the |
Hello dearest maintainers, I'm terribly sorry to bump this issue again, but it's currently blocking some dependency updates for us. Any chance to get a resolution/decision on this package? |
Hello!
I came across an issue sourcing
pytorch
from the pytorch channel, along with a lot of other dependencies from conda-forge. I'm using strict channel priority to get more predictable environments. For linux there is an issue that can occur, if any of the packages depend onlibjpeg-turbo
. "Current" version, according to conda-forge-pinnings oflibjpeg-turbo
is 3. So any recent versions of packages built in the conda-forge ecosystem depend on that version. Thelibjpeg-turbo
package on the pytorch channel is only available in version 2.0.0. As a result, environments might not be solvable (in strict mode).I'm not sure what a good solution to this is. I assume this package is there for a reason, so removal might not be an option. For me it could work to add the 3.0.0 libjpeg turbo version (from conda-forge) to the pytorch channel. However, this could be a maintenance nightmare, as libjpeg-turbo would've to be kept in sync. Removal of the main label would be preferable...
Cheers
Dominik
The text was updated successfully, but these errors were encountered: