One of the possibility is that rocm-docs-build take this into account
But the question is how many rocm package have this issue?
Shouldn't this be fixed upstream ?

Reply via email to