-
Notifications
You must be signed in to change notification settings - Fork 14
refactor: akmods
possibly needs to adjust to some upstream changes
#211
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
akmods
possibly needs to adjust to these changesakmods
possibly needs to adjust to some upstream changes
@gmpinder |
Ok so it's looking like we will need to remove the version prop and just use base. But we also need to have a way to specify the need for the nvidia image. |
My build is failing now:
|
This happens because Universal Blue separated akmods into VirtualBox akmod now resides in |
@lorduskordus Your reported issue is fixed, but usage of unstable CLI is required, until new GitHub Action gets released: https://blue-build.org/reference/github-action/#use_unstable_cli-optional This PR fixed it: |
All adapting |
Unfortunately, GH Action v1.4.0 released today uses BlueBuild CLI v0.8.4 but support for extra akmods is in v0.8.5, so I will still have to keep this issue open. This means that usage of unstable CLI is still required. |
New GHA version was released today containing those fixes |
ublue-os/akmods#176
ublue-os/akmods#171 (comment)
Upstream akmods refactor is not yet done, so we will see if there is anything else that needs to be done
The text was updated successfully, but these errors were encountered: