lm_sensors: 3.6.0 -> 3.6.2

[peterhoeg]

Current upstream is effectly dead (no activity since 2020), but openSUSE is actively maintaining a fork that gentoo also uses.

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• 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/)
• Nixpkgs 25.11 Release Notes (or backporting 24.11 and 25.05 Nixpkgs Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
• NixOS 25.11 Release Notes (or backporting 24.11 and 25.05 NixOS Release notes)
  • (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, pkgs/README.md, maintainers/README.md and other contributing documentation in corresponding paths.

---

Add a 👍 reaction to pull requests you find important.

[oxalica]

openSUSE is actively maintaining a fork that gentoo also uses.

Source1: https://build.opensuse.org/projects/Base:System/packages/sensors/files/sensors.spec
Source2: https://packages.gentoo.org/packages/sys-apps/lm-sensors

[oxalica]

👍 on the upstream switch. Builds and works for me.

Just a few nits.

[oxalica]

Does ${toString stdenv.hostPlatform.isStatic} work? The only difference is that toString false == "". Not sure if it breaks stuff.1

[peterhoeg]

While verbose, it's very clear what is going on so I favour this way of doing it for readability's sake.

[oxalica]

Is it okay to call it "openSUSE fork"? I'm not sure if @hramrach is doing it on behalf of OpenSUSE, or as a personal fork that is used by distros.

[peterhoeg]

My understanding is that it is in his capacity as a suse employee, but we can of course also just drop that bit here. We don't really gain anything by leaving it in here.

[wolfgangwalther]

Re-running CI due to a odd failure fixed in #416448

[oxalica]

Diff LGTM.