jiebi/CodeConvo huggingface dataset:
Change:
sha256 = "1nr990i4b04rnlw1ghd0xmgvvvhih698mb6lb6jylr76cs7zcnpi"; }; }); <del> s3transfer = super.s3transfer.overridePythonAttrs (oldAttrs: rec { version = "0.4.2"; src = oldAttrs.src.override { inherit version; sha256 = "sha256-ywIvSxZVHt67sxo3fT8JYA262nNj2MXbeXbn9Hcy4bI="; }; }); </del> }; }; in with py.pkgs; buildPythonApplication rec { pname = "awscli2"; <del> version = "2.2.4"; # N.B: if you change this, change botocore to a matching version too </del> <ins> version = "2.2.14"; # N.B: if you change this, change botocore to a matching version too </ins> src = fetchFromGitHub { owner = "aws"; repo = "aws-cli"; rev = version; <del> sha256 = "sha256-MctW31X012DXY16qS6AP6nLiaAt/cuA8iMwGm0oXi6M="; </del> <ins> sha256 = "sha256-LU9Tqzdi8ULZ5y3FbfSXdrip4NcxFkXRCTpVGo05LcM="; </ins> }; postPatch = '' <del> substituteInPlace setup.py --replace "colorama>=0.2.5,<0.4.4" "colorama>=0.2.5" substituteInPlace setup.py --replace "cryptography>=3.3.2,<3.4.0" "cryptography>=3.3.2" substituteInPlace setup.py --replace "docutils>=0.10,<0.16" "docutils>=0.10" substituteInPlace setup.py --replace "ruamel.yaml>=0.15.0,<0.16.0" "ruamel.yaml>=0.15.0" substituteInPlace setup.py --replace "wcwidth<0.2.0" "wcwidth" </del> <ins> substituteInPlace setup.py  --replace "awscrt==0.11.13" "awscrt"  --replace "colorama>=0.2.5,<0.4.4" "colorama"  --replace "cryptography>=3.3.2,<3.4.0" "cryptography"  --replace "docutils>=0.10,<0.16" "docutils"  --replace "ruamel.yaml>=0.15.0,<0.16.0" "ruamel.yaml"  --replace "wcwidth<0.2.0" "wcwidth" </ins> ''; checkInputs = [ jsonschema mock nose ];

Discussion:
Describe the bug build fails on Darwin during test phase. To Reproduce Steps to reproduce the behavior: -build -A awscli2 Expected behavior It builds. Additional context <details<summaryTest failures</summary</detailsNotify maintainers Metadata Maintainer information:
Ran into this issue as well. There must be a way to disable tests as a temporary workaround (living life dangerously, I know), but I don't know how to do that exactly with an override. doesn't work as its using .
You can just revert to a previous commit instead (same version even):
That is really neat, thank you for sharing!
No problem, this is one of the things I love about Nix. Unstable may break sometimes, but it's fairly easy to just override the broken package and roll forward. BTW I got the hash from , then clicking "Source" and looking at the history. There's also .
Change:
<ins> diff --git a/thirdparty/CMakeLists.txt b/thirdparty/CMakeLists.txt index f33b3bf3f..1214f179c 100644 --- a/thirdparty/CMakeLists.txt +++ b/thirdparty/CMakeLists.txt @@ -16,6 +16,5 @@ if(NOT "${SRB2_CONFIG_SYSTEM_LIBRARIES}") include("cpm-png.cmake") include("cpm-curl.cmake") include("cpm-openmpt.cmake") +	include("cpm-libgme.cmake") endif() - -include("cpm-libgme.cmake") </ins>

Discussion:
Package name: srb2 Latest released version: 2.2.13 <!-- Search your package here: --- Current version on the unstable channel: 2.2.11 Current version on the stable/release channel: 2.2.10 <!-- 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.
Looks like there were a bunch of CMake changes so the build needs to be changed. See: Not sure how to make this work in Nix yet so it might take some time before I figure things out.
Looks like openSUSE patched 2.2.13 with these changes: Will investigate more later.
The PR hasn't been merged yet, but you can play SRB2 with the following: Feel free to leave an approving review if it works for you.
been using it for a few days now, also I don't know how to review since i've never done it before could I be pointed to the relevant docs?
Here's the . Thanks in advance!
Change:
<del> { stdenv, fetchurl, perl, ppp, iproute, which }: </del> <ins> { stdenv, fetchurl, perl, ppp, iproute }: </ins> stdenv.mkDerivation rec { <del> name = "pptp-${version}"; </del> <ins> pname = "pptp"; </ins> version = "1.10.0"; src = fetchurl { <del> url = "mirror://sourceforge/pptpclient/${name}.tar.gz"; </del> <ins> url = "mirror://sourceforge/pptpclient/${pname}-${version}.tar.gz"; </ins> sha256 = "1x2szfp96w7cag2rcvkdqbsl836ja5148zzfhaqp7kl7wjw2sjc2"; }; <del> patchPhase = '' sed -e 's/install -o root/install/' -i Makefile ''; preConfigure = '' makeFlagsArray=( IP=${iproute}/bin/ip PPPD=${ppp}/sbin/pppd  BINDIR=$out/sbin MANDIR=$out/share/man/man8  PPPDIR=$out/etc/ppp ) ''; </del> <ins> prePatch = '' substituteInPlace Makefile --replace 'install -o root' 'install' ''; </ins> <del> nativeBuildInputs = [ perl which ]; </del> <ins> preConfigure = '' makeFlagsArray=( IP=${iproute}/bin/ip PPPD=${ppp}/sbin/pppd  BINDIR=$out/sbin MANDIR=$out/share/man/man8  PPPDIR=$out/etc/ppp ) ''; buildInputs = [ perl ]; postFixup = '' patchShebangs $out ''; </ins> meta = with stdenv.lib; { description = "PPTP client for Linux";

Discussion:
The pptp package generates a shell script called pptpsetup, which references an executable called pppd. pppd is present in the Nix store, but is not symlinked into the environment: Consequently, there's an error when I try to run pptpsetup:
I could be wrong, but doesn't sh say is not found?
That's what I thought at first, then I changed my mind, and now I think you're right. :) Pppd should probably be symlinked either way though.
Yes, pptpsetup should be patched to replace by
(triage) Looks like this was patched by
I have not patched this particular instance. What is the purpose of this script?
Are there any updates to this issue, please?
Change:
<del> { lib, stdenv, fetchFromGitHub, fetchpatch, autoreconfHook, pkg-config }: </del> <ins> { lib, stdenv, fetchFromGitHub, autoreconfHook, pkg-config }: </ins> stdenv.mkDerivation rec { <del> version = "1.0.8"; </del> <ins> version = "1.0.9"; </ins> pname = "libde265"; src = fetchFromGitHub { owner = "strukturag"; repo = "libde265"; rev = "v${version}"; <del> sha256 = "1dzflqbk248lz5ws0ni5acmf32b3rmnq5gsfaz7691qqjxkl1zml"; </del> <ins> sha256 = "sha256-OpiQapppuKCR27tIG5OW+KiNMP9ysv7CaobiBOW6VUI="; </ins> }; <del> patches = [ (fetchpatch { name = "CVE-2022-1253.patch"; url = "https://github.com/strukturag/libde265/commit/8e89fe0e175d2870c39486fdd09250b230ec10b8.patch"; sha256 = "sha256-F1BOWFx9oXR2trM22atyD3AJ5x6vVfURQ/PTlYP2Ibg="; }) ]; </del> nativeBuildInputs = [ autoreconfHook pkg-config ]; enableParallelBuilding = true;

Discussion:
, CVSSv3=7.8 (nixos-21.11, nixos-unstable) CVSSv3=6.5 (nixos-21.11, nixos-unstable) CVSSv3=5.5 (nixos-21.11, nixos-unstable) CVSSv3=5.5 (nixos-21.11, nixos-unstable) CVSSv3=5.5 (nixos-21.11, nixos-unstable) There is an Assertion `scalinglistpredmatrixiddelta==1' failed at in libde265 v1.0.8 when decoding file, which allows attackers to cause a Denial of Service (DoS) by running the application with a crafted file or possibly have unspecified other impact. An Incorrect Access Control vulnerability exists in libde265 v1.0.8 due to a SEGV in An issue was discovered in libde265 v1.0.8.There is a Heap-use-after-free in intrapred.h when decoding file using . A stack-buffer-overflow exists in libde265 v1.0.8 via fallback- in function putepelhvfallback when running program . An issue has been found in libde265 v1.0.8 due to incorrect access control. A SEGV caused by a READ memory access in function derive_boundaryStrength of has occurred. The vulnerability causes a segmentation fault and application crash, which leads to remote denial of service. Scanned versions: nixos-21.11: ; nixos-unstable: . Cc
See
Change:
hasBlacklistedLicense = assert areLicenseListsValid; attrs: hasLicense attrs && lib.lists.any (l: builtins.elem l blacklist) (lib.lists.toList attrs.meta.license); <del> allowBroken = config.allowBroken or false; </del> <ins> allowBroken = config.allowBroken or false || builtins.getEnv "NIXPKGS_ALLOW_BROKEN" == "1"; </ins> <del> allowUnsupportedSystem = config.allowUnsupportedSystem or false; </del> <ins> allowUnsupportedSystem = config.allowUnsupportedSystem or false || builtins.getEnv "NIXPKGS_ALLOW_UNSUPPORTED_SYSTEM" == "1"; </ins> isUnfree = licenses: lib.lists.any (l: !l.free or true) licenses;

Discussion:
Describe the bug Unable to evaluate due to bug To Reproduce Expected behavior does a nix-review Additional context Add any other context about the problem here. Metadata
Change:
cd "$gemdir" <ins> rm -f gemset.nix Gemfile.lock export BUNDLE_FORCE_RUBY_PLATFORM=1 </ins> bundler lock --update bundix '';

Discussion:
Architecture specific details are being included in the after called in . should be set to make it architecture agnostic for . Originally suggested here: already accounts for this by setting : It seems like other ruby packages are have various workarounds during updates: I noticed this while trying to use for updating (). Architecture details showed up for a gem and the platform section for the Resulted in a failure due to architecture specific pkg for , specifically : As well as the section in the containing many architectures (less of an issue since bundix seems to ignore this): The complete after following the steps above should be similar to: When calling the should be set to and gems should not have architecture spec versions after an update with to the . Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
export HOME=$TMPDIR ''; <ins> pythonImportsCheck = [ "weasyprint" ]; </ins> meta = with lib; { <del> homepage = "https://weasyprint.org/"; </del> description = "Converts web documents to PDF"; <ins> homepage = "https://weasyprint.org/"; </ins> license = licenses.bsd3; maintainers = with maintainers; [ elohmeier ]; };

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: <!-- 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: 54.3 desired version: 57.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.
Change:
${cfg.globalConfig} } ${cfg.extraConfig} <ins> ${concatMapStringsSep "n" mkVHostConf virtualHosts} </ins> ''; Caddyfile-formatted = pkgs.runCommand "Caddyfile-formatted" { nativeBuildInputs = [ cfg.package ]; } ''

Discussion:
I don't know if this is a bug or expected behaviour, but I've found that the caddyfile gets built differently depending on whether I'm using the unstable module or the 23.05 module with a base of 23.05. Specifically, it seems that the location of the contents of in the caddyfile change. In 23.05 (caddy version 2.6.x), I find that the contents of the caddyfile are in the following sequence: However, using unstable, it's changed to: Now this is a problem because I use to define a few common variables which are then used by my virtual hosts. Can this behaviour be changed or made explicit? Or can we have a option which comes after but before Virtual Hosts? Steps to reproduce the behavior: the unstable caddy module on a nixos 23.05 installation a global config section, an extra Config section, and a few virtual hosts and then check the way the caddyfile is made. The caddyfile to be made in the same way as it was in 23.05. - Pinging you because I see that you're the one who updated the package to the 2.7.x series. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
I am unable to reproduce this. Could you please share a minimal reproducer/code snippet for ? Thanks!
What I've got (with the extra stuff snipped out) is: : : The custom overlay does not change caddy in any way.
Update: This only happens when you mix channels, and not when you stick to unstable. I got the chance to try it out right now.
While I am not sure whether this is a general issue deep in the merging order of the nixos module system when using , I at least know how to workaround it. You can simply force the order via for now. I'll probably file an PR tomorrow or so that fixes this in the caddy module itself by using in Very interesting issue/edge case. Thanks for reporting!
Thanks for giving me a solution! It works perfectly. I will leave it to you to close this bug report post your PR, if you wish.
Change:
subPackages = [ "." ]; <ins> nativeBuildInputs = [ makeWrapper ]; </ins> postInstall = '' mkdir -p $out/lib/systemd/system substitute dist/systemd/zrepl.service $out/lib/systemd/system/zrepl.service  --replace /usr/local/bin/zrepl $out/bin/zrepl <ins> wrapProgram $out/bin/zrepl  --prefix PATH : ${lib.makeBinPath [ openssh ]} </ins> ''; meta = with lib; {

Discussion:
Describe the bug I wanted to use the connection type for a zrepl job like so in my : However the service then fails with this error, saying that ssh is missing from this package. I guess I could fix this with an overlay? I'm new to nixos and don't really know how I would go about doing that. (Would appreciate some pointers to examples where smth similar was done before) Notify maintainers Metadata Maintainer information:
Would you mind testing
how would I go about doing that easily in my current system? (sry this is my first day running nix/nixos)
with that snippet you can also use packages from master in your systemPackages
can confirm it's working, thx for the explanation!
Change:
nvidia-video-sdk = callPackage ../development/libraries/nvidia-video-sdk { }; <ins> nvidia-optical-flow-sdk = callPackage ../development/libraries/nvidia-optical-flow-sdk { }; </ins> nvtop = callPackage ../tools/system/nvtop { nvidia_x11 = linuxPackages.nvidia_x11.override { libsOnly = true; }; };

Discussion:
Describe the bug OpenCV 4 fails to build with cuda enabled due to missing NVIDIA optical flow sdk To Reproduce Steps to reproduce the behavior: -build -A opencv4 Expected behavior Either we disable OpenCV 4's option to compile with the NVIDIA optical flow SDK or allow compilation against the NVIDIA optical flow sdk headers. See: I've done some preliminary work towards this on the following branch:
Change:
./services/misc/polaris.nix ./services/misc/portunus.nix ./services/misc/preload.nix <ins> ./services/misc/private-gpt.nix </ins> ./services/misc/prowlarr.nix ./services/misc/pufferpanel.nix ./services/misc/pykms.nix

Discussion:
Project description Interact privately with your documents using the power of GPT, 100% privately, no data leaks Metadata homepage source license: asl-2 platforms: all?
i am really new to nix, and i made this by adding dependency until it worked.. but hopefully a good starting point now just need to do is, which will download the models and to run it.
Change:
vendorSha256 = "sha256-Y3O7ADzZPlLWFbXSYBcI6b5MAhMD0UnkhQxO9VJMpOY="; passthru.tests.nomad = nixosTests.nomad; preCheck = '' <del> export PATH="$PATH:/build/go/bin" </del> <ins> export PATH="$PATH:$NIX_BUILD_TOP/go/bin" </ins> ''; }; }

Discussion:
Steps to reproduce the behavior: -env -i nomad-1.5.8 Build fails for both nomad-1.5.8 and nomad-1.6.1. nomad-1.4.6 installs without build. Please run and paste the result.
thank you!
Change:
src = fetchzip { name   = "fail2ban-${version}-src"; url    = "https://github.com/fail2ban/fail2ban/archive/${version}.tar.gz"; <del> sha256 = "111xvy2gxwn868kn0zy2fmdfa423z6fk57i7wsfrc0l74p1cdvs5"; </del> <ins> sha256 = "1pwgr56i6l6wh2ap8b5vknxgsscfzjqy2nmd1c3vzdii5kf72j0f"; </ins> }; buildInputs = [ unzip ]; <del> pythonPath = (stdenv.lib.optional stdenv.isLinux systemd) ++ [ python.modules.sqlite3 gamin ]; </del> <ins> propagatedBuildInputs = [ python.modules.sqlite3 gamin ] ++ (stdenv.lib.optional stdenv.isLinux pythonPackages.systemd); </ins> preConfigure = '' <del> substituteInPlace setup.cfg  --replace /usr $out substituteInPlace setup.py  --replace /usr $out  --replace /etc $out/etc  --replace /var $TMPDIR/var  </del> for i in fail2ban-client fail2ban-regex fail2ban-server; do substituteInPlace $i  --replace /usr/share/fail2ban $out/share/fail2ban

Discussion:
with current current unstable channel, the fail2ban package misses its etc path. The package hasn't been updated for some time and the out path is apparently generated by rewriting pathes in its : This suggests that the breakage might be related to the recent python packaging rework, so /cc as well as pkg maintainers
Change:
openrouteservice = callPackage ../development/python-modules/openrouteservice { }; <ins> opensearch-py = callPackage ../development/python-modules/opensearch-py { }; </ins> opensensemap-api = callPackage ../development/python-modules/opensensemap-api { }; opensfm = callPackage ../development/python-modules/opensfm { };

Discussion:
Python module to connect with OpenSearch, Amazon's ElasticSearch fork. Also see and Metadata homepage URL: source URL: license: apache-2.0 platforms: unix, linux, darwin, ...
Change:
diff --git a/auto_cpufreq/core.py b/auto_cpufreq/core.py <del> index a685db8..1ca1ca1 100644 </del> <ins> index 83d0d64..04b5035 100644 </ins> --- a/auto_cpufreq/core.py +++ b/auto_cpufreq/core.py <del> @@ -72,7 +72,7 @@ def app_version(): print("Git commit:", check_output(["git", "describe", "--always"]).strip().decode()) else: print(getoutput("pacman -Qi auto-cpufreq | grep Version")) -    else: +    else: # source code (auto-cpufreq-installer) try: print("Git commit:", check_output(["git", "describe", "--always"]).strip().decode()) @@ -179,31 +179,13 @@ def get_current_gov(): return print("Currently using:", getoutput("cpufreqctl.auto-cpufreq --governor").strip().split(" ")[0], "governor") </del> <ins> @@ -204,35 +204,13 @@ def get_current_gov(): </ins> def cpufreqctl(): -    """

Discussion:
Describe the bug I believe the auto-cpufreq daemon should start on boot if enabled. To Reproduce auto-cpufreq daemon: . the system. . auto-cpufreq as dead/inactive. Expected behavior auto-cpufreq service should be started on boot. Additional context I was using the unstable service in 20.09 and it worked as expected. In 21.05 stable, the service starts dead/inactive and my system is very slow. I manually start the service and I'm back to the NixOS I know and love. I was able to fix this by adding the following to my configuration: Notify maintainers Metadata Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(pnelson): channels(root): nixpkgs: Maintainer information:
Sorry for being late, should fix this.
I have the exact same issue now, on 23.11.
Same here, also facing this problem on 23.11...
Thought this might be caused due to some false overwrites in the module config, so I decided to try out rewriting the systemd service. Doesn't work either...
For others who might still be hitting this, I thought I was too. When checking the logs I saw that power-profiles-daemon was starting up, causing auto-cpufreq to shut down. I fixed this by adding: From looking at this code, and be kind with me here since I'm a nix beginner, it is .  I think the best action would be to add an assertion to give users a prompt like with tlp. If this looks correct I can open a PR for it
Change:
libceph = ceph.lib; inherit (callPackages ../tools/filesystems/ceph { <del> boost = boost16x.override { enablePython = true; python = python38; }; </del> <ins> boost = boost172.override { enablePython = true; python = python38; }; </ins> }) ceph ceph-client;

Discussion:
, CVSSv3=7.1 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc Cc Cc Cc
Change:
pyexcel-xls = callPackage ../development/python-modules/pyexcel-xls { }; <ins> pyexiftool = callPackage ../development/python-modules/pyexiftool { }; </ins> pyexploitdb = callPackage ../development/python-modules/pyexploitdb { }; pyezviz = callPackage ../development/python-modules/pyezviz { };

Discussion:
Project description Python library for exiftool Metadata homepage URL: source URL: license: bsd and gpl3+ platforms: python Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
Log1(PCSC_LOG_INFO, "Disabling USB support for pcscd"); } #ifdef DEBUG_HOTPLUG <del> diff --git a/src/hotplug_linux.c b/src/hotplug_linux.c index bf69af8..64b0ed7 100644 --- a/src/hotplug_linux.c +++ b/src/hotplug_linux.c @@ -130,8 +130,8 @@ static LONG HPReadBundleValues(void) if (hpDir == NULL) { -		Log1(PCSC_LOG_INFO, -			"Cannot open PC/SC drivers directory: " PCSCLITE_HP_DROPDIR); +		Log2(PCSC_LOG_INFO, "Cannot open PC/SC drivers directory: %s", +			PCSCLITE_HP_DROPDIR); Log1(PCSC_LOG_INFO, "Disabling USB support for pcscd."); return -1; } @@ -219,8 +219,8 @@ end: if (bundleSize == 0) { -		Log1(PCSC_LOG_INFO, -			"No bundle files in pcsc drivers directory: " PCSCLITE_HP_DROPDIR); +		Log2(PCSC_LOG_INFO, "No bundle files in pcsc drivers directory: %s", +			PCSCLITE_HP_DROPDIR); Log1(PCSC_LOG_INFO, "Disabling USB support for pcscd"); } </del>

Discussion:
The package installs that contains an unconfigured variable: This results in the following message in system journal: Obviously, not critical, but still this doesn’t sound right. The contains , so it looks like gets replaced by literal , but I am not sure where this happens or why. Steps to reproduce the behavior: There should be no unsubstituted variables in the installed unit. Maintainer information:
Looks like this line was upstream in 1.9.2 and the version in nixpkgs was upgraded from 1.9.1 to 1.9.4 in October ().
Ok, I am not particularly good with Autotools, but it seems to me that it is an upstream bug. The generate does this replacement, but I think it is supposed to happen only in a context in which this will be further expanded, not in plaintext files intended to be simply copied to their final install location.
Yes, it’s definitely an upstream issue. This usage of is explicitly called out as incorrect in Autconf docs:
Reported upstream:
Fixed in 1.9.5 (just released):
Keep in mind that this needs to point at if it is to be used for anything instead of into the nix store.
Can we make an option to allow specific ? I can help to make a PR if you agree : )
Send a PR I guess? Although, I am not sure how useful this option will be, given that, I assume, all other packages have to be linked to the same pcsc that provides the daemon. On the other hand, many other packages have this option, and I don’t know if there is some pattern or policy in NixOS.
The fixes PR is merged, but if a stable user (, etc.) wants to solve these issues, he could be: nix overlays, let = the package from newer channel, this will cause rebuild of all package that depends on it. to override attribute of , which is tedious and error-prone. So I suggest either we add an option to allow specific the package,or backport the changes to stable branch...?
Change:
livepeer = callPackage ../servers/livepeer { }; <ins> lldap = callPackage ../servers/ldap/lldap { }; </ins> lwan = callPackage ../servers/http/lwan { }; labelImg = callPackage ../applications/science/machine-learning/labelimg { };

Discussion:
Project description An lightweight authentication server that provides an opinionated, simplified LDAP interface for authentication: clients that can only speak LDAP protocol can talk to it and use it as an authentication server. Metadata homepage URL: source URL: license: platforms: unix
Here is what I came up with so far (with big help from :heart:):
I marked this as stale due to inactivity. &rarr;
Still relevant
I gave it a try in in case someone would like to take a look at it :)