jiebi/CodeConvo huggingface dataset:
Change:
<ins> { stdenv , lib , fetchgit , libbsd , readline }: stdenv.mkDerivation rec { pname = "rosie"; version = "unstable-2020-01-11"; src = fetchgit { url = https://gitlab.com/rosie-pattern-language/rosie; rev = "670e9027563609ba2ea31e14e2621a1302742795"; sha256 = "0jc512dbn62a1fniknhbp6q0xa1p7xi3hn5v60is8sy9jgi3afxv"; fetchSubmodules = true; }; postUnpack = '' # The Makefile calls git to update submodules, unless this file exists touch ${src.name}/submodules/~~present~~ ''; preConfigure = '' patchShebangs src/build_info.sh # Part of the same Makefile target which calls git to update submodules ln -s src submodules/lua/include ''; postInstall = '' mkdir -p $out/share/emacs/site-lisp $out/share/vim-plugins $out/share/nvim mv $out/lib/rosie/extra/extra/emacs/* $out/share/emacs/site-lisp/ mv $out/lib/rosie/extra/extra/vim $out/share/vim-plugins/rosie ln -s $out/share/vim-plugins/rosie $out/share/nvim/site ''; makeFlags = [ "DESTDIR=${placeholder "out"}" ]; buildInputs = [ libbsd readline ]; meta = with lib; { homepage = https://rosie-lang.org; description = "Tools for searching using parsing expression grammars"; license = licenses.mit; maintainers = with maintainers; [ kovirobi ]; platforms = with platforms; linux ++ darwin; }; } </ins>

Discussion:
Project description A supercharged alternative to regular expressions (regex), matching patterns against any input text. Metadata homepage URL: https://rosie- source URL: license: mit platforms: unix PS: this may be relevant:
This is a cool program, I'll have a go at packaging :)
Hmm, this will require upstream changes too, as it doesn't seem that amenable to packaging as is. It'll take a bit longer than I hoped, I'll see if I have some quiet time over the holiday period to work on it. But we might be able to avoid the linked as that is about run-time paths, but we know at compile-time where things go.
But while I do that, you can have a play with (it's a hack of a package, but it seems to work, let me know if things are broken). Just clone that repo, and in the repo root directory do .
I think this can be closed since there is a pull request open for this now.
Add to the pr message so github will close the issue automatically when the pr is merged.
Change:
}; patches = [ <ins> # Replace git paths </ins> (substituteAll { src = ./hardcode-git-path.patch; git = "${lib.getBin git}/bin/git"; }) ]; <ins> nativeBuildInputs = [ pythonRelaxDepsHook ]; </ins> # setuptools is necessary since pkg_resources is required at runtime. propagatedBuildInputs = [ click

Discussion:
Build of failed on x86_64-linux as of . This is currently breaking . maintainers cc: maintainers cc: Other cc: n/a nixpkgs at commit This issue was automatically generated by . that created this issue. Internal tags: -
fixed in
Change:
let versions = [ { <ins> version = "13.1.0"; lang = "en"; language = "English"; sha256 = "sha256-LIpGAJ3uTkZgjc0YykwusyyHQKlCnTvrZGStFfSOz60="; installer = "Mathematica_13.1.0_BNDL_LINUX.sh"; } { </ins> version = "13.0.1"; lang = "en"; language = "English";

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 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: mathematica <!-- 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: mathematica-13.0.1 desired version: mathematica-13.1.0 <!-- 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.
This may help, and maybe hopefully prevent you from having to download the whole thing yourself (unless you really want to validate it, of course):
Sorry about the delay. The old friend of Qt plugins loading failure came along, and it took some time to resolve that.
Change:
"-/etc/nsswitch.conf" "-/etc/hosts" "-/etc/localtime" <ins> "-/etc/ssl/certs" "-/etc/static/ssl/certs" </ins> "-/run/postgresql" ] ++ (optional enableRedis redisServer.unixSocket); BindPaths = [

Discussion:
After updating paperless-ngx to 1.17.0 (from ), the mail fetching tasks stopped working, with the following ssl related error in the logs: Downgrading to 1.16.5 resulted in email working again. <!-- 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.
Sorry for the delay, haven't seen this Issue (am only in unstable maintainers for paperless-ngx, not 23.05 yet). Will take a look at it, and I think I have an idea on how to fix this
Change:
, withDNSTAP ? false , withTFO ? false , withRedis ? false <ins> # Avoid .lib depending on openssl.out # The build gets a little hacky, so in some cases we disable this approach. , withSlimLib ? stdenv.isLinux && !stdenv.hostPlatform.isMusl && !withDNSTAP </ins> , libnghttp2 }:

Discussion:
unbound-full cannot be built on the unstable channel error message: Steps to reproduce the behavior: build .#unbound-full It should obviously build cc Maintainer information:
This happened in the fixupPhase, maybe we should remove lines?
I've put some information on
Change:
libsecret self.node-gyp-build self.node-pre-gyp <ins> ] ++ lib.optionals stdenv.isDarwin [ darwin.apple_sdk.frameworks.AppKit darwin.apple_sdk.frameworks.Security </ins> ]; };

Discussion:
Describe the bug I am trying to install (cli version) on macos from the unstable channel but I a getting the following error: To Reproduce Steps to reproduce the behavior: Expected behavior joplin should be installed correctly Screenshots N/A Additional context Notify maintainers Unfortunaltely maintainers are not specified :( Metadata system: host os: multi-user?: sandbox: version: channels(dbarrosop): nixpkgs:
I marked this as stale due to inactivity. &rarr;
Change:
wrapQtApp $out/bin/electrum ''; <del> nativeCheckInputs = with python3.pkgs; [ pytestCheckHook pyaes pycryptodomex ]; </del> <ins> nativeCheckInputs = with python.pkgs; [ pytestCheckHook pyaes pycryptodomex ]; </ins> pytestFlagsArray = [ "tests" ];

Discussion:
Cannot use hardware wallet with electrum from nixos-unstable channel Steps to reproduce the behavior: to use hardware wallet with electrum (either via creating wallet or loading a wallet) :x: on "Choose Hardware Device" screen, be presented with debug error A list of connected hardware wallets when at least one is connected ! Issue is not present in package from nixos-23.11 channel hardware wallet used: Ledger Nano X Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
systemd.services.nitter = { description = "Nitter (An alternative Twitter front-end)"; wantedBy = [ "multi-user.target" ]; <del> after = [ "network.target" ]; </del> <ins> wants = [ "network-online.target" ]; after = [ "network-online.target" ]; </ins> serviceConfig = { DynamicUser = true; StateDirectory = "nitter";

Discussion:
This issue was described by kvtb at Quoting: Extende the ExecStartPre with something like: Currently the unit depends on , maybe there is something smarter to do.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
might be more suitable?
Change:
''; }; <del> pruneNames = mkOption { type = listOf str; </del> <ins> pruneNames = lib.mkOption { type = lib.types.listOf lib.types.str; </ins> default = lib.optionals (!isFindutils) [ ".bzr" ".cache" ".git" ".hg" ".svn" ]; <del> defaultText = literalMD '' </del> <ins> defaultText = lib.literalMD '' </ins> `[ ".bzr" ".cache" ".git" ".hg" ".svn" ]`, if supported by the locate implementation (i.e. mlocate or plocate). '';

Discussion:
Using more-or-less the default configuration for (with ), the list of results is printed twice whenever running . For example: Steps to reproduce the behavior: the module like so: the job with some file name that exists on the system Matching files should each be printed once. The issue is fixed if I unset the environment variable. plocate deliberately reads from both and the hard coded default path, even if they are the same: The comment claims that this is also the behavior of mlocate, but I do not have an mlocate database installed and haven't wanted to change my running system to use mlocate. It looks like recently started being set in NixOS in . Please run and paste the result.
Sounds to me like an upstream issue. Can you write a mail to the upstream maintainer? ;a=blob;f=README;h=;hb=HEAD#l40
Sure, I have done so. I'll follow up when I get a response.
The plocate maintainer says they do not consider this to be a bug in plocate, and is intentional behavior. Rather than setting the environment variable, could we just make a wrapper script for that uses the NixOS-configured dbpath, if we don't want to re-build itself when the path is changed?
I would be personally fine to just drop support for a custom place for the db. If people really want to have it somewhere else they could symlink it. Then we don't need a wrapper or to worry about the env.
I can confirm the behaviour with .
Could we just take out the variable setting? It isn't needed for or , and just causes this annoying behaviour. If it's needed for , maybe the setting could be made conditional. It would be nice to get something done about it sooner rather than later. This issue has been open for 4 months now.
Please take a look at
I've reviewed the PR and it LGTM. Thanks for doing this! It will be great to have this fixed.
Change:
]; }; <del> linux_5_16 = throw "linux 5.16 was removed because it has reached its end of life upstream"; </del> linux_5_17 = throw "linux 5.17 was removed because it has reached its end of life upstream"; linux_5_18 = throw "linux 5.18 was removed because it has reached its end of life upstream";

Discussion:
The Linux 4.9 LTS release will be EOL after 2023/01 and I hope we can remove it before the 22.11 release, so we don't carry it around until then. via cc kernel maintainer team
Thanks for the heads-up. I'd be fine with doing the removal right now (considering that it's LTS and having that one removed on stable may be an unpleasant surprise), but FWIW: we usually drop kernel releases when they get EOLed (also from stable branches), otherwise we wouldn't be able to provide non-LTS kernels on any stable branch anyways.
Change:
, pkg-config , openssl # darwin dependencies <del> , Security , CoreFoundation </del> <ins> , darwin </ins> , libiconv , curl }: rustPlatform.buildRustPackage rec { pname = "cargo-geiger"; <del> version = "0.11.5"; </del> <ins> version = "0.11.6"; </ins> src = fetchFromGitHub { owner = "rust-secure-code"; repo = pname; rev = "${pname}-${version}"; <del> sha256 = "sha256-PrrhxY+Hk1XfdV0u4GgIsbo8oNOFnqbCeivY2Ix6g+k="; </del> <ins> sha256 = "sha256-rGZJyCWGk2RUr52ICp4dVER3JMBrnLdOMusRm/GG2PE="; </ins> }; <del> cargoHash = "sha256-D3upXhKFkuZfEVOPJ9mCwoZkbkX9s2MltyTkKcBvb6I="; </del> <ins> cargoHash = "sha256-B6Ka35y2fJEDVd891P60TNppr5HGFnzVjLhhfoFCYUA="; </ins> buildInputs = [ openssl ] <del> ++ lib.optionals stdenv.isDarwin [ CoreFoundation Security libiconv curl ]; </del> <ins> ++ lib.optionals stdenv.isDarwin (with darwin.apple_sdk.frameworks; [ CoreFoundation Security libiconv curl ]); </ins> nativeBuildInputs = [ pkg-config ] # curl-sys wants to run curl-config on darwin ++ lib.optionals stdenv.isDarwin [ curl.dev ];

Discussion:
Steps to reproduce the behavior: It takes a while to compile, but when finished the memory usage goes really high in the testphase, during in the step . I have to keyboard interrupt before oom-killer nukes my GUI. I have 16 GiB of RAM, so low memory shouldn't be the problem. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- I'm on a flake based system, so no channels.
Thanks for raising. It's probably case 4 & 7: Have you tried building the upstream project, both as is & in a nix sandbox? I'm thinking this isn't a nixpkgs specific issue. If you could raise an issue on the upstream repo I'll update and disable all tests under for now
yep i just set up a registry for the master branch and build the new version with and no memory overload, so that fixed it gonna try to build 0.11.5 and 6 without nix now
building "as is" means just cloning the project and using right? or do i have to build on a different distro?
Yeah thats it. Im guessing it will work fine but building the normal project with no networking causes the issue.
Change:
ucx xorg.libxshmfence xorg.libxkbfile <del> ] ++ lib.optionals (lib.versionAtLeast version "12.1") (map lib.getLib [ </del> <ins> ] ++ (lib.optionals (lib.versionAtLeast version "12.1") (map lib.getLib ([ </ins> # Used by `/target-linux-x64/CollectX/clx` and `/target-linux-x64/CollectX/libclx_api.so` for: # - `libcurl.so.4` curlMinimal <del> # Used by `/target-linux-x64/libQt6Multimedia.so.6` for: # - `libgstaudio-1.0.so.0` # - `libgstvideo-1.0.so.0` # - `libgstpbutils-1.0.so.0` # - `libgstallocators-1.0.so.0` # - `libgstapp-1.0.so.0` # - `libgstbase-1.0.so.0` # - `libgstreamer-1.0.so.0` </del> <ins> # Used by `/host-linux-x64/Scripts/WebRTCContainer/setup/neko/server/bin/neko` </ins> gst_all_1.gstreamer gst_all_1.gst-plugins-base <del> ]); </del> <ins> ]) ++ (with qt6; [ qtmultimedia qttools qtpositioning qtscxml qtsvg qtwebchannel qtwebengine ]))); </ins> # Prepended to runpaths by autoPatchelf. # The order inherited from older rpath preFixup code

Discussion:
Some cuda packages come with vendored copies of libraries that are already available in nixpkgs. These vendored libraries still require patching their Runpaths, their presence reduces determinism, and breaks "deep replacement" (i.e. nixpkgs' feature allowing to ensure that everything in a package set uses the same revision of a dependency). For instance, ships , which otherwise is available as: Cf. Tasks [ ] Look into deleting these vendored libraries and re-linking their reverse dependencies against nixpkgs alternatives
Change:
<ins> { stdenv, kernel }: stdenv.mkDerivation { pname = "turbostat"; inherit (kernel) src version; makeFlags = [ "PREFIX=${placeholder "out"}" ]; postPatch = '' cd tools/power/x86/turbostat ''; meta = with stdenv.lib; { description = "Report processor frequency and idle statistics"; homepage = https://www.kernel.org/; license = licenses.gpl2; platforms = [ "i686-linux" "x86_64-linux" ]; # x86-specific }; } </ins>

Discussion:
Project description turbostat — Report processor frequency and idle statistics Metadata homepage URL: source URL: license: gpl2+ platforms: linux
Happened to put together a turbostat expression just a day or so ago, see the PR! :)
Change:
stdenv.mkDerivation rec { pname = "openasar"; <del> version = "unstable-2023-07-07"; </del> <ins> version = "unstable-2023-10-24"; </ins> src = fetchFromGitHub { owner = "GooseMod"; repo = "OpenAsar"; <del> rev = "5ac246dc92e9a2a9b314d899df728f37096c482b"; hash = "sha256-ODeVru4LCSl3rIeJCdezAwqzKP6IRo5WDaaUymqEcBs="; </del> <ins> rev = "eee9bab822e3dbd97a735d0050ddd41ba27917f2"; hash = "sha256-SSWQSqGgTZjowgrzF6qHZDTw/Y9xFHNTZvetxqZubYI="; </ins> }; postPatch = ''

Discussion:
Package name: openasar Latest released version: unstable-2023-10-24 <!-- Search your package here: --- Current version on the unstable channel: unstable-2023-07-07 Current version on the stable/release channel: unstable-2023-07-07 <!-- 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.
This is to fix Discord Canary & Development via this commit:
Change:
{ aspell , aspellDicts , makeWrapper <del> , symlinkJoin , runCommand </del> <ins> , buildEnv </ins> }: f:

Discussion:
Enchant cannot find any aspell dictionaries when aspellWithDicts was used to install aspell. The command on its own works fine. Put the following into your : succeeds, i.e. does not output any errors outputs: "Couldn't create a dictionary for en_US.UTF-8"; however, I expected it to succeed just like aspell System: NixOS: 17.09beta581. (Hummingbird) Nix version: 1.11.14 Nixpkgs version: 17.09beta581. Sandboxing enabled: false
I looked at the aspell wrapper: With the system-wide export of ASPELL_CONF, enchant works fine: So the problem seems to be that the wrapper only fixes the issue for the binary, but not for any other application that uses the aspell API directly.
Could you check ?
I'd love to help you, but I have just started using NixOS two days ago and do not yet know how to integrate your proposed change into my system. I downloaded your new to and the following to my : But gave me: error: value is a function while a set was expected, at Line 64 is: If you could show me how to do this most efficiently (possibly without needing to clone nixpkgs or rebuilding my whole system ^^), I would be most grateful! :)
you can pass with your original config; no need to import.
Thank you for your assistance, this worked perfectly. I have commented on . Out of curiosity, is it possible to integrate single packages like I wanted to do with in ?
You can indeed import Nix expressions, however, if you want to import packages from say another Nixpkgs version/tree, then you best import that Nixpkgs, and then the correct attribute from that set. Fixed with so closing.
Change:
{ lib <ins> , stdenv </ins> , fetchFromGitLab <del> , mkKdeDerivation </del> , breeze-icons , breeze , cmake

Discussion:
retains references to packages, bloating the closure massively. I'd expect to see no such results. If comparing to qt5: n/a Seems related to some wrapping issue. For example: <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --All examples above were built against Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Do we need the qt6 plugins for designer?
I achieved the following nix diff-closures with the diff: The patch is not perfect but maybe a starting point?
Maybe a separate output that's not $dev for those plugins?
That change brings the closure from (nominally) 1.05 GiB to 925 MiB. I think the other notably sized dependency would be which appears to add 100+ MiB of its own (as it brings along ), but it's indirectly coming from
Change:
<del> { lib, python3Packages, fetchFromGitHub }: python3Packages.buildPythonApplication rec { pname = "pyradio"; version = "0.8.9.9"; src = fetchFromGitHub { owner = "coderholic"; repo = pname; rev = version; sha256 = "04asw5alkkf2q5iixswarj6ddb0y4a6ixm7cckl6204jiyxpv6kc"; }; checkPhase = '' $out/bin/pyradio --help ''; meta = with lib; { homepage = "http://www.coderholic.com/pyradio/"; description = "Curses based internet radio player"; license = licenses.mit; maintainers = with maintainers; [ contrun ]; }; } </del>

Discussion:
The contains both radio communication software (for signal processing / software radio, e.g ) and internet music radio-players (e.g. . These belong to separate domains (hobbyist vs. end-user) and should therefore be separated. I believe it would make sense to put all the music radio players into the audio folder, as it already contains a few radio-players (e.g. , which --confusingly-- is also the name of a commonly used radio communication frequency) I would be willing to sift through the section and find all misplaced packages, but I don't know how to work with github and create pull requests.. :innocent:
Thank you! That looks like a good explanatory guide. I guess that leaves me with no choice to get my hands dirty then. (Might take me a while to get started, so only ping me if you didn't hear from in a week.) As for why I couldn't search for this guide myself?.. I guess there simply is a difference between being lost and having to find guidance yourself and getting a peer-reviewed recommendation.
Hey I created a pull request -- would you be willing to take a look?
Change:
}; }); <ins> game = buildPythonPackage rec { name = "pygame-1.9.1"; src = fetchurl { url = http://www.pygame.org/ftp/pygame-1.9.1release.tar.gz; sha256 = "0cyl0ww4fjlf289pjxa53q4klyn55ajvkgymw0qrdgp4593raq52"; }; patches = [ ./pygame.patch ]; # auto confirming missing dependencies: # PORTMIDI and PORTTIME still missing patchPhase = '' sed -i 's@raw_input(.*@"1"@' config_unix.py unset patchPhase patchPhase ''; installCommand = "python setup.py install --prefix=$out"; propagatedBuildInputs = [ pkgs.SDL pkgs.SDL_mixer pkgs.SDL_gfx pkgs.SDL_net pkgs.SDL_sound pkgs.SDL_ttf pkgs.SDL_image pkgs.smpeg pkgs.libpng pkgs.libjpeg ]; }; </ins> genshi = buildPythonPackage { name = "genshi-0.6";

Discussion:
Presumably since , 's makes use of the new section which our binutils 2.35 doesn't understand, leading to warnings such as this one: More context can be found here: which describes the section Since binutils 2.36, supports the new note section. However we have been hesitant to update binutils so far (since it usually introduces a lot of breakage, e. g. see ). Open question: Is this a serious problem? Should we apply the patch from 2.36? Should we disable in the meantime where we use it? Build any haskell package on a platform that supports (with if necessary). <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Maintainer information:
I'd expect this would get fixed by PR
I've tried but that doesn't seem to fix it for me. It leads to a lot of warnings when building some custom packages so curious about a solution.
All warnings I've experienced so far have been fixed by this (or some other change).
I think this is fixed now? Haven't seen the warning for a long time now.
Change:
''; depsBuildBuild = [ buildPackages.stdenv.cc ]; <del> nativeBuildInputs = [ bison flex python3 pkg-config autoconf automake gettext freetype ]; buildInputs = [ ncurses libusb-compat-0_1 freetype lvm2 fuse libtool ] </del> <ins> nativeBuildInputs = [ bison flex python3 pkg-config gettext freetype autoreconfHook ]; buildInputs = [ ncurses libusb-compat-0_1 freetype lvm2 fuse libtool bash ] </ins> ++ optional doCheck qemu ++ optional zfsSupport zfs;

Discussion:
After upgrading to 21.05, when running , I get the following warning: Everything else seems to work fine, but it's unclear what has gone wrong here, or if I should be worried. Metadata Maintainer information:
discussed here a bit you can safely ignore it to hide it we could add to the or to
Not sure if my case is related, but I had the same error after : The overall install didn't error. Attempting to reboot, it would be unable to boot:
My boot got fixed after converting my MBR to GPT and creating an ESP partition and setting it to use systemd-boot instead of GRUB. If GRUB continues to work with people that see this warning, it's unlikely that my boot problems are related. (But, still, a different bug; if MBR got deprecated, there should have been an announcement.)
But the issue is quite severe (I just lost hours on it because it happened on a remote server which boots very slowly on a web-mounted rescue iso), and I could only get my system running again by reverting to . I'd propose to throw out the new version () for now. I can't do GPT, because the system only has a legacy BIOS (no UEFI), it appears that this is the reason this issue has flown under the radar? Same error referenced , it appears to be an issue with the grub package itself. EDIT: since OP defined a "parallel" but much less severe bug, I made a new report here: