nexusmods-app: 0.7.1 -> 0.7.2

[MattSturgeon]

• Bump version: 0.7.1 -> 0.7.2
• Upstream's changelog
• Previous update PR

Also:

• Still need .NET 8 runtime available while building, for the StrawberryShake dependency 😦
• Replaced usage of convert with magick to resolve deprecation warnings in the build log.
• The package's tests still seem flaky, they failed when building locally
  • Actually building/running the app works fine though

Notes for end-users

Tip

When upgrading from version 0.7.0 or newer, it should be safe to upgrade without resetting/uninstalling.

Caution

When upgrading from a version older than 0.7.0, you will need a fresh start.
If you have configuration leftover from an old version, the updated app will crash.

See upstream's guide on how to uninstall the app.

Resetting tips

You can reset all modded games and wipe your nexusmods-app config using:

NexusMods.App uninstall-app

• This should be done before updating the app.
• Be careful: There's no way to recover a wiped config!

If you've run the appimage version from upstream, or a pre-0.6 nixpkgs version, you may also need to remove old desktop entries to avoid other issues:

rm ~/.local/share/applications/com.nexusmods.app.desktop

Caution

Known issues are listed on the changelog, but include:

• Stardew Valley (Native Linux version) is not detected when installed via Heroic Launcher on Linux. The Windows version of the game can be used instead until this issue is fixed.
• Bundled mods included with collections do not appear in the UI but are still applied to your game.
• The success rating for collections is not showing the correct value.
• The game version is not checked when adding a collection meaning you can install outdated mods without being warned.
• The Collections (WIP) page is not filtered by game.
• The "Switch View" option does not persist in the Library/Installed Mods view.
• The "Load Order" heading toggle does not persist in the Load Order view.

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/)
• 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.

[corngood]

Out of curiosity, did the update script work? I take it you didn't get an automatic update PR from the bot?

[MattSturgeon]

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 375824

---

x86_64-linux

✅ 2 packages built:

• nexusmods-app
• nexusmods-app-unfree

[MattSturgeon]

Out of curiosity, did the update script work?

I ran ./pkgs/by-name/ne/nexusmods-app/update.bash, out of habbit...

Testing again on master:

$ nix-shell maintainers/scripts/update.nix --argstr package nexusmods-app

Going to be running update for following packages:
 - nexusmods-app-0.7.1

Press Enter key to continue...

Running update for:
 - nexusmods-app-0.7.1: UPDATING ...
 - nexusmods-app-0.7.1: DONE.

Packages updated!

I noticed that unlike running update.bash manually, the update script sits on UPDATING ... for ages without printing any output from the underlying script. A little frustrating to not see any feedback.

But after waiting several minutes, it did complete successfully.

I take it you didn't get an automatic update PR from the bot?

I haven't seen one (not sure what it'd look like, unless you mean one like #329592). This release only came out yesterday though, so maybe the bot hasn't had chance to check for updates yet?

[corngood]

unless you mean one like #329592

Yeah, like that. Someone pointed me at where the logs live: https://r.ryantm.com/log/nexusmods-app/, and it looks like it's only run every couple weeks or so?

Thanks for checking.

[SuperSandro2000]

I don't understand why ofborg is failing to build the package

[MattSturgeon]

I don't understand why ofborg is failing to build the package

Interesting:

  Failed NexusMods.Games.StardewValley.Tests.StardewValleyInstallersTests.CanInstallMod(filename: "Portraits_for_Vendors.zip") [813 ms]
  Error Message:
   VerifyException : Directory: /build/NexusMods.App/tests/Games/NexusMods.Games.StardewValley.Tests
NotEqual:
  - Received: StardewValleyInstallersTests.CanInstallMod_filename=Portraits_for_Vendors.zip.received.txt
    Verified: StardewValleyInstallersTests.CanInstallMod_filename=Portraits_for_Vendors.zip.verified.txt

I also don't have this error locally...

Maybe we should add "NexusMods.Games.StardewValley.Tests.StardewValleyInstallersTests.CanInstallMod" to disabledTests?

Scrolling through the log, there's a few errors like Failed to start a process with file path 'xdg-settings' (also for xdg-open), but I think these are unrelated.

[MattSturgeon]

I've disabled the test. Ofborg seems happy now 🎉