You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During CI, we are not able to catch errors in the post-install script because dkms simply assumes such scripts work without any error and continues, leaving a possibly undefined and broken system state behind. In the vast amount of logging generated by package installers, such an error just disappears in the noise. The user has no clue that something failed, neither they can get an idea of how to fix it.
Suggestion:
dkms should die if an error happens in the run_build_script phase, probably also cleaning up as good as possible. This may require to bubble the error up to the caller instead of handling it right in this function.
The text was updated successfully, but these errors were encountered:
If we let udev evaluate our rules at position 60 (where most other
input rules sit), we can actually make use of uaccess and seat tags.
This allows proper access to the hidraw device because udev will now
assign ACLs for the current seat user to the device nodes.
Signed-off-by: Kai Krakow <[email protected]>
Most probable source of the problem:
dkms/dkms
Line 1064 in 218cd4e
Impact:
During CI, we are not able to catch errors in the post-install script because dkms simply assumes such scripts work without any error and continues, leaving a possibly undefined and broken system state behind. In the vast amount of logging generated by package installers, such an error just disappears in the noise. The user has no clue that something failed, neither they can get an idea of how to fix it.
Suggestion:
dkms should die if an error happens in the run_build_script phase, probably also cleaning up as good as possible. This may require to bubble the error up to the caller instead of handling it right in this function.
The text was updated successfully, but these errors were encountered: