Re: Code reorg in ROCm upstream
Hi Christian,
On 2025-08-22 06:22, Christian BAYLE wrote:
I noticed there is some code reorg in https://github.com/ROCm
https://github.com/ROCm/rocminfo has been deprecated and moved in
https://github.com/ROCm/rocm-systems
Though we still have https://salsa.debian.org/rocm-team/rocminfo
recently updated by Mario
There have been no official releases made from the rocm-systems
repository yet and I still don't know exactly what a release will look
like. We should be updating the upstream bug reporting URLs and project
homepages, but I don't think it has any other impact /yet/.
I'm told that despite the upstream development being moved to a single
super-repository, there will still be separate release tarballs for each
component. The reorganization is a big change for the upstream
developers, but it should not affect Debian much.
Upstream is mirroring commits from the rocm-systems repo back to the
original project repos and will be tagging the releases on the original
project repos for ROCm 7.0.0. Our existing uscan imports will remain an
option to fall back to if we have any difficulties using the initial
rocm-systems releases.
Also interesting to read this focuses on building pytorch:
------
ROCm Systems:
Welcome to the ROCm Systems super-repo. This repository consolidates
multiple ROCm systems projects into a single repository to streamline
development, CI, and integration. The first set of projects focuses on
requirements for building PyTorch.
------
To complete their reorganization in a timely manner, they've been
prioritizing the migration of libraries that are used by PyTorch. Most
of the libraries that are not used by PyTorch will probably get moved later.
This consolidation is basically so that building a full stack required
for PyTorch can be done by cloning three git repos, rather than cloning
a few dozen (and so that changes to coding standards that affect all
projects can be made with three pull requests rather than dozens).
I wouldn't read too much into the change. Whether you have one repo or
dozens of them, what matters is that you have tooling to support your
workflows. The upstream ROCm project has historically had very little
tooling to support common standards and workflows across multiple
repositories, so the theory is that it will be easier if there are fewer
repositories.
None of this is relevant to Debian, so I don't think it will have much
impact on our packaging.
I think we should probably try to stick more at the github/ROCm
structure on salsa.
We will need to see what the official releases look like before we make
changes.
Sincerely,
Cory Bloor
Reply to: