jiebi/CodeConvo huggingface dataset:
Code change:
wrapArgs="$wrapArgs --prefix PATH : $dep/bin" done wrapArgs="$wrapArgs --prefix PATH : ${gnused}/bin" <ins> wrapArgs="$wrapArgs --set HOME : /homeless-shelter" </ins> wrapProgram $out/bin/$name $wrapArgs }

Related discussion:
text: is non-deterministic if given both and . Here are a couple runs back-to-back: However, when I make this and :
Interestingly, itself is deterministic, despite being non-deterministic (at least from the command line). This is pretty curious.
Perhaps environment variables come into play? Does the shell script take care to clear the environment like a nix build does?
So, I tried diffing two of the outputs: That looks an awful lot like part of my git hooks that automatically generate tags. Sure enough: I'm of the opinion that we should override in the package, to prevent these kinds of problems. Thoughts?
Seems like those scripts in general should almost completely clear out your environment
Yeah, I don't know how much to get rid of, considering that someone may want to get the hash of their private repos or something.
Code change:
# NOTE: You must also bump: # <nixpkgs/pkgs/development/python-modules/libvirt/default.nix> # SysVirt in <nixpkgs/pkgs/top-level/perl-packages.nix> <del> version = "8.5.0"; </del> <ins> version = "8.6.0"; </ins> src = fetchFromGitLab { owner = pname; repo = pname; rev = "v${version}"; <del> sha256 = "sha256-x6TnMFYjcUSdQZd9ctN2hITCAl9TGVb7/qAObGb9xMk="; </del> <ins> sha256 = "sha256-bSId7G2o808WfHGt5ioFEIhPyy4+XW+R349UgHKOvQU="; </ins> fetchSubmodules = true; };

Related discussion:
text: When attempting to create a volume on a physical node pool parted is not found. Steps to reproduce the behavior: Create a physical disk node pool. Attempt to create a volume using that node pool. In this case I have created a node pool called and I am attempting to create a volume called Volume is created normally. If applicable, add screenshots to help explain your problem. I have tried to add parted manually using and overriding the package in the libvirtd module: but this did not fix the issue.
That won't work, it seems like we need to wrap to include in its . I'll take a look.
You most likely need to add it to in because libvirtd will probably call it.
Code change:
# NOTE: You must also bump: # <nixpkgs/pkgs/development/python-modules/libvirt/default.nix> # SysVirt in <nixpkgs/pkgs/top-level/perl-packages.nix> <del> version = "8.5.0"; </del> <ins> version = "8.6.0"; </ins> src = fetchFromGitLab { owner = pname; repo = pname; rev = "v${version}"; <del> sha256 = "sha256-x6TnMFYjcUSdQZd9ctN2hITCAl9TGVb7/qAObGb9xMk="; </del> <ins> sha256 = "sha256-bSId7G2o808WfHGt5ioFEIhPyy4+XW+R349UgHKOvQU="; </ins> fetchSubmodules = true; };

Related discussion:
text: I sometimes create a qemu VM in libvirt in "session mode", meaning that the libvirt daemon is running as my non-root user, and the system-wide libvirtd does not need to be running (). This VM has a network bridge, which libvirt apparently creates by calling , which in turn uses . The problem is that doesn't get fully populated until the system libvirtd gets started. Previously, in nixpkgs (from February), this wasn't noticeable because libvirtd.service was WantedBy libvirt-guests.service (which is WantedBy multi-), so libvirtd would always be started on boot to populate that directory. Now, with , this is no longer the case, and libvirtd.service does not get started (presumably, if libvirt-guests.service actually needed to start a VM, then libvirtd.service would be socket-activated, but for me this is not the case). As a result, doesn't get populated and my session-mode libvirt can't find . python: The VM's XML file defines a network bridge, which is why gets involved. the following output: The libvirt user session should be usable without first starting the system-wide libvirtd. If you start (and optionally stop) the system libvirtd.service before following the steps to reproduce, everything works fine, because the directory gets populated. Probably, should be put somewhere else, where session-mode daemons can use it without needing to have previously started system-mode libvirtd. (The same may be true of other stuff in too.) libvirt maintainers: Okay, but I'm using flakes and that channel looks old. See relevant commit hashes above.
Oof, happy to find this, it would have taken me a long time to figure out I needed to run first. Can't the sudo wrapper point to the file in the nix store?
Code change:
, sassc , udisks2 , wrapGAppsHook <ins> , libX11 , libXext , libXNVCtrl </ins> }: stdenv.mkDerivation rec { pname = "monitor"; <del> version = "0.11.0"; </del> <ins> version = "0.12.0"; </ins> src = fetchFromGitHub { owner = "stsdc"; repo = "monitor"; rev = version; <del> sha256 = "sha256-xWhhjn7zk/juXx50wLG2TpB5aqU+588kWBBquWrVJbM="; </del> <ins> sha256 = "1fv98yz9393ddp0k96bwbgccy6x9dmmg8g1pjd3xs6m4c1bnvfc7"; </ins> fetchSubmodules = true; };

Related discussion:
text: <!-- You can use the "Go to file" functionality on github to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the the current version of the package --- <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- name: <!-- The current version can be found easily with the same process than above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: desired version: <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: are you already working on it? if not i can do it
I have some exams to take tomorrow, so maybe I cannot open a PR in 17 hours. Feel free to open one if you have done the update.
I just wanted to make sure you haven't started to work on it, so we don't do duplicate work. I wish you great success with the exams!
Just also have a try on this, fails with . Actually I have no idea what happened so I just opened , downstream workaround should be something like , actually this seems to work, builds and launches. <img src="https://user-" width=50%Also I noticed that we maybe need in , haven't tested yet.
downstream workaround should be something like , actually this seems to work, builds and launches. i don't understand what it does, but it works Also I noticed that we maybe need in , haven't tested yet. I noticed before that the indicators do not work. I'll try it.
Code change:
''; # Register some undeclared runtime dependencies to be patched in by autoPatchelfHook <ins> # Note: dyalog.rt is used internally to run child APL processes in </ins> preFixup = '' <del> patchelf ${dyalogHome}/dyalog --add-needed libncurses.so </del> <ins> for exec in "dyalog" "dyalog.rt"; do patchelf ${dyalogHome}/$exec --add-needed libncurses.so done </ins> '' + lib.optionalString htmlRendererSupport '' patchelf ${dyalogHome}/libcef.so --add-needed libudev.so --add-needed libGL.so

Related discussion:
text: Isolates parallelEach doesn't work Steps to reproduce the behavior: run nix develop with then run: dyalog then in the dyalog repl type ⎕DL isolate.llEach (1 2 3) returning like its the case when using the .deb on lets say a debian host strace log reveals a lot of lines like which does not happen on a debian host when I install dyalog 19 via dpkg -i I have also tested this on a debian host that has nix installed and installed dyalog via nix instead of dpkg but I run into the same issue making me believe there is something wrong with the drv system: "x86_64-linux", multi-user?: yes, version: nix-env (Nix) 2.18.2, nixpkgs: /etc/channels/nixpkgs (I ran it against the current (1 hour ago) nixpkgs master/unstable branches) as in I pulled these 2 about 1 hour ago
I'll see what I can do about this. In the meantime, could you change the issue title to start with ?
sure
Phew, finally found it! The issue was with the class, which auto-crashed when created. I redirected its output to a file, and it turns out that because I didn't patch to require it wasn't able to load it, thus erroring out.
This is awesome, thanks for the incredibly fast response/fix time. I suspected it was something like this I initially thought that maybe some of the libraries weren't copied over since the nix expression is a little pickier than just cp *.so $out/lib but upon fixing that nothing change really. Usually knowing when to apply patchelf is quite clear as software will let you know if a library is missing so throwing ldd against it generally gives some pretty good insight. Though if you'd like sharing this information, would you mind telling me how you found out? Was it just intuition or did you use some sort of tool to debug it to come to the conclusion that this may be the issue. As i couldn't really get hold of logs making any sense when I tried it. This would be quite interesting to me as I most likely will get to fix more dyalog stuff in the future.
Code change:
''; # Register some undeclared runtime dependencies to be patched in by autoPatchelfHook <ins> # Note: dyalog.rt is used internally to run child APL processes in </ins> preFixup = '' <del> patchelf ${dyalogHome}/dyalog --add-needed libncurses.so </del> <ins> for exec in "dyalog" "dyalog.rt"; do patchelf ${dyalogHome}/$exec --add-needed libncurses.so done </ins> '' + lib.optionalString htmlRendererSupport '' patchelf ${dyalogHome}/libcef.so --add-needed libudev.so --add-needed libGL.so

Related discussion:
text: First of all, I somehow got my hand on the file that lists where it crashed exactly, then looked through it, found the definitions in the namespace explorer. It looked like it was supposed to start some processes and then connect to them, however they exited immediately. I was able to verify this by printing in . is an array of new objects, so I looked up the docs, and it turns out you can specify an OutFile, which specifies where a process should dump its logs (its the 5th parameter of ), so I overrode that to point to some known location. That file contained the following: In was required by the binary, so took care of it. However in they probably changed it to load dynamically using which can't be auto-detected with . I had to use with the normal binary to make it work, but I didn't know what was so I didn't do anything with it. Note: in a new binary named appeared, however I don't know where it's used, so I don't know what I should do with it. Might have to ask around for it.
thanks for taking the time to outline how you came to that conlcusion im sure that will help me in the future. Sorry for forgetting to close this its closed now
Well, the fix isn't merged yet, so I think that this issue staying open was not a problem.
oh sorry I forgot as I used the branch locally and then after many weeks I saw its still opened and somehow was under the assumption that it was merged. Sorry I skipped that
Code change:
nativeBuildInputs = [ file pkgconfig gnupg autoreconfHook git texinfo ] ++ lib.optionals pythonSupport [ python swig2 which ncurses ]; <ins> patches = [ (fetchpatch { name = "fix-key-expiry.patch"; url = "https://files.gnupg.net/file/data/fehgbjmataj5tc2pnfhj/PHID-FILE-aqck6l4elhw53tjanrie/file"; sha256 = "1h80m045gy7r0g7dzzlfpql6p065x88p274ij9jnf7d4lwwgrf1a"; }) ]; </ins> postPatch ='' substituteInPlace ./configure --replace /usr/bin/file ${file}/bin/file '';

Related discussion:
text: (this is a qt specific test): Loc: [t-(458)] PASS : TofuInfoTest::cleanupTestCase() Totals: 7 passed, 1 failed, 0 skipped, 0 blacklisted, 1047ms This seems to affect master too, but for some reason it's been built successfully once. The aarch64 build started failing when updating qt5 from 5.11 to 5.12 making it the likely root cause: Edit: the cause was expired testing keys: cc maintainer cc as you've been active in keeping plasma/kde up to date lately. ping staging next:
Did you found ? Sounds very similar and should be fixed...
No didn't find that, but yeah, that sure looks exactly like the same issue. I'm guessing the qt issue were never actually fixed: Blame on the test gives no change at least:
And applying the suggested patch does fix the test: diff +++ gpgme-1.10.0/lang/qt/tests/t- -455,7 +455,7 private Q_SLOTS: QVERIFY(result.numSignatures() == 1); auto sig = result.signatures()[0]; QVERIFY(sig.validity() == Signature::Marginal); QVERIFY(sig.validity() == Signature::Marginal sig.validity() == Signature::Unknown); auto stats = ().userID(0).tofuInfo(); QVERIFY(!stats.isNull());
So, what are we want to do? Do you maybe want to comment on the upstream issue?
Hmm, strange, I'm getting the same failure on master (using ), forcing single core does not fix the problem though, so probably not a race condition. I've reported the failure as you suggested:
The cause is most likely qt 5.11 to 5.12 upgrade, as the aarch64 build started failing the test then:
So the keys used in this test expired on 2019-01-06, which explains why we suddenly saw this without any apparent reason. :
Thanks for fixing this and sorry for my late reply... (Edit: And of course also thanks
Code change:
, stdenv , rustPlatform , fetchFromGitHub <ins> , installShellFiles , pkg-config </ins> , libxcb <del> # Darwin dependencies </del> <ins> , openssl # Darwin dependencies </ins> , AppKit }: rustPlatform.buildRustPackage rec { pname = "didyoumean"; <del> version = "1.1.0"; </del> <ins> version = "1.1.3"; </ins> src = fetchFromGitHub { owner = "hisbaan"; repo = "didyoumean"; rev = "v${version}"; <del> sha256 = "sha256-t2bmvz05vWIxQhC474q/9uky1kAQoFN8Z+qflw5Vj68="; </del> <ins> sha256 = "sha256-hHl9PGNDFN7Dad2JOlAy99dz0pC9OmphwYMJHBBwx7Y="; </ins> }; <del> cargoSha256 = "sha256-4DbziI9enib4pm9/P4WEu15glIxtejaV2GCqbzuxxyw="; </del> <ins> cargoSha256 = "sha256-rjkj9MO6fXVOk3fA87olGt/iIaJ8Zv/cy/Cqy/pg6yI="; </ins> <del> buildInputs = lib.optional stdenv.isLinux [ libxcb ] ++ lib.optionals stdenv.isDarwin [ AppKit ]; </del> <ins> nativeBuildInputs = [ installShellFiles ] ++ lib.optionals stdenv.isLinux [ pkg-config ]; buildInputs = lib.optionals stdenv.isLinux [ libxcb openssl ] ++ lib.optionals stdenv.isDarwin [ AppKit ]; postInstall = '' installManPage man/dym.1 installShellCompletion completions/dym.{bash,fish} installShellCompletion --zsh completions/_dym ''; # Clipboard doesn't exist in test environment doCheck = false; </ins> meta = with lib; { description = "A CLI spelling corrector for when you're unsure"; homepage = "https://github.com/hisbaan/didyoumean"; license = licenses.gpl3Plus; <del> maintainers = with maintainers; [ evanjs ]; </del> <ins> maintainers = with maintainers; [ evanjs wegank ]; </ins> mainProgram = "dym"; }; }

Related discussion:
text: name: didyoumean current version: 1.1.0 desired version: 1.1.3 maintainers: Version 1.1.3 comes with a man page as well as shell completions for a few shells (bash, zsh, fish, elvish). I'd like to have the script install these. I'm more than willing to do the actual update myself, but I'm very new to Nix, so I'll probably need some guidance, specifically on how to install these completions and the man page, and how to update the hash. Thanks!
To update the hashes, simply set and , and update them as suggested by . Having done it right, you'll haveTo install the man page and the shell completions, setYou may also need to set on some platforms (at least on ?). Before doing this, feel free to make a pull request.
I'm running into some issues trying to test it to ensure it's doing what I want it to. I'm going to the directory with in it and running but I'm running into issues regarding being undefined: Any pointers? I wasn't able to find anything searching through the web
needs to be in the attrset at the top of the file for you to be able to use it.
As explained, we need to add at the top of the file.
Code change:
}; }.${stdenv.hostPlatform.system} or (throw "Unsupported system: ${stdenv.hostPlatform.system}"); <del> nativeBuildInputs = [ autoPatchelfHook dpkg makeBinaryWrapper wrapGAppsHook3 ]; </del> <ins> nativeBuildInputs = [ autoPatchelfHook dpkg makeShellWrapper wrapGAppsHook3 ]; </ins> dontWrapGApps = true;

Related discussion:
text: ArmCord's wrapper seems unable to launch under Wayland, always chooses to launch under Steps to reproduce the behavior: sure and are properly set: Armcord: . ... 's on XWayland (as shown by ). I expect it to launch with Wayland instead of XWayland. Custom wrapper: Test case: Log output: <!-- 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]:
probably need makeShellWrapper instead of makeBinaryWrapper in the package
Thanks for jumping on a PR will review this evening.
Code change:
echo "Publishing plugin $1" dotnet publish $1 -p:ContinuousIntegrationBuild=true -p:Deterministic=true  --output $out/lib/ArchiSteamFarm/plugins/$1 --configuration Release  <del> -p:TargetLatestRuntimePatch=false -p:UseAppHost=false --no-restore  --framework=net7.0 </del> <ins> -p:TargetLatestRuntimePatch=false -p:UseAppHost=false </ins> } buildPlugin ArchiSteamFarm.OfficialPlugins.ItemsMatcher

Related discussion:
text: Looks like it now uses .NET 8 which probably made all existing plugins incompatible - Package name: ArchiSteamFarm Latest released version: 5.5.0.11 <!-- Search your package here: --- Current version on the unstable channel: 5.4.13.4 Current version on the stable/release channel: 5.4.12.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. --Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
The package/module has no official way to use plugins, so there is no way to use them unless people are using overlays which should be constructed in a smart way to re-use the same methods as archisteamfarm does. Anyway, here is the update
Code change:
stdenv.mkDerivation rec { pname = "bluemail"; <del> version = "1.136.21-1884"; </del> <ins> version = "1.140.8-1922"; </ins> # Taking a snapshot of the DEB release because there are no tagged version releases. # For new versions, download the upstream release, extract it and check for the version string. # In case there's a new version, create a snapshot of it on https://archive.org before updating it here. src = fetchurl { <del> url = "https://archive.org/download/blue-mail-1.136.21-1884/BlueMail.deb"; hash = "sha256-L9mCUjsEcalVxzl80P3QzVclCKa75So2sBG7KjjBVIc="; </del> <ins> url = "https://web.archive.org/web/20240208120704/https://download.bluemail.me/BlueMail/deb/BlueMail.deb"; hash = "sha256-dnYOb3Q/9vSDssHGS2ywC/Q24Oq96/mvKF+eqd/4dVw="; </ins> }; <ins> desktopItems = [ (makeDesktopItem { name = "bluemail"; icon = "bluemail"; exec = "bluemail"; desktopName = "BlueMail"; comment = meta.description; genericName = "Email Reader"; mimeTypes = [ "x-scheme-handler/me.blueone.linux" "x-scheme-handler/mailto" ]; categories = [ "Office" ]; }) ]; </ins> nativeBuildInputs = [ autoPatchelfHook <ins> copyDesktopItems </ins> makeWrapper dpkg wrapGAppsHook

Related discussion:
text: When installed through Nix, Bluemail does not create a desktop shortcut in $out/share/applications. The program can only be run through the terminal by default. The program also fails to load unless the --disable-gpu-sandbox option is used. Steps to reproduce the behavior: Bluemail by adding to , and rebuild. for Bluemail in the Application Launcher - not present in terminal - core dumps on gpu process not usable in terminal - bluemail opens with the default wayland icon What currently happens is detailed step-by-step above. What I'd expect to happen is that a desktop icon is created when I rebuild to install bluemail, and that clicking the application from the Application Launcher opens bluemail without a core dump. Installing from NixOS-Unstable Running on Intel UHD Graphics (10th Gen)
Code change:
<del> { lib, stdenv, fetchFromGitHub, pkg-config, avahi, libsoup, libjpeg </del> <ins> { lib, stdenv, fetchFromGitHub, pkg-config, avahi, libsoup, libjpeg, libpng </ins> , sane-backends, meson, ninja }: stdenv.mkDerivation rec { pname = "sane-airscan"; <del> version = "0.9.17"; </del> <ins> version = "0.99.0"; </ins> nativeBuildInputs = [ meson ninja pkg-config ]; <del> buildInputs = [ avahi libsoup libjpeg sane-backends ]; </del> <ins> buildInputs = [ avahi libsoup libjpeg libpng sane-backends ]; </ins> src = fetchFromGitHub { owner = "alexpevzner"; repo = pname; rev = version; <del> sha256 = "03y0c1z5s3wbvxa9nvji62w42cmvcgm2sw72j7wm831995q3abmx"; </del> <ins> sha256 = "0bbw3s95v5fmkpmmd26v9cf1c40dm85bgxlhs06ski5my803ck0a"; </ins> }; meta = with lib; {

Related discussion:
text: Describe the bug SANE does not find the backend To Reproduce Steps to reproduce the behavior: backend to the error Expected behavior SANE loads the airscan backend. Screenshots Listing of symlinks to SANE-Backends: Additional context is missing the version suffix, so SANE does not use the library. The issue has been fixed on upstream master, but no new version has been released yet. Should we just update the package via commit-hash (it's still in early development anyhow), or wait for the next release for updating it? Using in my local nixpkgs fixes the problem. Notify maintainers Metadata Maintainer information:
I will quickly get in touch with the maintainer of to see if he can cut another release for us. It feels important enough to cut a bugfix release ;) thanks for taking the time for writing such a detailed explanation!
Code change:
<ins> diff --git a/tests/test_strpdatetime.py b/tests/test_strpdatetime.py index 6c371d6..a3d0232 100644 --- a/tests/test_strpdatetime.py +++ b/tests/test_strpdatetime.py @@ -44,5 +44,4 @@ TEST_DATA = [ @pytest.mark.parametrize("string, format, expected", TEST_DATA) def test_datetime_strptime(string, format, expected): """Test datetime_strptime""" -    locale.setlocale(locale.LC_ALL, "en_US.UTF-8") assert strpdatetime(string, format) == expected </ins>

Related discussion:
text: Project description Python app to work with pictures and associated metadata from Apple Photos on macOS. Also includes a package to provide programmatic access to the Photos library, pictures, and metadata. Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
This was the most complex package i ever tried to write :sweat_smile:
Code change:
nativeBuildInputs = [ pkg-config <del> ] ++ lib.optionals atLeast24 [ </del> autoconf-archive autoreconfHook bison flex jq <del> ] ++ lib.optionals (atLeast24 && enableDocumentation) [ </del> <ins> ] ++ lib.optionals (enableDocumentation && !atLeast24) [ libxslt libxml2 docbook_xsl_ns docbook5 ] ++ lib.optionals (enableDocumentation && atLeast24) [ </ins> (lib.getBin lowdown) mdbook ] ++ lib.optionals (atLeast213 && enableDocumentation) [

Related discussion:
text: Package name: nix23 Latest released version: 2.3.17 (see ) Current version on the unstable channel: 2.3.16 Current version on the stable/release channel: 2.3.16 Notify maintainers Note for maintainers: Please tag this issue in your PR. See for context. The release script apparently doesn't upload source tarballs anymore, so 2.3.17 sources look more like the other ones. There's a bunch of expressions in that might need to be revisited.