Merge master into staging-next

In the scenario you are unable to run the resulting binary: this is arguably the most complicated as it could be any combination of the previous reasons. This type of failure typically occurs when a library attempts to load or open a library it depends on that it does not declare in its `DT_NEEDED` section. As a first step, ensure that dependencies are patched with [`autoAddDriverRunpath`](https://search.nixos.org/packages?channel=unstable&type=packages&query=autoAddDriverRunpath). Failing that, try running the application with [`nixGL`](https://github.com/guibou/nixGL) or a similar wrapper tool. If that works, it likely means that the application is attempting to load a library that is not in the `RPATH` or `RUNPATH` of the binary.

## Running Docker or Podman containers with CUDA support {#running-docker-or-podman-containers-with-cuda-support}

## Running Docker or Podman containers with CUDA support {#cuda-docker-podman}

It is possible to run Docker or Podman containers with CUDA support. The recommended mechanism to perform this task is to use the [NVIDIA Container Toolkit](https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/index.html).

    githubId = 535135;

    name = "Brennon Loveless";

  };

  bloxx12 = {

    email = "charlie@charlieroot.dev";

    github = "bloxx12";

    githubId = 75451918;

    name = "Charlie Root";

  };

  bluescreen303 = {

    email = "mathijs@bluescreen303.nl";

    github = "bluescreen303";

    githubId = 1931963;

    name = "David Sferruzza";

  };

  dsluijk = {

    name = "Dany Sluijk";

    email = "nix@dany.dev";

    github = "dsluijk";

    githubId = 8537327;

  };

  dstengele = {

    name = "Dennis Stengele";

    email = "dennis@stengele.me";

  This change requires granting access to the repositories to this user or

  setting the appropriate one through `services.cgit.some-instance.user`.

- `gradle_6` was removed due to being [unsupported upstream as of 10 Feb 2023](https://endoflife.date/gradle).

  Additionally, it had numerous security vulnerabilities that were only patched

  in later versions, such as [CVE-2021-29429](https://nvd.nist.gov/vuln/detail/CVE-2021-32751),

  [CVE-2021-29427](https://nvd.nist.gov/vuln/detail/CVE-2021-29427), [CVE-2021-29428](https://nvd.nist.gov/vuln/detail/CVE-2021-29428), and [CVE-2021-32751](https://nvd.nist.gov/vuln/detail/CVE-2021-32751).

- `nvimpager` was updated to version 0.13.0, which changes the order of user and

  nvimpager settings: user commands in `-c` and `--cmd` now override the

  respective default settings because they are executed later.

- The `services.prometheus.exporters.minio` option has been removed, as it's upstream implementation was broken and unmaintained.

  Minio now has built-in [Prometheus metrics exposure](https://min.io/docs/minio/linux/operations/monitoring/collect-minio-metrics-using-prometheus.html), which can be used instead.

- The `services.prometheus.exporters.tor` option has been removed, as its upstream implementation was broken and unmaintained.

- The `services.patroni.raft` option has been removed, as Raft has been [deprecated by upstream since 3.0.0](https://github.com/patroni/patroni/blob/master/docs/releases.rst#version-300)

- The `jd-cli` package was removed due to an inactive upstream and a dependency on the shut down

  JCenter JAR repository.

  Java decompilers already packaged in Nixpkgs include `bytecode-viewer` (GUI), `cfr` (CLI), and `procyon` (CLI).

- The `jd-gui` package was removed due to an inactive upstream and a dependency on the end-of-life Gradle 6.

  Java decompilers already packaged in Nixpkgs include `bytecode-viewer` (GUI), `cfr` (CLI), and `procyon` (CLI).

- `services.roundcube.maxAttachmentSize` will multiply the value set with `1.37` to offset overhead introduced by the base64 encoding applied to attachments.

- The `services.mxisd` module has been removed as both [mxisd](https://github.com/kamax-matrix/mxisd) and [ma1sd](https://github.com/ma1uta/ma1sd) are not maintained any longer.

    "statsd"

    "surfboard"

    "systemd"

    "tor"

    "unbound"

    "unifi"

    "unpoller"

          The Minio exporter has been removed, as it was broken and unmaintained.

          See the 24.11 release notes for more information.

        '')

        (lib.mkRemovedOptionModule [ "tor" ] ''

          The Tor exporter has been removed, as it was broken and unmaintained.

        '')

      ];

    };

    description = "Prometheus exporter configuration";

{ config, lib, pkgs, options, ... }:

let

  cfg = config.services.prometheus.exporters.tor;

  inherit (lib) mkOption types concatStringsSep;

in

{

  port = 9130;

  extraOpts = {

    torControlAddress = mkOption {

      type = types.str;

      default = "127.0.0.1";

      description = ''

        Tor control IP address or hostname.

      '';

    };

    torControlPort = mkOption {

      type = types.port;

      default = 9051;

      description = ''

        Tor control port.

      '';

    };

  };

  serviceOpts = {

    serviceConfig = {

      ExecStart = ''

        ${pkgs.prometheus-tor-exporter}/bin/prometheus-tor-exporter \

          -b ${cfg.listenAddress} \

          -p ${toString cfg.port} \

          -a ${cfg.torControlAddress} \

          -c ${toString cfg.torControlPort} \

          ${concatStringsSep " \\\n  " cfg.extraFlags}

      '';

    };

    # CPython requires a process to either have $HOME defined or run as a UID

    # defined in /etc/passwd. The latter is false with DynamicUser, so define a

    # dummy $HOME. https://bugs.python.org/issue10496

    environment = { HOME = "/var/empty"; };

  };

}