Hi Lorenzo, Lorenzo Bertini, on 2023-01-09: > Dear maintainer, > > rocminfo, rocm-device-libs and rocm-cmake packages have the same names as their > counterparts in the "official" repo in https://repo.radeon.com/rocm/apt/. When I add > this repository, apt tries to install the system version, so I have to manually > force the version the other packages in the repo need. > > How should this be handled? Thanks for your report, I must admit that has been bothering me as well at some point, but AMD actually provides an escape hatch for this case. Since ROCm 3.3, each package in repo.radeon.com has a versioned equivalent, e.g. rocminfo5.4.1 for the rocminfo command of ROCm 5.4.1. Note that if you use the versioned package names, you need to use it consistently for your whole ROCm installation. However this makes upgrading version a bit less transparent than using the unversioned packages allows; but I recall having read in ROCm documentation that certain version jumps used to require a full reinstallation anyway. An other option involves pinning package versions, but I'm not personally comfortable with this particular way of managing packages, but I believe it would work if you have to deal with older ROCm versions than 3.3. If you are trying to keep up with the lastest/ stream of packages, I'm not sure I have a good solution at hand right now. In hope this helps, -- Étienne Mollier <emollier@emlwks999.eu> Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/tty1, please excuse my verbosity. On air: Blind Guardian - Road Of No Release
Attachment:
signature.asc
Description: PGP signature