lmstudio: 0.3.11 -> 0.3.14-3

[deftdawg]

Things done

• Make lms command line tool available
• Rename lmstudio executable to lm-studio to match online documentation and appImage executable
  • If you ask DeepSeek or ChatGPT how to use lm-studio, it will tell you the command is lm-studio, so renamed to match that

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin (BROKEN UPSTREAM since lm-studio 0.3.6)
• 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/)
• 25.05 Release Notes (or backporting 24.11 and 25.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.

---

Add a 👍 reaction to pull requests you find important.

Ping maintainers @cig0 @eeedean @crertel

[crertel]

I'm a little iffy on the rename of lm-studio, 'cause it might break stuff for some folks, but I'm not strongly against it.

[crertel]

(testing out pr now)

[deftdawg]

I'm a little iffy on the rename of lm-studio, 'cause it might break stuff for some folks, but I'm not strongly against it.

I'm not sure why it was renamed from the source, maybe to match the package name?

ls /nix/store/*lm*extracted/lm-studio
/nix/store/8bpzvmlm54r83v8ynqihrn69w7v0d80m-lmstudio-0.3.11-extracted/lm-studio
/nix/store/f9l455zqngp7qwqhpfz2fzvbz0jwdhkz-lmstudio-0.3.6-extracted/lm-studio
/nix/store/gknfnzhkfv4slbjkqd7qcf05fn1hfsgq-lmstudio-0.3.10-extracted/lm-studio

[crertel]

So, the good news is that executable runs. The bad news seems to be it won't start.

Does it work on your machine?

[deftdawg]

The app has to be open for lms to connect to it

[crertel]

@deftdawg Mind bumping to 0.3.12, while you got the hood up? (hashes for both Linux and Mac too if possible).

[crertel]

LGTM, but I think maybe a typo snuck in to the mac hash?

[crertel]

@deftdawg we got scooped again...they're at 0.3.13 now, lol.

Mac (via nix-prefetch-url "https://installers.lmstudio.ai/darwin/arm64/0.3.13-1/LM-Studio-0.3.13-1-arm64.dmg" | xargs nix hash to-sri --type sha256):

sha256-fPrTbu/qN0SxLhX9ACd1/T3HLFxQDJ7czHg7QTATaLs=

Linux (via nix-prefetch-url "https://installers.lmstudio.ai/linux/x64/0.3.13-1/LM-Studio-0.3.13-1-x64.AppImage" | xargs nix hash to-sri --type sha256):

sha256-OSNxe2KFj9stnM5x11exMlFDiy+gOa31HRyxzwHtwAk=

[deftdawg]

It's a bit frustrating we can't get merges on this package done in a timely manner... Do we need all the maintainers to review before it can merge?

[crertel]

Agreed. I think there's a way of setting up an auto-update script that could help with this; I'll let you know what I find out.

[deftdawg]

Oh, okay no worries, I didn't know ofBorg worked off of commit messages like that. All good, I'll redo it that way in a couple hours when I'm back home. 🍻

commit message fixed

[crertel]

@jopejoe1 not to be a bother, but since you helped out last time, could you help us merge? (if not, that's fine!)

[deftdawg]

Evening @crertel! Just saw a beta for 0.3.14 pop-up on LM Studio's site so came over here to see if this is still pending review...

Was thinking if this doesn't merge before 0.3.14, my next push might just drop @cig0 and @eeedean from the maintainers list at the same time it bumps versions, so future merges can happen quicker.

[FliegendeWurst]

The easiest solution for fast updates is adding an updateScript, so r-ryantm will automatically update. Then you can merge the update with the merge bot, if you are listed in meta.maintainers.
Of course it would also be good if meta.maintainers contains only active maintainers.

[deftdawg]

Thanks @FliegendeWurst, I applied your changes and then re-squashed the PR.

[FliegendeWurst]

CI check for formatting failed, please run nixfmt 'pkgs/by-name/lm/lmstudio/package.nix' with nixpkgs' nixfmt

[deftdawg]

CI check for formatting failed, please run nixfmt 'pkgs/by-name/lm/lmstudio/package.nix' with nixpkgs' nixfmt

I used nix-shell to get nixfmt, then ran it on both files and re-squash committed and force pushed it, but nixfmt step still failed 😢

[FliegendeWurst]

You did nix-shell (no arguments) in the nixpkgs root, right? (or used the nixfmt-rfc-style package?)

[deftdawg]

You did nix-shell (no arguments) in the nixpkgs root, right? (or used the nixfmt-rfc-style package?)

I did nix-shell -p nixfmt, then ran nixfmt on each of the two files... It definitely reformatted them (changes are visible here: https://github.com/NixOS/nixpkgs/compare/e94b24304eb27b342a499a2abcf46c6211cbe29f..e564476c52dc13602ce46df1347a7f8997b4953b)

Was I supposed to use nixfmt-rfc-style instead of nixfmt?

[FliegendeWurst]

Yes. It is a bit confusing that the regular nixfmt is not the right version for use in nixpkgs.

You can do either

• nix-shell (no arguments!) in nixpkgs repository root
• nix-shell -p nixfmt-rfc-style

To get the right one.

[deftdawg]

Reformatted with nix-shell -p nixfmt-rfc-style, should be ready to go now 🤞

[crertel]

Thanks for your help @FliegendeWurst ! Congrats @deftdawg !