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
busybox: 1.28.3 -> 1.28.4, fix fsck exit code #41024
Conversation
Fixes NixOS#40174 Patch taken from upstream, added local copy because fetchpatch doesn't work with fetchurlBoot.
@nh2 is this something you can test, or otherwise approve/confirm fixes your issue? Thanks! |
No attempt on x86_64-darwin (full log) The following builds were skipped because they don't evaluate on x86_64-darwin: busybox Partial log (click to expand)
|
Success on x86_64-linux (full log) Attempted: busybox Partial log (click to expand)
|
Success on aarch64-linux (full log) Attempted: busybox Partial log (click to expand)
|
Staging has the update, closing due to lack of activity-- since patch is already in upstream it'll be included at some point so all this accomplishes is getting it in sooner :). |
@dtzWill I cannot test it super easily: It requires to trigger a fsck that fixes errors (e.g. by shutting down hard at the right time), and I found it on physical hardware (should be reproducible in VMs as well though). So I'm OK with having this in non-staging only with the next NixOS release. I have reviewed the upstream patch and it should fix our issue. |
Update and add fix for #40174 from upstream.
build-use-sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)