bcachefs-tools: 1.7.0 -> 1.7.0-unstable-2024-05-09

[JohnRTitor]

Description of changes

• Fixes cannot mount bcachefs from lvm raid0 device #313350 , which affects LVM users (unencrypted) who can not mount a bcachefs volume.
• Also vendor the updated patch added in bcachefs-tools: patch to fix unlocking encrypted fs at boot with bcachefs-tools-1.7.0 #310504, which affects encrypted partition mounting on boot
• Moved to pkgs/by-name

Things done

• Reviewed changelog koverstreet/bcachefs-tools@v1.7.0...3ac510f
• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• 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/)
• 24.05 Release Notes (or backporting 23.05 and 23.11 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.

---

CC @jezcope @codebam @reedriley for testing

Add a 👍 reaction to pull requests you find important.

[jezcope]

@JohnRTitor Seems to work for me:

❯ bcachefs version
1.7.0-unstable-2024-05-09

and everything is mounted correctly. Thanks! 👍🏻

[JohnRTitor]

Added a comment on why moving to unstable is necessary. Should be good to go now

[alyssais]

We can't backport whatever patch fixes the bug? Generally we prefer not to use non-release versions of packages.

[JohnRTitor]

I am not sure which commit specifically fixes that.

Also commits like these fix a bug that throws error messages at boot involving scanning other non-bcachefs filesystems.

I have reviewed the changelog and the changes are pretty harmless bug fixes, also daily driving this as we speak.

24.05 release is around the corner, I don't think we should ship a broken bcachefs-tools with that. That's why I decided to move to to a unstable commit which does not have any substantial changes.

Honestly, I wish that there was a point release to upgrade to. But there is not, so...

[github-actions]

Successfully created backport PR for release-24.05:

• [Backport release-24.05] bcachefs-tools: 1.7.0 -> 1.7.0-unstable-2024-05-09 #314826