Question: <del> <section xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xi="http://www.w3.org/2001/XInclude" version="5.0" xml:id="sec-custom-packages"> <title>Adding Custom Packages</title> <para> It’s possible that a package you need is not available in NixOS. In that case, you can do two things. First, you can clone the Nixpkgs repository, add the package to your clone, and (optionally) submit a patch or pull request to have it accepted into the main Nixpkgs repository. This is described in detail in the <link xlink:href="https://nixos.org/nixpkgs/manual">Nixpkgs manual</link>. In short, you clone Nixpkgs: <screen> <prompt>$ </prompt>git clone https://github.com/NixOS/nixpkgs <prompt>$ </prompt>cd nixpkgs </screen> Then you write and test the package as described in the Nixpkgs manual. Finally, you add it to <literal>environment.systemPackages</literal>, e.g. <programlisting> <xref linkend="opt-environment.systemPackages"/> = [ pkgs.my-package ]; </programlisting> and you run <command>nixos-rebuild</command>, specifying your own Nixpkgs tree: <screen> <prompt># </prompt>nixos-rebuild switch -I nixpkgs=/path/to/my/nixpkgs</screen> </para> <para> The second possibility is to add the package outside of the Nixpkgs tree. For instance, here is how you specify a build of the <link xlink:href="https://www.gnu.org/software/hello/">GNU Hello</link> package directly in <filename>configuration.nix</filename>: <programlisting> <xref linkend="opt-environment.systemPackages"/> = let my-hello = with pkgs; stdenv.mkDerivation rec { name = "hello-2.8"; src = fetchurl { url = "mirror://gnu/hello/${name}.tar.gz"; sha256 = "0wqd8sjmxfskrflaxywc7gqw7sfawrfvdxd9skxawzfgyy0pzdz6"; }; }; in [ my-hello ]; </programlisting> Of course, you can also move the definition of <literal>my-hello</literal> into a separate Nix expression, e.g. <programlisting> <xref linkend="opt-environment.systemPackages"/> = [ (import ./my-hello.nix) ]; </programlisting> where <filename>my-hello.nix</filename> contains: <programlisting> with import <nixpkgs> {}; # bring all of Nixpkgs into scope stdenv.mkDerivation rec { name = "hello-2.8"; src = fetchurl { url = "mirror://gnu/hello/${name}.tar.gz"; sha256 = "0wqd8sjmxfskrflaxywc7gqw7sfawrfvdxd9skxawzfgyy0pzdz6"; }; } </programlisting> This allows testing the package easily: <screen> <prompt>$ </prompt>nix-build my-hello.nix <prompt>$ </prompt>./result/bin/hello Hello, world! </screen> </para> </section> </del>

This tracks the conversion of from Docbook to CommonMark per . here that you intend to work on this. (Please also post if you stop working on this.) a new branch of nixpkgs master. : change to . to . the contents from Docbook to . Follow . Use existing sections in the NixOS and Nixpkgs manual for inspiration. the CommonMark back to DocBook xml with: from nixpkgs root dir with: a preview server with: your work at on steps 5-9. it looks good, commit both the new file and the generated file, submit a PR and reference this issue.
I opened a PR for and : PTAL, thanks in advance for reviewing :-)


Question: , xdg-utils , removeReferencesTo , libstemmer <ins> , wrapGAppsHook </ins> }: mkDerivation rec { pname = "calibre"; <del> version = "5.34.0"; </del> <ins> version = "5.37.0"; </ins> src = fetchurl { url = "https://download.calibre-ebook.com/${version}/${pname}-${version}.tar.xz"; <del> hash = "sha256-1NQB7vrcU0hR308/8keUn/rHhdvJk5Ab0pOMPyiU1+M="; </del> <ins> hash = "sha256-x2u4v0k05WMATSsuo76NnqChIz8BcTuZfPkZa0uLnMY="; </ins> }; # https://sources.debian.org/patches/calibre/${version}+dfsg-1

When using file picker in calibre e.g. on first launch after install that pops up file picker to select library path or by clicking "Add books" in menu calibre will crash with error Steps to reproduce the behavior: not yet crashed - select "Add books" item in menu Calibre should work without issues From i figured adding to solves problem, so running it like this works: Please run and paste the result.


Question: configureFlags = stdenv.lib.optionals(buildDocs) [ "--docdir=$(doc)" ]; preConfigure = '' export SAGE_NUM_THREADS="$NIX_BUILD_CORES" <del> export SAGE_ATLAS_ARCH=fast </del> export HOME=/tmp/sage-home export SAGE_ROOT="$PWD"

The recent changes seem to make sage crash when it tries to run some code using openblas (I think). I installed the sage derivation from the latest github repository. In the sage interpreter, run the following sage crashes with the following message: Please run and paste the results. system: host os: multi-user?: sandbox: version: channels(okideal): channels(root): nixpkgs:
Procedural: as it is , please specify the CPU model. Looks like the Sage build system had the idea to use somewhere… I.e. the local build could work. I wonder how feasible it is to find where Sage does it — the Sage derivation is allowed to rebuild a lot of dependencies because it is just too much pain to make it use the system versions.
Here is the output of lscpu
From the traceback it presumably crashes here: which is which indeed is an AMD-only instruction (MMX? thought that would be long obsolete by now...)
You were right. A local build works fine. Thanks for the help.
Thanks for your report. do we set to and give up?
This should be fixed by exporting (see ). I'm not quite ready to give up (even though it would probably be the healthier choice :grin:). I'm actually currently experimenting with doing it the "right way" and replacing the sage buildsytem with nix (with a mix of sage and system dependencies).
can you confirm that the latest binary works?
Sorry for the late answer. The binaries from the master branch seem to work. The initial crashes are gone and running gives only unrelated failures. Installing from still gives me the old, faulty binaries though.
Are you sure you updated the channel? What do you mean by "binaries from master"?
I meant that installing from the master branch of the git repository works. I was not aware that there is a difference between nixos-unstable and nixpkgs-unstable. The latter does not seem to include the fix yet. Installing from nixos-unstable works well. Thanks for your help.
Okay, I guess hydra is a bit overwhelmed by all the fixes for the upcoming release. Thanks for reporting.


Question: (cfg "runstatedir" "/run") (cfg "init_script" (if isDarwin then "none" else "systemd")) <ins> (cfg "qemu_datadir" (if isDarwin then "${qemu}/share/qemu" else "")) </ins> (feat "apparmor" isLinux) (feat "attr" isLinux)

On my M1 Mac, with homebrew-installed libvirt / qemu-system-aarch64, I'm able to run the VM defined in the config below without issue. However with libvirt / qemu installed via nix, I get: Some possibly related discussion . Looking at the , they're explicitly setting ; adding this seems to resolve the issue: I'm not sure whether disabling those failing tests is a reasonable thing to do. Steps to reproduce the behavior: to in A clear and concise description of what you expected to happen. Should run without , like it does with homebrew. Please run and paste the result.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
FWIW, I also encountered this issue, and have to use the following workaround: And -ing the efi firmware & vars manually. Fixing this bug can lead to great user experience: virt-manager can work out of box.
Where did you get ?


Question: <ins> { "version": "0b50c45", "hash": "sha256-SsgcXAiE7EvVkHAmqq4WIJt7ds2df3GvWCCUovmPS0M=" } </ins>

Package name: rnnoise Latest released version: 0.2 <!-- Search your package here: --- Current version on the unstable channel: 2021-01-22 Current version on the stable/release channel: 2021-01-22 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers Note for maintainers: Please tag this issue in your PR. Tried building with but it got a missing file. There’s also warning about not using SSE3/AVX/AVX2, but Nix only supports the bottom of the barrel, common x86 instructions, but I usually compile this one out with some flags. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]: [^1] or offering a non-proprietary, non-US-corporate-controlled mirror for this free software project. I wish to delete this Microsoft account in the future, but I need more projects like this to support alternative methods to send patches & contribute.
The missing file is downloaded as part of the '' It looks like they a step to the build process.
Perhaps it can be fetched using fetchurl/fetchpatch?
You're correct. The relevant file is retrieved in the script . It fetches a single file from the URL , where the version is extracted from the file , currently set to . Hence, we can emulate the download script and execute something similar to:
Alternatively you could use instead of a separate model + . While we are at it, we should be using the main repository instead just Microsoft GitHub which is explicitly listed as a mirror, not the primary code forge. Something like Referencing both mirrors would be more resilient for when one of these platforms goes down.
Made a PR , but still having trouble designing a .


Question: btc-rpc-explorer = callPackage ../tools/misc/btc-rpc-explorer { }; <del> butler = callPackage ../by-name/bu/butler/package.nix { inherit (darwin.apple_sdk.frameworks) Cocoa; }; </del> carbon-now-cli = callPackage ../tools/typesetting/carbon-now-cli { }; cf-vault = callPackage ../tools/admin/cf-vault { };

Package name: itch Latest released version: 26.1.3 Current version on the unstable channel: 26.1.3 Current version on the stable/release channel: 26.1.3 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- The current version is broken since butler is marked broken Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
The latest version on seems to be 26.1.3 which is used in the package.
There is 26.1.5 as a source code , but current package uses binaryBytecode


Question: name = "Fluid-3"; src = fetchurl { <del> url = "http://www.musescore.org/download/fluid-soundfont.tar.gz"; </del> <ins> url = "https://ftp.osuosl.org/pub/musescore/soundfont/fluid-soundfont.tar.gz"; </ins> sha256 = "1f96bi0y6rms255yr8dfk436azvwk66c99j6p43iavyq8jg7c5f8"; };

The soundfont that is packaged in is no longer available. The URL in that file is , but that page says: "Sorry, this is a wrong download link.". No packages depend on this package.


Question: +        // Nix Directories +        "--ro-bind", "@storeDir@", "@storeDir@", +        "--ro-bind", "/run/current-system", "/run/current-system", <del> +        "--ro-bind", "/run/opengl-driver", "/run/opengl-driver", </del> <ins> +        "--ro-bind-try", "@driverLink@/lib", "@driverLink@/lib", +        "--ro-bind-try", "@driverLink@/share", "@driverLink@/share", </ins> }; // We would have to parse ld config files for more info. bindPathVar(sandboxArgs, "LD_LIBRARY_PATH");

Describe the bug Epiphany crashes on startup with a bind mount error. To Reproduce Steps to reproduce the behavior: epiphany Expected behavior The browser should startup Additional context Error: exists and opengl is enabled I bet is relevant Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Metadata Maintainer information:
I can't reproduce this on my machine. Can you try running it with ?
Thanks for responding. I think this is the relevant part from :
Ah, this only shows that emits the error message. To trace what it actually does, could you try adding the flag?
I just piped it all into here:
The output got cut off there, unfortunately. Maybe you could just attach the text file directly to your reply?
Sorry about that, here is the file:
Thanks for the log! I think I've found the culprit. I've opened which seems to fix it - please try it out.


Question: <del> <section xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xi="http://www.w3.org/2001/XInclude" xml:id="sec-pkgs-dockerTools"> <title>pkgs.dockerTools</title> <para> <varname>pkgs.dockerTools</varname> is a set of functions for creating and manipulating Docker images according to the <link xlink:href="https://github.com/moby/moby/blob/master/image/spec/v1.2.md#docker-image-specification-v120"> Docker Image Specification v1.2.0 </link>. Docker itself is not used to perform any of the operations done by these functions. </para> <section xml:id="ssec-pkgs-dockerTools-buildImage"> <title>buildImage</title> <para> This function is analogous to the <command>docker build</command> command, in that it can be used to build a Docker-compatible repository tarball containing a single image with one or multiple layers. As such, the result is suitable for being loaded in Docker with <command>docker load</command>. </para> <para> The parameters of <varname>buildImage</varname> with relative example values are described below: </para> <example xml:id='ex-dockerTools-buildImage'> <title>Docker build</title> <programlisting> buildImage { name = "redis"; <co xml:id='ex-dockerTools-buildImage-1' /> tag = "latest"; <co xml:id='ex-dockerTools-buildImage-2' /> fromImage = someBaseImage; <co xml:id='ex-dockerTools-buildImage-3' /> fromImageName = null; <co xml:id='ex-dockerTools-buildImage-4' /> fromImageTag = "latest"; <co xml:id='ex-dockerTools-buildImage-5' /> contents = pkgs.redis; <co xml:id='ex-dockerTools-buildImage-6' /> runAsRoot = '' <co xml:id='ex-dockerTools-buildImage-runAsRoot' /> #!${pkgs.runtimeShell} mkdir -p /data ''; config = { <co xml:id='ex-dockerTools-buildImage-8' /> Cmd = [ "/bin/redis-server" ]; WorkingDir = "/data"; Volumes = { "/data" = {}; }; }; } </programlisting> </example> <para> The above example will build a Docker image <literal>redis/latest</literal> from the given base image. Loading and running this image in Docker results in <literal>redis-server</literal> being started automatically. </para> <calloutlist> <callout arearefs='ex-dockerTools-buildImage-1'> <para> <varname>name</varname> specifies the name of the resulting image. This is the only required argument for <varname>buildImage</varname>. </para> </callout> <callout arearefs='ex-dockerTools-buildImage-2'> <para> <varname>tag</varname> specifies the tag of the resulting image. By default it's <literal>null</literal>, which indicates that the nix output hash will be used as tag. </para> </callout> <callout arearefs='ex-dockerTools-buildImage-3'> <para> <varname>fromImage</varname> is the repository tarball containing the base image. It must be a valid Docker image, such as exported by <command>docker save</command>. By default it's <literal>null</literal>, which can be seen as equivalent to <literal>FROM scratch</literal> of a <filename>Dockerfile</filename>. </para> </callout> <callout arearefs='ex-dockerTools-buildImage-4'> <para> <varname>fromImageName</varname> can be used to further specify the base image within the repository, in case it contains multiple images. By default it's <literal>null</literal>, in which case <varname>buildImage</varname> will peek the first image available in the repository. </para> </callout> <callout arearefs='ex-dockerTools-buildImage-5'> <para> <varname>fromImageTag</varname> can be used to further specify the tag of the base image within the repository, in case an image contains multiple tags. By default it's <literal>null</literal>, in which case <varname>buildImage</varname> will peek the first tag available for the base image. </para> </callout> <callout arearefs='ex-dockerTools-buildImage-6'> <para> <varname>contents</varname> is a derivation that will be copied in the new layer of the resulting image. This can be similarly seen as <command>ADD contents/ /</command> in a <filename>Dockerfile</filename>. By default it's <literal>null</literal>. </para> </callout> <callout arearefs='ex-dockerTools-buildImage-runAsRoot'> <para> <varname>runAsRoot</varname> is a bash script that will run as root in an environment that overlays the existing layers of the base image with the new resulting layer, including the previously copied <varname>contents</varname> derivation. This can be similarly seen as <command>RUN ...</command> in a <filename>Dockerfile</filename>. <note> <para> Using this parameter requires the <literal>kvm</literal> device to be available. </para> </note> </para> </callout> <callout arearefs='ex-dockerTools-buildImage-8'> <para> <varname>config</varname> is used to specify the configuration of the containers that will be started off the built image in Docker. The available options are listed in the <link xlink:href="https://github.com/moby/moby/blob/master/image/spec/v1.2.md#image-json-field-descriptions"> Docker Image Specification v1.2.0 </link>. </para> </callout> </calloutlist> <para> After the new layer has been created, its closure (to which <varname>contents</varname>, <varname>config</varname> and <varname>runAsRoot</varname> contribute) will be copied in the layer itself. Only new dependencies that are not already in the existing layers will be copied. </para> <para> At the end of the process, only one new single layer will be produced and added to the resulting image. </para> <para> The resulting repository will only list the single image <varname>image/tag</varname>. In the case of <xref linkend='ex-dockerTools-buildImage'/> it would be <varname>redis/latest</varname>. </para> <para> It is possible to inspect the arguments with which an image was built using its <varname>buildArgs</varname> attribute. </para> <note> <para> If you see errors similar to <literal>getProtocolByName: does not exist (no such protocol name: tcp)</literal> you may need to add <literal>pkgs.iana-etc</literal> to <varname>contents</varname>. </para> </note> <note> <para> If you see errors similar to <literal>Error_Protocol ("certificate has unknown CA",True,UnknownCa)</literal> you may need to add <literal>pkgs.cacert</literal> to <varname>contents</varname>. </para> </note> <example xml:id="example-pkgs-dockerTools-buildImage-creation-date"> <title>Impurely Defining a Docker Layer's Creation Date</title> <para> By default <function>buildImage</function> will use a static date of one second past the UNIX Epoch. This allows <function>buildImage</function> to produce binary reproducible images. When listing images with <command>docker images</command>, the newly created images will be listed like this: </para> <screen> <prompt>$ </prompt>docker images REPOSITORY   TAG      IMAGE ID       CREATED        SIZE hello        latest   08c791c7846e   48 years ago   25.2MB </screen> <para> You can break binary reproducibility but have a sorted, meaningful <literal>CREATED</literal> column by setting <literal>created</literal> to <literal>now</literal>. </para> <programlisting><![CDATA[ pkgs.dockerTools.buildImage { name = "hello"; tag = "latest"; created = "now"; contents = pkgs.hello; config.Cmd = [ "/bin/hello" ]; } ]]></programlisting> <para> and now the Docker CLI will display a reasonable date and sort the images as expected: <screen> <prompt>$ </prompt>docker images REPOSITORY   TAG      IMAGE ID       CREATED              SIZE hello        latest   de2bf4786de6   About a minute ago   25.2MB </screen> however, the produced images will not be binary reproducible. </para> </example> </section> <section xml:id="ssec-pkgs-dockerTools-buildLayeredImage"> <title>buildLayeredImage</title> <para> Create a Docker image with many of the store paths being on their own layer to improve sharing between images. The image is realized into the Nix store as a gzipped tarball. Depending on the intended usage, many users might prefer to use <function>streamLayeredImage</function> instead, which this function uses internally. </para> <variablelist> <varlistentry> <term> <varname>name</varname> </term> <listitem> <para> The name of the resulting image. </para> </listitem> </varlistentry> <varlistentry> <term> <varname>tag</varname> <emphasis>optional</emphasis> </term> <listitem> <para> Tag of the generated image. </para> <para> <emphasis>Default:</emphasis> the output path's hash </para> </listitem> </varlistentry> <varlistentry> <term> <varname>contents</varname> <emphasis>optional</emphasis> </term> <listitem> <para> Top level paths in the container. Either a single derivation, or a list of derivations. </para> <para> <emphasis>Default:</emphasis> <literal>[]</literal> </para> </listitem> </varlistentry> <varlistentry> <term> <varname>config</varname> <emphasis>optional</emphasis> </term> <listitem> <para> Run-time configuration of the container. A full list of the options are available at in the <link xlink:href="https://github.com/moby/moby/blob/master/image/spec/v1.2.md#image-json-field-descriptions"> Docker Image Specification v1.2.0 </link>. </para> <para> <emphasis>Default:</emphasis> <literal>{}</literal> </para> </listitem> </varlistentry> <varlistentry> <term> <varname>created</varname> <emphasis>optional</emphasis> </term> <listitem> <para> Date and time the layers were created. Follows the same <literal>now</literal> exception supported by <literal>buildImage</literal>. </para> <para> <emphasis>Default:</emphasis> <literal>1970-01-01T00:00:01Z</literal> </para> </listitem> </varlistentry> <varlistentry> <term> <varname>maxLayers</varname> <emphasis>optional</emphasis> </term> <listitem> <para> Maximum number of layers to create. </para> <para> <emphasis>Default:</emphasis> <literal>100</literal> </para> <para> <emphasis>Maximum:</emphasis> <literal>125</literal> </para> </listitem> </varlistentry> <varlistentry> <term> <varname>extraCommands</varname> <emphasis>optional</emphasis> </term> <listitem> <para> Shell commands to run while building the final layer, without access to most of the layer contents. Changes to this layer are "on top" of all the other layers, so can create additional directories and files. </para> </listitem> </varlistentry> </variablelist> <section xml:id="dockerTools-buildLayeredImage-arg-contents"> <title>Behavior of <varname>contents</varname> in the final image</title> <para> Each path directly listed in <varname>contents</varname> will have a symlink in the root of the image. </para> <para> For example: <programlisting><![CDATA[ pkgs.dockerTools.buildLayeredImage { name = "hello"; contents = [ pkgs.hello ]; } ]]></programlisting> will create symlinks for all the paths in the <literal>hello</literal> package: <screen><![CDATA[ /bin/hello -> /nix/store/h1zb1padqbbb7jicsvkmrym3r6snphxg-hello-2.10/bin/hello /share/info/hello.info -> /nix/store/h1zb1padqbbb7jicsvkmrym3r6snphxg-hello-2.10/share/info/hello.info /share/locale/bg/LC_MESSAGES/hello.mo -> /nix/store/h1zb1padqbbb7jicsvkmrym3r6snphxg-hello-2.10/share/locale/bg/LC_MESSAGES/hello.mo ]]></screen> </para> </section> <section xml:id="dockerTools-buildLayeredImage-arg-config"> <title>Automatic inclusion of <varname>config</varname> references</title> <para> The closure of <varname>config</varname> is automatically included in the closure of the final image. </para> <para> This allows you to make very simple Docker images with very little code. This container will start up and run <command>hello</command>: <programlisting><![CDATA[ pkgs.dockerTools.buildLayeredImage { name = "hello"; config.Cmd = [ "${pkgs.hello}/bin/hello" ]; } ]]></programlisting> </para> </section> <section xml:id="dockerTools-buildLayeredImage-arg-maxLayers"> <title>Adjusting <varname>maxLayers</varname></title> <para> Increasing the <varname>maxLayers</varname> increases the number of layers which have a chance to be shared between different images. </para> <para> Modern Docker installations support up to 128 layers, however older versions support as few as 42. </para> <para> If the produced image will not be extended by other Docker builds, it is safe to set <varname>maxLayers</varname> to <literal>128</literal>. However it will be impossible to extend the image further. </para> <para> The first (<literal>maxLayers-2</literal>) most "popular" paths will have their own individual layers, then layer #<literal>maxLayers-1</literal> will contain all the remaining "unpopular" paths, and finally layer #<literal>maxLayers</literal> will contain the Image configuration. </para> <para> Docker's Layers are not inherently ordered, they are content-addressable and are not explicitly layered until they are composed in to an Image. </para> </section> </section> <section xml:id="ssec-pkgs-dockerTools-streamLayeredImage"> <title>streamLayeredImage</title> <para> Builds a script which, when run, will stream an uncompressed tarball of a Docker image to stdout. The arguments to this function are as for <function>buildLayeredImage</function>. This method of constructing an image does not realize the image into the Nix store, so it saves on IO and disk/cache space, particularly with large images. </para> <para> The image produced by running the output script can be piped directly into <command>docker load</command>, to load it into the local docker daemon: <screen><![CDATA[ $(nix-build) | docker load ]]></screen> </para> <para> Alternatively, the image be piped via <command>gzip</command> into <command>skopeo</command>, e.g. to copy it into a registry: <screen><![CDATA[ $(nix-build) | gzip --fast | skopeo copy docker-archive:/dev/stdin docker://some_docker_registry/myimage:tag ]]></screen> </para> </section> <section xml:id="ssec-pkgs-dockerTools-fetchFromRegistry"> <title>pullImage</title> <para> This function is analogous to the <command>docker pull</command> command, in that it can be used to pull a Docker image from a Docker registry. By default <link xlink:href="https://hub.docker.com/">Docker Hub</link> is used to pull images. </para> <para> Its parameters are described in the example below: </para> <example xml:id='ex-dockerTools-pullImage'> <title>Docker pull</title> <programlisting> pullImage { imageName = "nixos/nix"; <co xml:id='ex-dockerTools-pullImage-1' /> imageDigest = "sha256:20d9485b25ecfd89204e843a962c1bd70e9cc6858d65d7f5fadc340246e2116b"; <co xml:id='ex-dockerTools-pullImage-2' /> finalImageName = "nix"; <co xml:id='ex-dockerTools-pullImage-3' /> finalImageTag = "1.11";  <co xml:id='ex-dockerTools-pullImage-4' /> sha256 = "0mqjy3zq2v6rrhizgb9nvhczl87lcfphq9601wcprdika2jz7qh8"; <co xml:id='ex-dockerTools-pullImage-5' /> os = "linux"; <co xml:id='ex-dockerTools-pullImage-6' /> arch = "x86_64"; <co xml:id='ex-dockerTools-pullImage-7' /> } </programlisting> </example> <calloutlist> <callout arearefs='ex-dockerTools-pullImage-1'> <para> <varname>imageName</varname> specifies the name of the image to be downloaded, which can also include the registry namespace (e.g. <literal>nixos</literal>). This argument is required. </para> </callout> <callout arearefs='ex-dockerTools-pullImage-2'> <para> <varname>imageDigest</varname> specifies the digest of the image to be downloaded. This argument is required. </para> </callout> <callout arearefs='ex-dockerTools-pullImage-3'> <para> <varname>finalImageName</varname>, if specified, this is the name of the image to be created. Note it is never used to fetch the image since we prefer to rely on the immutable digest ID. By default it's equal to <varname>imageName</varname>. </para> </callout> <callout arearefs='ex-dockerTools-pullImage-4'> <para> <varname>finalImageTag</varname>, if specified, this is the tag of the image to be created. Note it is never used to fetch the image since we prefer to rely on the immutable digest ID. By default it's <literal>latest</literal>. </para> </callout> <callout arearefs='ex-dockerTools-pullImage-5'> <para> <varname>sha256</varname> is the checksum of the whole fetched image. This argument is required. </para> </callout> <callout arearefs='ex-dockerTools-pullImage-6'> <para> <varname>os</varname>, if specified, is the operating system of the fetched image. By default it's <literal>linux</literal>. </para> </callout> <callout arearefs='ex-dockerTools-pullImage-7'> <para> <varname>arch</varname>, if specified, is the cpu architecture of the fetched image. By default it's <literal>x86_64</literal>. </para> </callout> </calloutlist> <para> <literal>nix-prefetch-docker</literal> command can be used to get required image parameters: <screen> <prompt>$ </prompt>nix run nixpkgs.nix-prefetch-docker -c nix-prefetch-docker --image-name mysql --image-tag 5 </screen> Since a given <varname>imageName</varname> may transparently refer to a manifest list of images which support multiple architectures and/or operating systems, you can supply the <option>--os</option> and <option>--arch</option> arguments to specify exactly which image you want. By default it will match the OS and architecture of the host the command is run on. <screen> <prompt>$ </prompt>nix-prefetch-docker --image-name mysql --image-tag 5 --arch x86_64 --os linux </screen> Desired image name and tag can be set using <option>--final-image-name</option> and <option>--final-image-tag</option> arguments: <screen> <prompt>$ </prompt>nix-prefetch-docker --image-name mysql --image-tag 5 --final-image-name eu.gcr.io/my-project/mysql --final-image-tag prod </screen> </para> </section> <section xml:id="ssec-pkgs-dockerTools-exportImage"> <title>exportImage</title> <para> This function is analogous to the <command>docker export</command> command, in that it can be used to flatten a Docker image that contains multiple layers. It is in fact the result of the merge of all the layers of the image. As such, the result is suitable for being imported in Docker with <command>docker import</command>. </para> <note> <para> Using this function requires the <literal>kvm</literal> device to be available. </para> </note> <para> The parameters of <varname>exportImage</varname> are the following: </para> <example xml:id='ex-dockerTools-exportImage'> <title>Docker export</title> <programlisting> exportImage { fromImage = someLayeredImage; fromImageName = null; fromImageTag = null; name = someLayeredImage.name; } </programlisting> </example> <para> The parameters relative to the base image have the same synopsis as described in <xref linkend='ssec-pkgs-dockerTools-buildImage'/>, except that <varname>fromImage</varname> is the only required argument in this case. </para> <para> The <varname>name</varname> argument is the name of the derivation output, which defaults to <varname>fromImage.name</varname>. </para> </section> <section xml:id="ssec-pkgs-dockerTools-shadowSetup"> <title>shadowSetup</title> <para> This constant string is a helper for setting up the base files for managing users and groups, only if such files don't exist already. It is suitable for being used in a <varname>runAsRoot</varname> <xref linkend='ex-dockerTools-buildImage-runAsRoot'/> script for cases like in the example below: </para> <example xml:id='ex-dockerTools-shadowSetup'> <title>Shadow base files</title> <programlisting> buildImage { name = "shadow-basic"; runAsRoot = '' #!${pkgs.runtimeShell} ${shadowSetup} groupadd -r redis useradd -r -g redis redis mkdir /data chown redis:redis /data ''; } </programlisting> </example> <para> Creating base files like <literal>/etc/passwd</literal> or <literal>/etc/login.defs</literal> is necessary for shadow-utils to manipulate users and groups. </para> </section> </section> </del>

This issue tracks the conversion of from Docbook to CommonMark per . If you intend to work on this conversion, please comment below! here that you intend to work on it. (Please also post if you stop working on it.) a new branch of nixpkgs master. : change to . to . the contents from Docbook to . Follow . Use existing sections for inspiration. from the folder to build the manual. the manual on your computer at after running from folder: it looks good, submit a PR and reference this issue.
Hi I'd like to work in this issue. First one with documentation so I will probably need to understand a few things first.
Thanks, let us know if you need help!
Hi thanks for picking this up. Are you still working on this? If you're stuck, you could create a draft PR so someone can help, or if you've changed your mind that's also ok.
Hi Sorry for late reply. I worked a little bit, on and off during the holidays, I do not finished yet, I had some problems during the build of the documentation, but from what I read (pandoc output) I made some mistakes during the file conversion. For now, I didn't commit, It's on my personal computer only. As the week is a little difficult, I'll see if I finish it at the weekend. (Maybe I should have asked for this issue just now, just see 14 days ago and I was like "What ?! That was 2 weeks ago ?!" LOL) Thanks for asking!
Hi I followed your suggestion to create a draft PR, at the moment I'm stuck in two things, the first is how to create a note and the second reference errors during the build of the documentation. For the first, pandoc created notes with the following formats: , in this case I should use the default way to create notes in markdown (using ) or wrap this in docbook way? If I remove the references that generate the error below, I can verify that using the markdown format, this note is styled differently from the rest of the documentation. And for the build errors, here is log: For this I tried per but build fails with same error. Any help is appreciated.


Question: , xkeyboard_config , glib , libarchive <ins> , libxcrypt </ins> , python2 }:

it does not start anymore Steps to reproduce the behavior: davinci-resolve davinci-resolve Working Program. Installed from unstable 22.11pre420742.. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:


Question: }@attrs: let allIdrisDeps = idrisDeps <del> ++ lib.optional (!noPrelude) idrisPackages.prelude ++ lib.optional (!noBase) idrisPackages.base; idris-with-packages = idrisPackages.with-packages allIdrisDeps; </del> <ins> ++ lib.optional (!noPrelude) prelude ++ lib.optional (!noBase) base; idris-with-packages = with-packages allIdrisDeps; </ins> newAttrs = builtins.removeAttrs attrs [ "idrisDeps" "noPrelude" "noBase" "name" "version" "ipkgName" "extraBuildInputs" ] // { meta = attrs.meta // { <del> platforms = attrs.meta.platforms or idrisPackages.idris.meta.platforms; </del> <ins> platforms = attrs.meta.platforms or idris.meta.platforms; </ins> }; }; in

Overriding idris-no-deps in nixpkgs results in a mismatch between versions of builtin packages and the compiler. With this derivation: I would expect to end up overriding the version of idris-no-deps in idrisPackages would change the derivations of builtin packages to be built with the supplied version of Idris. However, instead they are built with the Idris from the channel used. Leading to this error at build time (for Idris2): By examining the final result of the build I can see 2 versions of idris being used: Please run and paste the results.
Thought I might be able to solve this issue by specifying overrides as well. But no luck This is what the derivation for base looks like Specifically: Which contains the wrong version of Idris.
Same issue with non builtin packages as well. Also perhaps this is a better demonstration of the build time dependencies:
Thanks for the report, above PR should fix it, let me know if it works for you, then I'll merge it :)
Well actually I know it will work, but still. As a workaround if you don't want to change nixpkgs, an overlay should give no problems too:
Brilliant! Yes it's working for me and I'm now able to build Idris 2. Thank you very much!


Question: <ins> { lib , stdenv , fetchFromGitHub , buildPythonPackage , unittestCheckHook , daqp , ecos , numpy , osqp , scipy , scs , quadprog }: buildPythonPackage rec { pname = "qpsolvers"; version = "3.4.0"; format = "flit"; src = fetchFromGitHub { owner = "qpsolvers"; repo = "qpsolvers"; rev = "v${version}"; hash = "sha256-GrYAhTWABBvU6rGoHi00jBa7ryjCNgzO/hQBTdSW9cg="; }; pythonImportsCheck = [ "qpsolvers" ]; propagatedBuildInputs = [ daqp ecos numpy osqp scipy scs ]; nativeCheckInputs = [ quadprog unittestCheckHook ]; meta = with lib; { description = "Quadratic programming solvers in Python with a unified API"; homepage = "https://github.com/qpsolvers/qpsolvers"; license = licenses.lgpl3Plus; maintainers = with maintainers; [ renesat ]; }; } </ins>

Project description qpsolvers is python library for solving quadratic programming problems. It contains wrappers for multiple solvers like osqp, cvxopt, quadprog and much more. Metadata homepage URL: source URL: license: LGPLv3 platforms: platform independent (python3.10)
This package wants new version of and new package - . I will try add PR today, but now you can use my NUR repo if you want:


Question: pkgconfig gobject-introspection gtk-doc docbook_xsl docbook_xml_dtd_43 ]; buildInputs = [ <del> harfbuzz fribidi </del> <ins> fribidi </ins> ] ++ optionals stdenv.isDarwin (with darwin.apple_sdk.frameworks; [ ApplicationServices Carbon CoreGraphics CoreText ]); <del> propagatedBuildInputs = [ cairo glib libintl ] ++ </del> <ins> propagatedBuildInputs = [ cairo glib libintl harfbuzz ] ++ </ins> optional x11Support libXft; <del> patches = [ (fetchpatch { # Add gobject-2 to .pc file url = "https://gitlab.gnome.org/GNOME/pango/commit/546f4c242d6f4fe312de3b7c918a848e5172e18d.patch"; sha256 = "1cqhy4xbwx3ad7z5d1ks7smf038b9as8c6qy84rml44h0fgiq4m2"; }) ]; </del> mesonFlags = [ <del> "-Denable_docs=${if stdenv.isDarwin then "false" else "true"}" </del> <ins> "-Dgtk_doc=${if stdenv.isDarwin then "false" else "true"}" </ins> ]; enableParallelBuilding = true;

, (nixos-19.09) Scanned versions: nixos-19.09: . May contain false positives.
This is now fixed for 1.43 on master and 19.09:
Thanks :heart:


Question: <ins> From 30534f48c6ede142dad0008d1641392d82b8a137 Mon Sep 17 00:00:00 2001 From: Liu Hao <lh_mouse@126.com> Date: Mon, 18 Apr 2016 11:50:55 +0800 Subject: [PATCH] Added 'mcf' thread model support from mcfgthread. Signed-off-by: Liu Hao <lh_mouse@126.com> --- config/gthr.m4                          |  1 + gcc/config.gcc                          |  3 +++ gcc/config/i386/mingw-mcfgthread.h      |  1 + gcc/config/i386/mingw-w64.h             |  2 +- gcc/config/i386/mingw32.h               | 11 ++++++++++- gcc/configure                           |  2 +- gcc/configure.ac                        |  2 +- libatomic/configure.tgt                 |  2 +- libgcc/config.host                      |  6 ++++++ libgcc/config/i386/gthr-mcf.h           |  1 + libgcc/config/i386/t-mingw-mcfgthread   |  2 ++ libgcc/configure                        |  1 + libstdc++-v3/configure                  |  1 + libstdc++-v3/libsupc++/atexit_thread.cc | 18 ++++++++++++++++++ libstdc++-v3/libsupc++/guard.cc         | 23 +++++++++++++++++++++++ 15 files changed, 71 insertions(+), 5 deletions(-) create mode 100644 gcc/config/i386/mingw-mcfgthread.h create mode 100644 libgcc/config/i386/gthr-mcf.h create mode 100644 libgcc/config/i386/t-mingw-mcfgthread diff --git a/config/gthr.m4 b/config/gthr.m4 index 7b29f1f3327..82e21fe1709 100644 --- a/config/gthr.m4 +++ b/config/gthr.m4 @@ -21,6 +21,7 @@ case $1 in tpf)	thread_header=config/s390/gthr-tpf.h ;; vxworks)	thread_header=config/gthr-vxworks.h ;; win32)	thread_header=config/i386/gthr-win32.h ;; +    mcf)	thread_header=config/i386/gthr-mcf.h ;; esac AC_SUBST(thread_header) ]) diff --git a/gcc/config.gcc b/gcc/config.gcc index 858b878d4b3..6f745790d64 100644 --- a/gcc/config.gcc +++ b/gcc/config.gcc @@ -1722,6 +1722,9 @@ i[34567]86-*-mingw* | x86_64-*-mingw*) if test x$enable_threads = xposix ; then tm_file="${tm_file} i386/mingw-pthread.h" fi +	if test x$enable_threads = xmcf ; then +		tm_file="${tm_file} i386/mingw-mcfgthread.h" +	fi tm_file="${tm_file} i386/mingw32.h" # This makes the logic if mingw's or the w64 feature set has to be used case ${target} in diff --git a/gcc/config/i386/mingw-mcfgthread.h b/gcc/config/i386/mingw-mcfgthread.h new file mode 100644 index 00000000000..ec381a7798f --- /dev/null +++ b/gcc/config/i386/mingw-mcfgthread.h @@ -0,0 +1 @@ +#define TARGET_USE_MCFGTHREAD 1 diff --git a/gcc/config/i386/mingw-w64.h b/gcc/config/i386/mingw-w64.h index fe11333a2d1..cac85802f38 100644 --- a/gcc/config/i386/mingw-w64.h +++ b/gcc/config/i386/mingw-w64.h @@ -48,7 +48,7 @@ along with GCC; see the file COPYING3.  If not see "%{mwindows:-lgdi32 -lcomdlg32} "  "%{fvtable-verify=preinit:-lvtv -lpsapi;  fvtable-verify=std:-lvtv -lpsapi} "  -		 "-ladvapi32 -lshell32 -luser32 -lkernel32" +		 LIB_MCFGTHREAD "-ladvapi32 -lshell32 -luser32 -lkernel32" #undef SPEC_32 #undef SPEC_64 diff --git a/gcc/config/i386/mingw32.h b/gcc/config/i386/mingw32.h index e04818966fa..7b75a372506 100644 --- a/gcc/config/i386/mingw32.h +++ b/gcc/config/i386/mingw32.h @@ -32,6 +32,14 @@ along with GCC; see the file COPYING3.  If not see | MASK_STACK_PROBE | MASK_ALIGN_DOUBLE  | MASK_MS_BITFIELD_LAYOUT) +#ifndef TARGET_USE_MCFGTHREAD +#define CPP_MCFGTHREAD()  ((void)0) +#define LIB_MCFGTHREAD     "" +#else +#define CPP_MCFGTHREAD()  (builtin_define("__USING_MCFGTHREAD__")) +#define LIB_MCFGTHREAD     " -lmcfgthread " +#endif + /* See i386/crtdll.h for an alternative definition. _INTEGRAL_MAX_BITS is for compatibility with native compiler.  */ #define EXTRA_OS_CPP_BUILTINS()					 @@ -50,6 +58,7 @@ along with GCC; see the file COPYING3.  If not see builtin_define_std ("WIN64");				 builtin_define ("_WIN64");				 }							 +	CPP_MCFGTHREAD();	 }								 while (0) @@ -93,7 +102,7 @@ along with GCC; see the file COPYING3.  If not see "%{mwindows:-lgdi32 -lcomdlg32} "  "%{fvtable-verify=preinit:-lvtv -lpsapi;  fvtable-verify=std:-lvtv -lpsapi} "  -                 "-ladvapi32 -lshell32 -luser32 -lkernel32" +                 LIB_MCFGTHREAD "-ladvapi32 -lshell32 -luser32 -lkernel32" /* Weak symbols do not get resolved if using a Windows dll import lib. Make the unwind registration references strong undefs.  */ diff --git a/gcc/configure b/gcc/configure index 954673c1c43..6b5667f1c70 100755 --- a/gcc/configure +++ b/gcc/configure @@ -11702,7 +11702,7 @@ case ${enable_threads} in target_thread_file='single' ;; aix | dce | lynx | mipssde | posix | rtems |  -  single | tpf | vxworks | win32) +  single | tpf | vxworks | win32 | mcf) target_thread_file=${enable_threads} ;; *) diff --git a/gcc/configure.ac b/gcc/configure.ac index 4c65d441e72..e6fa04ada4f 100644 --- a/gcc/configure.ac +++ b/gcc/configure.ac @@ -1593,7 +1593,7 @@ case ${enable_threads} in target_thread_file='single' ;; aix | dce | lynx | mipssde | posix | rtems |  -  single | tpf | vxworks | win32) +  single | tpf | vxworks | win32 | mcf) target_thread_file=${enable_threads} ;; *) diff --git a/libatomic/configure.tgt b/libatomic/configure.tgt index eab2765d7fd..f4058b6f4a2 100644 --- a/libatomic/configure.tgt +++ b/libatomic/configure.tgt @@ -124,7 +124,7 @@ case "${target}" in *-*-mingw*) # OS support for atomic primitives. case ${target_thread_file} in -          win32) +          win32 | mcf) config_path="${config_path} mingw" ;; posix) diff --git a/libgcc/config.host b/libgcc/config.host index 2b139b8befc..fb18d2a042e 100644 --- a/libgcc/config.host +++ b/libgcc/config.host @@ -712,6 +712,9 @@ i[34567]86-*-mingw*) posix) tmake_file="i386/t-mingw-pthread $tmake_file" ;; +	  mcf) +	    tmake_file="i386/t-mingw-mcfgthread $tmake_file" +	    ;; esac # This has to match the logic for DWARF2_UNWIND_INFO in gcc/config/i386/cygming.h if test x$ac_cv_sjlj_exceptions = xyes; then @@ -736,6 +739,9 @@ x86_64-*-mingw*) posix) tmake_file="i386/t-mingw-pthread $tmake_file" ;; +	  mcf) +	    tmake_file="i386/t-mingw-mcfgthread $tmake_file" +	    ;; esac # This has to match the logic for DWARF2_UNWIND_INFO in gcc/config/i386/cygming.h if test x$ac_cv_sjlj_exceptions = xyes; then diff --git a/libgcc/config/i386/gthr-mcf.h b/libgcc/config/i386/gthr-mcf.h new file mode 100644 index 00000000000..5ea2908361f --- /dev/null +++ b/libgcc/config/i386/gthr-mcf.h @@ -0,0 +1 @@ +#include <mcfgthread/gthread.h> diff --git a/libgcc/config/i386/t-mingw-mcfgthread b/libgcc/config/i386/t-mingw-mcfgthread new file mode 100644 index 00000000000..4b9b10e32d6 --- /dev/null +++ b/libgcc/config/i386/t-mingw-mcfgthread @@ -0,0 +1,2 @@ +SHLIB_PTHREAD_CFLAG = +SHLIB_PTHREAD_LDFLAG = -lmcfgthread diff --git a/libgcc/configure b/libgcc/configure index e7d6c75a6f7..664d0f852c4 100644 --- a/libgcc/configure +++ b/libgcc/configure @@ -5077,6 +5077,7 @@ case $target_thread_file in tpf)	thread_header=config/s390/gthr-tpf.h ;; vxworks)	thread_header=config/gthr-vxworks.h ;; win32)	thread_header=config/i386/gthr-win32.h ;; +    mcf)	thread_header=config/i386/gthr-mcf.h ;; esac diff --git a/libstdc++-v3/configure b/libstdc++-v3/configure index b5ae4213f94..c484d3aee5f 100755 --- a/libstdc++-v3/configure +++ b/libstdc++-v3/configure @@ -15177,6 +15177,7 @@ case $target_thread_file in tpf)	thread_header=config/s390/gthr-tpf.h ;; vxworks)	thread_header=config/gthr-vxworks.h ;; win32)	thread_header=config/i386/gthr-win32.h ;; +    mcf)	thread_header=config/i386/gthr-mcf.h ;; esac diff --git a/libstdc++-v3/libsupc++/atexit_thread.cc b/libstdc++-v3/libsupc++/atexit_thread.cc index e6520c1094f..3d6907796dd 100644 --- a/libstdc++-v3/libsupc++/atexit_thread.cc +++ b/libstdc++-v3/libsupc++/atexit_thread.cc @@ -25,6 +25,22 @@ #include <cstdlib> #include <new> #include "bits/gthr.h" + +#ifdef __USING_MCFGTHREAD__ + +#include <mcfgthread/gthread.h> + +extern "C" int +__cxxabiv1::__cxa_thread_atexit (void (*dtor)(void *), +				 void *obj, void *dso_handle) +  _GLIBCXX_NOTHROW +{ +  return ::_MCFCRT_AtThreadExit((void (*)(_MCFCRT_STD intptr_t))dtor, (_MCFCRT_STD intptr_t)obj) ? 0 : -1; +  (void)dso_handle; +} + +#else // __USING_MCFGTHREAD__ + #ifdef _GLIBCXX_THREAD_ATEXIT_WIN32 #define WIN32_LEAN_AND_MEAN #include <windows.h> @@ -163,3 +179,5 @@ __cxxabiv1::__cxa_thread_atexit (void (*dtor)(void *), void *obj, void */*dso_ha } #endif /* _GLIBCXX_HAVE___CXA_THREAD_ATEXIT_IMPL */ + +#endif // __USING_MCFGTHREAD__ diff --git a/libstdc++-v3/libsupc++/guard.cc b/libstdc++-v3/libsupc++/guard.cc index 9b617998ffe..a441fdbb616 100644 --- a/libstdc++-v3/libsupc++/guard.cc +++ b/libstdc++-v3/libsupc++/guard.cc @@ -28,6 +28,27 @@ #include <cxxabi.h> #include <exception> #include <new> + +#ifdef __USING_MCFGTHREAD__ + +#include <mcfgthread/gthread.h> + +namespace __cxxabiv1 { + +extern "C" int __cxa_guard_acquire(__guard *g){ +	return ::_MCFCRT_WaitForOnceFlagForever((::_MCFCRT_OnceFlag *)g) == ::_MCFCRT_kOnceResultInitial; +} +extern "C" void __cxa_guard_abort(__guard *g) throw() { +	::_MCFCRT_SignalOnceFlagAsAborted((::_MCFCRT_OnceFlag *)g); +} +extern "C" void __cxa_guard_release(__guard *g) throw() { +	::_MCFCRT_SignalOnceFlagAsFinished((::_MCFCRT_OnceFlag *)g); +} + +} + +#else // __USING_MCFGTHREAD__ + #include <ext/atomicity.h> #include <ext/concurrence.h> #if defined(__GTHREADS) && defined(__GTHREAD_HAS_COND)  @@ -424,3 +445,5 @@ namespace __cxxabiv1 #endif } } + +#endif -- 2.12.1 </ins>

Describe the bug is when building for MinGW, however an equivalent GCC 10 patch file doesn't exist. I tried looking for a GCC 10 patch on the master branch of , but the folder that contained the patches no longer exists. GCC9 is still currently the default on master, but this will break everything under MinGW the next time staging-next is merged to master. See Support for was originally in To Reproduce Steps to reproduce the behavior: Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(kira): nixpkgs: Maintainer information:
It has been moved to to upstream migration. Neither of these repos is stable; their master branches are constantly rebased on upstream and force-pushed.


Question: Rglpk = [ pkgs.glpk ]; RGtk2 = [ pkgs.gtk2.dev ]; rhdf5 = [ pkgs.zlib ]; <del> Rhdf5lib = [ pkgs.zlib ]; </del> <ins> Rhdf5lib = [ pkgs.zlib.dev ]; </ins> Rhpc = [ pkgs.zlib pkgs.bzip2.dev pkgs.icu pkgs.xz.dev pkgs.mpi pkgs.pcre.dev ]; Rhtslib = [ pkgs.zlib.dev pkgs.automake pkgs.autoconf pkgs.bzip2.dev pkgs.xz.dev pkgs.curl.dev ]; rjags = [ pkgs.jags ];

Describe the bug The rhdf5 library does not work on latest release. To Reproduce Expected behavior A shell with R and rhdf5. Additional context Instead I get: Notify maintainers Metadata Maintainer information:
"6.topic: rust" should be removed, this is an R package, not Rust.
This was fixed in


Question: ++ optionals withDBengine [ libuv lz4.dev judy ] ++ optionals withIpmi [ freeipmi ] ++ optionals withNetfilter [ libmnl libnetfilter_acct ] <ins> ++ optionals withCloud [ json_c ] </ins> ++ optionals withSsl [ openssl.dev ]; patches = [ # required to prevent plugins from relying on /etc # and /var ./no-files-in-etc-and-var.patch <del> # cgroups: fix network interfaces detection when using virsh (fetchpatch { url = "https://patch-diff.githubusercontent.com/raw/netdata/netdata/pull/11096.patch"; sha256 = "0f2rd7kgbwbyq9wyn085d213ifvivnpl3qlx1gjrg42rkbi4n8jj"; }) </del> ]; NIX_CFLAGS_COMPILE = optionalString withDebug "-O1 -ggdb -DNETDATA_INTERNAL_CHECKS=1";

Project description Netdata agent plugin Metadata homepage URL: source URL: license: GPL 3.0 platforms: unix, linux, darwin We already do have netdata, however it seems to be built without support for the cloud agent that allows it to stream to the cloud or other netdata servers.
I have a local checkout with some edits that allow me to build netdata with cloud support. Unfortunately they also require a change in the libwebsockets build expression. Should I open a PR to integrate my changes into nixpkgs?
A PR would be great! I'm not a maintainer, but if they decide it's out of scope for nixpkgs, perhaps one on NUR might work - I'd try for a PR here first though
Great, I think having a configuration option that is per default would make sense. Maybe ?
Yeah, that seems to fall in line with the various flags present in other packages
I marked this as stale due to inactivity. →
Upstream has incorporated some of the suggestions in this thread, I intend to pick up on it again soon
what would be needed to make this work? Perhaps I can help?
The newest major release of Netdata (1.30.0) includes a cloud link implementation without the need for vendored dependencies. Unfortunately, it is not currently in a reliable state because of a bug in the custom HTTPS implementation. The has already been merged into Netdata master and will be included in the next release. I plan to make a PR that enables cloud support as soon as that release is available.
v1.31.0 dropped 12 minutes ago :) Anything I can do to help?
Thanks, I've already gotten a notification for that. Planning to make a PR when I get off work today. When my PR is done, it would be helpful if you could test my changes on your machines.
Just FYI, I have opened the PR that enables cloud support a few days ago. If you are still interested it would be greatly appreciated if you could test if everything works for you and maybe drop a comment.
Sorry, missed this but the pr looks good! I propose we backport this to stable?


Question: }; buildFHSUserEnv = args: userFHSEnv { <del> env = buildFHSEnv (removeAttrs args [ "runScript" "extraBindMounts" "extraInstallCommands" "meta" ]); </del> <ins> env = buildFHSEnv (removeAttrs args [ "runScript" "extraBindMounts" "extraInstallCommands" "meta" "passthru" ]); </ins> runScript = args.runScript or "bash"; extraBindMounts = args.extraBindMounts or []; extraInstallCommands = args.extraInstallCommands or ""; <del> importMeta = args.meta or {}; </del> <ins> meta = args.meta or {}; passthru = args.passthru or {}; </ins> }; buildMaven = callPackage ../build-support/build-maven.nix {};

This weekend I tried these games, all deadlocked in the menu or character selection. Nyheim Oh...Sir! The Insult Simulator Reigns Unturned (free to play) You don't have to be worried to waste money in case you want to test a game. I have had no problem when requesting refunds, just go to I have played these games and found no issues with them: Dota 2 Counter-Strike TIS-100 World of goo Faster Than Light You Must Build a Boat Risk of Rain System: (NixOS: , Ubuntu/Fedora: , ...) 03pre99759. (Gorilla) Nix version: (run ) nix-env (Nix) 1.11.6 Nixpkgs version: (run ) "17.03pre99759." Integrated graphics card, 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06)
This is normal with steam on nixos unfortunately. There are many steam games that don't work for various reasons, unfortunately many linux steam game developers only make sure their games run on ubuntu and don't really care about relying only on dependencies from the steam runtime. Some games don't play nice with certain graphics cards or drivers as well. If you want to get a particular game working (I can list 150 games that work under nixos with nvidia card and drivers at least) then you'll need to do some work, or at least post any relevant logs from the game/steam so people can actually help you solve the problem. That is assuming that they own the game. :)
There's a slowly-growing list of extra dependencies in the Steam package. If you can figure out what's missing, you can add it there; e.g. as in
I don't have enough motivation to actually buy games for the sole purpose of fixing them and then refunding, sorry. Nevertheless, I'm happy to help if you can post logs and/or s -- those two are the most helpful for determining FHS-related problems.


Question: sed -i '/^s*"vscode-eslint-language-server":.*bin//d' package.json package-lock.json ''; <del> buildPhase = let extensions = "${vscode}/lib/vscode/resources/app/extensions"; in '' npx babel ${extensions}/css-language-features/server/dist/* --out-dir lib/css-language-server/node/ npx babel ${extensions}/html-language-features/server/dist/* --out-dir lib/html-language-server/node/ npx babel ${extensions}/json-language-features/server/dist/* --out-dir lib/json-language-server/node/ npx babel ${extensions}/markdown-language-features/server/dist/* --out-dir lib/markdown-language-server/node/ mv lib/markdown-language-server/node/workerMain.js lib/markdown-language-server/node/main.js ''; </del> <ins> buildPhase = let extensions = if stdenv.isDarwin then "${vscode}/Applications/Visual Studio Code.app/Contents/Resources/app/extensions" else "${vscode}/lib/vscode/resources/app/extensions"; in '' npx babel ${extensions}/css-language-features/server/dist/node  --out-dir lib/css-language-server/node/ npx babel ${extensions}/html-language-features/server/dist/node  --out-dir lib/html-language-server/node/ npx babel ${extensions}/json-language-features/server/dist/node  --out-dir lib/json-language-server/node/ npx babel ${extensions}/markdown-language-features/server/dist/node  --out-dir lib/markdown-language-server/node/ mv lib/markdown-language-server/node/workerMain.js lib/markdown-language-server/node/main.js ''; </ins> meta = with lib; { description = "HTML/CSS/JSON/ESLint language servers extracted from vscode.";

Steps to reproduce the behavior: nixos-unstable to home.packages -rebuild build Please run and paste the result.


Question: mkDerivation rec { pname = "organicmaps"; <del> version = "2023.03.05-5"; </del> <ins> version = "2023.04.02-7"; </ins> src = fetchFromGitHub { owner = "organicmaps"; repo = "organicmaps"; rev = "${version}-android"; <del> sha256 = "sha256-PfudozmrL8jNS/99nxSn0B3E53W34m4/ZN0y2ucB2WI="; </del> <ins> sha256 = "sha256-xXBzHo7IOo2f1raGnpFcsvs++crHMI5SACIc345cX7g="; </ins> fetchSubmodules = true; };

Package name: organicmaps Latest released version: 2023.04.02-7Current version on the unstable channel: 2023.03.05-5 Current version on the stable/release channel: 2023.01.25-3 Notify maintainers Note for maintainers: Please tag this issue in your PR.


Question: ] ++ lib.optional (!withSvmLight) ./svmlight-scrubber.patch; nativeBuildInputs = [ cmake swig ctags ] <del> ++ (with python2Packages; [ python jinja2 ply ]); </del> <ins> ++ (with python3Packages; [ python jinja2 ply ]); </ins> buildInputs = [ eigen

Using Shogun as a for another CMake-based project fails because the dependent project cannot properly find the shogun library (via its installed cmake files). Steps to reproduce the behavior: to build a derivation based on shogun files are wrong Everything builds correctly I am trying to build the following derivation However I get an error at the build generation step: This indicates that shogun CMake files are not in the right place and/or are pointing towards the wrong paths.
I fixed the issue with shogun. When installing the configuration files, CMake calculates the prefix to the installed library based on the output directory, instead of the default , and I missed it when I split the derivation into multiple outputs. I wonder why it's not a more widespread issue, only a few derivations patch it. But that derivation still doesn't build: This is in macOS, though. Maybe it works on Linux.
Thanks, is the fix committed yet? The other error is unrelated and I can fix it.
I'm working on the PR.


Question: start_all() server.wait_for_unit("mosquitto.service") <ins> with subtest("bind_interface"): addrs = dict() for iface in json.loads(server.succeed("ip -json address show")): for addr in iface['addr_info']: # don't want to deal with multihoming here assert addr['local'] not in addrs addrs[addr['local']] = (iface['ifname'], addr['family']) # mosquitto grabs *one* random address per type for bind_interface (has4, has6) = (False, False) for line in server.succeed("ss -HlptnO sport = ${toString bindTestPort}").splitlines(): items = line.split() if "mosquitto" not in items[5]: continue listener = items[3].rsplit(':', maxsplit=1)[0].strip('[]') assert listener in addrs assert addrs[listener][0] == "eth0" has4 |= addrs[listener][1] == 'inet' has6 |= addrs[listener][1] == 'inet6' assert has4 assert has6 </ins> with subtest("check passwords"): client1.succeed(publish("-m test", "password_store")) client1.succeed(publish("-m test", "password_file"))

lists a listener option called that can be used to listen for incoming network connections only on the specified interface. Unfortunately does not accept this option. Steps to reproduce the behavior: This should evaluate cleanly. Incidentally, that assertion message drops the component in the attribute path, it might be nice to fix that.


Question: ''; }; }; <del> }; </del> <ins> }).overrideAttrs (_: { # Add extra deps needed for postBuild hook. nativeBuildInputs = [ makeWrapper lua ]; }); </ins> in env

Describe the bug Building neovim doesn't work anymore. To Reproduce Checkout master branch, commit (latest as of now), then build: Expected behavior Building neovim should succeed.
The failing code is (...-stdenv-linux/setup: line 320):
Having the same issue when updating my system.
Ping I think this has something to do with the recent stdenv changes. Do you know how to fix it?
This is from which breaks this manual sourcing of setup hooks I say this is a good thing! We should make those proper dependencies. I will fix shortly.
I have a similar issue in stdenv-linux/setup /nix/store/fiaj00zrmb7dynd2q9xmcrh5rn0mjwj0-stdenv-linux/setup: line 97: $'r': command not found builder for '/nix/store/frqmqjyg649bkqivqhzq041fxbfvsikw-cockpit-' failed with exit code 127
Thanks!


Question: os.setuid(uid) <ins> def run_as_taskd_group(): gid = grp.getgrnam(TASKD_GROUP).gr_gid os.setgid(gid) </ins> def taskd_cmd(cmd, *args, **kwargs): """ Invoke taskd with the specified command with the privileges of the 'taskd'

So I today I spawned a machine with and satisfyingly the directory was generated with all of the certificates etc that taskwarrior needs, including the clients' certificates. I noticed that the users' keys located at are owned by root with read only permissions for the root user alone. No matter what are and . I'd like to enable the group read those client keys, as well as the file so that I can configure a client easily. Thankfully the group can read the file, but not the client keys. The manual indeed explains that the command: Could be used to get those keys, but I'd like to use syncthing for that to automate the process even further. I got a bit lost while reading the . Specifically, I'm not sure why does always works in the following umask: I mean, ~why not~ - a solution is suggested in . A word of comment will be appreciated. cc .


Question: , glib , gnome2 , gtk3 <ins> , libGL </ins> , libappindicator-gtk3 , libdrm , libnotify

Describe the bug Starting slack doesn't show the window in 8 out of 10 runs To Reproduce Steps to reproduce the behavior: Expected behavior Slack window should open Screenshots If applicable, add screenshots to help explain your problem. Additional context Add any other context about the problem here. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Metadata system: host os: multi-user?: sandbox: version: channels(ymatsiuk): channels(root): nixpkgs: Maintainer information:


Question: , systemd , taglib , unzip <del> , wayland , wayland-protocols </del> , xorg , zlib , chromecastSupport ? true, libmicrodns, protobuf , jackSupport ? false , onlyLibVLC ? false , skins2Support ? !onlyLibVLC, freetype <del> , withQt5 ? true, qtbase, qtsvg, qtx11extras, wrapQtAppsHook </del> <ins> , waylandSupport ? true, wayland, wayland-protocols , withQt5 ? true, qtbase, qtsvg, qtwayland, qtx11extras, wrapQtAppsHook </ins> }: # chromecastSupport requires TCP port 8010 to be open for it to work.

Packaged VLC does not seem to support wayland. Steps to reproduce the behavior: vlc with on e.g. sway opens as a XWayland window VLC opens as a Wayland native window Not applicable Possibly related to VLC not depending on qtwayland. Please run and paste the result. EDIT: Typo
It is strange. I built it and verified, it is not linked with QT libraries even if they are put as inputs.
Is also pulled in as an input?
Nope. Working on it now. First encounter: Wayland is considered experimental and disabled by default.
Can you test the patch?
Works like a charm, thanks a lot! :)
I'm on NixOS 23.05 and discovered that vlc prefers to use XWayland if var is set. If I unset then vlc starts in Wayland mode. Does anyone know how to make it to start on Wayland by default?
For now I hacked it with: Special thanks to
Well, if this is hardcoded on VLC, there is nothing to do (besides maybe searching some hidden commandline flag).
The "use QTQPAPLATFORM be damned" behavior is apparently just what QT does, and is not specific to VLC
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Here is the updated wrap that also addresses the desktop file


Question: cabextract --lowercase viewer1.cab # rename to more standard names <ins> # handle broken macOS file-system </ins> mv andalemo.ttf  Andale_Mono.ttf mv ariblk.ttf    Arial_Black.ttf <del> mv arial.ttf     Arial.ttf </del> <ins> mv arial.ttf     Arial.ttf.tmp mv Arial.ttf.tmp Arial.ttf </ins> mv arialbd.ttf   Arial_Bold.ttf mv arialbi.ttf   Arial_Bold_Italic.ttf mv ariali.ttf    Arial_Italic.ttf

Steps to reproduce the behavior: macOS: Since , this fails on macOS due to case-insensitivity (). The offending PR had no description, no reviews and no reports of tests on any platform. It was merged by the author four days after it was opened. Please run and paste the result.
Fuck MacOS and their stupid case insensitive file system.
Can you try mv'ing the file first to another name like?


Question: }; desktopItem = makeDesktopItem { <del> name = drvName; </del> <ins> name = pname; </ins> exec = pname; <del> icon = drvName; </del> <ins> icon = pname; </ins> desktopName = "Android Studio (${channel} channel)"; comment = "The official Android IDE"; categories = [ "Development" "IDE" ];

I'm using NixOS "/ on tmpfs" mode, so I persist my dconf by using a module of home-manager. When I persist the state of GNOME app drawer, I need to write down desktop file name to .nix config. But currently, Android Studio's desktop contains a string of version, this because contains . Details: I also notice used in icon too, which will cause icon file contains version string, I think we can remove them too. If maintainer agrees, I will make a PR to deal with this. Also, I noticed another maintainer deleted the account: Maybe I can send him / her an E-mail for asking what happened, and drop the maintainer info.


Question: dictu = callPackage ../development/compilers/dictu { }; <del> dotty = callPackage ../development/compilers/scala/dotty.nix { }; </del> ecl = callPackage ../development/compilers/ecl { }; ecl_16_1_2 = callPackage ../development/compilers/ecl/16.1.2.nix { };

Project description Scala 3 is more than a year old. It would be nice to have it packaged in nixpkgs as well. Maybe it is, but I couldn't find it under "scala-3" or respective versions. Metadata homepage URL: https://scala- source URL: license: Apache-2.0 License platforms: unix, linux, darwin, ...
is already packaged.
Indeed: the Scala 3 compiler started out under the codename 'dotty', and that's how it was packaged initially in nixpkgs. Now that dotty has become the 'official' scala 3 compiler (see also ), we should probably rename the package to as well? /cc
Feel free to update, rename and alias the old name :) Maybe should point at and can be


Question: (mkFlag mmsSupport "mms") (mkFlag mpg123Support "mpg123") (mkFlag aacSupport "aac") <del> (mkFlag pulseaudioSupport "pulse") (mkFlag jackSupport "jack") </del> <ins> (mkFlag (!stdenv.isDarwin && pulseaudioSupport) "pulse") (mkFlag (!stdenv.isDarwin && jackSupport) "jack") </ins> (mkFlag stdenv.isDarwin "osx") (mkFlag icuSupport "icu") (mkFlag gmeSupport "gme")

nix fails to build libjack2 and libpulseaudio on darwin too (probably another two issues should be filed?). mpd build log is the third one. After disabling libjack2: After disabling libpulseaudio: I'm no expert in c++ but quick googling shows that exceptions are disabled by default when building with xcode toolchain. On a side note, which way is proper to manage ? I'm editing expression in but not sure if that is the right way. I'm using OS X 10.10.4, nix-env 1.9, nixpkgs from master HEAD.
Compilation fails on throw from boost library and mpd sources are compiling with , so I've to mpd expression but still no luck here.
Seems like this didn't get resolved and it's been a while... I have mpd failing to build on Darwin also, but with a different error, CoreAudio related. I'm using a local nixpkgs checked out at , OS X 10.11.3. Here's the failure:


Question: <ins> { lib , buildPythonPackage , pytestCheckHook , fetchFromGitHub , python , pythonOlder , setuptools , setuptools-scm , numpy , wheel , hypothesis , pytest-cov }: buildPythonPackage rec { pname = "fast-histogram"; version = "0.12"; disabled = pythonOlder "3.6"; src = fetchFromGitHub { owner = "astrofrog"; repo = pname; rev = "v${version}"; sha256 = "sha256-Cz4BgbtxbUPxL2NSzvZYjbYIN4KUuliUV0bXRRtyvfM="; }; nativeBuildInputs = [ setuptools setuptools-scm wheel ]; propagatedBuildInputs = [ numpy ]; nativeCheckInputs = [ pytestCheckHook hypothesis pytest-cov ]; pytestFlagsArray = [ "${builtins.placeholder "out"}/${python.sitePackages}" ]; env.SETUPTOOLS_SCM_PRETEND_VERSION = version; pythonImportsCheck = [ "fast_histogram" ]; meta = with lib; { homepage = "https://github.com/astrofrog/fast-histogram"; description = "Fast 1D and 2D histogram functions in Python"; license = licenses.bsd2; maintainers = with maintainers; [ ifurther ]; }; } </ins>

Project description Glue is a python project to link visualizations of scientific datasets across many files. Click on the image for a quick demo: ! Metadata homepage URL: source URL: license: BSD Linux, BSD


Question: systemd-journal2gelf = callPackage ../tools/system/systemd-journal2gelf { }; <del> tailscale = callPackage ../servers/tailscale { }; </del> <ins> tailscale = callPackage ../servers/tailscale { buildGoModule = buildGo121Module; }; </ins> tailscale-systray = callPackage ../applications/misc/tailscale-systray { };

Package name: Latest released version: <!-- Search your package here: --- Current version on the unstable channel: Current version on the stable/release channel: <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR.
You don't need to open an issue if you're going to make a PR right after.
Apologies, my bad. I was not aware :(. I am only 1 day & 1 PR old here.


Question: mkdir -p $out/libexec/conkeror cp -r * $out/libexec/conkeror <del> makeWrapper ${firefox-esr}/bin/firefox $out/bin/conkeror  </del> <ins> makeWrapper ${firefox-esr-52}/bin/firefox $out/bin/conkeror  </ins> --add-flags "-app $out/libexec/conkeror/application.ini" '';

On running I get: Add to and run. system: host os: multi-user?: sandbox: version: channels(lev): channels(root): nixpkgs:
Well, the output has at least changed a bit:
my pull request fixes the . It broke down because the package had moved to but requires . But according to the browser is discontinued and `firefox-esr-5.2' is marked as unsecure so I would rather advocate for removing this package altogether.


Question: set -euo pipefail STATE_DIRECTORY="$1" <del> RUNTIME_DIRECTORY="$2" </del> <ins> WORK_DIRECTORY="$2" </ins> LOGS_DIRECTORY="$3" ${lines} ''; <del> runnerRegistrationConfig = getAttrs [ "name" "tokenFile" "url" "runnerGroup" "extraLabels" "ephemeral" ] cfg; </del> <ins> runnerRegistrationConfig = getAttrs [ "name" "tokenFile" "url" "runnerGroup" "extraLabels" "ephemeral" "workDir" ] cfg; </ins> newConfigPath = builtins.toFile "${svcName}-config.json" (builtins.toJSON runnerRegistrationConfig); currentConfigPath = "$STATE_DIRECTORY/.nixos-current-config.json"; newConfigTokenPath= "$STATE_DIRECTORY/.new-token";

Working with large repositories on low-memory systems (such as aarch64-linux SBCs) can lead to out-of-storage scenarios with the github-runner service because the working directory is set to by default , which is sized to 25% of the system memory by default . Ideally there can be an option to use storage instead of memory for the working directory. I'm opening an issue first because I am not sure if there is a way to work around this already; can the argument in the service be overridden, or is there another way to change for this service with a systemd setting? If there isn't a straightforward solution I can open a PR to add this as an option. Maintainers:
I also experienced issues with no space left on . So far, however, increasing its size did the job. Nevertheless, I'd also appreciate the option to use another filesystem for the runtime directory. We won't be able to use systemd for that as it demands a -like filesystem for the runtime directory.
I guess standard installs avoid this by using the directory. Maybe we should just document how increase size instead of adding another option?
You may pass an arbitrary path to the options of the configuration script. Our module currently always uses the runtime directory systemd assigns to the service.
Yeah, in our case using the runtime directory that provides makes the most sense for dynamic user, again, with documentation on how to increase the size of the runtime directory. Currently our module doesn't support static users so isn't very useful... though I'm guessing our lack of support for static users is an oversight - see details here:


Question: ]; }; <del> linux_5_8 = callPackage ../os-specific/linux/kernel/linux-5.8.nix { kernelPatches = [ kernelPatches.bridge_stp_helper kernelPatches.request_key_helper kernelPatches.export_kernel_fpu_functions."5.3" ]; }; </del> linux_testing = callPackage ../os-specific/linux/kernel/linux-testing.nix { kernelPatches = [ kernelPatches.bridge_stp_helper

Describe the bug The is failing. I bisected this problem to “linux: Init 5.8”. The error message matches , which points to both a workaround of recompiling systemd against Linux 5.8 headers, and an upstream systemd patch (systemd/systemd) that’s in systemd 246 () and was backported in 245.7 as systemd/systemd-stable To Reproduce Steps to reproduce the behavior: Notify maintainers Cc Metadata Please run and paste the result. Maintainer information:
My PR wasn't merged, Linux 5.8 ended up being by someone else.
Linking for visibility: that PR was
The PR bumping systemd to 245.7 is at
Is it really helpful to send systemd 245.7 to given that will be unable to advance without it? Or are you thinking we also want to revert the bump in for now?
Maybe we should revert in master, and re-revert it in staging again. I let and decide about this, they've been doing the staging rounds.
Hey all, question: How do you spot which tests block the channels? I always track and every few days I notice nixos-unstable doesn't progress. When it don't I see an issue with the "channel blocker" label and I always wonder..
Click on the “Hydra job for tests” link and go to the “Constituents” tab.


Question: qt6.qthttpserver qt6.qtwebengine qt6.qt5compat <ins> qt6.qttools </ins> shaderc vulkan-headers wayland

Package name: gpt4all Latest released version: 3.2.1 <!-- Search your package here: --- Current version on the unstable channel: 2.8.0 Current version on the stable/release channel: 2.7.5 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Hi, I don't maintain GPT4All any longer, I switched to some other technologies (Open-WebUI).
haha, maybe i'll give that one a try then :) ty for all your hard work


Question: }; passwordFile = mkOption { type = types.str; <del> description = lib.mdDoc "Password file for the postgresql connection. Must be readable by user `nginx`. Ignored if `database.host` is set to `localhost`, as peer authentication will be used."; </del> <ins> description = lib.mdDoc '' Password file for the postgresql connection. Must be formated according to PostgreSQL .pgpass standard (see https://www.postgresql.org/docs/current/libpq-pgpass.html) but only one line, no comments and readable by user `nginx`. Ignored if `database.host` is set to `localhost`, as peer authentication will be used. ''; </ins> }; dbname = mkOption { type = types.str;

I tried to install Roundcube with an non-local PostgreSQL. The DB user password should be stored in a password file. I ran into problems with this setup: the password file is used in two locations: the Roundcube the systemd that initializes the roundcube database Unfortunately the neccessary file content differs for these two services: the roundcube the passwordfile should only contain the PASSWORD (even without a trailing newline) expects an entry like "hostname:port:database:username:password" () So one of these two services will fail. Setup Roundcube with remote PostgreSQL server and password file for DB user password. My solution for now would be, to add a line to the roundcube Please run and paste the result. Cheers, Andreas
Your solution sounds reasonable to me, if you replace with something that takes into account escaped . Would you mind opening a PR? Tag me on it, I'll review it. As you can see the remote db feature of the module has probably never been used except by you; if you want this use case to be better maintained consider contributing a nixos test exercising it.
Fixed by


Question: }); in appimageTools.wrapAppImage { <del> inherit name; </del> <ins> inherit pname version; </ins> src = appimageContents; multiPkgs = null; # no 32bit needed

name: flexoptix-app current version: 5.11.0 desired version: 5.12.1 maintainers: Please tag this issue in your PR.


Question: tests.slim = callTest tests/slim.nix {}; tests.smokeping = callTest tests/smokeping.nix {}; tests.snapper = callTest tests/snapper.nix {}; <ins> tests.switchTest = callTest tests/switch-test.nix {}; </ins> tests.taskserver = callTest tests/taskserver.nix {}; tests.tomcat = callTest tests/tomcat.nix {}; tests.udisks2 = callTest tests/udisks2.nix {};

When executing switch-to-configuration in a pure environment it fails: I am calling switch-to-configuration via systemd-run to active a new profile using the Hail update tool. The actual executed script is as follows: Actual output: <preactivating the configuration... perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = (unset), LCALL = (unset), LANG = "enUS.UTF-8" are supported and installed on your system. perl: warning: Falling back to the standard locale ("C"). setting up /etc... perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = (unset), LCALL = (unset), LANG = "enUS.UTF-8" are supported and installed on your system. perl: warning: Falling back to the standard locale ("C"). setting up tmpfiles Too few arguments. sh: systemctl: command not found </preThe script works if I pass on the PATH and LOCALE_ARCHIVE environment variables: System: (NixOS: 17.09pre-git (Hummingbird)) Nix version: nix-env (Nix) 1.11.13 Nixpkgs version: nixos-unstable (Commit ) Sandboxing enabled: no (Related Hail issue: )


Question: owner = "mov-cli"; repo = "mov-cli"; rev = version; <del> hash = "sha256-OJhZtrSB5rjPY80GkTSU82hkcBgFYpW7Rc24BlBH7CE="; </del> <ins> hash = "sha256-Q5fzxdMEUDL1VgeTTgU76z0nksocgjyonAroP/m/Q+0="; </ins> }; propagatedBuildInputs = with python3.pkgs; [ beautifulsoup4 click colorama <ins> deprecation </ins> httpx <ins> inquirer </ins> krfzf-py lxml poetry-core pycrypto <ins> python-decouple </ins> setuptools six <ins> thefuzz </ins> tldextract <ins> toml typer unidecode (callPackage ./mov-cli-test.nix {}) ]; nativeBuildInputs = [ python3.pkgs.pythonRelaxDepsHook </ins> ]; pythonRelaxDeps = [

Package name: Latest released version: <!-- Search your package here: --- Current version on the unstable channel: Current version on the stable/release channel: <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important].
PR:


Question: + optionalString isClang '' # Escape twice: once for this script, once for the one it gets substituted into. export march=${escapeShellArg <del> (optionalString (targetPlatform ? gcc.arch && !disableMarch) </del> <ins> (optionalString (targetPlatform ? gcc.arch) </ins> (escapeShellArg "-march=${targetPlatform.gcc.arch}"))} export defaultTarget=${targetPlatform.config} substituteAll ${./add-clang-cc-cflags-before.sh} $out/nix-support/add-local-cc-cflags-before.sh

Since was merged into the master, swift cannot be built on aarch64. Steps to reproduce the behavior: reported in I'm not familiar with swift or clang, but I'm using the following overlay as a workaround until it's fixed. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
states that this only fixed the swift build but all downstream packages are still broken. re-opening.
Actually, it seems only dark-mode-notify is broken, others seem fine. Probably because it uses Cocoa or disables sandbox. I don't know for sure.
I noticed that my personal package does not build either. Maybe it's because of swift itself or swiftpm?
The above open PR seems to run into the same issue…


Question: linux_6_1_hardened = linuxKernel.kernels.linux_6_1_hardened; linuxPackages_6_5_hardened = linuxKernel.packages.linux_6_5_hardened; linux_6_5_hardened = linuxKernel.kernels.linux_6_5_hardened; <ins> linuxPackages_6_6_hardened = linuxKernel.packages.linux_6_6_hardened; linux_6_6_hardened = linuxKernel.kernels.linux_6_6_hardened; </ins> # GNU Linux-libre kernels linuxPackages-libre = linuxKernel.packages.linux_libre;

Project description Hardened patchset got released for Linux 6.6. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Hi, created the following merge request. Would appreciate a review.
will try to check that tomorrow's morning if my ibs allows me to, thanks


Question: export DATABASE_PASSWORD="$(<"${cfg.dbpassFile}")" '' + '' export DATABASE_URL="${dbUrl}" <del> ${cfg.package}/bin/notify_push --glob-config '${config.services.nextcloud.datadir}/config/config.php' </del> <ins> ${cfg.package}/bin/notify_push '${config.services.nextcloud.datadir}/config/config.php' </ins> ''; serviceConfig = { User = "nextcloud";

Enabling fails with: Steps to reproduce the behavior: and enable Nextcloud The notify_push service starts. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
Hm, I thought I had tested that. Can you test if it works if you modify the module to drop the parameters from the script where it executes ?
Doesn't work either. I don't know PHP, but it seems that is unable to parse the inline function.
Yeah, notify_push is written in rust and doesn't actually execute php to parse the config, which is why this doesn't work.
Upon further investigation, dropping only works. Dropping the whole result a failure with: It needs an option to set .
can be set like . Maybe we should transition away from putting a function into the nextcloud config and just modify the file in the setup service.
it works, but if the Redis URL has a password it ends up in the Nix store.
I have the same and I can't reproduce this issue.
do you have the line in your ? I think the reason is because I'm using an external DB and S3 storage.
If you have passwords used in the config the nixos module does inject that lookup function. In the initial PR of notifypush was already a discussion how to handle that, and there was already a suggestion to drop I dont remember why it was not done there, i basically withed to non password authentication (as everything is running on the same machine anyways, so using the socket solved the issue back then, so i forgot about it).
nope, I am using socket authentication.


Question: ./force-enable-steamvr_lh.patch ]; <ins> passthru.tests = { basic-service = nixosTests.monado; }; </ins> meta = with lib; { description = "Open source XR runtime"; homepage = "https://monado.freedesktop.org/";

The [monado] package doesn't install the udev rules generated by the [xr-hardware util] from the Monado project. Install the package and check the lack of udev rules in It was expected for the udev rules to be installted with the package. The udev rules are needed as some hmd's have some strange and specific permissions. Maybe instead of adding this to the package, monado could turn into an option like . <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]: [monado]: [xr-hardware util]:
Trying packaging the udev rules similar to how . [brscan4]:
I was working on a Monado NixOS module. Perhaps I can deal with udev rules there. See


Question: <ins> { lib , rustPlatform , fetchFromGitHub , pkg-config , openssl , vulkan-loader }: rustPlatform.buildRustPackage { pname = "hayabusa"; version = "unstable-2023-11-29"; src = fetchFromGitHub { owner = "notarin"; repo = "hayabusa"; rev = "306167c632173f6633e51c5610fe32af7718ec25"; hash = "sha256-e2zoVIhxcE9cUypi8Uzz3YZe2JvIaEVuWOGpqHVtxn8="; }; cargoHash = "sha256-aoticMTrKZkRtjVXgdiBfyXJN3YcwBpM3yt07BBd3do="; enableParallelBuilding = true; nativeBuildInputs = [ pkg-config ]; buildInputs = [ openssl vulkan-loader ]; postPatch = '' substituteInPlace src/daemon/hayabusa.service  --replace "/usr/local" "$out" ''; postInstall = '' install -Dm444 src/daemon/hayabusa.service -t $out/lib/systemd/system/ ''; meta = { description = "A swift rust fetch program"; homepage = "https://github.com/notarin/hayabusa"; license = lib.licenses.cc-by-nc-nd-40; maintainers = with lib.maintainers; [ eclairevoyant ]; mainProgram = "hayabusa"; platforms = lib.platforms.linux; }; } </ins>

Hayabusa is a swift rust fetch program. <!-- Describe the project a little: --Metadata homepage URL: source URL: license: Attribution-NonCommercial-NoDerivatives 4.0 International platforms: linux, windows Priorities Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


Question: osl = libsForQt5.callPackage ../development/compilers/osl { boost = boost179; <ins> libclang = llvmPackages_15.libclang; clang = if stdenv.cc.libcxx != null then (overrideLibcxx llvmPackages_15.stdenv).cc else clang_15; llvm = llvm_15; </ins> }; osqp = callPackage ../development/libraries/science/math/osqp { };

rendered in : ! bumping osl to did not work. Applying did not work <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --- system: host os: multi-user?: sandbox: version: nixpkgs:
I have verified that the problem exists with the current derivation even with version , which was updated away from in . I guess somehow the ZLIB_VERSION is replaced improperly , but I've got no idea what could be causing it, and I'm really confused why it's only become a problem recently, as it doesn't look like osl has been touched in either.
I've tracked it down to , and reverting it seems to fix it. I also believe it's a cmake issue. Consider this file Output: Maybe because the header changed to (? But if I'm reading the correctly, I think it should just set the version to an empty string? Either way, this patch seems to fix it I don't think it's worth raising with zlib because with the next patch version they're going to fix it anyway. It might be worth warning them in advance of 1.4. It's probably worth raising with cmake, because they will want to support all version, and then zlib won't have to care anymore either. I can open a PR for this tomorrow or when I have time, but don't wait for me if anybody wants to do it before.
Nice catch! One minor note: you are looking at 's master branch. It seems to be already fixed there as: We'll need that backport to . UPDATE: or wait for to reach master. With now is in .


Question: , enableGhostscript ? false, ghostscript ? null, gtk3 , enableGtk2 ? false, pygtk ? null, gobjectIntrospection , enableGtk3 ? false, cairo <ins> , enableTk ? false, tcl ? null, tk ? null, tkinter ? null, libX11 ? null </ins> , Cocoa, Foundation, CoreData, cf-private, libobjc, libcxx }: assert enableGhostscript -> ghostscript != null; assert enableGtk2 -> pygtk != null; <ins> assert enableTk -> (tcl != null) && (tk != null) && (tkinter != null) && (libX11 != null) ; </ins> buildPythonPackage rec { name = "matplotlib-${version}";

While going through the documentation I came about a that explicitly requires matplotlib with the TkAgg backend. I tried to generate a nix-shell with matplotlib and tcl/tk and tkinter. However, the script does not execute and instead I get the following error message: In a simplified form: Start nix-shell:Start Python:Try to import matplotlib, configure the backend, and import parts of Tk:Observe the following error message:System: NixPkgs on openSuse 13.2 (Harlequin) (x86_64) Nix version: nix-env (Nix) 1.10 Nixpkgs version: "16.09pre83147." Matplotlib Maintainer:
Judging from the matplotlib expression we don't build against tcl/tk.
I made an attempt to build matplotlib against tcl/tk with the following patch: Unfortunately, compilation fails with the following error message: The linker cannot find the tcl/tk libraries. The linker flags are quite off: They include and the like. This must be due to matplotlib's own build script, as no such flags are set in my bash environment and is executed with the flag anyway.


Question: <ins> { lib , buildGoModule , fetchFromGitHub }: buildGoModule rec { pname = "ooniprobe-cli"; version = "3.14.2"; src = fetchFromGitHub { owner = "ooni"; repo = "probe-cli"; rev = "v${version}"; hash = "sha256-9n/Ozyy1QzjFum/R/X2DChzTHl70e+JQuo09nToAIcE="; }; vendorSha256 = "/fN9nRYOy00EeI8zZQFkCgTMGLZ0pFbYmRdTr2NLIsc="; subPackages = [ "cmd/ooniprobe" ]; meta = with lib; { description = "The Open Observatory of Network Interference command line network probe"; homepage = "https://ooni.org/install/cli"; license = licenses.gpl3Plus; maintainers = with maintainers; [ dotlambda ]; }; } </ins>

Project description The Open Observatory of Network Interference (OONI) is a free software project that aims to empower decentralized efforts in increasing transparency of Internet censorship around the world. please package as "ooniprobe-cli" ("ooniprobe" as alias) and "ooniprobe-desktop" like used here: Metadata homepage URL: source URL: license: mit (hidden in ) / BSD 3-Clause platforms: unix, linux, darwin, windows
I marked this as stale due to inactivity. →
...
I marked this as stale due to inactivity. →
Still relevant.


Question: { stdenv, fetchurl, fetchpatch, cmake, pcre, pkgconfig, python2 <del> , libX11, libXpm, libXft, libXext, libGLU, libGL, zlib, libxml2, lzma, gsl_1 </del> <ins> , libX11, libXpm, libXft, libXext, libGLU, libGL, zlib, libxml2, lz4, lzma, gsl_1, xxHash </ins> , Cocoa, OpenGL, noSplash ? false }: stdenv.mkDerivation rec { pname = "root"; <del> version = "5.34.36"; </del> <ins> version = "5.34.38"; </ins> src = fetchurl { url = "https://root.cern.ch/download/root_v${version}.source.tar.gz"; <del> sha256 = "1kbx1jxc0i5xfghpybk8927a0wamxyayij9c74zlqm0595gqx1pw"; </del> <ins> sha256 = "1ln448lszw4d6jmbdphkr2plwxxlhmjkla48vmmq750xc1lxlfrc"; </ins> }; nativeBuildInputs = [ pkgconfig ]; <del> buildInputs = [ cmake pcre python2 zlib libxml2 lzma gsl_1 ] </del> <ins> buildInputs = [ cmake pcre python2 zlib libxml2 lz4 lzma gsl_1 xxHash ] </ins> ++ stdenv.lib.optionals (!stdenv.isDarwin) [ libX11 libXpm libXft libXext libGLU libGL ] ++ stdenv.lib.optionals (stdenv.isDarwin) [ Cocoa OpenGL ] ;

, CVSSv3=8.8 (nixos-20.03, nixos-unstable) Scanned versions: nixos-20.03: ; nixos-unstable: . May contain false positives. Cc


Question: <ins> diff --git a/bottles/backend/utils/vulkan.py b/bottles/backend/utils/vulkan.py index 6673493..07f70d1 100644 --- a/bottles/backend/utils/vulkan.py +++ b/bottles/backend/utils/vulkan.py @@ -29,6 +29,8 @@ class VulkanUtils: "/etc/vulkan", "/usr/local/share/vulkan", "/usr/local/etc/vulkan" +        "/run/opengl-driver/share/vulkan/", +        "/run/opengl-driver-32/share/vulkan/", ] if "FLATPAK_ID" in os.environ: __vk_icd_dirs += [ </ins>

Vulkan/dxvk doesnt work on bottles. Vulkan is working correctly on my laptop as vkcube, vulkaninfo and the game im trying to run on bottles (that i ran thru wineWowPackages.staging + dxvk install from the official archive file) run perfectly. Steps to reproduce the behavior: bottles a bottle for gaming a game. the "directx error" pop up. Also, the dxvk log files say that the "VKKHRsurface" extension failed to load. DXVK/Vulkan should work on bottles. ! Please run and paste the result.
Having the exact same Issue on 22.11pre393800. (Raccoon)
If fails then there is a driver issue. Vulkan wont be able to draw anything to screen without it. When it occurs in proton issues it's usually a missing 32bit Vulkan library. Tho there can ofc probably be other causes
update: using the system wine doesn't fix dxvk either. only running thru the command line does. As i said, running it thru wine on the terminal does work, so something in the bottles thing is not working right.
I found the cause: these hardcoded paths right there: With this extra lines in , Vulkan will work on Bottles: I'm not sure if this is the best way to solve it, though. Tested only on a 64-bit bottle (I don't know if 32-bit bottles need to also link ). .
!!! nice find!


Question: <ins> diff --git a/bottles/backend/utils/vulkan.py b/bottles/backend/utils/vulkan.py index 6673493..07f70d1 100644 --- a/bottles/backend/utils/vulkan.py +++ b/bottles/backend/utils/vulkan.py @@ -29,6 +29,8 @@ class VulkanUtils: "/etc/vulkan", "/usr/local/share/vulkan", "/usr/local/etc/vulkan" +        "/run/opengl-driver/share/vulkan/", +        "/run/opengl-driver-32/share/vulkan/", ] if "FLATPAK_ID" in os.environ: __vk_icd_dirs += [ </ins>

<!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on GitHub to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the current version of the package --- <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- name: bottles <!-- The current version can be found easily with the same process as above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 2022.5.28-trento-3 desired version: 2022.7.14-brescia-1 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Please tag this issue in your PR.
While automatic update using was removed by in you need to wait while we will "get auto updates from r-rynatm"
That not true. I removed the over complicated updater in which wasn't necessary at all. Since r-ryantm also uses nix-update there was also no need to replace it. That's wrong. You can always create an update PR yourself by running ` or by manually update the package and create a PR with that. r-ryantm goes through all packages so it can sometimes take a few days until the update PR is created. Also nix-update is very lightweight with minimal dependencies, so there is not really a reason to not use it. It also does not require any kind of token or authentication.
Bottles the version released after the one currently present in nixpkgs, was released on June 13. Over one month has passed, so something about the auto-updater isn't working.
The latest r-ryantm log is here . Not sure why that is not working like it should.
I guess a update script is needed for this case :disappointed: Since the package is using , it HAS a fallback update script , so nixpkgs-update is no longer trying to figure out the latest version itself but just run the script.


Question: <ins> diff --git a/bottles/backend/utils/vulkan.py b/bottles/backend/utils/vulkan.py index 6673493..07f70d1 100644 --- a/bottles/backend/utils/vulkan.py +++ b/bottles/backend/utils/vulkan.py @@ -29,6 +29,8 @@ class VulkanUtils: "/etc/vulkan", "/usr/local/share/vulkan", "/usr/local/etc/vulkan" +        "/run/opengl-driver/share/vulkan/", +        "/run/opengl-driver-32/share/vulkan/", ] if "FLATPAK_ID" in os.environ: __vk_icd_dirs += [ </ins>

However seems like cannot handle the version , so it will fail at You may just try Repology gets software latest version from various Linux distributions that ships this app, so since AUR and OpenMandriva have 2022.6.14 (no suffix) the latest version is 2022.6.14. Looks like there is also an related report in Note that nixpkgs-update does not really tries to bump package in this way because it has an fallback update script.


Question: let go-d-plugin = callPackage ./go.d.plugin.nix {}; in stdenv.mkDerivation rec { <del> version = "1.30.1"; </del> <ins> version = "1.31.0"; </ins> pname = "netdata"; src = fetchFromGitHub { owner = "netdata"; repo = "netdata"; rev = "v${version}"; <del> sha256 = "0cp6gbn38f1cr0jkr64vvwz005cvnwj3hgfxs147wap9w228k46r"; </del> <ins> sha256 = "0735cxmljrp8zlkcq7hcxizy4j4xiv7vf782zkz5chn06n38mcik"; fetchSubmodules = true; </ins> }; nativeBuildInputs = [ autoreconfHook pkg-config ];

Project description Netdata agent plugin Metadata homepage URL: source URL: license: GPL 3.0 platforms: unix, linux, darwin We already do have netdata, however it seems to be built without support for the cloud agent that allows it to stream to the cloud or other netdata servers.
I have a local checkout with some edits that allow me to build netdata with cloud support. Unfortunately they also require a change in the libwebsockets build expression. Should I open a PR to integrate my changes into nixpkgs?
A PR would be great! I'm not a maintainer, but if they decide it's out of scope for nixpkgs, perhaps one on NUR might work - I'd try for a PR here first though
Great, I think having a configuration option that is per default would make sense. Maybe ?
Yeah, that seems to fall in line with the various flags present in other packages
I marked this as stale due to inactivity. →
Upstream has incorporated some of the suggestions in this thread, I intend to pick up on it again soon
what would be needed to make this work? Perhaps I can help?
The newest major release of Netdata (1.30.0) includes a cloud link implementation without the need for vendored dependencies. Unfortunately, it is not currently in a reliable state because of a bug in the custom HTTPS implementation. The has already been merged into Netdata master and will be included in the next release. I plan to make a PR that enables cloud support as soon as that release is available.
v1.31.0 dropped 12 minutes ago :) Anything I can do to help?
Thanks, I've already gotten a notification for that. Planning to make a PR when I get off work today. When my PR is done, it would be helpful if you could test my changes on your machines.
Just FYI, I have opened the PR that enables cloud support a few days ago. If you are still interested it would be greatly appreciated if you could test if everything works for you and maybe drop a comment.
Sorry, missed this but the pr looks good! I propose we backport this to stable?