<@tflink:fedora.im>
16:33:03
!startmeeting fedora-pytorch
<@meetbot:fedora.im>
16:33:04
Meeting started at 2024-03-28 16:33:03 UTC
<@meetbot:fedora.im>
16:33:04
The Meeting name is 'fedora-pytorch'
<@tflink:fedora.im>
16:33:18
!topic intro
<@tflink:fedora.im>
16:33:37
sorry for the delay, my computer suddenly started having issues and my keyboard stopped working
<@tflink:fedora.im>
16:33:45
!hello
<@zodbot:fedora.im>
16:33:47
Tim Flink (tflink)
<@trix:fedora.im>
16:38:54
me too
<@trix:fedora.im>
16:39:12
different issues, same results
<@tflink:fedora.im>
16:39:22
fun times
<@tflink:fedora.im>
16:39:59
it's just the two of us but it's also 10 minutes since the scheduled start. I assume that nobody else is attending
<@tflink:fedora.im>
16:40:26
I suppose that we should just quickly go through the agenda for the purpose of documenting updates
<@trix:fedora.im>
16:40:35
sounds good
<@tflink:fedora.im>
16:40:40
!topic rocm+torch progress
<@tflink:fedora.im>
16:41:06
!info torch 2.3 has rocm enabled in rawhide, will need more testing
<@trix:fedora.im>
16:41:27
2.3-rc6 as of yesterday.
<@trix:fedora.im>
16:41:36
yes much more testing needed
<@tflink:fedora.im>
16:41:55
we should probably prepare statements as to why rocm and cuda aren't enabled in f40. I expect we're going to get questions and complaints once f40 releases
<@trix:fedora.im>
16:42:56
behold the wonders of rawhide!
<@tflink:fedora.im>
16:43:00
but I don't think that there's much else to say on this topic. I need to get a better test case documented and public but that's a slightly different topic
<@trix:fedora.im>
16:44:59
2.3 is wip some stuff works some doesn't.. i ran into the miopen problem you reported after getting torchvision updated and testing the examples again.
<@tflink:fedora.im>
16:45:17
the work continues :)
<@tflink:fedora.im>
16:45:27
anyhow, moving on
<@tflink:fedora.im>
16:45:28
!topic are more pytorch packages needed?
<@tflink:fedora.im>
16:45:42
most of the basic packages are in rawhide, at least
<@tflink:fedora.im>
16:46:04
are there other torch-related packages that should be packaged?
<@trix:fedora.im>
16:46:08
i think just 3-4 other pytorch packages
<@trix:fedora.im>
16:46:43
it could be a very big list
<@tflink:fedora.im>
16:47:14
since nobody else is here, we should start a discourse topic asking for input
<@trix:fedora.im>
16:47:23
groovy
<@tflink:fedora.im>
16:47:28
I expect we may get more requests once F40 is released
<@tflink:fedora.im>
16:47:34
but for now ... crickets :)
<@tflink:fedora.im>
16:47:57
!topic pytorch vs python-torch naming
<@tflink:fedora.im>
16:48:06
!link https://bugzilla.redhat.com/show_bug.cgi?id=2272064
<@trix:fedora.im>
16:48:18
i'm adding the provides: in rawhide
<@trix:fedora.im>
16:48:24
it costs nothing
<@tflink:fedora.im>
16:49:15
apparently, there was a typo in some F40 release docs that has been corrected but `dnf install pytorch` was listed as the way to install pytorch. this has changed into a request to enable that command via requires so that people can use `dnf install pytorch`
<@tflink:fedora.im>
16:49:38
and then be confused when you can't effectively use `import pytorch` in python
<@tflink:fedora.im>
16:50:00
I still think it's stupid but isn't going to argue it more
<@trix:fedora.im>
16:50:01
daahhhh.. that cost to fix is a lot more.. so no
<@tflink:fedora.im>
16:50:11
that's upstream's problem
<@tflink:fedora.im>
16:51:05
that rhbz is going to be updated to include F40 for the provides change if it's only fixed in rawhide
<@trix:fedora.im>
16:52:03
at this point i don't know about f40
<@tflink:fedora.im>
16:52:25
not sure I follow, don't know what about f40?
<@trix:fedora.im>
16:52:57
i am waiting on the big ask for rocm in f40
<@tflink:fedora.im>
16:53:15
f40 final freeze is tuesday, I think
<@trix:fedora.im>
16:53:47
ahhh good times.
<@tflink:fedora.im>
16:54:43
again, I expect complaints about the state of pytorch in F40 once F40 releases, maybe sooner now that beta is out
<@tflink:fedora.im>
16:55:08
people won't read the docs and will expect pytorch to have support for cuda
<@trix:fedora.im>
16:55:48
yeah, well when a problem comes in that needs a fix, the provides: can be added then.
<@tflink:fedora.im>
16:56:40
I think that the request was for F40 but I'm removing myself from the discussion :)
<@tflink:fedora.im>
16:57:02
!topic F40 and HW acceleration
<@trix:fedora.im>
16:57:21
por is no.
<@tflink:fedora.im>
16:57:33
por?
<@tflink:fedora.im>
16:57:42
am I just being slow today?
<@trix:fedora.im>
16:57:54
plan of record - a fancy way to say no
<@tflink:fedora.im>
16:58:05
on second thought, lets leave this topic off for now
<@tflink:fedora.im>
16:58:08
!undo
<@tflink:fedora.im>
16:58:17
!topic open floor
<@trix:fedora.im>
16:58:25
in rawhide, yes!
<@tflink:fedora.im>
16:58:28
any other topics that folks want to bring up?
<@tflink:fedora.im>
16:58:56
ah, plan of record makes sense
<@trix:fedora.im>
16:59:23
for accel, i ahve rocm fine, looking for others to help with cuda and xpu
<@trix:fedora.im>
16:59:41
and any other backend people really care about
<@trix:fedora.im>
16:59:53
care == willing to do the work on it
<@tflink:fedora.im>
17:00:23
yeah, I expect complaints either way, though :)
<@tflink:fedora.im>
17:00:42
but for F40, we've been pretty clear about pytorch being CPU only so that won't get far
<@tflink:fedora.im>
17:01:26
we're at the top of the hour, though so I move that we close the meeting out
<@tflink:fedora.im>
17:01:48
!action tflink to create topic in Fedora discourse about desired/required pytorch related packages
<@trix:fedora.im>
17:01:58
yup sounds good
<@tflink:fedora.im>
17:01:59
should have done that earlier
<@tflink:fedora.im>
17:02:19
anyhow, thanks for coming
<@tflink:fedora.im>
17:02:47
!info next meeting is scheduled for 2024-04-11 on google meet
<@tflink:fedora.im>
17:02:52
!endmeeting