Bug 2276797 - dependency error in python3-torch
Summary: dependency error in python3-torch
Keywords:
Status: CLOSED DUPLICATE of bug 2272514
Alias: None
Product: Fedora
Classification: Fedora
Component: python-torch
Version: 40
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Tom Rix
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-04-24 03:23 UTC by Jeff
Modified: 2024-04-24 11:49 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-04-24 11:49:27 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jeff 2024-04-24 03:23:54 UTC
python3-torch package cannot be installed using dnf

A workaround was found but most will not find it easily.  Description below in the additional information.

Reproducible: Always

Steps to Reproduce:
1. Attemot to install pytorch (python3-torch) package on fedora 40 using the `dnf install python3-torch' command

2.
3.
Actual Results:  
error message

# dnf install python3-torch 
Last metadata expiration check: 0:07:31 ago on Tue 23 Apr 2024 09:36:04 PM CDT.
Error: 
 Problem: conflicting requests
  - nothing provides libonnx.so.1.14.0()(64bit) needed by python3-torch-2.1.2-3.fc40.x86_64 from fedora
  - nothing provides libonnx_proto.so.1.14.0()(64bit) needed by python3-torch-2.1.2-3.fc40.x86_64 from fedora
(try to add '--skip-broken' to skip uninstallable packages)


Expected Results:  
Proper dependencies should have been available and installation should have succeeded

I searched for the missing version of onnx-devel, found it in the f39 repo.
Used 'dnf install onnx-devel --releasever 39' to install it.
Following that then `dnf install python3-torch' was able to complete successfully.

The addition of pytorch was one of the features of the Fedora 40 release but cannot be installed properly.

Comment 1 Miro Hrončok 2024-04-24 11:49:27 UTC

*** This bug has been marked as a duplicate of bug 2272514 ***


Note You need to log in before you can comment on or make changes to this bug.