jiebi/CodeConvo huggingface dataset:
Code change:
<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-snapTools"> <title>pkgs.snapTools</title> <para> <varname>pkgs.snapTools</varname> is a set of functions for creating Snapcraft images. Snap and Snapcraft is not used to perform these operations. </para> <section xml:id="ssec-pkgs-snapTools-makeSnap-signature"> <title>The makeSnap Function</title> <para> <function>makeSnap</function> takes a single named argument, <parameter>meta</parameter>. This argument mirrors <link xlink:href="https://docs.snapcraft.io/snap-format">the upstream <filename>snap.yaml</filename> format</link> exactly. </para> <para> The <parameter>base</parameter> should not be specified, as <function>makeSnap</function> will force set it. </para> <para> Currently, <function>makeSnap</function> does not support creating GUI stubs. </para> </section> <section xml:id="ssec-pkgs-snapTools-build-a-snap-hello"> <title>Build a Hello World Snap</title> <example xml:id="ex-snapTools-buildSnap-hello"> <title>Making a Hello World Snap</title> <para> The following expression packages GNU Hello as a Snapcraft snap. </para> <programlisting><xi:include href="./snap/example-hello.nix" parse="text" /></programlisting> <para> <command>nix-build</command> this expression and install it with <command>snap install ./result --dangerous</command>. <command>hello</command> will now be the Snapcraft version of the package. </para> </example> </section> <section xml:id="ssec-pkgs-snapTools-build-a-snap-firefox"> <title>Build a Hello World Snap</title> <example xml:id="ex-snapTools-buildSnap-firefox"> <title>Making a Graphical Snap</title> <para> Graphical programs require many more integrations with the host. This example uses Firefox as an example, because it is one of the most complicated programs we could package. </para> <programlisting><xi:include href="./snap/example-firefox.nix" parse="text" /></programlisting> <para> <command>nix-build</command> this expression and install it with <command>snap install ./result --dangerous</command>. <command>nix-example-firefox</command> will now be the Snapcraft version of the Firefox package. </para> <para> The specific meaning behind plugs can be looked up in the <link xlink:href="https://docs.snapcraft.io/supported-interfaces">Snapcraft interface documentation</link>. </para> </example> </section> </section> </del>

Related discussion:
text: 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.
Code change:
<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-snapTools"> <title>pkgs.snapTools</title> <para> <varname>pkgs.snapTools</varname> is a set of functions for creating Snapcraft images. Snap and Snapcraft is not used to perform these operations. </para> <section xml:id="ssec-pkgs-snapTools-makeSnap-signature"> <title>The makeSnap Function</title> <para> <function>makeSnap</function> takes a single named argument, <parameter>meta</parameter>. This argument mirrors <link xlink:href="https://docs.snapcraft.io/snap-format">the upstream <filename>snap.yaml</filename> format</link> exactly. </para> <para> The <parameter>base</parameter> should not be specified, as <function>makeSnap</function> will force set it. </para> <para> Currently, <function>makeSnap</function> does not support creating GUI stubs. </para> </section> <section xml:id="ssec-pkgs-snapTools-build-a-snap-hello"> <title>Build a Hello World Snap</title> <example xml:id="ex-snapTools-buildSnap-hello"> <title>Making a Hello World Snap</title> <para> The following expression packages GNU Hello as a Snapcraft snap. </para> <programlisting><xi:include href="./snap/example-hello.nix" parse="text" /></programlisting> <para> <command>nix-build</command> this expression and install it with <command>snap install ./result --dangerous</command>. <command>hello</command> will now be the Snapcraft version of the package. </para> </example> </section> <section xml:id="ssec-pkgs-snapTools-build-a-snap-firefox"> <title>Build a Hello World Snap</title> <example xml:id="ex-snapTools-buildSnap-firefox"> <title>Making a Graphical Snap</title> <para> Graphical programs require many more integrations with the host. This example uses Firefox as an example, because it is one of the most complicated programs we could package. </para> <programlisting><xi:include href="./snap/example-firefox.nix" parse="text" /></programlisting> <para> <command>nix-build</command> this expression and install it with <command>snap install ./result --dangerous</command>. <command>nix-example-firefox</command> will now be the Snapcraft version of the Firefox package. </para> <para> The specific meaning behind plugs can be looked up in the <link xlink:href="https://docs.snapcraft.io/supported-interfaces">Snapcraft interface documentation</link>. </para> </example> </section> </section> </del>

Related discussion:
text: 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.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
I opened a PR here: Thanks in advance for reviewing :-)
Code change:
}; listenerAsserts = prefix: listener: <del> assertKeysValid prefix freeformListenerKeys listener.settings </del> <ins> assertKeysValid "${prefix}.settings" freeformListenerKeys listener.settings </ins> ++ userAsserts prefix listener.users ++ imap0 (i: v: authAsserts "${prefix}.authPlugins.${toString i}" v)

Related discussion:
text: 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.
Code change:
src = fetchFromGitHub { owner = "nvim-treesitter"; repo = "nvim-treesitter"; <del> rev = "97691940d1c9cdaef2ca73c4fae50987fdcadc6c"; sha256 = "13cz5hjp7w1fmjw35n41gw3yyizs9y3jnbz228j6n8zz3awdin9g"; </del> <ins> rev = "b995eebe84df88092a41cbfd591bfc1565f70d8e"; sha256 = "1738mssq22n1njrpi004apgfv00fxn7yx00r3175qn57bjw9bks9"; </ins> }; meta.homepage = "https://github.com/nvim-treesitter/nvim-treesitter/"; };

Related discussion:
text: Project description Various vim plugins iamcco/coc-tailwindcss coc-extensions/coc-svelte evanleck/vim-svelte
Code change:
opacity, edge thickness, and right- or left-handedness, for this cursor theme.  This package's derivation has an output for each of these variants, named following the upstream convention, and the attribute for <del> an output must be used to install a variant.  E.g.: <programlisting language="nix"> environment.systemPackages = [ comixcursors.Blue comixcursors.Opaque_Orange comixcursors.Slim_Red comixcursors.Opaque_Slim_White comixcursors.LH_Green comixcursors.LH_Opaque_Black comixcursors.LH_Slim_Orange comixcursors.LH_Opaque_Slim_Blue ]; </programlisting> Attempting to use just <literal>comixcursors</literal>, i.e. without an output attribute, will not install any variants.  To install all the variants, use <literal>comixcursors.all</literal> (which is a list), e.g.: <programlisting language="nix"> environment.systemPackages = comixcursors.all ++ [...]; </programlisting> The complete list of output attributes is: <programlisting> ${concatStringsSep "n" variants} </programlisting> </del> <ins> an output must be used to install a variant, e.g. `comixcursors.LH_Opaque_Slim_Blue`.  Attempting to use only `comixcursors`, i.e. without an output attribute, will not install any variants.  To install all the variants, use `comixcursors.all` (which is a list). </ins> ''; homepage = "https://gitlab.com/limitland/comixcursors"; changelog = "https://gitlab.com/limitland/comixcursors/-/blob/HEAD/NEWS";

Related discussion:
text: The  package (which I and maintain) has a that is rendering wrong at It seems that I used the wrong markup language. I'd like to ask: what is the markup language that we're supposed to use in s? I've been unable to find an answer to this in the documentation, and unable to find a working example in some package's file, even though IIRC I've come across some description in search results that correctly rendered some quoted code with extra styling. When I first wrote my package's description, it was 4 months ago with NixOS 21.05, and I'd somehow thought that DocBook was the correct language to use. Looking at other packages' descriptions, I see some other attempts to use markup (or Markdown), which is maybe what influenced me, but now I see that these are also rendering wrong. My longer more-structured description looks especially bad, so it should be fixed.
As far as is just plain text.
Code change:
dontBuild = true; nativeBuildInputs = [ wrapQtAppsHook makeWrapper python3 ]; <del> propagatedBuildInputs = with python3.pkgs; [ pyqt5 docutils ]; </del> <ins> propagatedBuildInputs = with python3.pkgs; [ pyqt6 docutils ]; </ins> desktopItem = makeDesktopItem { name = "leo-editor";

Related discussion:
text: A config file is read-only, which causes the program to fail entirely. The leo text editor should run when invoked. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Not fixed:
this has been fixed on the master branch however has not been backported. I'll create a PR to backport this, in the meantime if using flakes you can update nixpkgs to follow master or nixpkgs-unstable otherwise you can update your channel to follow unstable. works fine for me. EDIT:
Are you sure? Are you sure?
!
works on my machine, which makes it extra strange that installing it locally with a flake that is pinned to does not.
Code change:
buildFeatures = [ "zstd/pkg-config" ]; <ins> preCheck = '' substituteInPlace tests/ui.rs  --replace 'format!(r"/private{path}")' 'path.to_string()' ''; </ins> postInstall = '' installManPage artifacts/*.1 installShellCompletion artifacts/ouch.{bash,fish} --zsh artifacts/_ouch ''; <del> env.OUCH_ARTIFACTS_FOLDER = "artifacts"; </del> <ins> env = { OUCH_ARTIFACTS_FOLDER = "artifacts"; } // # Work around https://github.com/NixOS/nixpkgs/issues/166205. lib.optionalAttrs stdenv.cc.isClang { NIX_LDFLAGS = "-l${stdenv.cc.libcxx.cxxabi.libName}"; }; </ins> meta = with lib; { description = "A command-line utility for easily compressing and decompressing files and directories";

Related discussion:
text: Steps to reproduce the behavior: ouch on x86_64 darwin Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Code change:
patchShebangs --build configure ''; <ins> # JDK's build system attempts to specifically detect # and special-case WSL, and we don't want it to do that, # so pass the correct platform names explicitly configurePlatforms = ["build" "host"]; </ins> configureFlags = [ "--with-boot-jdk=${openjdk-bootstrap.home}" "--with-version-build=${version.build}"

Related discussion:
text: They're trying to be smart: We should probably patch that check out, but maybe people with actual Java experience will have better ideas.
We need to patch that. Neither do we want to provide cygpath nor can we wslpath because that would most likely try to escape the sandbox.
The thing here is that they see WSL and automatically assume we're cross-compiling to a Windows target, which we're not. We can patch this out, or maybe we can force it to not cross-compile somehow, or maybe we can make lie.
I would recommend to just patch that out.
Code change:
patchShebangs --build configure ''; <ins> # JDK's build system attempts to specifically detect # and special-case WSL, and we don't want it to do that, # so pass the correct platform names explicitly configurePlatforms = ["build" "host"]; </ins> configureFlags = [ "--with-boot-jdk=${openjdk-bootstrap.home}" "--with-version-build=${version.build}"

Related discussion:
text: I'm trying to use it on aarch64 and this is failing: [6/257] Building CXX object FAILED: /nix/store/fsn9mccnjinl212ypa3rx8b8647s9klh-gcc-wrapper-12.2.0/bin/g++ -DCEFUSESANDBOX -DNDEBUG -DWRAPPINGCEFSHARED -DFILEOFFSETBITS=64 -DSTDCCONSTANTMACROS -DSTDCFORMATMACROS -I/build/source/thirdparty/cef/cefbinary104.4.26+g4180781+chromium-104.0.5112.102linux64minimal -O3 -DNDEBUG -fno-strict-aliasing -fPIC -fstack-protector -funwind-tables -fvisibility=hidden --param=ssp-buffer-size=4 -pipe -pthread -Wall -Werror -Wno-missing-field-initializers -Wno-unused-parameter -Wno-error=comment -Wno-comment -Wno-deprecated-declarations -m64 -march=x86-64 -fno-exceptions -fno-rtti -fno-threadsafe-statics -fvisibility-inlines-hidden -std=c++14 -Wsign-compare -Wno-undefined-var-template -Wno-literal-suffix -Wno-narrowing -Wno-attributes -O2 -fdata-sections -ffunction-sections -fno-ident -UFORTIFYSOURCE -DFORTIFYSOURCE=2 -MD -MT -MF -o -c /build/source/thirdparty/cef/cefbinary104.4.26+g4180781+chromium- g++: error: unrecognized command-line option '-m64' ninja: build stopped: subcommand failed. error: builder for '/nix/store/a7r53z6050vvhlmwnxac6c6kp41gcz2g-jcef-jetbrains-' failed with exit code 1; last 10 log lines: For full logs, run 'nix log /nix/store/a7r53z6050vvhlmwnxac6c6kp41gcz2g-jcef-jetbrains-'.
Code change:
patchShebangs --build configure ''; <ins> # JDK's build system attempts to specifically detect # and special-case WSL, and we don't want it to do that, # so pass the correct platform names explicitly configurePlatforms = ["build" "host"]; </ins> configureFlags = [ "--with-boot-jdk=${openjdk-bootstrap.home}" "--with-version-build=${version.build}"

Related discussion:
text: error: 1 dependencies of derivation '/nix/store/9mds0h6675lnh8hgam63xycvv8lrb01v-jetbrains-jdk-jcef-17.0.6-' failed to build
WSL2 on aarch64? Also, this error is for Chromium.
Sorry, never mind. I'm having an issue with , that has a dependency on CEF. I posted in an incorrect place. I opened a separate ticket. Please ignore.
Code change:
hcl2json = callPackage ../applications/misc/hcl2json { }; <ins> hcledit = callPackage ../tools/text/hcledit { }; </ins> hcxtools = callPackage ../tools/security/hcxtools { }; hcxdumptool = callPackage ../tools/security/hcxdumptool { };

Related discussion:
text: Project description A command line editor for HCL Metadata homepage URL: source URL: license: mit platforms: darwinarm64, linuxarm64, windows_arm64 Release page: Copied install info from readme: If you are macOS user: Download the latest compiled binaries and put it anywhere in your executable path. If you have Go 1.20+ development environment:
Code change:
meta.homepage = "https://github.com/tpope/vim-surround/"; }; <ins> vim-svelte = buildVimPluginFrom2Nix { pname = "vim-svelte"; version = "2022-02-17"; src = fetchFromGitHub { owner = "evanleck"; repo = "vim-svelte"; rev = "1080030d6a1bc6582389c133a07552ba0a442410"; sha256 = "0kwx0rkb6879v5c3jyavzh1hklxl2q1qwnm28x1p32kdcwqkccjp"; }; meta.homepage = "https://github.com/evanleck/vim-svelte/"; }; </ins> vim-swap = buildVimPluginFrom2Nix { pname = "vim-swap"; version = "2021-08-08";

Related discussion:
text: Project description Various vim plugins iamcco/coc-tailwindcss coc-extensions/coc-svelte evanleck/vim-svelte
Code change:
--replace 'DESTINATION usr/share' "DESTINATION share" ''; <ins> postConfigure = '' substituteInPlace cmake_install.cmake  --replace "/var/empty" "/usr" ''; </ins> meta = with lib; { description = "A full configuration manager for JWM"; homepage = "https://joewing.net/projects/jwm";

Related discussion:
text: The repo URL is missing for: To fix it, you can fork (I forked it for preservation but neither of us made changes: ) then change the GitHub username in the nix file to yours. I don't have NixOS or have any way to test this. I ran into your nix file while trying to find the maintainer: I asked whether the repo has moved because it is deleted from GitHub. I contacted him via 's contact form and I'm awaiting a response (I didn't try an e-mail address found here yet: ).
Recently I have read somewhere that the author was absent from some social media, and that for personal reasons he has removed his account on github, and that this software is still available on launchpad. Github was just a second home for it. But I am not finding this info anymore.
Ok, the author responded to me via e-mail that the launchpad URL is correct, but that he isn't maintaining it. He says he's more likely to rewrite it in Rust rather than update it. The nix file can be corrected to use launchpad, but in light of that information, using one of the GitHub forks or forking one of them yourself and turning on the "Issues" feature is probably the best route to a future for it, even to a minimal extent of getting bugfixes.
I am changing the upstream source to the launchpad repository, as it is the most correct. I am also watching the two forks on github, so that I will be notified of new actions on them.
Code change:
fetchSubmodules = true; }; <ins> patches = [ # This patch can be removed when a new version of barrier (greater than 2.4.0) # is released, which will contain this commit. (fetchpatch { name = "add-missing-cstddef-header.patch"; url = "https://github.com/debauchee/barrier/commit/4b12265ae5d324b942698a3177e1d8b1749414d7.patch"; sha256 = "sha256-ajMxP7szBFi4h8cMT3qswfa3k/QiJ1FGI3q9fkCFQQk="; }) ]; </ins> buildInputs = [ curl xorg.libX11 xorg.libXext xorg.libXtst avahiWithLibdnssdCompat qtbase ]; nativeBuildInputs = [ cmake wrapGAppsHook ];

Related discussion:
text: The package is failing to build Steps to reproduce the behavior: The package to build successfully without errors
I'm sorry, I haven't used in years - but also nothing with that package has changed in some while. I'd assume an upstream problem?
I don't use but took a look out of curiosity. It was an upstream problem that is fixed by a few commits after the latest 2.4.0 release. There hasn't been a new release since then. Is the best thing to do here pull down that commit as an isolated patch or to bump the revision that's pulled down to that (untagged) revision?
Can we use in the meantime?
Code change:
, makeWrapper , ncurses5 , nspr <del> , nss </del> <ins> , nss_latest </ins> , pciutils , pkgsi686Linux , ps

Related discussion:
text: A clear and concise description of what the bug is. Steps to reproduce the behavior: to or -build switch to install android-studio android-studio and open one project the right-top button to sign to Google will open a dialog show nothing happened android-studio can open the default browser and success to sign in google. ! Add any other context about the problem here. <!-- 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.
This is the same problem as , which I'm experiencing. Clicking documentation links from within Android Studio does nothing other than showing a jumping icon of Firefox besides the cursor for a few seconds (on KDE Plasma, X11), while it's expected to open the page in Firefox.
Code change:
{ lib <ins> , stdenv </ins> , buildPythonPackage , pythonOlder , fetchFromGitHub

Related discussion:
text: Steps to reproduce the behavior: python3Packages.rapidfuzz Introduced in . Please run and paste the result.
It appears that cmake selects an incorrect linker. I am currently unsure what's the reason for this. Following I think I might need to set: I have zero experience with nix os + no access to a mac. Is there any way to patch in the build system here to check whether this solves the issue?
Code change:
# All packages built with the Musl libc. This will override the # default GNU libc on Linux systems. Non-Linux systems are not <del> # supported. pkgsMusl = if stdenv.hostPlatform.isLinux then nixpkgsFun { </del> <ins> # supported. 32-bit is also not supported. pkgsMusl = if stdenv.hostPlatform.isLinux && stdenv.buildPlatform.is64bit then nixpkgsFun { </ins> overlays = [ (self': super': { pkgsMusl = super'; })] ++ overlays;

Related discussion:
text: I get this error when the packages i build contain any musl one. Blocking me from reviewing PRs. Full error: Issue for a more helpful error message: Steps to reproduce the behavior: No error. I think the solution would be to disable musl libc on i686-linux until it actually works. So Nix or nixpkgs-review don't even try to build it. <!-- 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: channels(root): nixpkgs:
Collecting information: this looks fine maybe here needs to be a check for 64-bit
Code change:
homepage = "https://www.warp.dev"; license = licenses.unfree; sourceProvenance = with lib.sourceTypes; [ binaryNativeCode ]; <del> maintainers = with maintainers; [ emilytrau Enzime imadnyc ]; </del> <ins> maintainers = with maintainers; [ emilytrau Enzime imadnyc donteatoreo ]; </ins> platforms = platforms.darwin ++ [ "x86_64-linux" ]; };

Related discussion:
text: When I try to open the warp-terminal on wayland it crashes without opening any window and get the following logs: Steps to reproduce the behavior: to open warp-terminal happens It should open the warp-terminal window and prompt. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Might be helpful:
Fixed in , I tried running () on KDE Wayland and everything works as expected
A warp-terminal dev has stated that wayland support is explicitly still experimental and off by default for this reason. Please do not open issues concerning configurations that are explicitly unsupported by upstream.
Sorry, I didn't know it was explicitly unsupported by the upstream since it was working before just fine on Wayland. Thanks a lot anyway!
Code change:
cfg = config.services.tailscale; isNetworkd = config.networking.useNetworkd; in { <del> meta.maintainers = with maintainers; [ danderson mbaillie twitchyliquid64 ]; </del> <ins> meta.maintainers = with maintainers; [ danderson mbaillie twitchyliquid64 mfrw ]; </ins> options.services.tailscale = { enable = mkEnableOption (lib.mdDoc "Tailscale client daemon");

Related discussion:
text: 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.