Skip to content
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

run_build_script doesn't check for errors #148

Open
kakra opened this issue Mar 24, 2021 · 0 comments
Open

run_build_script doesn't check for errors #148

kakra opened this issue Mar 24, 2021 · 0 comments

Comments

@kakra
Copy link

kakra commented Mar 24, 2021

Most probable source of the problem:

dkms/dkms

Line 1064 in 218cd4e

exec $run

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.

kakra referenced this issue in atar-axis/xpadneo Mar 24, 2021
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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants