On 2023-05-31 19:28, Adam D. Barratt wrote:
> In the versions in testing, both packages only built for amd64. In
> unstable, they have also built for arm64. Migrating the arm64 hipsparse
> binaries from unstable therefore requires migrating a version of
> rocsparse with arm64 binaries.
Oh, that's a good catch, never thought of that, mainly because in
practice, we only look at amd64. This is a rather new ecosystem and
we're still ironing out the kinks.
A successful build on arm64 is a bit annoying, as we don't expect many
users there -- I'd be surprised if one manages to even get the required
mainboard.
I'm willing to do what it takes to get this fixed in testing, but I'm
not sure which solution, if any, is agreeable to the RT:
(1) Request an unblock for the rocsparse/5.3.0+dfsg-3 as-is
(2) Re-upload hipsparse with a reduced arch: amd64
(3) Prepare new (minimal debdiff) upload for rocsparse, file unblock
request
(4) Remove the arm64 binaries (is that even possible?)
(5) Fix this in the first point release
(6) Alternatives?
Please let me know what, if any, option you'd prefer.
I'm aware that we are shortly before the release and that this might
limit the available options.
Best,
Christian
