Hi Paul,
On 2026-10-19 12:21, Paul Gevers wrote:
On Sun, 22 Mar 2026 09:00:05 +0100 Paul Gevers <[email protected]> wrote:
Issues preventing migration:
∙ ∙ removing libhsakmt-dev/6.4.3+dfsg-4/amd64 from testing makes
Build-Depends of src:rocminfo uninstallable
∙ ∙ removing libhsakmt-dev/6.4.3+dfsg-4/amd64 from testing makes
Build-Depends of src:ucc uninstallable
∙ ∙ removing libhsakmt-dev/6.4.3+dfsg-4/amd64 from testing makes
Build-Depends of src:ucx uninstallable
is apparently caused by:
* Drop libhsakmt1 and libhsakmt-dev binary packages as they
may not have a stable interface going forward
* Drop d/p/0007-shared-libhsakmt.patch
* Drop d/p/0009-fix-missing-symbols.patch
It doesn't look like this has been communicated to the reverse
Build-Depends. Maybe better to add the binaries back for now such that
src:rocr-runtime can migrate and coordinate its removal ahead of the
actual removal?
Good point. I only searched the binary package archive for reverse
dependencies, and didn't think to check B-D. Fortunately, nothing
actually used libhsakmt-dev, despite it being listed in the B-D. It
could be dropped from the B-D rocminfo, ucx, and ucc without any further
changes.
The latest uploads to unstable for rocminfo, ucx, and ucc have removed
libhsakmt-dev from their B-D, so rocr-runtime should be able to migrate
after those components.
Sincerely,
Cory Bloor
