RE: tarballs for rocm-libraries
[AMD Official Use Only - AMD Internal Distribution Only]
AFAIK, there is no plan to start a ROCm/origami project.
I believe the monorepo's will have the subproject tarballs soon, maybe in 7.1.1 next week (?) or 7.2
Here is a precursor to that I used for origami https://src.fedoraproject.org/rpms/rocm-origami/blob/rawhide/f/fetch.sh
I like the idea of sharing code between Debian and Fedora about 80% of the magic in the rules file in the cmake config.
As an extreme example, here is the compiler on Fedora
https://src.fedoraproject.org/rpms/rocm-compilersupport/blob/rawhide/f/rocm-compilersupport.spec#_439
Here is rough port of same compiler on Debian
https://salsa.debian.org/trix/rocm-llvm/-/blob/debian/latest/debian/rules?ref_type=heads#L61
Fedora is already shared with OpenSUSE, here is similar
https://build.opensuse.org/projects/home:trix/packages/rocm-compilersupport/files/rocm-compilersupport.spec?expand=1
A risk Debian should consider is if/when the ROCm component repos stop being updated and there is only the monorepos being updated. It would be very disruptive to the workflow if 20-30 components all had to change at the same time, to my guess, a bare /debian directory like the rocm-llvm compiler above.
Tom
-----Original Message-----
From: Christian BAYLE <bayle@debian.org>
Sent: Saturday, November 8, 2025 3:03 AM
To: debian-ai@lists.debian.org
Subject: Re: tarballs for rocm-libraries
Hello,
all these moves are quite confusing
There is a document here
https://github.com/ROCm/rocm-libraries/blob/develop/docs/migration-process.md
I wonder if we should continue using the various tarballs or have some kind of standard watch file to extract subprojects
for rocm-systems and rocm-libraries
we could probably also gather some lib based on the https://github.com/ROCm/rocm-libraries/blob/develop/docs/continuous-integration.md
graph to facilitate transitions
This would also be a good idea we share more with fedora as it was already suggested by Cory if I remember well, and thank you for sharing this.
I suppose one of the starting point for fedora is https://fedoraproject.org/wiki/SIGs/HC
Quite interesting to be able to compare easily https://trix.fedorapeople.org/composable_kernel.spec
and
https://salsa.debian.org/rocm-team/composable-kernel/-/blob/experimental/debian/rules
and to work on common tarballs ;-)
Le 06/11/2025 à 16:00, Rix, Tom a écrit :
> [Public]
>
>
> If you look at the ROCm repositories ex/ ROCm/rocBLAS: [DEPRECATED]
> Moved to ROCm/rocm-libraries repo <https://github.com/rocm/rocBLAS>
>
> You will see that they are being moved to a mono repo rocm-libraries
> ROCm/rocm-libraries: monorepo for rocm libraries <https://github.com/
> ROCm/rocm-libraries> and other mono repo rocm-systems
>
> While tarballs are still being posted to the old locations, there are
> problems now with projects without existing individual public locations.
>
> Hipblaslt is now dependent on a code generator ‘origami’
> rocm-libraries/ shared/origami at develop · ROCm/rocm-libraries
> <https://github.com/ ROCm/rocm-libraries/tree/develop/shared/origami>
>
> For Fedora, I have submitted this PR to create tarballs similar to the
> llvm-project as a first step.
>
> A script for exporting tarballs. by trixirt · Pull Request #2494 ·
> ROCm/ rocm-libraries
> <https://github.com/ROCm/rocm-libraries/pull/2494>
>
> Please review to make sure it will work for you as well.
>
I don't see any reason why it wouldn't work
> Ideally one would update just the tarball URL for the projects to the
> new (not yet implemented) tarball location.
>
Is the plan to create an ROCm/origami project ?
> And we could gently migrate packages to use to the new locations.
>
> Tom
>
Christian B.
Reply to: