text:
colima: 0.5.6 -> 0.6.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/colima/versions.
meta.description for colima is: Container runtimes with minimal setup
meta.homepage for colima is: https://github.com/abiosoft/colima
Updates performed

Golang update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.6.0 with grep in /nix/store/qzwki7iyaaz0aqd3gnn9i6lssb5fbw2j-colima-0.6.0
found 0.6.0 in filename of file in /nix/store/qzwki7iyaaz0aqd3gnn9i6lssb5fbw2j-colima-0.6.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
colima

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/qzwki7iyaaz0aqd3gnn9i6lssb5fbw2j-colima-0.6.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A colima https://github.com/r-ryantm/nixpkgs/archive/fe70b976b09a7f4a7692cf15caddd4f995e2ac7c.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/fe70b976b09a7f4a7692cf15caddd4f995e2ac7c#colima

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/qzwki7iyaaz0aqd3gnn9i6lssb5fbw2j-colima-0.6.0
ls -la /nix/store/qzwki7iyaaz0aqd3gnn9i6lssb5fbw2j-colima-0.6.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

colima

Maintainer pings
cc @aaschmid @tricktron for testing.

https://github.com/abiosoft/colima/releases/tag/v0.6.2

https://github.com/NixOS/nixpkgs/pull/264446 colima >= 0.6.0 requires lima >= 0.18.0

@NixOS/darwin-maintainers: Can somebody test this on native x86_64-darwin?

Let's wait for CI otherwise :)

i'm not a darwin maintainer but it works on my x86_64-darwin machine

authors: infinisil mjgallag r-ryantm tricktron


text:
jruby: 9.0.5.0 -> 9.1.5.0

Motivation for this change
Things done

[ ] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[ ] NixOS
[x] macOS
[x] Linux

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Thanks!

source: gharchive/pull-request

repo: NixOS/nixpkgs

license: MIT

license_type: permissive

license_source: github-api


text:
nixos/snapraid: remove from top-level

I don't use this tool but saw it in the top level and that's not where it should live.
This could arguably also be seen as a backup tool; it's a bit of an in-between.
Description of changes

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

[x] Fits CONTRIBUTING.md.

Priorities
Add a :+1: reaction to pull requests you find important.

I am not sure hardware is the right place as it does not install any drivers. iirc I put it in tasks as it's the same place as swraid.nix, which is probably the closest tool in nixpkgs. Maybe under services is best?

I am not sure hardware is the right place as it does not install any drivers. iirc I put it in tasks as it's the same place as swraid.nix, which is probably the closest tool in nixpkgs. Maybe under services is best?

i am also in favour of software as essentially snapraid is a daemon which periodically creates parity files of a set of folders. Maybe borgbackup (also under software) is a better comparison?

authors: Atemu lunik1 makefu


text:
nexus-mods-app: init at 0.2.2

Description of changes
From the project:

a mod installer, creator and manager for all your popular games

Closes #270358.
Things done

Built on platform(s)

[x] 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/)
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.

Priorities
Add a :+1: reaction to pull requests you find important.

This builds but I can't really get any functionality out of it although I may not be using it correctly. Most commands I've tried seem to fail.

Thank you so much for testing this with more commands! I'll try adding more tests to have a baseline which we can use to communicate upstream.

From the project FAQ:

Do not ask for support for these tools until official announcements and a product launch is made.

So we should probably leave this as a draft PR until launch.

tests which rely on third party services anywhere in nixpkgs

I didn't even think this was possible. Isn't everything sandboxed?
Also, after looking at this again, the failing commands still return 0 exit status (from the server itself I'm guessing) so I don't think these tests are even working correctly.
It looks like a cool app that could really improve the modding experience on Linux and NixOS especially. Please let me know if/when you pick this back up I would be happy to test it.

v0.3 in case someone wants to test it.

Still no luck for me.
This complains about skia.
nix run github:l0b0/nixpkgs/nexus-mods-app#nexus-mods-app:
00:00:00.127 [DEBUG] Starting UI window
00:00:00.133 [DEBUG] Using sqlite data store at /home/chris/.local/share/NexusMods.App/DataModel/DataModel.sqlite
00:00:00.314 [FATAL] Exception crashed the application!|System.TypeInitializationException: The type initializer for 'SkiaSharp.SKImageInfo' threw an exception.
 ---> System.DllNotFoundException: Unable to load shared library 'libSkiaSharp' or one of its dependencies. In order to help diagnose loading problems, consider using a tool like strace. If you're using glibc, consider setting the LD_DEBUG environment variable:
libfontconfig.so.1: cannot open shared object file: No such file or directory
/nix/store/jj2z9pz1y9p64apynww6mn7ipcbv5whm-dotnet-runtime-8.0.1/shared/Microsoft.NETCore.App/8.0.1/libSkiaSharp.so: cannot open shared object file: No such file or directory
/nix/store/ajw4lal6ibywj9yjf84lnc7ss0w4shn7-nexus-mods-app-0.3/lib/nexus-mods-app/liblibSkiaSharp.so: cannot open shared object file: No such file or directory
/nix/store/jj2z9pz1y9p64apynww6mn7ipcbv5whm-dotnet-runtime-8.0.1/shared/Microsoft.NETCore.App/8.0.1/liblibSkiaSharp.so: cannot open shared object file: No such file or directory
/nix/store/ajw4lal6ibywj9yjf84lnc7ss0w4shn7-nexus-mods-app-0.3/lib/nexus-mods-app/libSkiaSharp: cannot open shared object file: No such file or directory
/nix/store/jj2z9pz1y9p64apynww6mn7ipcbv5whm-dotnet-runtime-8.0.1/shared/Microsoft.NETCore.App/8.0.1/libSkiaSharp: cannot open shared object file: No such file or directory
/nix/store/ajw4lal6ibywj9yjf84lnc7ss0w4shn7-nexus-mods-app-0.3/lib/nexus-mods-app/liblibSkiaSharp: cannot open shared object file: No such file or directory
/nix/store/jj2z9pz1y9p64apynww6mn7ipcbv5whm-dotnet-runtime-8.0.1/shared/Microsoft.NETCore.App/8.0.1/liblibSkiaSharp: cannot open shared object file: No such file or directory

   at SkiaSharp.SkiaApi.sk_colortype_get_default_8888()
   at SkiaSharp.SKImageInfo..cctor()
   --- End of inner exception stack trace ---
   at Avalonia.Skia.PlatformRenderInterface..ctor(Nullable`1 maxResourceBytes)
   at Avalonia.Skia.SkiaPlatform.Initialize(SkiaOptions options)
   at Avalonia.SkiaApplicationExtensions.<>c.<UseSkia>b__0_0()
   at Avalonia.AppBuilder.SetupUnsafe()
   at Avalonia.AppBuilder.Setup()
   at Avalonia.AppBuilder.SetupWithLifetime(IApplicationLifetime lifetime)
   at Avalonia.ClassicDesktopStyleApplicationLifetimeExtensions.StartWithClassicDesktopLifetime(AppBuilder builder, String[] args, Action`1 lifetimeBuilder)
   at NexusMods.App.Startup.Main(IServiceProvider provider, String[] args) in /build/source/src/NexusMods.App/Startup.cs:line 26
00:00:00.711 [DEBUG] Startup handler returned 0

I can't tell if this is trying to make a file or run one, but it also fails.
nix run github:l0b0/nixpkgs/nexus-mods-app#nexus-mods-app -- nexus-login
00:00:00.153 [DEBUG] Running command: nexus-login
00:00:00.172 [DEBUG] Using sqlite data store at /home/chris/.local/share/NexusMods.App/DataModel/DataModel.sqlite
00:00:00.248 [ERROR] Error running command|System.ComponentModel.Win32Exception (2): Failed to start a process with file path 'update-desktop-database'. Target file or working directory doesn't exist, or the provided credentials are invalid. ---> System.ComponentModel.Win32Exception (2): An error occurred trying to start process 'update-desktop-database' with working directory '/home/chris'. No such file or directory
   at System.Diagnostics.Process.ForkAndExecProcess(ProcessStartInfo startInfo, String resolvedFilename, String[] argv, String[] envp, String cwd, Boolean setCredentials, UInt32 userId, UInt32 groupId, UInt32[] groups, Int32& stdinFd, Int32& stdoutFd, Int32& stderrFd, Boolean usesTerminal, Boolean throwOnNoExec)
   at System.Diagnostics.Process.StartCore(ProcessStartInfo startInfo)
   at CliWrap.Utils.ProcessEx.Start() in /_/CliWrap/Utils/ProcessEx.cs:line 56
   at CliWrap.Utils.ProcessEx.Start() in /_/CliWrap/Utils/ProcessEx.cs:line 68
   at CliWrap.Command.ExecuteAsync(CancellationToken forcefulCancellationToken, CancellationToken gracefulCancellationToken) in /_/CliWrap/Command.Execution.cs:line 307
   at CliWrap.Command.ExecuteAsync(CancellationToken cancellationToken) in /_/CliWrap/Command.Execution.cs:line 326
   at NexusMods.CrossPlatform.Process.ProcessFactory.ExecuteAsync(Command command, CancellationToken cancellationToken) in /build/source/src/NexusMods.CrossPlatform/Process/ProcessFactory.cs:line 14
   at NexusMods.CrossPlatform.ProtocolRegistration.ProtocolRegistrationLinux.Register(String protocol, String friendlyName, String workingDirectory, String commandLine) in /build/source/src/NexusMods.CrossPlatform/ProtocolRegistration/ProtocolRegistrationLinux.cs:line 68
   at NexusMods.CrossPlatform.ProtocolRegistration.ProtocolRegistrationLinux.RegisterSelf(String protocol) in /build/source/src/NexusMods.CrossPlatform/ProtocolRegistration/ProtocolRegistrationLinux.cs:line 36
   at NexusMods.Networking.NexusWebApi.LoginManager.LoginAsync(CancellationToken token) in /build/source/src/Networking/NexusMods.Networking.NexusWebApi/LoginManager.cs:line 103
   at NexusMods.Networking.NexusWebApi.LoginVerbs.NexusLogin(LoginManager loginManager, CancellationToken token) in /build/source/src/Networking/NexusMods.Networking.NexusWebApi/LoginVerbs.cs:line 18
   at System.CommandLine.Invocation.InvocationPipeline.<>c__DisplayClass4_0.<<BuildInvocationChain>b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass17_0.<<UseParseErrorReporting>b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass12_0.<<UseHelp>b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.CommandLine.Invocation.InvocationPipeline.<InvokeAsync>g__FullInvocationChainAsync|2_0(InvocationContext context)
   at System.CommandLine.Parsing.ParseResultExtensions.InvokeAsync(ParseResult parseResult, IConsole console)
   at System.CommandLine.Parsing.ParserExtensions.InvokeAsync(Parser parser, String[] args, IConsole console)
   at NexusMods.SingleProcess.CommandLineConfigurator.RunAsync(String[] args, IRenderer renderer, CancellationToken token)
   at NexusMods.App.StartupHandler.HandleCliCommandAsync(String[] args, IRenderer renderer, CancellationToken token) in /build/source/src/NexusMods.App/StartupHandler.cs:line 24
00:00:00.577 [DEBUG] Startup handler returned 0

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/warnings-when-getting-net-dependencies/39844/1

@siph The latest push applies some things I found in other packages:

doCheck defaults to false, but I'd like to run tests if at all possible.
Supports only Linux, because I don't have hardware to test on any other hardware.
Adds desktop item, which needs testing (icon, hover text, etc.)
I'm not certain startupNotify = true is correct, but a lot of other applications do seem to assume it.

nix-build --attr pkgs.nexus-mods-app.passthru.tests currently fails. Possibly relevant log lines:
/build/tmp.EEl8FbbzGH/.nuget/packages/microsoft.sourcelink.common/8.0.0/build/Microsoft.SourceLink.Common.targets(53,5): warning : Source control information is not available - the generated source link is empty. [/build/source/src/Abstractions/NexusMods.Abstractions.GameLocators/NexusMods.Abstractions.GameLocators.csproj]

/nix/store/1i9r9alwzyfflv6n5kpk9k1zacssm1hj-dotnet-sdk-8.0.101/sdk/8.0.101/Current/SolutionFile/ImportAfter/Microsoft.NET.Sdk.Solution.targets(36,5): warning NETSDK1194: The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds. [/build/source/NexusMods.App.sln]

/nix/store/1i9r9alwzyfflv6n5kpk9k1zacssm1hj-dotnet-sdk-8.0.101/sdk/8.0.101/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.ConflictResolution.targets(112,5): error NETSDK1152: Found multiple publish output files with the same relative path: /build/source/tests/NexusMods.StandardGameLocators.TestHelpers/xunit.runner.json, /build/source/tests/NexusMods.UI.Tests/xunit.runner.json. [/build/source/tests/NexusMods.UI.Tests/NexusMods.UI.Tests.csproj]

Latest push reintroduces projectFile, based on this.

@siph The desktop client starts now.

Great! I did get the application to run and was able to log-in through the browser. It was also able to auto-discover Skyrim in the steam folder.
This is about as far as I got. I couldn't get it to download any mods or run any games through either the GUI or the CLI.

This is about as far as I got. I couldn't get it to download any mods or run any games through either the GUI or the CLI.

Specific error messages from the command line might shed some light on this. Would you mind posting the logs?

I haven't forgotten about this, I just don't have much time at the moment. I wasn't actually getting any errors while installing mods, it just failed silently with the CLI and and through the browser. I will take a closer look soon.

Nice one. One nitpick... the nxm links are currently registered like so:
❯  cat ~/.local/share/applications/nexusmods-app-nxm.desktop
[Desktop Entry]
Name=NexusMods.App NXM Handler
Terminal=false
Type=Application
Path=/nix/store/dsrjmc2r89x67vznl7zq0hpj0b3z2f3r-nexus-mods-app-0.4/lib/nexus-mods-app
Exec=/nix/store/dsrjmc2r89x67vznl7zq0hpj0b3z2f3r-nexus-mods-app-0.4/lib/nexus-mods-app/NexusMods.App protocol-invoke --url %u
MimeType=x-scheme-handler/nxm
NoDisplay=true

That is an issue:
❯  /nix/store/dsrjmc2r89x67vznl7zq0hpj0b3z2f3r-nexus-mods-app-0.4/lib/nexus-mods-app/NexusMods.App protocol-invoke --url "nxm://oauth/callback?code=....&state=...."
You must install .NET to run this application.

App: /nix/store/dsrjmc2r89x67vznl7zq0hpj0b3z2f3r-nexus-mods-app-0.4/lib/nexus-mods-app/NexusMods.App
Architecture: x64
App host version: 8.0.3
.NET location: Not found

Learn more:
https://aka.ms/dotnet/app-launch-failed

Download the .NET runtime:
https://aka.ms/dotnet-core-applaunch?missing_runtime=true&arch=x64&rid=linux-x64&os=nixos.24.05&apphost_version=8.0.3

But it does work if I change to the executable in bin directory, like so:
/nix/store/dsrjmc2r89x67vznl7zq0hpj0b3z2f3r-nexus-mods-app-0.4/bin/NexusMods.App protocol-invoke --url "nxm://oauth/callback?code=....&state=...."

One more nitpick... bin directory should have only app's executable:
❯  ls /nix/store/dsrjmc2r89x67vznl7zq0hpj0b3z2f3r-nexus-mods-app-0.4/bin
7zz  libe_sqlite3.so  libHarfBuzzSharp.so  libSkiaSharp.so  NexusMods.App  SharpZstd.Native.linux-x64.so

Nice one. One nitpick... the nxm links are currently registered [in  ~/.local/share/applications/nexusmods-app-nxm.desktop which uses an executable in lib/]

That is an issue [because dotnet is not available]
But it does work if I change to the executable in bin directory.

I believe the app itself creates the desktop entries at runtime. I guess we'd need to disable that behaviour and write the files ourselves.
Alternatively, if runtime creation is preferred (to support an in-app "handle nxm links" toggle), we'd have to patch the relevant code to use the wrapped exe.

Maybe this solution could help?  https://discourse.nixos.org/t/how-to-set-the-value-of-0-inside-wrapped-script-when-using-makewrapper-wrapprogram/8733

After changing to use the main project file the tests are running, but a bunch of them are not passing. If anyone manages to get any of them to run that would be really helpful. I'm not really familiar with this type of project.

The upstream project has included the 7zz binary executables in the repo. I'll try to overwrite that with the nixpkgs one.

All the tests appear to be passing, now to deal with NETSDK1152.

I think I have another fix, this time for NETSDK1152, it builds for me: https://github.com/l0b0/nixpkgs/pull/2

Also, would it make sense to have an -unfree variant in nixpkgs with rar support? Otherwise users would have to overlay the package to enable this.

I don't know what the norm is, but I'd be happy to do so. Seems better than randomly failing to install mods.
Do you know of any example packages which do this? I'd want to reuse all the code from the free version in the unfree version, without duplication.
And thank you heaps for testing!

You could add multiple entries in all-packages.nix  and pass different arguments to callPackage. This might be helpful as well.

You could add multiple entries in all-packages.nix and pass different arguments to callPackage. This might be helpful as well.

Good point, done! There's now nexus-mods-app and nexus-mods-app-unfree, and only the latter has RAR support.

Some interesting stuff going on here. You don't have to do hacky workarounds to get this to work. As an example, we can add an option to disable the runtime generation of desktop entry files and provide a template to be used instead. We can also add a build option that disables copying the 7zz executable to the output directory. These things are trivial to implement, feel free to open an issue on the repo and I can take a look.

I've added an update script based on others, but the last line fails:

cp: cannot stat '/tmp/deps-nexus-mods-app-4mor2K/home/.nuget/packages/*': No such file or directory

Does anyone know how to fix it?

I've added an update script based on others, but the last line fails:

cp: cannot stat '/tmp/deps-nexus-mods-app-4mor2K/home/.nuget/packages/*': No such file or directory

Does anyone know how to fix it?

I get that error, but the update appears to have been done anyway.
I suspect the error is in something being run after updating package.nix?

I think this quote from Packaging a Dotnet Application might help be relevant?

nugetDeps takes either a path to a deps.nix file, or a derivation. The deps.nix file can be generated using the script attached to passthru.fetch-deps. If the argument is a derivation, it will be used directly and assume it has the same output as mkNugetDeps.

Perhaps there is something wrong with the "default" fetch-deps script and you need to add your own to passthru?
Or alternatively, maybe assigning a derivation to nugetDeps instead of using a deps.nix file would work?
I'm just spitballing though, I'm afraid.

I've posted about the issue here.

Have you seen this section of the nix dotnet guide?

Have you seen this section of the nix dotnet guide?

I hadn't seen that, but I based my update script on looking through several other .NET package update scripts. So I don't understand why it doesn't work in my particular case.

Are we good to go with 0.4.1 for now?

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/4025

I don't know why CI is failing, it seems to work fine locally

I don't know why CI is failing, it seems to work fine locally

Damn, I missed that. Why are they showing up as "neutral" rather than failed?
Looks like the problem might be this:

[xUnit.net 00:00:00.12] NexusMods.Games.BethesdaGameStudios.Tests: Exception filtering tests: Incorrect format for TestCaseFilter Error: Invalid Condition 'FullyQualifiedName!=NexusMods.UI.Tests.ImageCacheTests.Test_LoadAndCache_ImageStoredFileFullyQualifiedName!=NexusMods.Games.FOMOD.Tests.FomodXmlInstallerTests.InstallsFilesSimple_UsingRar'. Specify the correct format and try again. Note that the incorrect format can lead to no test getting executed.

This has highlighted another issue:

/nix/store/8y83na7h81fw5kr1msmjc7rvx329djp0-dotnet-sdk-8.0.300/sdk/8.0.300/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.Publish.targets(351,5): error MSB3021: Unable to copy file "/build/source/src/ArchiveManagement/NexusMods.FileExtractor/runtimes/linux-x64/native/7zz" to "/nix/store/4f0xxir8gd0lihxf2gv8lcphjjh6y12i-nexus-mods-app-0.4.1/lib/nexus-mods-app/runtimes/linux-x64/native//7zz". Access to the path '/nix/store/4f0xxir8gd0lihxf2gv8lcphjjh6y12i-nexus-mods-app-0.4.1/lib/nexus-mods-app/runtimes/linux-x64/native/7zz' is denied. [/build/source/tests/NexusMods.DataModel.Tests/NexusMods.DataModel.Tests.csproj]

Does Nix have naming scheme requirements? If not, is it possible to use nexusmods-app for the package name? I'm currently updating our docs and that will be the suggested package name for package maintainers.

Since you're building from source, you should also set INSTALLATION_METHOD_PACKAGE_MANAGER. We have an integrated updater that will notify the user about a new version. If you set this compile constant, we will tell the user to update using their package manager.

Does Nix have naming scheme requirements? If not, is it possible to use nexusmods-app for the package name? I'm currently updating our docs and that will be the suggested package name for package maintainers.

Nixpkgs is flexible about names. I've renamed it. Thank you!

Since you're building from source, you should also set INSTALLATION_METHOD_PACKAGE_MANAGER. We have an integrated updater that will notify the user about a new version. If you set this compile constant, we will tell the user to update using their package manager.

I can't find it in the code. Did you mean one of these, or is it a coming feature? If it's the latter I'd rather put it on the to do list for later versions.

Since you're building from source, you should also set INSTALLATION_METHOD_PACKAGE_MANAGER. We have an integrated updater that will notify the user about a new version. If you set this compile constant, we will tell the user to update using their package manager.

I can't find it in the code.

It's in this PR: Nexus-Mods/NexusMods.App#1530

Typically we wouldn't set environment variables that have no effect on the targeted version.
I don't see any harm in setting it now, or adding a TODO comment referencing the PR. But it won't have any effect until the package is bumped to whatever version that PR lands in.

Description of changes
From the project:

a mod installer, creator and manager for all your popular games

Closes #270358.
Name recommended by @erri120 #270372 (comment).
Replaces the 7zz binary executable included with the upstream project for safety and reproducibility.
Requires an enableUnfree = true override to support RAR format mods.
Disables tests marked as requiring networking (actually requiring Nexus Mods API key according to Nexus-Mods/NexusMods.App#1222 (comment)), and one other tests which requires networking.
To do
* [x]  Adapt [upstream build instructions](https://github.com/Nexus-Mods/NexusMods.App/blob/main/.github/workflows/build-linux-pupnet.yaml)

* [x]  Run upstream tests successfully

* [x]  Fix [desktop entries](https://github.com/NixOS/nixpkgs/pull/270372#issuecomment-2056721955)

* [x]  Verify app use:

  * [x]  Nexus Mods login
  * [x]  Detects supported games (tested with Skyrim Special Edition)
  * [x]  Installs mods
  * [x]  Runs mods (_some_ mods load; [issue](https://github.com/Nexus-Mods/NexusMods.App/issues/1303))

* [ ]  (Optional) [Specify `NEXUSMODS_APP_USE_SYSTEM_EXTRACTOR=1`](https://github.com/Nexus-Mods/NexusMods.App/issues/1306#issuecomment-2095755699) once the next release is out

Things done
* Built on platform(s)

  * [x]  x86_64-linux
  * [ ]  aarch64-linux
  * [ ]  x86_64-darwin
  * [ ]  aarch64-darwin

* For non-Linux: Is sandboxing enabled in `nix.conf`? (See [Nix manual](https://nixos.org/manual/nix/stable/command-ref/conf-file.html))

  * [ ]  `sandbox = relaxed`
  * [ ]  `sandbox = true`

* [ ]  Tested, as applicable:

  * [NixOS test(s)](https://nixos.org/manual/nixos/unstable/index.html#sec-nixos-tests) (look inside [nixos/tests](https://github.com/NixOS/nixpkgs/blob/master/nixos/tests))
  * and/or [package tests](https://nixos.org/manual/nixpkgs/unstable/#sec-package-tests)
  * or, for functions and "core" functionality, tests in [lib/tests](https://github.com/NixOS/nixpkgs/blob/master/lib/tests) or [pkgs/test](https://github.com/NixOS/nixpkgs/blob/master/pkgs/test)
  * made sure NixOS tests are [linked](https://nixos.org/manual/nixpkgs/unstable/#ssec-nixos-tests-linking) to the relevant packages

* [x]  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](https://github.com/Mic92/nixpkgs-review#usage)

* [ ]  Tested basic functionality of all binary files (usually in `./result/bin/`)

* [23.11 Release Notes](https://github.com/NixOS/nixpkgs/blob/master/nixos/doc/manual/release-notes/rl-2311.section.md) (or backporting [23.05 Release notes](https://github.com/NixOS/nixpkgs/blob/master/nixos/doc/manual/release-notes/rl-2305.section.md))

  * [ ]  (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

* [x]  Fits [CONTRIBUTING.md](https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md).

Priorities
Add a 👍 reaction to pull requests you find important.

0.5.3 is out. So I assume we can do NEXUSMODS_APP_USE_SYSTEM_EXTRACTOR now right?

authors: MattSturgeon autrimpo eclairevoyant erri120 l0b0 matejc nixos-discourse nyabinary siph


text:
ollama: 0.1.11 -> 0.1.17

Description of changes
there is just that one weird test that tries to verify that the version 0.0.0, but appart from that it's just a simple version bump.
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/)
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.

Add a :+1: reaction to pull requests you find important.

there is just that one weird test that tries to verify that the version 0.0.0, but appart from that it's just a simple version bump.

For the upcoming version that will be fixed on their end. In case you will be the one updating the package again keep in mind that your substitution of 0.0.0 can be removed.

Thank you for the heads up!

authors: alinanorakari happysalada


text:
yo: 4.3.1 -> 5.0.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/yeoman/yo/releases.
meta.description for yo is: CLI tool for running Yeoman generators
meta.homepage for yo is: https://github.com/yeoman/yo
Updates performed

NPM version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 5.0.0 with grep in /nix/store/7x3bk5kavfjhx7wqq6qgdxvwilkv4iak-yo-5.0.0
found 5.0.0 in filename of file in /nix/store/7x3bk5kavfjhx7wqq6qgdxvwilkv4iak-yo-5.0.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
yo

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/7x3bk5kavfjhx7wqq6qgdxvwilkv4iak-yo-5.0.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A yo https://github.com/r-ryantm/nixpkgs/archive/781987f98387b741ca27ee7d8aa67555d6128c0a.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/781987f98387b741ca27ee7d8aa67555d6128c0a#yo

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/7x3bk5kavfjhx7wqq6qgdxvwilkv4iak-yo-5.0.0
ls -la /nix/store/7x3bk5kavfjhx7wqq6qgdxvwilkv4iak-yo-5.0.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

yo

Maintainer pings

Result of nixpkgs-review pr 276636 at 781987f9 run on x86_64-linux 1

1 package built successfully:

yo

authors: natsukium r-ryantm


text:
tuner: reorder gst plugins, add glib-networking; fix runtime

fix tuner by reordering the gstreamer plugins. ordering the bad plugin before the good plugin results in errors and no stations listed. reordering the plugins fixes this. glib-networking is a requirement for libsoup to access TLS streams.
Description of changes

Things done

Built on platform(s)

[x] 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
[x] 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.

Add a :+1: reaction to pull requests you find important.

glib-networking is already provided by one of the dependencies via the propagatedBuildInputs. the ordering of plugins doesn't seem to matter and the tuner app works or not works somewhat non-deterministically.


text:
archivebox: 0.6.2 -> 0.7.1

Description of changes
Bump archivebox.
Add two optional node runtime deps.
Add deps in PATH which are recomended at each startup.
Disable one django extensions test which is not going to be fixed anymore (upstream is working on migration to a modern version)
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] 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/)
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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@ofborg build postlight-parser readability-extractor

meta.homepage and meta.changelog would be nice

Added where they exist and aren't auto-propagated.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/3249

authors: nixos-discourse viraptor


text:
python311Packages.trezor-agent: rename from trezor_agent

Description of changes
part of #245383
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/)
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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 279353 run on x86_64-linux 1

4 packages built:

python310Packages.trezor-agent
python310Packages.trezor-agent.dist
trezor-agent (python311Packages.trezor-agent)
trezor-agent.dist (python311Packages.trezor-agent.dist)


text:
profanity support for unix

Motivation for this change
I wanted to be able to use profanity for MacOS (in that case 10.12.6 Sierra). Currently it is only available for Linux
Things done
It is really confusing what is behind the platforms variable. I tried switching platforms.linux to platforms.unix (maybe there is an option to be more specific). When i ran nix-build -A profanity nix told me that libmesode is not availble for unix, so i upgraded the platforms there as well.

[ ] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[x] macOS
[ ] Linux

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

platforms is basically «there are reasons to believe this will work on the following systems». If you have managed to build it without any other modification — it is a good reason to update the list, thanks for sharing the knowledge.

Explanation for platforms variables:
It instruct nix and therefor hydra on which operating systems and architecture a package builds:
$ nix-repl
nix-repl> :l <nixpkgs>
nix-repl> lib.platforms.linux
[ "aarch64-linux" "armv5tel-linux" "armv6l-linux" "armv7l-linux" "mips64el-linux" "i686-linux" "x86_64-linux" ]
nix-repl> lib.platforms.unix
[ "aarch64-linux" "armv5tel-linux" "armv6l-linux" "armv7l-linux" "mips64el-linux" "i686-cygwin" "i686-freebsd" "i686-linux" "i686-netbsd" "i686-openbsd" "x86_64-cygwin" "x86_64-darwin" "x86_64-freebsd" "x86_64-linux" "x86_64-netbsd" "x86_64-openbsd" "x86_64-solaris" ]


text:
ut1999: init at 469d

Description of changes
This introduces the classic game Unreal Tournament 1999 to NixOS. The way it's achieved is heavily inspired by gog-unreal-tournament-goty from AUR.
The way it works is:

It downloads the OldUnreal patch.
It expects the user to provide the GOG version 2.0.0.5 of the game.
Applies the OldUnreal patch according to the instructions of its README.

Things done

Built on platform(s)

[x] 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
[x] 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.

Add a :+1: reaction to pull requests you find important.

@Atemu , I've refactored it quite a bit. Please re-review.

@Atemu , please re-review.

Result of nixpkgs-review pr 292888 run on x86_64-linux 1

1 package built:

ut1999


text:
musescore: 4.2.1 -> 4.3.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/musescore/MuseScore/releases.
meta.description for musescore is: Music notation and composition software
meta.homepage for musescore is: https://musescore.org/
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 4.3.0 with grep in /nix/store/yq0f2192c7r1slbj309b411c96yhggxr-musescore-4.3.0
found 4.3.0 in filename of file in /nix/store/yq0f2192c7r1slbj309b411c96yhggxr-musescore-4.3.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

musescore

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/yq0f2192c7r1slbj309b411c96yhggxr-musescore-4.3.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A musescore https://github.com/r-ryantm/nixpkgs/archive/5223087841daf625ff458aa16db21f5b9fdd2d46.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/5223087841daf625ff458aa16db21f5b9fdd2d46#musescore

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/yq0f2192c7r1slbj309b411c96yhggxr-musescore-4.3.0
ls -la /nix/store/yq0f2192c7r1slbj309b411c96yhggxr-musescore-4.3.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

musescore

Maintainer pings
cc @vandenoever @doronbehar for testing.

I'm ignoring the x86_64-linux timeout error in ofborg, since r-ryantm was able to build it on that platform successfully. I'm also not waiting for aarch64-darwin, as the x86_64-darwin build succeeded and usually that's a good indication.

authors: doronbehar r-ryantm


text:
python311Packages.psygnal: 0.11.0 -> 0.11.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.psygnal is: Implementation of Qt Signals
meta.homepage for python311Packages.psygnal is: https://github.com/pyapp-kit/psygnal
meta.changelog for python311Packages.psygnal is: https://github.com/pyapp-kit/psygnal/blob/v0.11.1/CHANGELOG.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.11.1 with grep in /nix/store/ld85r6khs09a6bpnj33kwc2nx8kwawxm-python3.11-psygnal-0.11.1
found 0.11.1 in filename of file in /nix/store/ld85r6khs09a6bpnj33kwc2nx8kwawxm-python3.11-psygnal-0.11.1

Rebuild report (if merged into master) (click to expand)

26 total rebuild path(s)

26 package rebuild(s)

First fifty rebuilds by attrpath

napari
python311Packages.altair
python311Packages.anywidget
python311Packages.app-model
python311Packages.gradio
python311Packages.gradio-client
python311Packages.gradio-pdf
python311Packages.ipyniivue
python311Packages.magicgui
python311Packages.napari
python311Packages.napari-npe2
python311Packages.psygnal
python311Packages.streamlit
python311Packages.vega
python312Packages.altair
python312Packages.anywidget
python312Packages.app-model
python312Packages.gradio
python312Packages.gradio-client
python312Packages.gradio-pdf
python312Packages.ipyniivue
python312Packages.magicgui
python312Packages.napari-npe2
python312Packages.psygnal
streamlit

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ld85r6khs09a6bpnj33kwc2nx8kwawxm-python3.11-psygnal-0.11.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python311Packages.psygnal https://github.com/r-ryantm/nixpkgs/archive/6013508600dafce8f87f4191701ca887cbc43d4f.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/6013508600dafce8f87f4191701ca887cbc43d4f#python311Packages.psygnal

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/ld85r6khs09a6bpnj33kwc2nx8kwawxm-python3.11-psygnal-0.11.1
ls -la /nix/store/ld85r6khs09a6bpnj33kwc2nx8kwawxm-python3.11-psygnal-0.11.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

18 packages failed to build:

napari (python311Packages.napari)
napari.dist (python311Packages.napari.dist)
python311Packages.gradio
python311Packages.gradio-client
python311Packages.gradio-client.dist
python311Packages.gradio-pdf
python311Packages.gradio-pdf.dist
python311Packages.gradio.dist
python312Packages.gradio
python312Packages.gradio-client
python312Packages.gradio-client.dist
python312Packages.gradio-pdf
python312Packages.gradio-pdf.dist
python312Packages.gradio.dist
python312Packages.magicgui
python312Packages.magicgui.dist
python312Packages.napari-npe2
python312Packages.napari-npe2.dist

28 packages built:

python311Packages.altair
python311Packages.altair.dist
python311Packages.anywidget
python311Packages.anywidget.dist
python311Packages.app-model
python311Packages.app-model.dist
python311Packages.ipyniivue
python311Packages.ipyniivue.dist
python311Packages.magicgui
python311Packages.magicgui.dist
python311Packages.napari-npe2
python311Packages.napari-npe2.dist
python311Packages.psygnal
python311Packages.psygnal.dist
streamlit (python311Packages.streamlit)
streamlit.dist (python311Packages.streamlit.dist)
python311Packages.vega
python311Packages.vega.dist
python312Packages.altair
python312Packages.altair.dist
python312Packages.anywidget
python312Packages.anywidget.dist
python312Packages.app-model
python312Packages.app-model.dist
python312Packages.ipyniivue
python312Packages.ipyniivue.dist
python312Packages.psygnal
python312Packages.psygnal.dist

Maintainer pings
cc @SomeoneSerge for testing.

Done in https://github.com/NixOS/nixpkgs/commit/20c64960ace9c3143b4c847509cfbe2837d4d91a.

authors: r-ryantm wegank


text:
mono: init at 4.8

Motivation for this change
Introduce mono-4.8 to nixpkgs.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

This is the replacement PR for #25230. Ping @copumpkin, @disassembler, @abbradar and @pSub.

While testing all the binaries, I noticed:
$ ./soapsuds
Unhandled Exception:
System.Runtime.Serialization.SerializationException: Unable to find assembly 'soapsuds, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null'.

is that to be expected?

Let's merge, I'd like to continue my Mono work atop this (I'd lke to update to the latest versions as much packages in Nixpkgs as possible and 5.0 is indeed not as stable). I'll merge after it builds locally.

authors: Mic92 abbradar kuznero


text:
plex: 1.9.5 -> 1.9.7

Motivation for this change
New version of plex released.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

@GrahamcOfBorg plex

@bflyblue this is the plex pass version, we can't include that in nixpkgs.

Ack!!! Sorry @LnL7, I missed your comment. Reverted here: https://github.com/NixOS/nixpkgs/pull/31635
Sorry @bflyblue, we'll have to try this again in a different PR.

Updating to 1.9.6 is fine, you can toggle it on the download page to get the public version.

Ok that's embarassing, I thought I had turned off Pass versions. I'll be more careful in future and submit a new PR for 1.9.6!

authors: LnL7 bflyblue grahamc


text:
ad-miner: 1.2.0 -> 1.4.0

Diff: https://github.com/Mazars-Tech/AD_Miner/compare/refs/tags/v1.2.0...v1.4.0
Changelog: https://github.com/Mazars-Tech/AD_Miner/blob/v1.4.0/CHANGELOG.md
Description of changes

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/)
24.11 Release Notes (or backporting 23.11 and 24.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 :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 319550 run on x86_64-linux 1

2 packages built:

ad-miner
ad-miner.dist


text:
qovery-cli: 0.94.11 -> 0.94.13

Diff: https://github.com/Qovery/qovery-cli/compare/refs/tags/v0.94.11...v0.94.13
Changelog: https://github.com/Qovery/qovery-cli/releases/tag/v0.94.13
Description of changes

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/)
24.11 Release Notes (or backporting 23.11 and 24.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 :+1: reaction to pull requests you find important.

Duplicate of #320934


text:
vcpkg: fix binaries not being able to find libstdc++

Description of changes

At the moment, if you try to run a binary that was installed by vcpkg, then you will get this error:

error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory

This PR prevents that error from happening.
Fixes #317553.
Things done

Built on platform(s)

[x] 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

[x] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Please use X_VCPKG_RPATH_KEEP_SYSTEM_PATHS, as vcpkg need to patch rpath for dependencies with dynamic libraries installed in the installation prefix

I'll merge this tomorrow unless you have any more comments @gracicot @Guekka

Cool stuff, thank you!


text:
deepin desktop environment: update

Description of changes
minor update for dde

Things done

Built on platform(s)

[x] 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/)
24.11 Release Notes (or backporting 23.11 and 24.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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@ofborg test deepin

@ofborg test deepin

@ofborg test deepin


text:
nixos/teleport: add required utils to path

Description of changes
Attempts to solve https://github.com/NixOS/nixpkgs/issues/315389. See here for a list of binaries that Teleport expects to exist in PATH.
Things done

Built on platform(s)

[x] 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

[x] 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.11 Release Notes (or backporting 23.11 and 24.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 :+1: reaction to pull requests you find important.

has this been tested, or is it a speculative fix? putting sudo and shadow on PATH is suspicious because most functionality of those packages require them to be set-uid, but the /nix/store paths for those packages won't be set-uid.
if teleport needs these to be set-uid, that could be done by using the security.wrappers options (or just programs.sudo, etc, which sit atop that) and adding /run/wrappers/bin -- where the set-uid versions of these packages are installed -- to PATH.

if teleport needs these to be set-uid, that could be done by using the security.wrappers options (or just programs.sudo, etc, which sit atop that) and adding /run/wrappers/bin -- where the set-uid versions of these packages are installed -- to PATH.

Teleport runs as root in the first place, so the setuid bit might be irrelevant in that case? Also note that the original issue is about getent, not necessarily sudo - I've only added sudo and the like for completeness sake, since Teleport's documentation mentions binaries from them being required.
Also, Teleport seems to only use visudo. It's been a while since I worked on Teleport, but I assume this is to potentially make the new user a sudoer when Teleport is creating them. That part will probably not work anyway, since /etc/sudoers on NixOS says:
# Don't edit this file. Set the NixOS options ‘security.sudo.configFile’
# or ‘security.sudo.extraRules’ instead.

I've previously mentioned this as a workaround in the linked issue, and people have confirmed it gets rid of the errors. Again, the error was primarily about getent.

if you care to create the backport, then it does meet the criteria for one AIUI. we are in the middle of preparing the 24.11 release: i think the timeline for that means it's OK to do backports right now, but i'll want to run it by someone closer to the release process before merging it.
but yeah 👍 worst case we just have to wait a few extra days before merging it.

authors: justinas uninsane


text:
cri-tools: 1.30.1 -> 1.31.1

Description of changes
Update to the latest release.
cc @NixOS/podman
Things done

Built on platform(s)

[x] 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

[x] 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

[x] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Bumped to v1.31.1.


text:
steampipe: 0.24.0 -> 0.24.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for steampipe is: Dynamically query your cloud, code, logs & more with SQL
meta.homepage for steampipe is: https://steampipe.io/
meta.changelog for steampipe is: https://github.com/turbot/steampipe/blob/v0.24.2/CHANGELOG.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.24.2 with grep in /nix/store/kfpcb240ji6cv9gsskpgpghdiz4rnw8p-steampipe-0.24.2
found 0.24.2 in filename of file in /nix/store/kfpcb240ji6cv9gsskpgpghdiz4rnw8p-steampipe-0.24.2

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

steampipe

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/kfpcb240ji6cv9gsskpgpghdiz4rnw8p-steampipe-0.24.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A steampipe https://github.com/r-ryantm/nixpkgs/archive/b5116d5369473c79a6c5d95c6a8ece48086a9401.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/b5116d5369473c79a6c5d95c6a8ece48086a9401#steampipe

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/kfpcb240ji6cv9gsskpgpghdiz4rnw8p-steampipe-0.24.2
ls -la /nix/store/kfpcb240ji6cv9gsskpgpghdiz4rnw8p-steampipe-0.24.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

steampipe

Maintainer pings
cc @hardselius @anthonyroussel for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

@NixOS/nixpkgs-merge-bot merge

authors: anthonyroussel r-ryantm


text:
presenterm: 0.8.0 -> 0.9.0

Things done
Changelog: https://github.com/mfontanini/presenterm/releases/tag/v0.9.0

presenter: format
presenterm: 0.8.0 -> 0.9.0

Built on platform(s)

[x] 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/)
24.11 Release Notes (or backporting 23.11 and 24.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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 346937

x86_64-linux

:white_check_mark: 1 package built:

presenterm

aarch64-linux

:white_check_mark: 1 package built:

presenterm

x86_64-darwin

:white_check_mark: 1 package built:

presenterm

aarch64-darwin

:white_check_mark: 1 package built:

presenterm


text:
handlr-regex: 0.11.2 -> 0.12.0

Updated handlr-regex to 0.12.0 and updated postInstall phase to address breaking changes in regards to installing man pages and shell completion scripts.
Changes: https://github.com/Anomalocaridid/handlr-regex/compare/v0.11.2...Anomalocaridid:handlr-regex:v0.12.0
Things done

Built on platform(s)

[x] 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

[x] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

darwin breakage is not a regression according to hydra

authors: Anomalocaridid pbsds


text:
bottom: add gpu recognition, new apple sdk, refactor

Closes https://github.com/ClementTsang/bottom/issues/1629
Tracking: https://github.com/NixOS/nixpkgs/issues/354146, can't test it as I don't have a darwin machine, but in another commit (9a78e6734410) I saw this exact change so most likely it works.
Things done

Built on platform(s)

[x] 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

[x] 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

[x] 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
[x] 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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 360568

aarch64-darwin

:white_check_mark: 1 package built:

bottom

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 360568

x86_64-linux

:white_check_mark: 1 package built:

bottom

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 360568

aarch64-darwin

:white_check_mark: 1 package built:

bottom

authors: gepbird uncenter


text:
desmume: avoid errors with with -fpermissive

Prior to this change, desmume would fail to build on nixos-unstable due to an error:
utils/libfat/directory.cpp:142:33: error: ISO C++ forbids comparison between pointer and integer [-fpermissive]
I guess this is due to the recent switch to GCC7.
Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

:crying_cat_face: I'm pretty sure that evaluation error is unrelated, it builds and runs fine from this branch locally.

@GrahamcOfBorg eval
Yeah, a PR mistakenly broke master :) Should be fixed up now. Sorry!

@GrahamcOfBorg build desmume

Failure on x86_64-darwin (full log)
Partial log (click to expand)
Package ‘desmume-0.9.11’ in /private/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/lnl7-mac/pkgs/misc/emulators/desmume/default.nix:44 is not supported on ‘x86_64-darwin’, refusing to evaluate.

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowBroken = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowBroken = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Partial log (click to expand)
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/q9az497sqn6zpn5hsn5v8c1q5lcppp75-desmume-0.9.11
shrinking /nix/store/q9az497sqn6zpn5hsn5v8c1q5lcppp75-desmume-0.9.11/bin/desmume-cli
shrinking /nix/store/q9az497sqn6zpn5hsn5v8c1q5lcppp75-desmume-0.9.11/bin/desmume
gzipping man pages under /nix/store/q9az497sqn6zpn5hsn5v8c1q5lcppp75-desmume-0.9.11/share/man/
strip is /nix/store/b0zlxla7dmy1iwc3g459rjznx59797xy-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/q9az497sqn6zpn5hsn5v8c1q5lcppp75-desmume-0.9.11/bin
patching script interpreter paths in /nix/store/q9az497sqn6zpn5hsn5v8c1q5lcppp75-desmume-0.9.11
checking for references to /tmp/nix-build-desmume-0.9.11.drv-0 in /nix/store/q9az497sqn6zpn5hsn5v8c1q5lcppp75-desmume-0.9.11...
/nix/store/q9az497sqn6zpn5hsn5v8c1q5lcppp75-desmume-0.9.11

Success on aarch64-linux (full log)
Partial log (click to expand)
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/ibfq95ym5gs9mbc1q5hac2glvykxgnc9-desmume-0.9.11
shrinking /nix/store/ibfq95ym5gs9mbc1q5hac2glvykxgnc9-desmume-0.9.11/bin/desmume-cli
shrinking /nix/store/ibfq95ym5gs9mbc1q5hac2glvykxgnc9-desmume-0.9.11/bin/desmume
gzipping man pages under /nix/store/ibfq95ym5gs9mbc1q5hac2glvykxgnc9-desmume-0.9.11/share/man/
strip is /nix/store/lvx1acn1ig1j2km8jds5x3ggh3f2wa8v-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/ibfq95ym5gs9mbc1q5hac2glvykxgnc9-desmume-0.9.11/bin
patching script interpreter paths in /nix/store/ibfq95ym5gs9mbc1q5hac2glvykxgnc9-desmume-0.9.11
checking for references to /build in /nix/store/ibfq95ym5gs9mbc1q5hac2glvykxgnc9-desmume-0.9.11...
/nix/store/ibfq95ym5gs9mbc1q5hac2glvykxgnc9-desmume-0.9.11

@grahamc @Mic92 thanks!

authors: GrahamcOfBorg Mic92 eqyiel grahamc


text:
Add Deja-Vu fonts to jenkins environment and run as AWT headless

Motivation for this change

Avoids warnings in jenkins service output.
Consistent with recommended run script: https://wiki.jenkins.io/display/JENKINS/JenkinsLinuxStartupScript

Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg test jenkins

No attempt on aarch64-linux
The following builds were skipped because they don't evaluate on aarch64-linux: tests.jenkins
No log is available.

Success on x86_64-linux (full log)
Attempted: tests.jenkins
Partial log (click to expand)
master: exit status 0
test script finished in 88.85s
cleaning up
killing slave (pid 593)
killing master (pid 604)
0jenkins users
0jenkins users
vde_switch: EOF on stdin, cleaning up and exiting
vde_switch: Could not remove ctl dir '/build/vde1.ctl': Directory not empty
/nix/store/gg97jbw6gphm0c9miz2126hwhnkn356j-vm-test-run-jenkins

also backported to 18.03.

authors: GrahamcOfBorg Mic92 coreyoconnor


text:
libtirpc: 1.0.2 -> 1.0.3

Semi-automatic update generated by https://github.com/ryantm/nix-update tools. These checks were done:

built on NixOS
Warning: no binary found that responded to help or version flags. (This warning appears even if the package isn't expected to have binaries.)
found 1.0.3 with grep in /nix/store/npaq7mvly8z13h38c8g1x0y4ggxi77k0-libtirpc-1.0.3
directory tree listing: https://gist.github.com/ad3687f7d46ffd3201e6fbe6e2e090b9

cc @abbradar for review

Success on x86_64-linux (full log)
Attempted: libtirpc
Partial log (click to expand)
make[1]: Leaving directory '/build/libtirpc-1.0.3'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/npaq7mvly8z13h38c8g1x0y4ggxi77k0-libtirpc-1.0.3
shrinking /nix/store/npaq7mvly8z13h38c8g1x0y4ggxi77k0-libtirpc-1.0.3/lib/libtirpc.so.3.0.0
gzipping man pages under /nix/store/npaq7mvly8z13h38c8g1x0y4ggxi77k0-libtirpc-1.0.3/share/man/
strip is /nix/store/fzcs0fn6bb04m82frhlb78nc03ny3w55-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/npaq7mvly8z13h38c8g1x0y4ggxi77k0-libtirpc-1.0.3/lib
patching script interpreter paths in /nix/store/npaq7mvly8z13h38c8g1x0y4ggxi77k0-libtirpc-1.0.3
checking for references to /build in /nix/store/npaq7mvly8z13h38c8g1x0y4ggxi77k0-libtirpc-1.0.3...
/nix/store/npaq7mvly8z13h38c8g1x0y4ggxi77k0-libtirpc-1.0.3

No attempt on x86_64-darwin
The following builds were skipped because they don't evaluate on x86_64-darwin: libtirpc
No partial log is available.

Success on aarch64-linux (full log)
Attempted: libtirpc
Partial log (click to expand)
make[1]: Leaving directory '/build/libtirpc-1.0.3'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/82v5gjx6apfbwn42yk9hwqa2las9q67g-libtirpc-1.0.3
shrinking /nix/store/82v5gjx6apfbwn42yk9hwqa2las9q67g-libtirpc-1.0.3/lib/libtirpc.so.3.0.0
gzipping man pages under /nix/store/82v5gjx6apfbwn42yk9hwqa2las9q67g-libtirpc-1.0.3/share/man/
strip is /nix/store/3zq400fri5dv7d30lpxlqm2v9y1iis6j-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/82v5gjx6apfbwn42yk9hwqa2las9q67g-libtirpc-1.0.3/lib
patching script interpreter paths in /nix/store/82v5gjx6apfbwn42yk9hwqa2las9q67g-libtirpc-1.0.3
checking for references to /build in /nix/store/82v5gjx6apfbwn42yk9hwqa2las9q67g-libtirpc-1.0.3...
/nix/store/82v5gjx6apfbwn42yk9hwqa2las9q67g-libtirpc-1.0.3

@GrahamcOfBorg build rpcbind

No attempt on x86_64-darwin
The following builds were skipped because they don't evaluate on x86_64-darwin: rpcbind
No partial log is available.

Success on x86_64-linux (full log)
Attempted: rpcbind
Partial log (click to expand)
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/wdfnhn27xx9y3nhk5dcs4jn7xz7bld4l-rpcbind-0.2.4
shrinking /nix/store/wdfnhn27xx9y3nhk5dcs4jn7xz7bld4l-rpcbind-0.2.4/bin/rpcinfo
shrinking /nix/store/wdfnhn27xx9y3nhk5dcs4jn7xz7bld4l-rpcbind-0.2.4/bin/rpcbind
gzipping man pages under /nix/store/wdfnhn27xx9y3nhk5dcs4jn7xz7bld4l-rpcbind-0.2.4/share/man/
strip is /nix/store/fzcs0fn6bb04m82frhlb78nc03ny3w55-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/wdfnhn27xx9y3nhk5dcs4jn7xz7bld4l-rpcbind-0.2.4/bin
patching script interpreter paths in /nix/store/wdfnhn27xx9y3nhk5dcs4jn7xz7bld4l-rpcbind-0.2.4
checking for references to /build in /nix/store/wdfnhn27xx9y3nhk5dcs4jn7xz7bld4l-rpcbind-0.2.4...
/nix/store/wdfnhn27xx9y3nhk5dcs4jn7xz7bld4l-rpcbind-0.2.4

Success on aarch64-linux (full log)
Attempted: rpcbind
Partial log (click to expand)
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/qcbfy7pfj8l1pd0nphr17av9p8xzqk4r-rpcbind-0.2.4
shrinking /nix/store/qcbfy7pfj8l1pd0nphr17av9p8xzqk4r-rpcbind-0.2.4/bin/rpcinfo
shrinking /nix/store/qcbfy7pfj8l1pd0nphr17av9p8xzqk4r-rpcbind-0.2.4/bin/rpcbind
gzipping man pages under /nix/store/qcbfy7pfj8l1pd0nphr17av9p8xzqk4r-rpcbind-0.2.4/share/man/
strip is /nix/store/3zq400fri5dv7d30lpxlqm2v9y1iis6j-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/qcbfy7pfj8l1pd0nphr17av9p8xzqk4r-rpcbind-0.2.4/bin
patching script interpreter paths in /nix/store/qcbfy7pfj8l1pd0nphr17av9p8xzqk4r-rpcbind-0.2.4
checking for references to /build in /nix/store/qcbfy7pfj8l1pd0nphr17av9p8xzqk4r-rpcbind-0.2.4...
/nix/store/qcbfy7pfj8l1pd0nphr17av9p8xzqk4r-rpcbind-0.2.4

authors: GrahamcOfBorg abbradar ryantm


text:
gitAndTools.git-open: 1.3.1 -> 2.0.0

Semi-automatic update generated by https://github.com/ryantm/nix-update tools. These checks were done:

built on NixOS
Warning: no binary found that responded to help or version flags. (This warning appears even if the package isn't expected to have binaries.)
found 2.0.0 with grep in /nix/store/bl1bdnjxn6k22is2w6qvdjl7kvhzjv2s-git-open-2.0.0
directory tree listing: https://gist.github.com/7c26064e56c054ea6ba2b4d9162267cd

cc @jlesquembre for review

Success on aarch64-linux (full log)
Attempted: gitAndTools.git-open
Partial log (click to expand)
no Makefile, doing nothing
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/v7bs034px4fn7rc080vz28kcps2sy2jd-git-open-2.0.0
strip is /nix/store/3zq400fri5dv7d30lpxlqm2v9y1iis6j-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/v7bs034px4fn7rc080vz28kcps2sy2jd-git-open-2.0.0/bin
patching script interpreter paths in /nix/store/v7bs034px4fn7rc080vz28kcps2sy2jd-git-open-2.0.0
/nix/store/v7bs034px4fn7rc080vz28kcps2sy2jd-git-open-2.0.0/bin/.git-open-wrapped: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/3gg2p6n4kv2f0lsxd41f5iz1ivkbzyzr-bash-4.4-p19/bin/bash"
checking for references to /build in /nix/store/v7bs034px4fn7rc080vz28kcps2sy2jd-git-open-2.0.0...
/nix/store/v7bs034px4fn7rc080vz28kcps2sy2jd-git-open-2.0.0

Success on x86_64-linux (full log)
Attempted: gitAndTools.git-open
Partial log (click to expand)
no Makefile, doing nothing
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/bl1bdnjxn6k22is2w6qvdjl7kvhzjv2s-git-open-2.0.0
strip is /nix/store/fzcs0fn6bb04m82frhlb78nc03ny3w55-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/bl1bdnjxn6k22is2w6qvdjl7kvhzjv2s-git-open-2.0.0/bin
patching script interpreter paths in /nix/store/bl1bdnjxn6k22is2w6qvdjl7kvhzjv2s-git-open-2.0.0
/nix/store/bl1bdnjxn6k22is2w6qvdjl7kvhzjv2s-git-open-2.0.0/bin/.git-open-wrapped: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/q1g0rl8zfmz7r371fp5p42p4acmv297d-bash-4.4-p19/bin/bash"
checking for references to /tmp/nix-build-git-open-2.0.0.drv-0 in /nix/store/bl1bdnjxn6k22is2w6qvdjl7kvhzjv2s-git-open-2.0.0...
/nix/store/bl1bdnjxn6k22is2w6qvdjl7kvhzjv2s-git-open-2.0.0

Success on x86_64-darwin (full log)
Attempted: gitAndTools.git-open
Partial log (click to expand)
no configure script, doing nothing
building
no Makefile, doing nothing
installing
post-installation fixup
strip is /nix/store/vb6mgjqgd9h11nbv60fvrp1ls9nxck2y-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/2mh1vm9xlvqnr2mmrax75cqqfq6nw98c-git-open-2.0.0/bin
patching script interpreter paths in /nix/store/2mh1vm9xlvqnr2mmrax75cqqfq6nw98c-git-open-2.0.0
/nix/store/2mh1vm9xlvqnr2mmrax75cqqfq6nw98c-git-open-2.0.0/bin/.git-open-wrapped: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/8hdxjv3m14jgdnawi5l0mz2h59qkk2g9-bash-4.4-p19/bin/bash"
/nix/store/2mh1vm9xlvqnr2mmrax75cqqfq6nw98c-git-open-2.0.0

Good for me

authors: GrahamcOfBorg jlesquembre ryantm


text:
Enable WINE on macOS

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

Incredible work!!!

I fixed the remaining issues.

authors: Ericson2314 angerman matthewbauer


text:
nixos/tomcat: add purifyOnStart option

With this option enabled, before creating file/directories/symlinks in baseDir according to configuration, old occurences of them are removed.
This prevents remainders of an old configuration (libraries, webapps, you name it) from persisting after activating a new configuration.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

The new version specifically keeps logs in place. Not sure if find is the best way to do it (with all the options), but it works fine.

Now, it is possible that people added their own files into baseDir and expect them to stay there after restart or reconfiguration; this patch will break their configuration. However, leaving bits of old configuration (especially old libraries or old webapps) may be even worse. Not sure how to handle this.
This PR, while it very much makes sense by itself, is a pre-requisite of another PR which would add management of the tomcat-users.xml file.

If deleting specific stuff is too clunky, an alternative is to write state into versioned dirs and use symlinks to point to whatever is current. That way old stuff can be garbage collected manually --- the tradeoff obviously being accumulating lots of junk over time & the overhead of managing the links ...

@Mic92 I replaced removal of "everything except logs" with removal of specific directories/symlinks.

@joachifm Did you mean versioning the whole tomcat directory? This would prevent loss of old files, but it's a solution that is way too "heavy" to be practical, and it doesn't prevent the main problem at hand: unexpected change of behaviour of the startup procedure.

For some reason, the previous commit actually did not include the advertised changes ("I replaced removal of "everything except logs" with removal of specific directories/symlinks"), now this is corrected by
fefcd78.
Any chance for merging this soon?

Just in case — @danbst do you want to comment on the list of directories to clean?

@pvgoran @7c6f434c
I think all good, but only enable if services.tomcat.purifyOnStart = true; is set (option to be created). Tomcat management is essentially stateful (the whole startup script is an example of this madness) and so many rely on this. For example, I have mutable webapp deploy to webapps dir - after this PR my webapp would be removed on tomcat restart (I can't put webapp into configuration.nix)

@danbst Makes sense. This new option is supposed to be disabled by default, right?

@danbst Makes sense. This new option is supposed to be disabled by default, right?

@pvgoran @7c6f434c
I think all good, but only enable if services.tomcat.purifyOnStart = true; is set (option to be created). Tomcat management is essentially
stateful (the whole startup script is an example of this madness) and so
many rely on this. For example, I have mutable webapp deploy to webapps
dir - after this PR my webapp would be removed on tomcat restart (I can't
put webapp into configuration.nix)
нд, 21 жовт. 2018 о 10:58 Michael Raskin notifications@github.com пише:

Just in case — @danbst https://github.com/danbst do you want to comment
on the list of directories to clean?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/pull/44303#issuecomment-431647551, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAtWkbFmH5s6mdZADsJUjO6IECZMJg1Sks5unCkvgaJpZM4VqfSm
.

@pvgoran right! It is pretty destructive feature. I also am not in favor of
changing defaults.
пн, 22 жовт. 2018 о 07:09 pvgoran notifications@github.com пише:

@danbst https://github.com/danbst Makes sense. This new option is
supposed to be disabled by default, right?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/pull/44303#issuecomment-431734518, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAtWkb3O-J0JH4vLrBPIw8ZPPmY-OZMLks5unUT-gaJpZM4VqfSm
.

«Once the option is added was precisely about purifyOnStart»

@danbst @Mic92 I added the purifyOnStart option to protect against removing things by default.
Now that it's in place, I'm thinking about going back to deleting everything (except the specifically preserved subdirectories) from baseDir, instead of deleting explicitly listed items. What do you think about it?

What is more likely, that they add one more directory we want to keep or that they add one more directory we want to clean?
Intuitively I would consider an explicit removal of known-problematic subdirectories (with a comment about what and why we still keep) the cleanest approach.

What is more likely, that they add one more directory we want to keep or that they add one more directory we want to clean?

Both of these look improbable to me, if we are talking about Tomcat developers adding something. NixOS developers, on the other hand, could add something; in this case, I think it will be rather something we want to clean.
But this is not how I see this choice. I think it's more about what to do with unknown files which were not created by NixOS: keep them or remove them? The currently implemented approach is "keep", but personally I'd prefer "remove".

But this is not how I see this choice. I think it's more about what to do with unknown files which were not created by NixOS: keep them or remove them? The currently implemented approach is "keep", but personally I'd prefer "remove".

What is your mental model of where these files would actually (probably) come from? Is there a need to add an option to extend the whitelist?

@pvgoran yes, you can remove everything. Those who don't want this behavior should remove purifyOnStart = true; declaration.
@7c6f434c

Is there a need to add an option to extend the whitelist?

Don't think so. Tomcat is pretty much stabilized software, which hasn't changed conceptually for ages.

What is your mental model of where these files would actually (probably) come from? Is there a need to add an option to extend the whitelist?
It could be something like custom logs, or data files/directories created by web applications. In this case, an explicit whitelist would be beneficial. However, I don't think this use case will appear (or at least appear frequently), so it's not worth adding an option now, until someone actually needs/requests it.

maybe leave logs?
Yes, and also work which (by default) contains session files.

@Mic92 Previously I switched from the "whitelist" approach (delete everything except selected directories) to the "blacklist" approach (delete only known directories that we create) by your request. Now, do you agree with going back to the "whitelist" approach with introduction of the purifyOnStart option?

What is your mental model of where these files would actually (probably) come from? Is there a need to add an option to extend the whitelist?
It could be something like custom logs, or data files/directories created by web applications. In this case, an explicit whitelist would be beneficial. However, I don't think this use case will appear (or at least appear frequently), so it's not worth adding an option now, until someone actually needs/requests it.

To me that sounds like an argument for a blacklist (if anything extra is created it is custom logs or data files, and we keep the known logs and session data files). But I won't use the module anyway.

To me that sounds like an argument for a blacklist (if anything extra is created it is custom logs or data files, and we keep the known logs and session data files). But I won't use the module anyway.

The thing is, this use case is just a speculation on my part, "what if someone does this". I have no evidence someone would actually need to organize files like this.

I implemented the "whitelist" approach (removing of all baseDir contents except for logs and work) in  #49729. I keep this PR as it is in case it will be preferred.
My preference is the "whitelist" approach (#49729), and I don't see strong arguments against it, now that the purifyOnStart option was added.
@Mic92 @7c6f434c @danbst Please review this and commit one of these two PRs, at last.

@7c6f434c @pvgoran on second thought, I'd prefer this one, "blacklist" approach. Because we allow users to change baseDir, someone can set it to /home/XXX, and eventually add purifyOnStart. Which will be uh-oh. With current approach the disaster won't be that large, as with "whitelist" approach.

I do not claim arguments for blacklist are strong, it is all about reasonable arguments on both sides. And now this bikeshed is freshly painted. Thanks to everyone.

authors: 7c6f434c danbst joachifm pvgoran


text:
chefdk: 2.4.17 -> 3.3.23

Motivation for this change
This package has been severely outdated for a long time.
i have no idea if it actually works ;)
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Fits CONTRIBUTING.md.

Could you rebase this on current master and resolve conflicts?

https://github.com/NixOS/nixpkgs/pull/80858

authors: c0bw3b manveru nlewo


text:
python36Packages.moviepy: 0.2.2.11 -> 0.2.3.5

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/python3.6-moviepy/versions.
meta.description for python36Packages.moviepy is: '"Video editing with Python"'.

Checks done (click to expand)

built on NixOS

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 0.2.3.5 with grep in /nix/store/nilaxns3bj6wpkcc6b1skv2h9vf2j2p5-python3.6-moviepy-0.2.3.5

directory tree listing: https://gist.github.com/b7fd9d198a9ede6a61005ad0c1133626

du listing: https://gist.github.com/22d1f237128fbd4ab14de695e13ffc68

Outpath report (click to expand)

Outpath difference report
8 total rebuild paths
2 package rebuilds
2 x86_64-linux rebuilds
2 i686-linux rebuilds
2 x86_64-darwin rebuilds
2 aarch64-linux rebuilds
First ten rebuilds by attrpath
python27Packages.moviepy
python36Packages.moviepy

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/nilaxns3bj6wpkcc6b1skv2h9vf2j2p5-python3.6-moviepy-0.2.3.5 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A python36Packages.moviepy https://github.com/r-ryantm/nixpkgs/archive/3e5abf1215aa4718ef36cb2b310e7721a40f9add.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/nilaxns3bj6wpkcc6b1skv2h9vf2j2p5-python3.6-moviepy-0.2.3.5
ls -la /nix/store/nilaxns3bj6wpkcc6b1skv2h9vf2j2p5-python3.6-moviepy-0.2.3.5/bin

Success on x86_64-linux (full log)
Attempted: python36Packages.moviepy
Partial log (click to expand)
Requirement already satisfied: pillow in /nix/store/kaymr52l64afckrlprsfxnnhy1lj5bxd-python3.6-Pillow-5.2.0/lib/python3.6/site-packages (from imageio<3.0,>=2.1.2->moviepy==0.2.3.5) (5.2.0)
Installing collected packages: moviepy
Successfully installed moviepy-0.2.3.5
/build/moviepy-0.2.3.5
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/nilaxns3bj6wpkcc6b1skv2h9vf2j2p5-python3.6-moviepy-0.2.3.5
strip is /nix/store/vcc4svb8gy29g4pam2zja6llkbcwsyiq-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/nilaxns3bj6wpkcc6b1skv2h9vf2j2p5-python3.6-moviepy-0.2.3.5/lib
patching script interpreter paths in /nix/store/nilaxns3bj6wpkcc6b1skv2h9vf2j2p5-python3.6-moviepy-0.2.3.5
checking for references to /build in /nix/store/nilaxns3bj6wpkcc6b1skv2h9vf2j2p5-python3.6-moviepy-0.2.3.5...

Success on x86_64-darwin (full log)
Attempted: python36Packages.moviepy
Partial log (click to expand)
Requirement already satisfied: imageio<3.0,>=2.1.2 in /nix/store/077iha76h2x7xxyzw2anm2fcyvbgikpk-python3.6-imageio-2.4.1/lib/python3.6/site-packages (from moviepy==0.2.3.5) (2.4.1)
Requirement already satisfied: tqdm<5.0,>=4.11.2 in /nix/store/mci0wxrp8j00rl11598cid8rsan9b1m5-python3.6-tqdm-4.25.0/lib/python3.6/site-packages (from moviepy==0.2.3.5) (4.25.0)
Requirement already satisfied: pillow in /nix/store/vx360j117sgzx2d8yvk9zww08a32yyix-python3.6-Pillow-5.2.0/lib/python3.6/site-packages (from imageio<3.0,>=2.1.2->moviepy==0.2.3.5) (5.2.0)
Installing collected packages: moviepy
Successfully installed moviepy-0.2.3.5
/private/tmp/nix-build-python3.6-moviepy-0.2.3.5.drv-0/moviepy-0.2.3.5
post-installation fixup
strip is /nix/store/g5r4apl0za012ffs6ladinwa5w0m1l3k-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/27wfzm7n39cfa34z63h1pbny818ga50b-python3.6-moviepy-0.2.3.5/lib
patching script interpreter paths in /nix/store/27wfzm7n39cfa34z63h1pbny818ga50b-python3.6-moviepy-0.2.3.5

Success on aarch64-linux (full log)
Attempted: python36Packages.moviepy
Partial log (click to expand)
Installing collected packages: moviepy
Successfully installed moviepy-0.2.3.5
/build/moviepy-0.2.3.5
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/g2ckgpn7abdg2qf8qhvyi5kysjqxawfr-python3.6-moviepy-0.2.3.5
strip is /nix/store/p9akxn2sfy4wkhqdqa3li97pc6jaz3r1-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/g2ckgpn7abdg2qf8qhvyi5kysjqxawfr-python3.6-moviepy-0.2.3.5/lib
patching script interpreter paths in /nix/store/g2ckgpn7abdg2qf8qhvyi5kysjqxawfr-python3.6-moviepy-0.2.3.5
checking for references to /build in /nix/store/g2ckgpn7abdg2qf8qhvyi5kysjqxawfr-python3.6-moviepy-0.2.3.5...
/nix/store/g2ckgpn7abdg2qf8qhvyi5kysjqxawfr-python3.6-moviepy-0.2.3.5

authors: GrahamcOfBorg r-ryantm