commit 470614b671f4a55fe0a509f4208dba2bb40c5a17 · pyrox.dev/nixpkgs

+1 -1

doc/hooks/mpi-check-hook.section.md

···

       3
       3
        
       

     

       4
       4
        
       This hook can be used to setup a check phase that

     

       5
       5
        
       requires running a MPI application. It detects the

     

       6
       6
       -
       used present MPI implementaion type and exports

     

       6
       6
       +
       used present MPI implementation type and exports

     

       7
       7
        
       the neceesary environment variables to use

     

       8
       8
        
       `mpirun` and `mpiexec` in a Nix sandbox.

     

       9
       9

+1 -1

doc/languages-frameworks/dotnet.section.md

···

       161
       161
        
       They can be installed either as a global tool for the entire system, or as a local tool specific to project.

     

       162
       162
        
       

     

       163
       163
        
       The local installation is the easiest and works on NixOS in the same way as on other Linux distributions.

     

       164
       164
       -
       [See dotnet documention](https://learn.microsoft.com/en-us/dotnet/core/tools/global-tools#install-a-local-tool) to learn more.

     

       164
       164
       +
       [See dotnet documentation](https://learn.microsoft.com/en-us/dotnet/core/tools/global-tools#install-a-local-tool) to learn more.

     

       165
       165
        
       

     

       166
       166
        
       [The global installation method](https://learn.microsoft.com/en-us/dotnet/core/tools/global-tools#install-a-global-tool)

     

       167
       167
        
       should also work most of the time. You have to remember to update the `PATH`

+2 -2

doc/languages-frameworks/haskell.section.md

···

       221
       221
        
       interested in the alternative [haskell.nix] framework, which, be warned, is

     

       222
       222
        
       completely incompatible with packages from `haskellPackages`.

     

       223
       223
        
       

     

       224
       224
       -
       <!-- TODO(@maralorn) Link to package set generation docs in the contributers guide below. -->

     

       224
       224
       +
       <!-- TODO(@maralorn) Link to package set generation docs in the contributors guide below. -->

     

       225
       225
        
       

     

       226
       226
        
       ## `haskellPackages.mkDerivation` {#haskell-mkderivation}

     

       227
       227
        
       

     
···

       1192
       1192
        
       Since the interrelated parts, i.e. the package set and GHC, are connected

     

       1193
       1193
        
       via the Nixpkgs fixpoint, we need to modify them both in a way that preserves

     

       1194
       1194
        
       their connection (or else we'd have to wire it up again manually). This is

     

       1195
       1195
       -
       achieved by changing GHC and the package set in seperate overlays to prevent

     

       1195
       1195
       +
       achieved by changing GHC and the package set in separate overlays to prevent

     

       1196
       1196
        
       the package set from pulling in GHC from `prev`.

     

       1197
       1197
        
       

     

       1198
       1198
        
       The result is two overlays like the ones shown below. Adjustable parts are

+1 -1

doc/languages-frameworks/php.section.md

···

       200
       200
        
          composer repository on the filesystem containing dependencies specified in

     

       201
       201
        
          `composer.json`. This process uses the function

     

       202
       202
        
          `php.mkComposerRepository` which in turn uses the

     

       203
       203
       -
          `php.composerHooks.composerRepositoryHook` hook. Internaly this function uses

     

       203
       203
       +
          `php.composerHooks.composerRepositoryHook` hook. Internally this function uses

     

       204
       204
        
          a custom

     

       205
       205
        
          [Composer plugin](https://github.com/nix-community/composer-local-repo-plugin) to

     

       206
       206
        
          generate the repository.

+1 -1

nixos/doc/manual/release-notes/rl-2105.section.md

···

353
353

354
354

Another benefit of the refactoring is that we can now issue reloads via either `pkill -HUP unbound` and `systemctl reload unbound` to reload the running configuration without taking the daemon offline. A prerequisite of this was that unbound configuration is available on a well known path on the file system. We are using the path `/etc/unbound/unbound.conf` as that is the default in the CLI tooling which in turn enables us to use `unbound-control` without passing a custom configuration location.

355
355

356
356
-
The module has also been reworked to be [RFC 0042](https://github.com/NixOS/rfcs/blob/master/rfcs/0042-config-option.md) compliant. As such, `sevices.unbound.extraConfig` has been removed and replaced by [services.unbound.settings](options.html#opt-services.unbound.settings). `services.unbound.interfaces` has been renamed to `services.unbound.settings.server.interface`.

356
356
+
The module has also been reworked to be [RFC 0042](https://github.com/NixOS/rfcs/blob/master/rfcs/0042-config-option.md) compliant. As such, `services.unbound.extraConfig` has been removed and replaced by [services.unbound.settings](options.html#opt-services.unbound.settings). `services.unbound.interfaces` has been renamed to `services.unbound.settings.server.interface`.

357
357

358
358

`services.unbound.forwardAddresses` and `services.unbound.allowedAccess` have also been changed to use the new settings interface. You can follow the instructions when executing `nixos-rebuild` to upgrade your configuration to use the new interface.

359
359

+3 -3

nixos/doc/manual/release-notes/rl-2305.section.md

···

87
87

88
88

- [gmediarender](https://github.com/hzeller/gmrender-resurrect), a simple, headless UPnP/DLNA renderer. Available as [services.gmediarender](options.html#opt-services.gmediarender.enable).

89
89

90
90
-
- [go2rtc](https://github.com/AlexxIT/go2rtc), a camera streaming appliation with support for RTSP, WebRTC, HomeKit, FFMPEG, RTMP and other protocols. Available as [services.go2rtc](options.html#opt-services.go2rtc.enable).

90
90
+
- [go2rtc](https://github.com/AlexxIT/go2rtc), a camera streaming application with support for RTSP, WebRTC, HomeKit, FFMPEG, RTMP and other protocols. Available as [services.go2rtc](options.html#opt-services.go2rtc.enable).

91
91

92
92

- [goeland](https://github.com/slurdge/goeland), an alternative to rss2email written in Golang with many filters. Available as [services.goeland](#opt-services.goeland.enable).

93
93

···

203
203

204
204

- `graylog` has been updated to version 5, which can not be updated directly from the previously packaged version 3.3. If you had installed the previously packaged version 3.3, please follow the [upgrade path](https://go2docs.graylog.org/5-0/upgrading_graylog/upgrade_path.htm) from 3.3 to 4.0 to 4.3 to 5.0.

205
205

206
206
-
- `buildFHSUserEnv` is now called `buildFHSEnv` and uses FlatPak's Bubblewrap sandboxing tool rather than Nixpkgs' own chrootenv. The old chrootenv-based implemenation is still available via `buildFHSEnvChroot` but is considered deprecated and will be removed when the remaining uses inside Nixpkgs have been migrated. If your FHSEnv-wrapped application misbehaves when using the new bubblewrap implementation, please create an issue in Nixpkgs.

206
206
+
- `buildFHSUserEnv` is now called `buildFHSEnv` and uses FlatPak's Bubblewrap sandboxing tool rather than Nixpkgs' own chrootenv. The old chrootenv-based implementation is still available via `buildFHSEnvChroot` but is considered deprecated and will be removed when the remaining uses inside Nixpkgs have been migrated. If your FHSEnv-wrapped application misbehaves when using the new bubblewrap implementation, please create an issue in Nixpkgs.

207
207

208
208

- `nushell` has been updated to at least version 0.77.0, which includes potential breaking changes in aliases. The old aliases are now available as `old-alias` but it is recommended you migrate to the new format. See [Reworked aliases](https://www.nushell.sh/blog/2023-03-14-nushell_0_77.html#reworked-aliases-breaking-changes-kubouch).

209
209

···

555
555

556
556

- `buildDunePackage` now defaults to `strictDeps = true` which means that any library should go into `buildInputs` or `checkInputs`. Any executable that is run on the building machine should go into `nativeBuildInputs` or `nativeCheckInputs` respectively. Example of executables are `ocaml`, `findlib` and `menhir`. PPXs are libraries which are built by dune and should therefore not go into `nativeBuildInputs`.

557
557

558
558
-
- `buildFHSUserEnv` is now called `buildFHSEnv` and uses FlatPak's Bubblewrap sandboxing tool rather than Nixpkgs' own chrootenv. The old chrootenv-based implemenation is still available via `buildFHSEnvChroot` but is considered deprecated and will be removed when the remaining uses inside Nixpkgs have been migrated. If your FHSEnv-wrapped application misbehaves when using the new bubblewrap implementation, please create an issue in Nixpkgs.

558
558
+
- `buildFHSUserEnv` is now called `buildFHSEnv` and uses FlatPak's Bubblewrap sandboxing tool rather than Nixpkgs' own chrootenv. The old chrootenv-based implementation is still available via `buildFHSEnvChroot` but is considered deprecated and will be removed when the remaining uses inside Nixpkgs have been migrated. If your FHSEnv-wrapped application misbehaves when using the new bubblewrap implementation, please create an issue in Nixpkgs.

559
559

560
560

- Top-level `buildPlatform`, `hostPlatform`, `targetPlatform` have been deprecated, use `stdenv.X` instead.

561
561

+3 -3

nixos/doc/manual/release-notes/rl-2311.section.md

···

       293
       293
        
       

     

       294
       294
        
       - `services.nginx` gained a `defaultListen` option at server-level with support for PROXY protocol listeners, also `proxyProtocol` is now exposed in `services.nginx.virtualHosts.<name>.listen` option. It is now possible to run PROXY listeners and non-PROXY listeners at a server-level, see [#213510](https://github.com/NixOS/nixpkgs/pull/213510/) for more details.

     

       295
       295
        
       

     

       296
       296
       -
       - `services.restic.backups` now adds wrapper scripts to your system path, which set the same environment variables as the service, so restic operations can easly be run from the command line. This behavior can be disabled by setting `createWrapper` to `false`, per backup configuration.

     

       296
       296
       +
       - `services.restic.backups` now adds wrapper scripts to your system path, which set the same environment variables as the service, so restic operations can easily be run from the command line. This behavior can be disabled by setting `createWrapper` to `false`, per backup configuration.

     

       297
       297
        
       

     

       298
       298
        
       - `services.prometheus.exporters` has a new exporter to monitor electrical power consumption based on PowercapRAPL sensor called [Scaphandre](https://github.com/hubblo-org/scaphandre), see [#239803](https://github.com/NixOS/nixpkgs/pull/239803) for more details.

     

       299
       299
        
       

     

       300
       300
       -
       - The MariaDB C client library was upgraded from 3.2.x to 3.3.x. It is recomended to review the [upstream release notes](https://mariadb.com/kb/en/mariadb-connector-c-33-release-notes/).

     

       300
       300
       +
       - The MariaDB C client library was upgraded from 3.2.x to 3.3.x. It is recommended to review the [upstream release notes](https://mariadb.com/kb/en/mariadb-connector-c-33-release-notes/).

     

       301
       301
        
       

     

       302
       302
        
       - The module `services.calibre-server` has new options to configure the `host`, `port`, `auth.enable`, `auth.mode` and `auth.userDb` path, see [#216497](https://github.com/NixOS/nixpkgs/pull/216497/) for more details.

     

       303
       303
        
       

     
···

       381
       381
        
       

     

       382
       382
        
       - The `qemu-vm.nix` module by default now identifies block devices via

     

       383
       383
        
         persistent names available in `/dev/disk/by-*`. Because the rootDevice is

     

       384
       384
       -
         identfied by its filesystem label, it needs to be formatted before the VM is

     

       384
       384
       +
         identified by its filesystem label, it needs to be formatted before the VM is

     

       385
       385
        
         started. The functionality of automatically formatting the rootDevice in the

     

       386
       386
        
         initrd is removed from the QEMU module. However, for tests that depend on

     

       387
       387
        
         this functionality, a test utility for the scripted initrd is added

+1 -1

pkgs/README.md

···

       29
       29
        
       Before adding a new package, please consider the following questions:

     

       30
       30
        
       

     

       31
       31
        
       * Is the package ready for general use? We don't want to include projects that are too immature or are going to be abandoned immediately. In case of doubt, check with upstream.

     

       32
       32
       -
       * Does the project have a clear license statement? Remember that softwares are unfree by default (all rights reserved), and merely providing access to the source code does not imply its redistribution. In case of doubt, ask upstream.

     

       32
       32
       +
       * Does the project have a clear license statement? Remember that software is unfree by default (all rights reserved), and merely providing access to the source code does not imply its redistribution. In case of doubt, ask upstream.

     

       33
       33
        
       * How realistic is it that it will be used by other people? It's good that nixpkgs caters to various niches, but if it's a niche of 5 people it's probably too small.

     

       34
       34
        
       * Are you willing to maintain the package? You should care enough about the package to be willing to keep it up and running for at least one complete Nixpkgs' release life-cycle.

     

       35
       35

+1 -1

pkgs/applications/networking/cluster/k3s/README.md

···

       25
       25
        
       

     

       26
       26
        
       As such, we would like to have only the newest K3s version in each NixOS

     

       27
       27
        
       release at the time the release branch is branched off, which will ensure the

     

       28
       28
       -
       K3s version in that release will receieve updates for the longest duration

     

       28
       28
       +
       K3s version in that release will receive updates for the longest duration

     

       29
       29
        
       possible.

     

       30
       30
        
       

     

       31
       31
        
       However, this conflicts with another desire: we would like people to be able to upgrade between NixOS stable releases without needing to make a large enough k3s version jump that they violate the Kubernetes version skew policy.

+1 -1

pkgs/applications/science/math/sage/README.md

···

       2
       2
        
       

     

       3
       3
        
       Sage is a pretty complex package that depends on many other complex packages and patches some of those. As a result, the sage nix package is also quite complex.

     

       4
       4
        
       

     

       5
       5
       -
       Don't feel discouraged to fix, simplify or improve things though. The individual files have comments explaining their purpose. The most importent ones are `default.nix` linking everything together, `sage-src.nix` adding patches and `sagelib.nix` building the actual sage package.

     

       5
       5
       +
       Don't feel discouraged to fix, simplify or improve things though. The individual files have comments explaining their purpose. The most important ones are `default.nix` linking everything together, `sage-src.nix` adding patches and `sagelib.nix` building the actual sage package.

     

       6
       6
        
       

     

       7
       7
        
       ## The sage build is broken

     

       8
       8

+1 -1

pkgs/development/haskell-modules/HACKING.md

···

       137
       137
        
           This is a list of Haskell packages that are known to be broken.

     

       138
       138
        
       

     

       139
       139
        
       -   [`hackage-packages.nix`](hackage-packages.nix) will be regenerated.  This

     

       140
       140
       -
           will mark all Haskell pacakges in `configuration-hackage2nix/broken.yaml`

     

       140
       140
       +
           will mark all Haskell packages in `configuration-hackage2nix/broken.yaml`

     

       141
       141
        
           as `broken`.

     

       142
       142
        
       

     

       143
       143
        
       -   The

+1 -1

pkgs/development/lisp-modules-new-obsolete/doc/api.md

···

       76
       76
        
       to the Nix store. This prevents ASDF from referring to uncompiled

     

       77
       77
        
       systems on run time.

     

       78
       78
        
       

     

       79
       79
       -
       Also useful when the `pname` is differrent than the system name, such

     

       79
       79
       +
       Also useful when the `pname` is different than the system name, such

     

       80
       80
        
       as when using [reverse domain naming]. (see `jzon` ->

     

       81
       81
        
       `com.inuoe.jzon`)

     

       82
       82

+1 -1

pkgs/development/lisp-modules-new-obsolete/doc/nix-cl.md

···

       31
       31
        
       

     

       32
       32
        
       ## Using libraries not available in repositories

     

       33
       33
        
       

     

       34
       34
       -
       There are useful and working libraries out there, that are nontheless

     

       34
       34
       +
       There are useful and working libraries out there, that are nonetheless

     

       35
       35
        
       unavailable to users of package managers such as Quicklisp or

     

       36
       36
        
       Ultralisp. Two real-world examples are [jzon] and [cl-tar].

     

       37
       37

+1 -1

pkgs/development/misc/resholve/README.md

···

       203
       203
        
       add more at this early date will only ensure that I spend more time updating

     

       204
       204
        
       docs and less time filling in feature gaps.

     

       205
       205
        
       

     

       206
       206
       -
       Full documentation may be greatly accellerated if someone can help me sort out

     

       206
       206
       +
       Full documentation may be greatly accelerated if someone can help me sort out

     

       207
       207
        
       single-sourcing. See: https://github.com/abathur/resholve/issues/19

     

       208
       208
        
       -->

     

       209
       209