Re: Status of MIOpen?

To: Cordell Bloor <cgmb@slerp.xyz>
Cc: Christian Kastner <ckk@debian.org>, Debian ROCm Team <debian-ai@lists.debian.org>
Subject: Re: Status of MIOpen?
From: Xuanteng Huang <xuanteng.huang@outlook.com>
Date: Wed, 19 Feb 2025 03:25:23 +0000
Message-id: <[🔎] 03F0E5C9-61EC-492D-BCA1-4B3001A3BE60@outlook.com>
In-reply-to: <[🔎] 281f2254-3925-4496-963c-27de52e574f3@slerp.xyz>
References: <[🔎] 281f2254-3925-4496-963c-27de52e574f3@slerp.xyz>

Hi Cory,

> On Feb 17, 2025, at 16:54, Cordell Bloor <cgmb@slerp.xyz> wrote:
> 
> What's the plan for migrating MIOpen from experimental to unstable? It's been on experimental for quite a while now [1]. The Debian ROCm CI is not able to display test results for packages that do not exist on unstable, which is rather unfortunate.

MIOpen currently depends on libhalf-dev [1], which is on experimental as well. So we may need to migrate it first?

Best,
Xuanteng

[1]: https://packages.debian.org/search?keywords=libhalf-dev

Reply to:

Follow-Ups:
- Re: Status of MIOpen?
  - From: Christian Kastner <ckk@debian.org>

References:
- Status of MIOpen?
  - From: Cordell Bloor <cgmb@slerp.xyz>

Prev by Date: Re: pytorch-cuda: What range of GPUs to support?
Next by Date: Processed: Bug#1098205 marked as pending in onnxruntime
Previous by thread: Status of MIOpen?
Next by thread: Re: Status of MIOpen?
Index(es):
- Date
- Thread