Request to create new "rocm" package-set for resolute

Mon Feb 16 14:18:50 UTC 2026

On Mon, Feb 16, 2026 at 1:25 PM Talha Can Havadar <
talha.can.havadar at canonical.com> wrote:

> Hello Christian,
>
> Thank you very much for the feedback, please see the reworked list and
> descriptions below:
>
> ### Brief Introduction for ROCm
> > AMD ROCm™ is an open software stack including drivers, development
> tools, and APIs that enable GPU programming from low-level kernel to
> end-user applications. ROCm is optimized for Generative AI and HPC
> applications, and it is easy to migrate existing code into ROCm software.
> As explained in AMDs website:
> https://www.amd.com/en/products/software/rocm.html
>
> As part of our efforts to enable ROCm 7 in Ubuntu, we updated the packages
> listed below, they are core part of the ROCm stack and essential for
> tools/applications built upon ROCm. A super set of these packages can be
> found in https://salsa.debian.org/rocm-team/ as well.
> Debian's rocm-team can also be used to cross-check the relevance of the
> packages in this list.
>

I'm myself guilty of too long explanations, let me do you a favor just as
others helped me:

I'd suggest that the middle part "ROCm is optimized ... rocm.html" has no
meaning in regard to what packges are part of it and which are not. So I'd
leave that one out.

I understand the (tm) but I'm not sure the tools will survive the special
characters. Drop it or make it pure ASCII.

Further it is a bit too much marketing copy & paste. Shortening the intro
sentence and some of the middle section. Also the last to effectively say
the same.

With all that - how about:

"AMD ROCm (tm) is a stack including drivers, development tools, and APIs
that enable AMD GPU programming. This set covers the packages required to
build upon ROCm. A superset of these packages can be found in
https://salsa.debian.org/rocm-team/."

P.S. you forgot some not yet existing packages like MIOpen, but let us just
agree that we'd only add those that exist and as others get added you can
ping for inclusion - ok?

> Below list only includes packages we believe the core/essential part of
> ROCm stack (excluding the ones are not available in the archive)
> ```
> amdsmi
> rocm-llvm  => not a full fork of llvm, it builds on top of llvm-21 and
> provides additional tools/libraries like rocm-device-libs-21, hipcc,
> libamd-comgr . These are essential for the rest of the stack to build upon
> rocm-cmake => providing cmake scripts to help find ROCm packages using
> macros like find_package etc.
> rocm-smi-lib
> pkg-rocm-tools => One of the essential packages for building the whole
> stack, any change in this package may possibly trigger rebuild of all
> packages in the stack (and even for some not in this list, like ggml), this
> provides predefined list of supported GPU ISAs
> rocr-runtime
> hipify
> hipblas-common
> rocalution
> rocm-hipamd
> rocminfo
> rocrand
> rocdbgapi
> rccl
> hiprand
> rocprim
> roctracer
> rocblas
> rocfft
> rocsparse
> rocthrust
> hipcub
> hipfft
> hipsparse
> rocsolver
> hipblas
> hipsolver
> hipblaslt
> MIOpen
> ```
>
> I hope this is better than the first request :) Please let me know if more
> information needed.
>
> Best Regards,
> Talha
>
> On Mon, Feb 16, 2026 at 8:22 AM Christian Ehrhardt <
> christian.ehrhardt at canonical.com> wrote:
>
>>
>>
>> On Wed, Feb 11, 2026 at 5:50 PM Talha Can Havadar via Devel-permissions <
>> devel-permissions at lists.ubuntu.com> wrote:
>>
>>> Hello,
>>>
>>> I would like to request a new package set for rocm packages we are
>>> working on for resolute.
>>>
>>> I dont know what is the correct procedure for such a request
>>>
>>
>> Hi Talha,
>> that is not your fault - it was moved from the old Wiki to the project
>> docs, but there still is hidden in the staging area.
>> But we are actively working on picking from that old content as it
>> applies, revamping it, improving it and hopefully soon to land again.
>> Until then let me point to that content on the ongoing PR -
>> https://canonical-ubuntu-documentation-library--364.com.readthedocs.build/project/who-makes-ubuntu/councils/dmb-manage-packagesets/#types-of-packagesets
>>
>> What you ask for sounds very much like what we call there "logical
>> packageset".
>>
>> Starting with a list is good, but it also needs a definition.
>> Your second mail tried to "explain what it is" but please rework that to
>> be like
>> a description that validates your initial set that you request but also
>> would be
>> the thing we look up when you ask in the future for things to be
>> added/removed.
>>
>> Furthermore we are not granting permissions on non existing packages.
>> I know some are in the NEW queue, but of your list let us start with
>> those at least somewhat known.
>> And as things get added you can reach out and say "per that approved
>> definition of the set, please also add ..."
>>
>> Due to that I think you'd have to drop:
>>
>> rocm
>> rocm-core
>> composable-kernel
>> rocwmma
>> hipsparselt
>> MIOpen
>>
>> As those do not (yet) exist in Resolute AFAICS.
>>
>> Please also watch out for one aspect when you ask for things to be added
>> or dropped, an that is the impact and reach of a package.
>> Sometimes it is better to leave one package out, as it would raise the
>> bar too much for people to join the uploaders.
>> That is also explained in the doc I shared, search for "Common reasons
>> for exceptions to a pure seed = packageset approach are" there.
>>
>> So much for the packageset request to guide you.
>>
>> You also hinted at the application as an uploader and that you have been
>> unsure.
>> I have not read
>> https://discourse.ubuntu.com/t/application-rocm-package-set-talha-can-havadar/76780
>> yet but from far away it looks fine.
>> The step you are missing is to grab a slot in the agenda
>> https://discourse.ubuntu.com/t/application-core-developer-ural-tunaboyu/75044/1
>> as outlined in
>> https://documentation.ubuntu.com/project/who-makes-ubuntu/developers/dmb-application/
>> (there you find a lot more that can help you)
>>
>> I hope that helps,
>> Christian
>>
>>
>>> but I also mentioned request of creation on my upload rights application
>>> here:
>>> https://discourse.ubuntu.com/t/application-rocm-package-set-talha-can-havadar/76780
>>>
>>> Please let me know about the correct procedure if this is not the one.
>>>
>>> And please see the source names below:
>>> ```
>>> amdsmi
>>> rocm-llvm
>>> rocm
>>> rocm-cmake
>>> rocm-smi-lib
>>> pkg-rocm-tools
>>> rocr-runtime
>>> hipify
>>> rocm-core
>>> hipblas-common
>>> rocalution
>>> rocm-hipamd
>>> rocminfo
>>> rocrand
>>> rocdbgapi
>>> rccl
>>> composable-kernel
>>> hiprand
>>> rocprim
>>> roctracer
>>> rocblas
>>> rocfft
>>> rocsparse
>>> rocthrust
>>> hipcub
>>> hipfft
>>> hipsparse
>>> rocsolver
>>> rocwmma
>>> hipblas
>>> hipsolver
>>> hipblaslt
>>> hipsparselt
>>> MIOpen
>>> ```
>>>
>>> --
>>> Best Regards
>>>
>>> [image: Canonical-20th-anniversary]
>>>
>>> Talha Can Havadar
>>>
>>> Email:
>>>
>>> talha.can.havadar at canonical.com
>>>
>>> Location:
>>>
>>> The Netherlands
>>>
>>>
>>> canonical.com
>>>
>>> ubuntu.com
>>> --
>>> Devel-permissions mailing list
>>> Devel-permissions at lists.ubuntu.com
>>> Modify settings or unsubscribe at:
>>> https://lists.ubuntu.com/mailman/listinfo/devel-permissions
>>>
>>
>>
>> --
>> Christian Ehrhardt
>> Director of Engineering, Ubuntu Server
>> Canonical Ltd
>>
>

-- 
Christian Ehrhardt
Director of Engineering, Ubuntu Server
Canonical Ltd
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/devel-permissions/attachments/20260216/66718aab/attachment-0001.html>