[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Upstream reorganization of rocm-device-libs, rocm-compilersupport and rocm-hipamd



On 2024-03-01 21:20, Cordell Bloor wrote:
> The tricky question is how to handle the transition to rocm-clr. The
> last ROCm release using the old rocm-hipamd repo was ROCm 5.6.1. If
> we're go to send it through NEW for the switchover to rocm-clr, I
> suppose we might as well skip ROCm 5.7.1 and go straight to ROCm 6 since
> that version needs to go through NEW anyway. An alternative approach
> would be to take the rocm-clr sources into rocm-hipamd so we can update
> to HIP from ROCm 5.7.1, and then transition the source package from
> rocm-hipamd to rocm-clr with the update to ROCm 6.0 when it's going
> through NEW anyway.
> 
> I must admit, part of my apprehension on renaming the rocm-hipamd source
> package immediately is that this would mean that Ubuntu 24.04 would get
> HIP 5.6.1 rather than 5.7.1. The changelog for 5.7.1 is pretty short and
> nothing stands out as vital [1], but the commit log suggests more
> substantial changes [2]. If possible, I would prefer to help them to
> freeze for their LTS release on the final release in the ROCm 5 series.

Oh. With that added perspective, I'd postpone the immediate rename, for
the reason mentioned in the last sentence.

> However, if that would require an approach that is contrary to
> best-practice in Debian, then upstream made their bed and will have to
> lie in it.

In the end, it's about delivering the best results for users, so some
maintenance pragmatism is always acceptable, I think. Especially in
context of an LTS.

Best,
Christian


Reply to: