jiebi/CodeConvo huggingface dataset:
Change:
--set NIX_REDIRECTS ${builtins.concatStringsSep ":" redirects}  --set LOCALE_ARCHIVE "${glibcLocales.out}/lib/locale/locale-archive"  "''${gappsWrapperArgs[@]}" <ins> # We need to replace the ssh-askpass-sublime executable because the default one # will not function properly, in order to work it needs to pass an argv[0] to # the sublime_merge binary, and the built-in version will will try to call the # sublime_merge wrapper script which cannot pass through the original argv[0] to # the sublime_merge binary. Thankfully the ssh-askpass-sublime functionality is # very simple and can be replaced with a simple wrapper script. rm $out/ssh-askpass-sublime makeWrapper $out/.${primaryBinary}-wrapped $out/ssh-askpass-sublime  --argv0 "/ssh-askpass-sublime" </ins> ''; }; in stdenv.mkDerivation (rec {

Discussion:
Describe the bug When using Sublime-Merge, pushing to remote results in an error message: To Reproduce Steps to reproduce the behavior: both sublime-merge and git. a repository. something, so that the local master is ahead of the remote. a push. Expected behavior A password prompt appears, and the push continues as normal. Additional context Some earlier discussion occurred in on the Sublime team's own github. We eventually found that the for sublime-merge seems to build, patch, and then discard a copy of . This may be the source of the issue. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Metadata Please run and paste the result. Output: Maintainer information:
Hi Thanks for letting me know, I've never tried entering a SSH passphrase directly through Sublime Merge before so I've never run into this issue, my ssh-agent just always handles it. I can say that the binary IS being included by the nix package and that the executable is finding and executing it properly (I confirmed this with strace), however for whatever reason the executable is just not creating the popup to ask for the passphrase and I don't understand why. I've followed up with the Sublime Merge team in , hopefully they will get back to me with some context about what the executable is looking for so that we can update the package to provide that.
So after discussing this with the helpful folks on the Sublime Merge repository, I was able to figure out what the problem is, it is happening because the functionality for actually depends on passing a special value as the to the executable. However the file that is trying to pass the to is actually a wrapper script that calls to run the actual binary after setting up the proper environment variables. There doesn't appear to be any way for the bash script to detect the argv[0] that was passed to bash as $0 is overwritten with the path to the bash script. I'm not sure how we will resolve this issue but at least we know what is causing it now. Maybe we can create a wrapper for the script that helps it execute the call properly against the un-wrapped binary or something.
Howdy , I created that should fix this issue. Would you be able to try this fix out yourself to see if it works for you?
Change:
postFixup = '' substituteInPlace "$out/bin/run-singularity"  --replace "/usr/bin/env ${projectName}" "$out/bin/${projectName}" <ins> # Respect PATH from the environment/the user. # Fallback to bin paths provided by Nixpkgs packages. </ins> wrapProgram "$out/bin/${projectName}"  <del> --prefix PATH : "$inputsDefaultPath" </del> <ins> --suffix PATH : "$systemDefaultPath"  --suffix PATH : "$inputsDefaultPath" </ins> # Make changes in the config file ${lib.optionalString forceNvcCli '' substituteInPlace "$out/etc/${projectName}/${projectName}.conf" 

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:
githubId = 11824817; name = "Marti Serra"; }; <ins> xworld21 = { email = "1962985+xworld21@users.noreply.github.com"; github = "xworld21"; githubId = 1962985; name = "Vincenzo Mantova"; }; </ins> xwvvvvwx = { email = "davidterry@posteo.de"; github = "xwvvvvwx";

Discussion:
Project description From the project website: "mftrace is a small Python program that lets you trace a TeX bitmap font into a PFA or PFB font (A PostScript Type1 Scalable Font) or TTF (TrueType) font." I came across it while trying to compile the . It doesn't seem to be used a lot, but it seems nice to have, and I have just packaged it for myself anyway. Working packaging attempt , just two notes: mftrace needs texlive at runtime only (it finds fonts via and uses metafont binaries), I have left it out so that it works with any installed texlive, but it's also broken if there is none, is that ok? I have not a maintainer! Metadata homepage URL: source URL: licenses: gpl2-only, free platforms: unix, windows (judging from the source – I have not tested it)
If it only needs a small texlive without many packages, it might be worth adding that to . Is there a part that's licensed under GPLv2? Besides that, you should use . Then nothing should stop a pull request from being merged.
Ok, I know which binaries are needed, I can try. If it doesn't work out, I'll add a comment. All of the python files are GPLv2 without the "any later version" text and COPYING is GPLv2. The C file has a custom free license from . The README claims that is licensed under the GPL (no version) with a generic link, but it's also a 15 years old line... I would err on the side of . Ah, sure! I suppose I can add myself to the maintainer list if nobody wants it. This should be a very low maintenance package anyway. I'll send a PR in a few days, after I have time to sort out the runtime binaries issue.
PR is up, with a few tweaks compared to my first attempt. Thanks for the pointers
Change:
<ins> { lib, python3 }: with python3.pkgs; buildPythonApplication rec { pname = "mutt-ics"; version = "0.9.2"; src = fetchPypi { inherit version; pname = "mutt_ics"; sha256 = "d44d4bec4e71c7f14df01b90fdb9563cdc784ece4250abfea5b0b675cfe85a50"; }; propagatedBuildInputs = [ icalendar ]; meta = with lib; { homepage = "https://github.com/dmedvinsky/mutt-ics"; description = "A tool to show calendar event details in Mutt"; license = licenses.mit; maintainers = with maintainers; [ mh182 ]; }; } </ins>

Discussion:
Project description A tool to show calendar event details in Mutt. Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin, (all platforms supporting Python)
Change:
"--disable-console" ]; <del> postInstall = '' # Remove seafile binary rm -rf "$out/bin/seafile" # Remove cli client binary rm -rf "$out/bin/seaf-cli" ''; </del> meta = with stdenv.lib; { homepage = https://github.com/haiwen/seafile; description = "Shared components of Seafile: seafile-daemon, libseafile, libseafile python bindings, manuals, and icons";

Discussion:
seafile-client 6.1.8 fails to build at cmake configuration step with the following error message: run
I've tried updating Seafile to 6.2.0, which supports Qt 5.11, here: However, I ran into an issue:
With Qt 5.11.1, the error is gone, but the current version is still incompatible with Qt 5.11.x:
Change:
, functools32, typing ? null , pytestCheckHook , pyaml <ins> , poetry-core </ins> }: buildPythonPackage rec { pname = "tomlkit"; <del> version = "0.11.6"; </del> <ins> version = "0.11.8"; format = "pyproject"; </ins> src = fetchPypi { inherit pname version; <del> hash = "sha256-cblS5XIWiJN/sCz501TbzweFBmFJ0oVeRFMevdK2XXM="; </del> <ins> hash = "sha256-kzD8f6odtntUGyjmIBjBfSC+czF30pChOyTGLRYU4MM="; </ins> }; <ins> nativeBuildInputs = [ poetry-core ]; </ins> propagatedBuildInputs = lib.optionals isPy27 [ enum34 functools32 ] ++ lib.optional isPy27 typing;

Discussion:
changed behaviour between nixos 22.11 and NixOS 23.05, apparently producing semantically different outputs (which broke our telegraf module) Bisect implies this is the commit that broke(?) remarshal: Was this intentional?
cc as maintainer of remarshal cc as author (I think?) of
Oh yeah that's definitely not intentional, at least from Nixpkgs side. It's unfortunate that we depend on a third-party for this.. We could pin to prevent such breakages, but we should definitely have a test case that covers this breakage.
Change:
useMoldLinker = stdenv: let bintools = stdenv.cc.bintools.override { extraBuildCommands = '' <del> wrap ld.mold ${../build-support/bintools-wrapper/ld-wrapper.sh} ${pkgs.mold}/bin/ld.mold wrap ld ${../build-support/bintools-wrapper/ld-wrapper.sh} ${pkgs.mold}/bin/ld.mold </del> <ins> wrap ${stdenv.cc.bintools.targetPrefix}ld.mold ${../build-support/bintools-wrapper/ld-wrapper.sh} ${pkgs.mold}/bin/ld.mold wrap ${stdenv.cc.bintools.targetPrefix}ld ${../build-support/bintools-wrapper/ld-wrapper.sh} ${pkgs.mold}/bin/ld.mold </ins> ''; }; in stdenv.override (old: {

Discussion:
is a fast and multi threaded modern linker. We already have it in Nixpkgs, however, unlike , it has not been wrapped in a package so that it can find the libraries to dynamically link against. Hence, dynamic linking in in NixOS fails. This issue is created so that we can wrap mold inside a shell script, like what happens to when it is installed through or even normal . I would be open to helping port such a script for .
I have tried simply replacing the executable with in the wrapper script, but it didn't seem to work. I am not very familiar with how this script works or what I am missing For more information, see
After some discussion on Matrix (thanks !), I was able to get mold working in a dev shell by using the following snippet: Is there any way we can just expose this as a wrapped mold in Nixpkgs so we don't have to add this to every shell we need mold in?
Is this relevant anymore? In addition to , we also have now. Here's a test we have for it in :
Further work is to rename to so users have to choose explicitly
Change:
, rustPlatform , fetchCrate , pkg-config <del> , libgit2_1_5 </del> <ins> , libgit2 </ins> , openssl , zlib , stdenv , Security <ins> , SystemConfiguration </ins> }: rustPlatform.buildRustPackage rec { pname = "cargo-audit"; <del> version = "0.18.3"; </del> <ins> version = "0.19.0"; </ins> src = fetchCrate { inherit pname version; <del> hash = "sha256-8KLH6aPZhHtxC4hbMaebv1JiVkZH8p5QqnUXkJrmr4w="; </del> <ins> hash = "sha256-NPRtSoITOS9i/v9hgdULVSmLaFbXZZeoO4SdqqANDxk="; </ins> }; <del> cargoHash = "sha256-8MOZvhREm4ch2flstx7J25j8mvwV3uGez5f1xkZ+S7I="; </del> <ins> cargoHash = "sha256-cQ2ZEZJ7PgNUxzZXR9Of1R5v2wu1b3xOlENu1DZU/rQ="; </ins> nativeBuildInputs = [ pkg-config ]; buildInputs = [ <del> libgit2_1_5 </del> <ins> libgit2 </ins> openssl zlib ] ++ lib.optionals stdenv.isDarwin [ Security <ins> SystemConfiguration </ins> ]; buildFeatures = [ "fix" ];

Discussion:
Steps to reproduce the behavior: libgit2 Just tried to update to current nixos-unstable but this build failure prevented that. <!-- 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 failure is not happening for me. I need more information about what you are building and how you are building it exactly.
Hi I'm observing this with
Suspect caused by
that could certainly be the case, I only tested libgit2 but I am removing all older libgit2 versions in which should also fix this issue
Sorry for missing that. It comes up when building cargo-update-13.3.0.
Yep - I noticed this because the latest version of crane doesn't work in all cases: cargo-audit can't be built on nixpkgs latest.
This due to the usage of system level http-parser instead of the bundled http-parser which handles . An easy fix that works: However, I am not sure what the other implications are when using the bundled version versus the system-wide version which was introduced .
Change:
, fontconfig , tzdata , nss <ins> , libgudev </ins> }: stdenv.mkDerivation rec {

Discussion:
Describe the bug In the Cinnmaon desktop manager, changing the screen brightness does not work. This is not a hardware support issue, does work. To Reproduce Steps to reproduce the behavior: Cinnamon DE the brightness down/up key no change in screen brightness Expected behavior Screen brightness changes, and maybe a nice popup which tells me what is happening (similar to the volume popup)? Additional context Worth noting is, that I found this in my session logs: Indeed, in the package quite a lot of relevant binaries seem to reside in , not in . Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(wucke13): nixpkgs: Maintainer information:
This is already supported, just the bug prevents it from working My problem is that for me it's a hardware issue since the light command doesn't work on this laptop, so I can't debug this properly
Issues seems csd-backlight-helper binary missing, link target does not exist
Yep, that is in fact the issue. From looking at it should for sure be there. From looking at , I think because libgudev is not in buildInputs (this is a guess), it was never compiled.
Perfect, I hope it'll get back-ported soon :)
Works now on 20.09 :+1:
Change:
cmt = callPackage ../applications/audio/cmt {}; codimd = callPackage ../servers/web-apps/codimd { <del> nodejs = nodejs-10_x; </del> <ins> nodejs = nodejs-12_x; </ins> }; colord = callPackage ../tools/misc/colord { };

Discussion:
Describe the bug Using sqlite as backend yields the following error How should sqlite be ? Should yarn be ran again? To Reproduce Notify maintainers Metadata Maintainer information:
I did some digging into why this does not work anymore and it seems that this probably did not work for a long time without anyone noticing (including me), even though this should have been caught by the test. The node module is built with using , but on startup I could see that node looks for the module with . Also according to node version 10 does not seem to be officially supported by . Adding.. ..directly after calling for does work, but I am pretty sure that this hack could have weird consequences during runtime :) Building codimd with node version 12, which is officially supported by sqlite3, is probably our best option here and I just successfully ran the test with it. I'll open a PR with the update later this evening. /cc
Working well now, thanks!
Change:
}; installPhase = '' <del> mkdir -p $out/lib/node_modules/three cp -r build version $out/lib/node_modules/three </del> <ins> mkdir -p "$out/lib/node_modules/three/" cp version "$out/lib/node_modules/three" cp -r build "$out/lib/node_modules/three/$(cat version)" </ins> ''; }

Discussion:
When using the viewer for plot3d, the generated html file contains the wrong path for Call the following code in sage Then your browser would open the generated file in . The browser console would report that Upon further inspection, the wanted file is actually at and upon loading the page with this update path, it works. A clear and concise description of what you expected to happen. 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. Maintainer information:
Thanks for the bug report. Unfortunately we can't use vanilla because it does not include some exports used by sage (see the README at ), but it looks like threejs-sage is indeed installed into the wrong directory. I will fix it today.
By the way, the threejs-sage installation directory was changed upstream in , which landed in 9.4. I missed this when updating Sage in .
Change:
the <literal>--keep-vm-state</literal> flag. </para> <programlisting> <del> $ ./result/bin/nixos-test-driver --interactive --keep-vm-state </del> <ins> $ ./result/bin/nixos-test-driver --keep-vm-state </ins> </programlisting> <para> The machine state is stored in the

Discussion:
When building an interactive test driver with and running the generated binary, the test just runs without an interactivity. Steps to reproduce the behavior: that the test just starts instead of displaying the interactive prompt. I'd expect to be dropped into the interactive prompt. cc as someone who's touched a lot.
Mostly reviews and minor additions though. Maybe broke it, but that's just a guess. Probably best to bisect with if going back to before that doesn't fix the problem.
Ah, it was broken by
Change:
<del> {stdenv, fetchurl, fetchpatch, which, nixosTests}: let s = # Generated upstream information rec { baseName="firejail"; version="0.9.62"; name="${baseName}-${version}"; url="mirror://sourceforge/firejail/firejail/firejail-${version}.tar.xz"; sha256="1q2silgy882fl61p5qa9f9jqkxcqnwa71jig3c729iahx4f0hs05"; }; buildInputs = [ which ]; in stdenv.mkDerivation { inherit (s) name version; inherit buildInputs; src = fetchurl { inherit (s) url sha256; name = "${s.name}.tar.bz2"; </del> <ins> { lib, stdenv, fetchFromGitHub, fetchpatch, which, xdg-dbus-proxy, nixosTests }: stdenv.mkDerivation rec { pname = "firejail"; version = "0.9.64.4"; src = fetchFromGitHub { owner = "netblue30"; repo = "firejail"; rev = version; sha256 = "sha256-q/XL8cznHlUXdubUEptEAVma1jRUqFb5XcLAV0RVCzs="; </ins> }; <ins> buildInputs = [ which ]; </ins> patches = [ <del> (fetchpatch { name = "CVE-2020-17367.patch"; url = "https://github.com/netblue30/firejail/commit/2c734d6350ad321fccbefc5ef0382199ac331b37.patch"; sha256 = "1gxz4jxp80gxnn46195qxcpmikwqab9d0ylj9zkm62lycp84ij6n"; }) (fetchpatch { name = "CVE-2020-17368.patch"; url = "https://github.com/netblue30/firejail/commit/34193604fed04cad2b7b6b0f1a3a0428afd9ed5b.patch"; sha256 = "0n4ch3qykxx870201l8lz81f7h84vk93pzz77f5cjbd30cxnbddl"; }) </del> # Adds the /nix directory when using an overlay. # Required to run any programs under this mode. ./mount-nix-dir-on-overlay.patch

Discussion:
Describe the bug Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(user): nixpkgs: Maintainer information:
Seems like updating to 0.9.64.4 is the way to go?
Can be closed?!
Change:
python, sip, which, <ins> buildPackages, </ins> # runtime cairo,

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:
postFixup = '' wrapQtApp "$out/bin/gns3" ''; <ins> postPatch = '' substituteInPlace requirements.txt  --replace "sentry-sdk==1.3.1" "sentry-sdk>=1.3.1"  ''; </ins> meta = with lib; { description = "Graphical Network Simulator 3 GUI (${branch} release)";

Discussion:
On nixos-unstable, the package does not install: is installed No maintainer but pinging who last touched Please run and paste the result.
was updated to 4.0.1 a while back. is pinning most of it's dependencies thus the issue. Looks like that could need an update (available 2.2.18, upstream 2.2.27).
So I can build the upgraded package with the following: But it doesn't look right. I guess we shouldn't blindly replace pinned versions with incompatible versions. How does nixpkgs usually deals with this?
Change:
libgksu = callPackage ../development/libraries/libgksu { }; <ins> libgnt = callPackage ../development/libraries/libgnt { }; </ins> libgpgerror = callPackage ../development/libraries/libgpg-error { }; # https://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgpg-error.git;a=blob;f=README;h=fd6e1a83f55696c1f7a08f6dfca08b2d6b7617ec;hb=70058cd9f944d620764e57c838209afae8a58c78#l118

Discussion:
Looks like there has been a new release this year: maintainer: cc it adds XDG portal support, which might be necessary for screen sharing on phosh and other Wayland clients.
PR:
I marked this as stale due to inactivity. &rarr;
Change:
]; propagatedBuildInputs = with python3Packages; [ <del> requests psutil </del> dnspython <ins> netifaces psutil python-dateutil requests rich </ins> ]; checkPhase = ''

Discussion:
Steps to reproduce the behavior: I'm using Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Just a heads-up that the latest stable is and has dropped python2 support.
Change:
(fetchNuGet { pname = "BouncyCastle.Cryptography"; version = "2.2.1"; sha256 = "13fx7cg5hmk2y33438wjz0c74c0lvbmh8fa33gwldldmf72mwcr8"; }) (fetchNuGet { pname = "CommandLineParser"; version = "2.9.1"; sha256 = "1sldkj8lakggn4hnyabjj1fppqh50fkdrr1k99d4gswpbk5kv582"; }) (fetchNuGet { pname = "CsvHelper"; version = "30.0.1"; sha256 = "0v01s672zcrd3fjwzh14dihbal3apzyg3dc80k05a90ljk8yh9wl"; }) <del> (fetchNuGet { pname = "Dinah.Core"; version = "7.2.2.1"; sha256 = "1mh0jy9mdkv416lyg0b34wqacq9gjbp0gzy7p6dw0kdm5mcrrf4k"; }) (fetchNuGet { pname = "Dinah.Core"; version = "7.3.0.1"; sha256 = "0zgbd40xn411hcl357pc93xilgs5ah91paqn0rmm5j93mbrcixlm"; }) (fetchNuGet { pname = "Dinah.EntityFrameworkCore"; version = "7.3.0.1"; sha256 = "1gx1980sx9gjas44x6i3gbyxcfqbv16fy792dqly3y558pibv2zp"; }) </del> <ins> (fetchNuGet { pname = "Dinah.Core"; version = "8.0.0.1"; sha256 = "1kfnc7bfs6bmy41rvnybhpfwrd2p4rjgg8jzzajk7v7smci1m04d"; }) (fetchNuGet { pname = "Dinah.EntityFrameworkCore"; version = "8.0.0.1"; sha256 = "1125s6lypmk447d6pba6kn5r82c552l6ck54a7mgaa9n2448lcn5"; }) </ins> (fetchNuGet { pname = "DynamicData"; version = "7.9.5"; sha256 = "1m9qx8g6na5ka6kd9vhg8gjmxrnkzb6v5cl5yqp1kdjsw4rcwy6x"; }) (fetchNuGet { pname = "Enums.NET"; version = "4.0.1"; sha256 = "13r5dvs86v86mvq4lrv1nqs3841w623nn054miyz2fp5nacs0db5"; }) (fetchNuGet { pname = "HarfBuzzSharp"; version = "2.8.2.3"; sha256 = "115aybicqs9ijjlcv6k6r5v0agkjm1bm1nkd0rj3jglv8s0xvmp2"; })

Discussion:
Package name: libation Latest released version: 11.3.1 <!-- Search your package here: --- Current version on the unstable channel: 11.1.0 Current version on the stable/release channel: 11.1.0 <!-- 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:
inherit (python3Packages) sphinx; }; <ins> rmw = callPackage ../tools/misc/rmw { }; </ins> rng-tools = callPackage ../tools/security/rng-tools { }; rnnoise = callPackage ../development/libraries/rnnoise { };

Discussion:
Project description rmw (ReMove to Waste) is a trashcan/recycle bin utility for the command line. It can move and restore files to and from directories specified in a configuration file, and can also be integrated with your regular desktop trash folder (if your desktop environment uses the Trash specification). One of the unique features of rmw is the ability to purge items from your waste (or trash) directories after x number of days. Metadata homepage URL: https://remove-to- source URL: license: gpl3+ platforms: unix, linux, darwin, bsd