jiebi/CodeConvo huggingface dataset:
Change:
url = "https://github.com/thestinger/vte-ng/commit/342e26574f50dcd40bbeaad9e839c2a6144d0c1c.patch"; sha256 = "1b0k9ys545q85vfki417p21kis9f36yd0hyp12phayynss6fn715"; }) <del> (fetchpatch { name = "0002-expose-function-for-setting-cursor-position.patch"; url = "https://github.com/thestinger/vte-ng/commit/5ae3acb69474fe5bc43767a4a3625e9ed23607a1.patch"; sha256 = "091sb44g2pl0zbxnxidpfmsqqc65dmkakhjb0wvlnsjckqalhs89"; }) (fetchpatch { name = "0003-add-function-for-setting-the-text-selections.patch"; url = "https://github.com/thestinger/vte-ng/commit/742d57ecf15e24f6a5f2133a81b6c70acc8ff03c.patch"; sha256 = "12rq3svbj1nzridbssxsvmmb8njky3w8qdnkymz7850b3kqg277x"; }) </del> <ins> # Derived from https://github.com/thestinger/vte-ng/commit/5ae3acb69474fe5bc43767a4a3625e9ed23607a1.patch ./vte-ng-modified-patches/vte-0002-expose-function-for-setting-cursor-position.patch # Derived from https://github.com/thestinger/vte-ng/commit/742d57ecf15e24f6a5f2133a81b6c70acc8ff03c.patch ./vte-ng-modified-patches/vte-0003-add-function-for-setting-the-text-selections.patch </ins> (fetchpatch { name = "0004-add-functions-to-get-set-block-selection-mode.patch"; url = "https://github.com/thestinger/vte-ng/commit/08748fd9cb82bd191e5c476b1682ca71f7732572.patch"; sha256 = "1cnhd8f7ywdgcyd6xmcd2nn39jjxzkxp4d0zsj2k7m5v74nhcs1g"; }) <del> (fetchpatch { name = "0005-expose-function-for-getting-the-selected-text.patch"; url = "https://github.com/thestinger/vte-ng/commit/dd74ae7c06e8888af2fc090ac6f8920a9d8227fb.patch"; sha256 = "0pbnbkwqxm4p9xsgvqwayvh8srk5z1kyjnigmahf9mlqn7hi6v27"; }) </del> <ins> # Derived from "https://github.com/thestinger/vte-ng/commit/dd74ae7c06e8888af2fc090ac6f8920a9d8227fb.patch"; ./vte-ng-modified-patches/vte-0005-expose-function-for-getting-the-selected-text.patch </ins> ]; });

Discussion:
Describe the bug When building termite, one of the patches fails to apply. To Reproduce Steps to reproduce the behavior: Screenshots Notify maintainers Metadata system: host os: multi-user?: sandbox: version: nixpkgs: Maintainer information:
Upstream hasn't updated the vte-ng patchset past 0.56 (I guess the same patches happened to work up until 0.62?), looks like it's ~unmaintained -- perhaps we should just keep vte 0.60 around for vte-ng?
Nevermind, it was actually pretty easy to update - PRing
Change:
# A hack to make `nix-env -qa` and `nix search` ignore broken packages. # TODO(@oxij): remove this assert when something like NixOS/nix#1771 gets merged into nix. name = assert validity.handled; name + lib.optionalString <del> (stdenv.hostPlatform != stdenv.buildPlatform) </del> <ins> # Fixed-output derivations like source tarballs shouldn't get a host # suffix. But we have some weird ones with run-time deps that are # just used for their side-affects. Those might as well since the # hash can't be the same. See #32986. (stdenv.hostPlatform != stdenv.buildPlatform && runtimeSensativeIfFixedOutput) </ins> ("-" + stdenv.hostPlatform.config); builder = attrs.realBuilder or stdenv.shell;

Discussion:
I'm currently working on bringing up my cross-compilation environment. The latest issue is that fails to build when cross-compiling with: Note the name of the source archive: . The target suffix means that 's setup hooks fails to fire: It's not obvious to me how best to solve this. There are several options: generalize the setup hook (and others) to catch names with such suffixes the original filename to files fetch with and teach the unpacker hooks to use this instead of the derivation name teach the splicer not to add a suffix to source archives else
Pinging
and I discussed this via IRC, The conclusion is that we will simply avoid adding a host suffix for fixed-output derivations without host runtime dependencies (e.g. like source tarballs).
For the record, I work around this in bgamari/nixpkgs
Just was hit by this myself, is this still the preferred workaround?
I've never hit this personally, but should finish up. Feel free to give it a shot!
Change:
sri_get() { local ouput sri output=$(nix-build  --expr  <del> 'with import <nixpkgs>{}; </del> <ins> "with import $nixpkgs {}; </ins> fetchurl { <del> url = "'"$1"'"; }' 2>&1 || true) </del> <ins> url = "$1"; }" 2>&1 || true) </ins> sri=$(echo "$output" | awk '/^s+got:s+/{ print $2 }') [[ -z "$sri" ]] && err "$output" echo "$sri"

Discussion:
Package name:warp-terminal Latest released version: <!-- Search your package here: --- Current version on the unstable channel:v0.2024.03.12.08.02.stable01 Current version on the stable/release channel:0.2023.11.07.08.02.stable00 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
''; serviceConfig = { ExecStart = '' <del> ${pkgs.jre}/bin/java -Xmx${toString cfg.maxMemory}m  </del> <ins> ${pkgs.jre8}/bin/java -Xmx${toString cfg.maxMemory}m  </ins> -Dairsonic.home=${cfg.home}  -Dserver.address=${cfg.listenAddress}  -Dserver.port=${toString cfg.port} 

Discussion:
Describe the bug The Airsonic service fails to start. To Reproduce Steps to reproduce the behavior: = true; to your config. reveals the following error: Cannot load configuration class: which causes the application to enter a restart loop. <details<summaryError trace</summary<p</p</detailsExpected behavior It doesn't error, and instead runs successfully. Additional context It doesn't seem to be due to an Airsonic update that this started to fail, so my guess is that something got changed with the JRE. I think Airsonic will only work with JDK 8 (see: ), but I'm not very familiar with how Java works, so I'm not sure. Notify maintainers Metadata Fails on both of the following systems: Maintainer information:
Change:
hushboard = python3.pkgs.callPackage ../applications/audio/hushboard { }; <ins> husky = callPackage ../development/tools/misc/husky { }; </ins> hydrogen = qt5.callPackage ../applications/audio/hydrogen { }; hydrogen_0 = callPackage ../applications/audio/hydrogen/0.nix { }; # Old stable, has GMKit.

Discussion:
Project description Modern native git hooks made easy Husky improves your commits and more woof! You can use it to lint your commit messages, run tests, lint code, etc... when you commit or push. Husky supports . Zero dependencies and lightweight (6 kB) Powered by modern new Git feature (core.hooksPath) Follows and best practices regarding autoinstall User-friendly messages Optional install Like husky 4, supports macOS, Linux and Windows Git GUIs Custom directories Monorepos Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin, windows
Change:
mkdir -p $out cp -R conf docs lib ${name}.jar $out mkdir -p $out/bin <del> cp -R bin/{zkCli,zkCleanup,zkEnv}.sh $out/bin </del> <ins> cp -R bin/{zkCli,zkCleanup,zkEnv,zkServer}.sh $out/bin </ins> for i in $out/bin/{zkCli,zkCleanup}.sh; do wrapProgram $i  --set JAVA_HOME "${jre}"  --prefix PATH : "${bash}/bin" done <ins> substituteInPlace $out/bin/zkServer.sh  --replace /bin/echo ${coreutils}/bin/echo  --replace "/usr/bin/env bash" ${bash}/bin/bash </ins> chmod -x $out/bin/zkEnv.sh mkdir -p $out/share/zooinspector

Discussion:
We currently have a nice ZooKeper module and package, but apparently all the cool kids run ZK via , which we don't have packaged or any module around. Anyone feel like packaging and/or writing a module for it? cc who have dealt with ZK
I would like to own this. Thank you for bringing this up.
Let's assign it to you then &ndash; informally, as GitHub only allows that for organization members (or some similar condition).
Thanks
is this happening?
Sorry for the delay. Yes I am working on this.
any progress?
FYI, I took a crack at this in
Change:
quickemu, testers, installShellFiles, <del> fetchpatch2, </del> }: let runtimePaths = [

Discussion:
Package name: quickemu Latest released version: 4.9.5 <!-- Search your package here: --- Current version on the unstable channel: 4.9.4 Current version on the stable/release channel: 4.9.5 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --fedx- Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
# See https://github.com/cyberus-technology/virtualbox-kvm/issues/12 assert enableKvm -> !enableHardening; <ins> # The web services use Java infrastructure. assert enableWebService -> javaBindings; </ins> with lib; let

Discussion:
Steps to reproduce the behavior: following configuration: # nixos-rebuild switch <!-- 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]:
~ tells me the first bad commit was . I'm not sure if this is correct, because this commit is a qemu version bump (). This build failure can also be seen in the pull request: EDIT: I've tried building it again on another machine and it worked. I think a file somehow got corrupted on the other machine, because the build contains strange errors like and Additionally, was set to false.
Notify maintainers:
your are more then welcome to fix it and create a PR
The issue seems to be that we use a JDK that doesn't have anymore. See also: Can you check whether this PR ( ) fixes things for you? Ideally, if you could run on that PR, I'd be super grateful!
Sorry for the delay. The PR worked, I can with the configuration above. Thanks for the work.
Hi, I'm afraid I'm still experiencing this issue even though the changes landed in . Would anyone mind taking a look at my (shortened for brevity) to see what I did wrong? Thanks!
Change:
schemaspy = callPackage ../development/tools/database/schemaspy { }; <ins> scenebuilder = callPackage ../development/tools/scenebuilder { }; scenic-view = callPackage ../development/tools/scenic-view { }; </ins> shncpd = callPackage ../tools/networking/shncpd { }; sigrok-cli = callPackage ../development/tools/sigrok-cli { };

Discussion:
Project description Scene Builder is a drag n drop layout tool for designing JavaFX application user interfaces. It is now distributed under 3-clause BSD License, without the need of registration or manually accept EULAs. There was a pull request when it had not been open-sourced (). Now it would be easier to package. Metadata homepage URL: source URL: license: bsd3 platforms: unix
I marked this as stale due to inactivity. &rarr;
I am still looking forward to this one.
If you're still interested, you could build scenebuilder from my PR linked above, test if it works for you or if I missed anything and report your results there.
Change:
lib.concatStringsSep " " [ "--replace-fail" (addShellDoubleQuotes (lib.escapeShellArg originalDefaultPath)) <del> (addShellDoubleQuotes ''$inputsDefaultPath''${inputsDefaultPath:+:}${lib.escapeShellArg originalDefaultPath}'') </del> <ins> (addShellDoubleQuotes ''$systemDefaultPath''${systemDefaultPath:+:}${lib.escapeShellArg originalDefaultPath}''${inputsDefaultPath:+:}$inputsDefaultPath'') </ins> ] ) originalDefaultPaths }

Discussion:
Nixpkgs's package of Sylabs SingularityCE () now fails to execute image. After initial examination, the known cause is the failure to substitute default FHS s for some files, but the fix is WIP. Steps to reproduce the behavior: error. should succeed. If applicable, add screenshots to help explain your problem. 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]:
singularity isn't supposed to work without setuid?
Yup. The error seems to result from failure to replace all the default paths after source file hierarchy changes.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
sha256 = "0i19c6krc0p9krwrqy9s5xahaafigqzxcn31piidmlaqadyn4f8r"; }; <ins> patches = [ (fetchpatch { url = "https://github.com/dbry/WavPack/commit/26cb47f99d481ad9b93eeff80d26e6b63bbd7e15.patch"; name = "CVE-2018-10536-CVE-2018-10537.patch"; sha256 = "0s0fyycd4x7pw4vl1yp2vp4zrlk04j85idvnxz5h96fj6196anw6"; }) (fetchpatch { url = "https://github.com/dbry/WavPack/commit/6f8bb34c2993a48ab9afbe353e6d0cff7c8d821d.patch"; name = "CVE-2018-10538-CVE-2018-10539-CVE-2018-10540.patch"; sha256 = "03qzmaq9mwiqbzrx1lvkgkhz3cjv7dky1b4lka3d5q2rwdlyw5qk"; }) (fetchpatch { url = "https://github.com/dbry/WavPack/commit/d5bf76b5a88d044a1be1d5656698e3ba737167e5.patch"; name = "CVE-2018-6767.patch"; sha256 = "158c60i188kbxl0hzb7g74g21pknz7fk429vnbbx9zk1mlyyyl5b"; }) (fetchpatch { url = "https://github.com/dbry/WavPack/commit/bf408e95f43fafdcef42c3f5f9c9d0e6ab0331b9.patch"; name = "CVE-2019-11498-1.patch"; sha256 = "161dw759v1lzbhj7daw2gbmcji8s0njpa65xmqhqw73bwpzb3xkd"; }) (fetchpatch { url = "https://github.com/dbry/WavPack/commit/cd353bccafb1274a525c3536aaff8c48c3a33aa0.patch"; name = "CVE-2019-11498-2.patch"; sha256 = "120sb1iqkq2gadh0qydqvca4vwx31zb7gk1d0nm0y5agav2ai0dk"; }) (fetchpatch { url = "https://github.com/dbry/WavPack/commit/4c0faba32fddbd0745cbfaf1e1aeb3da5d35b9fc.patch"; name = "CVE-2019-11498-3.patch"; sha256 = "12744yn1035mf7wzgqrkyadw5mwqf9v34ckj2m5sirk97k47k0wa"; }) (fetchpatch { url = "https://github.com/dbry/WavPack/commit/bc6cba3f552c44565f7f1e66dc1580189addb2b4.patch"; name = "CVE-2019-11498-4.patch"; sha256 = "0qdw071b14hmxkjw6kn83d8hzq89l3hqh64pl1f1wb8m51w5xfg7"; }) ]; </ins> meta = with stdenv.lib; { description = "Hybrid audio compression format"; homepage    = http://www.wavpack.com/;

Discussion:
, (nixos-unstable) (nixos-unstable) (nixos-unstable) (nixos-unstable) (nixos-unstable) (nixos-unstable) (nixos-unstable) Scanned versions: nixos-unstable: . May contain false positives.
I can't see this reported for 19.03, but the version is the same, so I cherry-picked that PR anyway.
Change:
inherit (common) src; <ins> patches = [ # Fix for ghostscript>=9.27 # Backport of # https://github.com/mgieseki/dvisvgm/commit/bc51951bc90b700c28ea018993bdb058e5271e9b ./dvisvgm-fix.patch # Needed for ghostscript>=9.50 (fetchpatch { url = "https://github.com/mgieseki/dvisvgm/commit/7b93a9197b69305429183affd24fa40ee04a663a.patch"; sha256 = "1gmj76ja9xng39wxckhs9q140abixgb8rkrcfv2cdgq786wm3vag"; stripLen = 1; extraPrefix = "texk/dvisvgm/dvisvgm-src/"; }) ]; </ins> nativeBuildInputs = [ pkgconfig ]; # TODO: dvisvgm still uses vendored dependencies <del> buildInputs = [ core/*kpathsea*/ ghostscript zlib freetype potrace xxHash ]; </del> <ins> buildInputs = [ core/*kpathsea*/ ghostscript zlib freetype /*potrace xxHash*/ ]; </ins> preConfigure = "cd texk/dvisvgm";

Discussion:
I was getting errors with the version of dvisvgm bundled with texlive 2019 so I created a separate, texlive-independent version which works well. (If you're curious about the issue I was seeing it was related to compatibility between ghostscript and dvisvgm. I can be more specific if anyone wants, but reporting that issue is not the main purpose of this). Here's the build expression I'm using ( is ): How would people feel about a PR with a dvisvgm package uncoupled from the texlive version in addition to the one currently there? I could name it or or something like that. Note that I'm currently using this as a separate build expression but for a PR I'd put it in the texlive bin nix file. Note also that this package can be used identically to any other texlive package. The only difference to the end user is to get an option of a newer version.
What is the issue, though?
it's been reported . The issue is apparently fixed in dvisvgm 2.7.2 (ours is 2.6.3). Here's an additional MWE to test. The same example with v2.8.1 (in the build expression above) works fine.
So what you say, is that our dvisvgm is broken because of the incompatible ghostscript version. Then, I think, we should be fixing dvisvgm for all of our users, not just those who opt into using the separate package you propose. I would prefer to just patch the version from texlive, but, unfortunately, doesn't apply cleanly, so we would have to craft our own patch or pin to 2.8.1 (in this case, need to leave a TODO comment to remind to unpin for texlive 2020).
To clarify, the idea is to generate a patch from a newer texlive version of dvisvgm and apply that to the existing derivation (along with the code comment about this being a temporary fix until 2020)?
Does fix the issue for you?
Change:
}; testScript = '' <del> machine.succeed("findmnt --kernel --type overlay /etc") machine.fail("stat /etc/newgen") </del> <ins> with subtest("/etc is mounted as an overlay"): machine.succeed("findmnt --kernel --type overlay /etc") </ins> <del> machine.succeed("/run/current-system/specialisation/new-generation/bin/switch-to-configuration switch") </del> <ins> with subtest("switching to the same generation"): machine.succeed("/run/current-system/bin/switch-to-configuration test") </ins> <del> assert machine.succeed("cat /etc/newgen") == "newgen" </del> <ins> with subtest("switching to a new generation"): machine.fail("stat /etc/newgen") machine.succeed("/run/current-system/specialisation/new-generation/bin/switch-to-configuration switch") assert machine.succeed("cat /etc/newgen") == "newgen" </ins> ''; }

Discussion:
Steps to reproduce the behavior: /run/current-system/bin/switch-to-configuration test Does not crash system/systemd This can be reproduced using this test in sops-nix: Edit to have this change <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
Related to
It seems like it's reusing the same loop device when mounting the new overlay...
Change:
{ "owner": "zammad", "repo": "zammad", <del> "rev": "eefae45c2ad6e6a96b8df631d2f50f290ecbd27d", "sha256": "EjowvM//+UsAfEH9/0jgLkiD7EWH34M1NQ9U2DotBqc=", </del> <ins> "rev": "d71bd90ef964426230664cdfbaa2572325bfed4f", "sha256": "yzDTkjnRBl71REtSKRblkanJWhj7gp/+exhWjxGCFWw=", </ins> "fetchSubmodules": true }

Discussion:
, CVSSv3=7.5 (nixos-unstable) CVSSv3=7.5 (nixos-unstable) A lack of password length restriction in Zammad v5.1.0 allows for the creation of extremely long passwords which can cause a Denial of Service (DoS) during password verification. A lack of rate limiting in the 'forgot password' feature of Zammad v5.1.0 allows attackers to send an excessive amount of reset requests for a legitimate user, leading to a possible Denial of Service (DoS) via a large amount of generated e-mail messages. Scanned versions: nixos-unstable: . Cc Cc Cc
Change:
easeprobe = callPackage ../tools/misc/easeprobe { }; emscripten = callPackage ../development/compilers/emscripten { <del> llvmPackages = llvmPackages_18; </del> <ins> llvmPackages = llvmPackages_git; </ins> }; emscriptenPackages = recurseIntoAttrs (callPackage ./emscripten-packages.nix { });

Discussion:
Package name: emscripten Latest released version: 3.1.57 <!-- Search your package here: --- Current version on the unstable channel: 3.1.51 Current version on the stable/release channel: 3.1.47 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
tl;dr: 3.1.57 is not currently compatible with the version of llvm in tree (18.1.5). The latest compatible version with llvm 18.1.5 appears to be Emscripten 3.1.54. The emscripten nixpkg (3.1.51) currently uses an LLVM17 environment which needs be migrated to LLVM18. The configuration as it exists today doesn't work in some cases. (Godot4.3dev6 web template builds failed missing in , prompting finding this issue) Emscripten 3.1.51 seems to be compatible with the LLVM 18.1.5 currently in nixpkgs unstable. Emscripten 3.1.59 (current as of this comment) and 3.1.57 are not compatible with that version of LLVM (In my usage, ran into errors with and ). These flags were introduced in Emscripten 3.1.55 making the last compatible version against the current in-tree dependencies 3.1.54. <details<summaryThis override was able to successfully build the godot4.3dev6 web templates using Emscripten 3.1.54</summary<p</p</details
Change:
gammu-smsd = 228; pdnsd = 229; octoprint = 230; <ins> avahi-autoipd = 231; </ins> # When adding a uid, make sure it doesn't match an existing gid. And don't use uids above 399!

Discussion:
To reproduce: create new (ethernet) connection, with ip4 set to link-local. When ing the connection, the following errors are thrown: An reveals the problem: I thought the following would fix it (): but this creates a new problem:
add that new user when NM is enabled in the nixos module.
Did suggestion work? I was just bitten by this issue.
Did not try it futher yet. If you want you can try it.
Change:
src = fetchurl { name = "vscode-server-${rev}.tar.gz"; url = "https://update.code.visualstudio.com/commit:${rev}/server-linux-x64/stable"; <del> sha256 = "100nhm231gzav24lz84vxwxnqkn777kfn0fkkjmdcd30kc7g7ig9"; </del> <ins> sha256 = "17563d413czlqpy3921gq5ja7mi3lgb8yjgvsqfn3fkaj70gr1hq"; </ins> }; };

Discussion:
Package name: vscode Latest released version: <!-- Search your package here: --- Current version on the unstable channel: 1.88.1 Current version on the stable/release channel: 1.85.2 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. -- Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
genericName = "Chat with your friends (matrix client)"; categories = [ "Chat" "Network" "InstantMessaging" ]; }; buildInputs = [ gtk3 libsecret jsoncpp ]; nativeBuildInputs = [ autoPatchelfHook wrapGAppsHook imagemagick ];

Discussion:
Fluffychat cannot use e2e encryption in the new version. Sorry everyone, I, and the new fluffychat version, broke this. Working on the fix