-
-
Notifications
You must be signed in to change notification settings - Fork 14k
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
zfsUnstable: 2.1.13 -> 2.2.0-rc4 #246163
zfsUnstable: 2.1.13 -> 2.2.0-rc4 #246163
Conversation
a6340eb
to
3492f63
Compare
There is some discussion in duplicate #245330 about waiting until 2.2.0 is released before updating zfsUnstable. |
I chatted about it with Mic92 in private FWIW. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
zfs 2.2.0 will also add armv7l to the cpu targets block; please add isAarch32
in meta.platforms accordingly
I would prefer we go for #246300 first, then we can consider this open until 2.2.0-rcX is run enough by our maintainers I'd say? |
openzfs/zfs#15140 FWIW |
Works well so far on my machine. |
Updated to latest rc, which also fixes openzfs/zfs#15140 |
Commit and PR title are both incorrect. 2.1.13 and 2.2.0-rc4 I've applied the kernel module to one of my systems running 6.1.x, but getting a failure from
|
I think the PR should allow 6.5 kernel or did I miss something? |
@ofborg build zfs |
Yes, this is still failing to build stage1 for me.
|
Interesting. I am using
Cannot reproduce this issue. I found an error in the test, that I fixed here: #255484 |
Ok, I narrowed it down to the Here's a pared down config that will fail:
|
Found the issue: In extra-utils for the initrd we do: |
Update this is not the actual issue. But here is the fix: #255583 |
then linuxKernel.packages.linux_6_4 | ||
else linuxKernel.packages.linux_6_1; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is inconsistent with the rest of the file
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are you nitpicking a formatting inconsistency 3 weeks after a PR was merged?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because I only stumbled upon this PR yesterday when I dug up my old zfsUnstable bump PR.
Description of changes
Things done
sandbox = true
set innix.conf
? (See Nix manual)nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)