jiebi/CodeConvo huggingface dataset:
Change:
</part> <part> <title>Contributing to Nixpkgs</title> <del> <xi:include href="contributing/quick-start.xml" /> <xi:include href="contributing/coding-conventions.xml" /> </del> <ins> <xi:include href="contributing/quick-start.chapter.xml" /> <xi:include href="contributing/coding-conventions.chapter.xml" /> </ins> <xi:include href="contributing/submitting-changes.chapter.xml" /> <xi:include href="contributing/vulnerability-roundup.chapter.xml" /> <del> <xi:include href="contributing/reviewing-contributions.xml" /> <xi:include href="contributing/contributing-to-documentation.xml" /> </del> <ins> <xi:include href="contributing/reviewing-contributions.chapter.xml" /> <xi:include href="contributing/contributing-to-documentation.chapter.xml" /> </ins> </part> </book>

Discussion:
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. to . the contents from Docbook to CommonMark. Follow . Use existing .md sections for inspiration. from the folder to build the manual. the manual on your computer at after running from doc/ 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:
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:
I am currently working on it :-)
I opened a PR here: Thanks in advance for reviewing :-)
I'll do the section.
Nice! I amended the issue title for correctness sake.
Change:
sha256 = "sha256-OX41ChtHX36lVRL7O2gH21Dfw6GPPEClD+yafR/PFm8="; }; <del> buildInputs = [ btrfs-progs ]; </del> <ins> buildInputs = [ btrfs-progs' ]; </ins> installFlags = [ "PREFIX=${placeholder "out"}"

Discussion:
Steps to reproduce the behavior: compsize 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
The reason is update makes it build again on current master Something there breaks it: Seems like quite a few things that used got removed:
Here's a quick workaround:
Seems due to this commit: and this:
Here's the corresponding compsize upstream bug:
Change:
, librttopo , libspatialite , libxml2 <ins> , libz </ins> , minizip , proj , readosm

Discussion:
Steps to reproduce the behavior: <!-- 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]:
The build fails with
Adding to the buildInputs fixes the issue, I'll create a PR…
Mind giving the PR commit a try,
Supah! Now I can continue setting up valhalla. :+1:
Happy I could help, a review and formal approval on would greatly be appreciated and help move the PR addressing this issue forward
Change:
}) ]; <ins> # https://github.com/wxWidgets/Phoenix/issues/2575 postPatch = '' ln -s ${lib.getExe buildPackages.waf} bin/waf substituteInPlace build.py  --replace-fail "distutils.dep_util" "setuptools.modified" ''; </ins> nativeBuildInputs = [ attrdict pkg-config

Discussion:
Steps to reproduce the behavior: It looks like the was at 9 July 2024 at 4:10:47 am GMT+2. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
see
Change:
, libuv, lua, ncurses, pkg-config , unibilium, xsel, gperf , libvterm-neovim <ins> , tree-sitter </ins> , glibcLocales ? null, procps ? null # now defaults to false because some tests can be flaky (clipboard etc)

Discussion:
Describe the bug I have an overlay to install neovim from a recent commit. When you use that overlay on a intel macbook neovim is compiled against luajit 2.1.0-beta3 while the same derivation on an M1 macbook compiles against Lua 5.1. I tried checking why that might be given it's the same exact overlay and luajit seems to compile just fine on aarch64 but I am afraid my nix skills weren't good enough. To Reproduce neovim with the following overlay: neovim the command On intel you will see: While on arm: Main issue is that lots of nvim plugins require luajit and don't work with lua 5.1 Expected behavior neovim should be compiled against luajit. Screenshots N/A Additional context Add any other context about the problem here. Notify maintainers Metadata Intel: Arm: Maintainer information:
This is alredy done in
Oh, thanks for the quick response and for the great work. Closing this :)
Reopening, since this will again be the case once is merged. By some reason builds with luajit on aarch64 still fail and I do not know why. As explained in , simply updating luajit does not help.
fixed in
switched back to using Lua 5.1 due to I think this issue should be reopened. Especially due to from the OP Also see my comment above
I've been messing around with this for a few days without much success, but I do think that compiling with openresty-luajit does work (at least, luarocks builds successfully and the error in question with goes away). I am utterly lost in the maze of Nix abstractions though and don't know the best way to do this. I've tried using overlays to set LuaJIT to be the openresty version which seems to half work, but when I try and build neovim it's still using the version of luarocks built with LuaJIT 2.1. Can someone who knows their way around Nix a little better take a deeper look into this? EDIT: I got it to work! I'm using the following overlay: This issue helped me figure out why my overriden value of wasn't applying to the packages.

I had to add to the override function.
Maybe make a pr for that so nixpkgs will use this version of luajit by default on macOS aarch64.
Done
merged.
This problem appear again, I used on ubuntu22.04 aarch64 (m1 Docker), and got same error with the NVIM 0.7.2: And my luaSnip plugin can not work. (It's ok under intel x64)
I'm also hitting this issue again on aarch64 (m1 Docker) on ubuntu 22.04 and 20.04
Same here, exact same environment and output as
I am also seeing the same error in ubuntu 22.04 VM running on M1 MAC. This is based on aarch64. Anyone know how to fix the issue?
Change:
name = "rust_${crate.crateName}-${crate.version}${lib.optionalString buildTests_ "-test"}"; version = crate.version; depsBuildBuild = [ pkgsBuildBuild.stdenv.cc ]; <del> nativeBuildInputs = [ rustc' cargo' jq ] </del> <ins> nativeBuildInputs = [ rust cargo jq ] </ins> ++ lib.optionals stdenv.hasCC [ stdenv.cc ] ++ lib.optionals stdenv.buildPlatform.isDarwin [ libiconv ] ++ (crate.nativeBuildInputs or [ ]) ++ nativeBuildInputs_;

Discussion:
I'm running an issue with overriding the rust toolchain since , I pass the following to crate2nix: to set the toolchain when building something, since I don't want to override the toolchain globally. But after this PR it doesn't work because it uses the toolchain in instead of the one I'm passing in. Now I don't really know how to override the rust toolchain to the version I want. is a nightly version I got from This problem is caused by this optimization: Another issue is that the attribute is missing in rust-overlay:
I'm having this issue as well. I've overridden my input to my flake to as a workaround for now.
Hi, sorry for the delay, I'm back home now from "holiday". Can any of you give me a minimal flake that reproduces the issue so I can experiment and find the best way to fix it?
I'm also hitting this. I don't have a minimal flake but I can at least offer the error message which seems to be missing from the OP.
Let me know if this fixes it.
unfortunately it does not, because it still defaults to for the rustc compiler. I've created a reproduction here: As you can see in I'm overriding rustc and cargo to the specific nightly version I want, but when I run I get the following output: This is the rustc version that's current in nixpkgs, not the nightly I specified. Thanks a lot for looking into this
One problem with your reproducer is that it uses the for which takes an arg called not . I think that still wouldn't have solved it. I made some changes in the PR that would allow passing a custom toolchain via the but also using . I did some refactoring to get rid of the and variables.
Change:
) ''; <ins> # append module paths to xorg.conf postInstall = '' cat ${xorgModulePaths} >> $out/etc/xpra/xorg.conf ''; </ins> doCheck = false; enableParallelBuilding = true;

Discussion:
Describe the bug Attempting to start xpra fails with the following X server log: To Reproduce Steps to reproduce the behavior: run start :200
Change:
stdenv.mkDerivation rec { pname = "argyllcms"; <del> version = "2.2.0"; </del> <ins> version = "2.2.1"; </ins> src = fetchzip { # Kind of flacky URL, it was reaturning 406 and inconsistent binaries for a # while on me. It might be good to find a mirror url = "https://www.argyllcms.com/Argyll_V${version}_src.zip"; <del> sha256 = "sha256-EcVwYJfJbWWXl58O3ulsrWgUYTgR4uWdMgb0Z140Pu4="; </del> <ins> sha256 = "sha256-umY3wQfG26Okqnw+MCUnlwWTAyJ6MR/FHe5oe61KBh0="; </ins> }; <del> patches = [ ./gcc5.patch ]; </del> # The contents of this file comes from the Jamtop file from the # root of the ArgyllCMS distribution, rewritten to pick up Nixpkgs # library paths. When ArgyllCMS is updated, make sure that changes # in that file is reflected here. jamTop = writeText "argyllcms_jamtop" '' DESTDIR = "/" ; <del> REFSUBDIR = "ref" ; </del> <ins> REFSUBDIR = "share/argyllcms" ; </ins> # Keep this DESTDIR anchored to Jamtop. PREFIX is used literally ANCHORED_PATH_VARS = DESTDIR ;

Discussion:
<!-- 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 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: argyllcms <!-- The current version can be found easily with the same process than 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: 2.2.0 desired version: 2.2.1 last edited by testing it is only possible with gnome color manager setting, since displaycal is broken you also need special, expensive hardware
Change:
postInstall = with python3Packages; '' wrapProgram $out/bin/pymol  <del> --prefix PYTHONPATH : ${lib.makeSearchPathOutput "lib" python3.sitePackages [ pyqt5 pyqt5.pyqt5-sip ]} </del> <ins> --prefix PYTHONPATH : ${lib.makeSearchPathOutput "lib" python3Packages.python.sitePackages [ pyqt5 pyqt5.pyqt5-sip ]} </ins> mkdir -p "$out/share/icons/" <del> ln -s $out/${python3.sitePackages}/pymol/pymol_path/data/pymol/icons/icon2.svg "$out/share/icons/pymol.svg" </del> <ins> ln -s $out/${python3Packages.python.sitePackages}/pymol/pymol_path/data/pymol/icons/icon2.svg "$out/share/icons/pymol.svg" </ins> '' + lib.optionalString stdenv.hostPlatform.isLinux '' cp -r "${desktopItem}/share/applications/" "$out/share/" '';

Discussion:
Steps to reproduce the behavior: pymol 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Note: This seems to be failure of test check. With no check (doCheck=false;), the package builds and runs as expected.
Change:
githubId = 4303706; keys = [ { fingerprint = "B00F E582 FD3F 0732 EA48  3937 F558 14E4 D687 4375"; } ]; }; <ins> pladypus = { name = "Peter Loftus"; email = "loftusp5976+nixpkgs@gmail.com"; github = "pladypus"; githubId = 56337621; }; </ins> plchldr = { email = "mail@oddco.de"; github = "plchldr";

Discussion:
Project description A VS Code theme for the night owls out there. Now introducing Light Owl theme for daytime usage. Decisions were based on meaningful contrast for reading comprehension and for optimal razzle dazzle. Metadata homepage URL: https://open- source URL: license: mit platforms: unix, linux, darwin, ... Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I'm creating this issue hoping to get some recommendations on where to look for information on how to package a vscode extension. I'm under the impression (correct me if I'm wrong) that a vscode extension should be a simpler project to package for my first shot at it. I've followed the contribution instructions for nixpkgs so I have the repo forked and ready to go. I'm just unfamiliar with what changes I actually need to make. Any assistance with this would be greatly appreciated.
Have a look in: Read the Edit: Build as:
Great, thanks. I'll look into those.
In case you can't solve your problem, we need to update docs. But then, I need to know what problem you are having.
I'm getting stuck on the value for that I'm suppose to use. Based on the other extensions I'm confident I'm not just using the commit hash but I'm not sure where the sha256 values are coming from. Do you have any additional information on this?
When you try to build it will generate the hash for you, so you copy and paste it. (What you have to do is just to erase the hash so it gets recomputed.)
Did it work for you? In case yes, consider upstreaming. (And closing this issue.)
I've kept the PR as a draft while I work out any issues with it and finish reading through the contribution docs. Is there any directions on how to correct the formatting? I thought I was following it while first making the
thanks for all your help with this process.
Change:
dbus-map = callPackage ../tools/misc/dbus-map { }; <del> deepspeech = callPackage ../misc/deepspeech { }; </del> dell-530cdn = callPackage ../misc/drivers/dell-530cdn {}; demjson = with python3Packages; toPythonApplication demjson;

Discussion:
<!-- 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 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: tts <!-- The current version can be found easily with the same process than 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: 0.0.9 desired version: 0.0.11 maintainers: mozilla fired the team and they founded a new company to continue their work new releases can be found here
We are aware of the forks, we'll probably get to it before the branch-off. STT (DeepSpeech) was recently packaged, but does not build from source, so my interest in that package is limited.
Same also not a STT user.
can you update deepspeech to the new repo, call it stt and deprecate deepspeech? how to deprecate a package is documented here: please add a review. when anything is unclear, i would like to improve it
How about we call it instead?
i don't think that is very helpful for the end-user. the package name should match the upstream project name
do you want to update tts again?
Hello, just wanted to say that there has been a new release , in case someone wants to give it a shot.
Change:
, withMultithread ? true # Multithreading via pthreads/win32 threads , withNetwork ? withHeadlessDeps # Network support , withPixelutils ? withHeadlessDeps # Pixel utils in libavutil <del> , withLTO ? false # build with link-time optimization </del> /* *  Program options */

Discussion:
on fails to build if is set to Steps to reproduce the behavior: with set to should build <details<summaryFull build log</summary<br</details Maintainer information:
I marked this as stale due to inactivity. &rarr;
Still an issue
still an issue
Option has been renamed to . Still broken.
Here's the exact error: Since it doesn't work and, judging by this issue, hasn't for a while, let's just remove that flag.
Change:
# file RPATH_CHANGE could not write new RPATH "-DCMAKE_SKIP_BUILD_RPATH=ON" <ins> # always link against static build of LLVM "-DZIG_STATIC_LLVM=ON" </ins> # ensure determinism in the compiler build "-DZIG_TARGET_MCPU=baseline" ];

Discussion:
nixpkgs
Please don't assign people to issues without talking to them first. I am not that into Darwin to be a help here.
ncdu is no longer compatible with Zig 0.10, so WONTFIX until LLVM issues on Darwin are resolved.
TIL that exists — I'm switching to that, until these ongoing (upstream) stability issues are resolved.
Change:
cd python ${python3Packages.python.pythonOnBuildForHost.interpreter} setup.py build ${python3Packages.python.pythonOnBuildForHost.interpreter} setup.py install --prefix=$out <ins> mv $out/lib/python*/site-packages/OpenMM*.egg/{openmm,simtk} $out/lib/python*/site-packages/. </ins> ''; postFixup = ''

Discussion:
Importing before other packages with C extensions results in with when the latter package is imported. In nixpkgs tree, on master: results in Note: this does not occur if the import order is switched: does not result in an error. Scipy is used as an example, but this also occurs when importing other packages with C extensions after openmm (e.g. rdkit): The above commands should not result in s. Seems likely to be a result of overriding and to use GCC 11 in (Removing these overrides results in a build failure with , so maybe not easy to fix..) <!-- 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(matt): channels(root): nixpkgs:
I am afraid it is the override of stdenv and gfortran. The override became necessary due to and and I am afraid for the moment I cannot fix both this issue and until the upstream problems are gone. However, only hits you if you compile the OpenCL kernels, so if disabling OpenCL in OpenMM is an option for you, you should be able to use plain and and work around the python import issue.
Ah, thanks! I don't need the OpenCL kernels, so this is an option for me. Confirmed that disabling OpenCL and overriding to use the default stdenv and gfortran is a solution: (no errors) :tada:
Change:
<ins> { lib , stdenv , fetchFromGitHub , rustPlatform , pkg-config , openssl , CoreServices }: rustPlatform.buildRustPackage rec { pname = "rathole"; version = "0.4.3"; src = fetchFromGitHub { owner = "rapiz1"; repo = pname; rev = "v${version}"; sha256 = "sha256-gqWgx03mUk6+9K4Yw5PHEBwFxsOR+48wvngT+wQnN1k="; }; cargoSha256 = "sha256-dafOgZtiszkoi97PpAVMtdvJd5O3EK9hDVNLJ32FYzE="; nativeBuildInputs = [ pkg-config ]; buildInputs = [ openssl ] ++ lib.optional stdenv.isDarwin [ CoreServices ]; __darwinAllowLocalNetworking = true; meta = with lib; { description = "A lightweight and high-performance reverse proxy for NAT traversal, written in Rust"; homepage = "https://github.com/rapiz1/rathole"; license = licenses.asl20; maintainers = with maintainers; [ dit7ya ]; }; } </ins>

Discussion:
Project description A lightweight and high-performance reverse proxy for NAT traversal, written in Rust. An alternative to frp and ngrok. Metadata homepage URL: source URL: license: asl20 ( Apache-2.0 license ) platforms: linux
see
Ah.. thanks, I was going to make one.
Change:
(lib.cmakeBool "ENABLE_XCB_RANDR" x11Support) (lib.cmakeBool "ENABLE_XFCONF" (x11Support && (!stdenv.isDarwin))) (lib.cmakeBool "ENABLE_XRANDR" x11Support) <ins> ] ++ lib.optionals stdenv.isLinux [ (lib.cmakeOptionType "filepath" "CUSTOM_PCI_IDS_PATH" "${hwdata}/share/hwdata/pci.ids") (lib.cmakeOptionType "filepath" "CUSTOM_AMDGPU_IDS_PATH" "${libdrm}/share/libdrm/amdgpu.ids") </ins> ]; postInstall = ''

Discussion:
uses and to convert PCI device ID to human-readable product name. Currently their paths are hard coded as and . It won't work with NixOS of course. I found some packages that have similar issues. They are patched directly before building: Fastfetch needs to be patched too. Steps to reproduce the behavior: N/A Fastfetch can properly find and N/A Reference: Fastfetch provided cmake config option  for but not for . I can add one if needed. N/A Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Hi thanks for the detailed issue report! This should be pretty straightforward to fix. If you could add a config option for the path that would be great! Many thanks.
.
was released with support
Many thanks! Much appreciated.
Change:
<del> { lib, buildPythonPackage, fetchFromGitHub, pythonOlder, django </del> <ins> { lib , buildPythonPackage , fetchFromGitHub , django </ins> , factory_boy <del> , glibcLocales </del> , mock , pygments <del> , pytest , pytest-cov </del> , pytest-django <del> , python-dateutil </del> <ins> , pytestCheckHook </ins> , shortuuid <del> , six , tox , typing ? null </del> , vobject , werkzeug }: buildPythonPackage rec { pname = "django-extensions"; <del> version = "3.1.3"; </del> <ins> version = "3.1.5"; </ins> src = fetchFromGitHub { owner = pname; repo = pname; rev = version; <del> sha256 = "03mhikhh49z8bxajbjf1j790b9c9vl4zf4f86iwz7g0zrd7jqlvm"; </del> <ins> sha256 = "sha256-NAMa78KhAuoJfp0Cb0Codz84sRfRQ1JhSLNYRI4GBPM="; </ins> }; <del> LC_ALL = "en_US.UTF-8"; __darwinAllowLocalNetworking = true; </del> <ins> postPatch = '' substituteInPlace setup.cfg  --replace "--cov=django_extensions --cov-report html --cov-report term" "" ''; </ins> <del> propagatedBuildInputs = [ six ] ++ lib.optional (pythonOlder "3.5") typing; </del> <ins> propagatedBuildInputs = [ django ]; __darwinAllowLocalNetworking = true; </ins> checkInputs = [ <del> django </del> factory_boy <del> glibcLocales </del> mock pygments # not explicitly declared in setup.py, but some tests require it <del> pytest pytest-cov </del> pytest-django <del> python-dateutil </del> <ins> pytestCheckHook </ins> shortuuid <del> tox </del> vobject werkzeug ]; <del> # remove tests that need network access checkPhase = '' rm tests/management/commands/test_pipchecker.py DJANGO_SETTINGS_MODULE=tests.testapp.settings  pytest django_extensions tests ''; </del> <ins> disabledTestPaths = [ # requires network access "tests/management/commands/test_pipchecker.py" ]; </ins> meta = with lib; { description = "A collection of custom extensions for the Django Framework";

Discussion:
python38Packages.djangoextensions and python39Packages.djangoextensions Fails to build. I discovered it as it was a dependency of Archivebox that also doesnt build now. Simple way to reproduce is: a file : I expected the package to build and not fail with errors. It appears it is the test's that fail and not the actual build. ! I have much larger file that I choose not to include as it is the same error i got in the minimal version and all the other clutter likely is not responsible. No maintainers for either of the packages :( Please run and paste the result. this path will be fetched (0.06 MiB download, 0.30 MiB unpacked):
Change:
kirigami-addons = self.callPackage ./misc/kirigami-addons {}; kio-extras-kf5 = self.callPackage ./misc/kio-extras-kf5 {}; kio-fuse = self.callPackage ./misc/kio-fuse {}; <ins> klevernotes = self.callPackage ./misc/klevernotes {}; </ins> ktextaddons = self.callPackage ./misc/ktextaddons {}; kunifiedpush = self.callPackage ./misc/kunifiedpush {}; kup = self.callPackage ./misc/kup {};

Discussion:
Project description A note-taking and management application using markdown. Metadata homepage URL: source URL: license: gpl3+ platforms: linux Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]: