Hello,
We’re looking to see if it’s possible to install / lock a specific version (at any time) of the following dkms module. For example:
dnf module install nvidia-driver:latest-dkms:<version>
We can do this for the most up-to-date version when it is available, but once there is a more recent version, if we try to install the second-to-most-recent version, the install fails.
Said differently, is there a way for us to “lock” the “nvidia-driver:latest-dkms” version to ensure builds are reproducible?
Judging by the discussion here, I’m not sure that it is, but want to be absolutely sure.
Please let me know if anything needs clarification and appreciate the help!
@generix thanks so much for the response and the resource.
I should have indicated in the original post that we’re looking to specifically pin the exact version.
For example a previous exact version was 20240403121530. If I try to install dnf module install nvidia-driver:latest-dkms:20240403121530 now I will get the following error:
missing groups or modules: nvidia-driver:latest-dkms:
Is there a way to pin to this exact version, even after a newer version is released?
The reason we need it so for reproducible builds to ensure that we always have the same version until we want to explicitly upgrade.
Let me know if anything needs clarification!
I don’t think it will work that way, seems contradictory to what module streams are made for. If you want to stick to a specific version, I guess you’ll have to do a plain direct install of the packages kmod-nvidia-dkms-latest-version and nvidia-driver-version, then set the kmod package to “dependency” and a versionlock on the nvidia-driver package.
1 Like