zfsUnstable: 2.1.12 → 2.1.13-unstable-2023-08-02

[toastal]

https://github.com/openzfs/zfs/commits/zfs-2.1.13-staging

With anecdote from a NixOS user that it’s working
openzfs/zfs#15125

…working for me as well as I built+booted from this commit.

Description of changes

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 23.11 Release Notes (or backporting 23.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

[toastal]

I didn't write this `if`?

[RaitoBezarius]

I didn't write this if?

Yes you didn't but you should keep the semantics :P.

[toastal]

Oh, so it was removed in the last commit. I see what y’all’re trying to say now.

[toastal]

The update has been pushed a while ago.

[toastal]

I’ve been booting successfully from this commit (with rebases) for a week now.

[toastal]

This has built & been successfully ran for me from kernels

• 6.4.6
• 6.4.7
• 6.4.8
• 6.4.9
• 6.4.10
• 6.4.11

[magneticflux-]

Should zfsUnstable track the 2.2.0 release candidates, or just the staging branch of the next patch?

[toastal]

@magneticflux-

https://github.com/NixOS/nixpkgs/blob/master/pkgs/os-specific/linux/zfs/unstable.nix#L20-L22

Historically & according to this comment, zfsUnstable points to the most recent staging. If you’re here because you too would like to keep on the latest stable Linux kernel, I too am not sure what the hold up is as this unstable is supposed to follow latest staging from OpenZFS. On that note: tested on 6.4.11 with success too. I’ve been rebasing often tho because I’m using this branch as my machines’ Nixpkgs while I await a merge to stay with 6.4.x.

[RaitoBezarius]

Basically it's moving all the time, I do not have time to test it and I am on vacations :). Le sam. 19 août 2023 à 17:42, toastal ***@***.***> a écrit :

…

@magneticflux- <https://github.com/magneticflux-> https://github.com/NixOS/nixpkgs/blob/master/pkgs/os-specific/linux/zfs/unstable.nix#L20-L22 Historically & according to this comment, zfsUnstable points to the most recent staging. If you’re here because you too would like to keep on the latest stable Linux kernel, I too am not sure what the hold up is as this unstable is *supposed* to follow latest staging from OpenZFS. On that note: tested on 6.4.11 with success too. — Reply to this email directly, view it on GitHub <#246300 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACMZRHX7UXAC3RC3KIRMMTXWDNIHANCNFSM6AAAAAA25XDGQU> . You are receiving this because your review was requested.Message ID: ***@***.***>

[toastal]

@RaitoBezarius but the last commit for 2.1.13 staging in upstream is @RaitoBezarius ’s own commit. Didn’t you test before it was merged?? 😅

[RaitoBezarius]

But I don't understand why the PR is being repushed force everyday then? Le dim. 20 août 2023 à 12:42, toastal ***@***.***> a écrit :

…

@RaitoBezarius <https://github.com/RaitoBezarius> but the last commit for 2.1.13 staging in upstream is @RaitoBezarius <https://github.com/RaitoBezarius> ’s own commit. Didn’t you test before it was merged?? 😅 — Reply to this email directly, view it on GitHub <#246300 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACMZRCVR6VDFPCLZK65XJLXWHSZHANCNFSM6AAAAAA25XDGQU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[toastal]

I'm using this merge request as my NixOS config’s Nixpkgs on two machines, otherwise I couldn’t get around the version lock & will need to downgrade to the LTS kernel. To get the latest packages, I gotta rebase. -- toastal ไข่ดาว | https://toast.al PGP: 7944 74b7 d236 dab9 c9ef e7f9 5cce 6f14 66d4 7c9e