We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I've submitted a PR to upstream zfs so that all "generic" or "redhat" custom RPMs built from the source tree can be signed by default.
Once this lands in a released version of ZFS, the existing patch needs to be removed.
openzfs/zfs#15744
The text was updated successfully, but these errors were encountered:
Looks like this was merged today. 🥳 So, I have a tentative assumption that this should be present in the next release... zfs 2.2.3.
Sorry, something went wrong.
Looks like ZFS 2.2.3 is nearing release and that includes the patch we use to ensure kmods sign...
openzfs/zfs#15836
Here I will stage a change for the kmod signing here such that we only patch on 2.2.2 and older.
chore: don't patch for zfs 2.2.3 or newer (#12)
e2b0f81
Relates to: ublue-os/ucore#112
refactor: zfs version patch logic is more correct
464f859
Fixes: ublue-os/ucore#112
Successfully merging a pull request may close this issue.
I've submitted a PR to upstream zfs so that all "generic" or "redhat" custom RPMs built from the source tree can be signed by default.
Once this lands in a released version of ZFS, the existing patch needs to be removed.
openzfs/zfs#15744
The text was updated successfully, but these errors were encountered: