jiebi/CodeConvo huggingface dataset:
Change:
nativeBuildInputs = [ cmake ninja <ins> wrapGAppsHook </ins> wrapQtAppsHook ];

Discussion:
I encountered this error when attempting to open files from qBittorrent: It's working fine on . Steps to reproduce the behavior: Run nix shell nixpkgs#qbittorrent. Open qBittorrent. Navigate to Files -Add torrent files. The app crashes. It should open my File Manager. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Seems to be a case of the first error in the . Would you mind trying out
Change:
else nix; <del> stable = addFallbackPathsCheck self.nix_2_18; </del> <ins> stable = addFallbackPathsCheck self.nix_2_19; </ins> unstable = self.nix_2_19; } // lib.optionalAttrs config.allowAliases {

Discussion:
Package name: nix Latest released version: 2.19.2 Current version on the unstable channel: 2.18.1 Current version on the stable/release channel: 2.18.1 Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --After the NixOS 23.11 release, I checked the nix website and also saw the latest nix version is . When I run: My nix version doesn't get updated. After running I found that points to . Is this update not automated during releases? I couldn't find much information about this other than seeing one merged PR where gets introduced to . Can we upgrade the expression to asap so upgrades to properly. What I currently get:
Don't know much about the Nix release process but I'm using on unstable to fix Not sure if it's stable yet since 2.19.2 gives me these warnings when rebuilding:
Change:
''; patches = optional enableHardening ./hardened.patch <del> ++ [ ./qtx11extras.patch ./linux-4.14.patch ]; </del> <ins> ++ [ ./qtx11extras.patch ]; </ins> postPatch = '' sed -i -e 's|/sbin/ifconfig|${nettools}/bin/ifconfig|' 

Discussion:
In a lot of cases, upstream sources or releases become unavailable (e.g. grsecurity) or even get modified (e.g. texlive) which breaks the package in older versions of nixpkgs. It would be nice to duplicate the sources via a torrent. This doesn't involve any trust, because the hash of the sources is known beforehand and would allow older nixpkgs to work as long as someone uses the desired package.
We've discussed a before but have mostly resisted because unless we build deep support for it into a persistent Nix daemon, as we could implement today would be a terrible "torrent citizen", and would never seed. Probably more promising is to build support for IPFS into Nix itself. See discussion at and Either way, I don't think most of the work would happen inside nixpkgs, so if you think the above issues don't cover what you want, I'd suggest posting more information on the Nix issue tracker rather than in here.
FWIW I had an experimental via but dropped it because of the same reasons -- it'd be an awful "torrent citizen".
Actually, the ipfs issue seems to be exactly what I wanted, so I'll close this issue.
can you share your please? I'm currently thinking about packaging the program where using aria2c for install is an official way to install
moved to PR <detailspkgs/build-
Change:
<ins> diff --git a/libqtile/core/lifecycle.py b/libqtile/core/lifecycle.py index 0d4d119d..c37d1799 100644 --- a/libqtile/core/lifecycle.py +++ b/libqtile/core/lifecycle.py @@ -25,7 +25,7 @@ class LifeCycle: def _atexit(self) -> None: if self.behavior is Behavior.RESTART: -            argv = [sys.executable] + sys.argv +            argv = sys.argv if "--no-spawn" not in argv: argv.append("--no-spawn") argv = [s for s in argv if not s.startswith("--with-state")] @@ -33,7 +33,7 @@ class LifeCycle: argv.append("--with-state=" + self.state_file) logger.warning("Restarting Qtile with os.execv(...)") # No other code will execute after the following line does -            os.execv(sys.executable, argv) +            os.execv(sys.argv[0], argv) elif self.behavior is Behavior.TERMINATE: logger.warning("Qtile will now terminate") elif self.behavior is Behavior.NONE: </ins>

Discussion:
In , the patch was removed. Without this patch, trying to restart qtile just kills it and goes to the display manager, closing all of your apps. Steps to reproduce the behavior: into qtile any key combination to to press this combination Qtile restarts without closing any apps Qtile just quits and goes to the DM Maintainer information:
This patch can fix the issue
I think most of this can be done in the wrapper. I was hoping that buildenv would solve the issue as the python interpreter would have all of the dependencies it would need.
I dug a little deeper and found the cause to be the following: Qtile restarts with sys.executable, which leads to the following full command on my machine (ignore the package name, not important here): This results in a syntax error So it's trying to execute a bash script through python, which leads to a syntax error. I see some related issues on nixpkgs, , Do you have any idea how to continue? Edit: To add, we could re-introduce a patch like this (this is for current qtile master) But the whole idea was that we wanted to get rid of the patches :/
I'm okay with doing minor patches like that. It was just before were were modifying the entry point significantly. But I'm also not a qtile user, was just trying to get qtile to a more recent version. If you want to create a PR, I'll be happy to review it.
Change:
quart-cors = callPackage ../development/python-modules/quart-cors { }; <ins> quaternion = callPackage ../development/python-modules/quaternion { }; </ins> qudida = callPackage ../development/python-modules/qudida { }; querystring_parser = callPackage ../development/python-modules/querystring-parser { };

Discussion:
Project description This package creates a quaternion type in python, and further enables numpy to create and manipulate arrays of quaternions. The usual algebraic operations (addition and multiplication) are available, along with numerous properties like norm and various types of distance measures between two quaternions. There are also additional functions like “squad” and “slerp” interpolation, and conversions to and from axis-angle, matrix, and Euler-angle representations of rotations. The core of the code is written in C for speed. Metadata homepage URL: source URL: license: mit, platforms: unix, linux, darwin, python
Change:
hunt = callPackage ../tools/misc/hunt { }; hypr = callPackage ../applications/window-managers/hyprwm/hypr { <del> cairo = cairo.override { xcbSupport = true; }; </del> <ins> cairo = cairo.override { xcbSupport = true; };  }; hyprland = callPackage ../applications/window-managers/hyprwm/hyprland { stdenv = gcc12Stdenv; wlroots = pkgs.callPackage ../applications/window-managers/hyprwm/hyprland/wlroots.nix { }; udis86 = pkgs.callPackage ../applications/window-managers/hyprwm/hyprland/udis86.nix { }; </ins> }; <del> hyprland = callPackage ../applications/window-managers/hyprwm/hyprland { }; </del> <ins> hyprland-protocols = callPackage ../applications/window-managers/hyprwm/hyprland-protocols { }; hyprland-share-picker = libsForQt5.callPackage ../applications/window-managers/hyprwm/xdg-desktop-portal-hyprland/hyprland-share-picker.nix { }; </ins> <del> hyprpaper = callPackage ../applications/window-managers/hyprwm/hyprpaper { }; </del> <ins> hyprpaper = callPackage ../applications/window-managers/hyprwm/hyprpaper { stdenv = gcc12Stdenv; }; hyprpicker = callPackage ../applications/window-managers/hyprwm/hyprpicker { }; </ins> hysteria = callPackage ../tools/networking/hysteria { };

Discussion:
Project description A wlroots-compatible Wayland color picker that does not suck. Metadata homepage URL: source URL: license: platforms: linux Just because you made available on NixOS, I wanted to point you on hyprpicker, too - if you're interested to have a look into this(?)
I'll take a look into packaging this.
Change:
<ins> { stdenv, fetchurl, bison, re2c, scons }: let version = "4.5.4"; in stdenv.mkDerivation rec { name = "gringo-${version}"; src = fetchurl { url = "mirror://sourceforge/project/potassco/gringo/${version}/gringo-${version}-source.tar.gz"; sha256 = "16k4pkwyr2mh5w8j91vhxh9aff7f4y31npwf09w6f8q63fxvpy41"; }; buildInputs = [ bison re2c scons ]; patches = [ ./gringo-4.5.4-cmath.patch ./gringo-4.5.4-to_string.patch ]; buildPhase = '' scons WITH_PYTHON= --build-dir=release ''; installPhase = '' mkdir -p $out/bin cp build/release/gringo $out/bin/gringo ''; meta = with stdenv.lib; { description = "Converts input programs with first-order variables to equivalent ground programs"; homepage = http://potassco.sourceforge.net/; platforms = platforms.linux; maintainers = [ maintainers.hakuch ]; license = licenses.gpl3Plus; }; } </ins>

Discussion:
The OCaml package manager () depends on an external solver. When the package was updated, it changed the compiler configuration, and a dependent package () of the solver () no longer compiled. The fix () uses a different monolithic package of the solver and its various tools (called "clingo") that for unknown reasons breaks : Install and attempt to run . System: Nix version: Nixpkgs version:
Change:
# function for creating a working environment from a set of TL packages combine = import ./combine.nix { inherit bin combinePkgs buildEnv lib makeWrapper writeText <del> stdenv python3 ruby perl gnused gnugrep coreutils; </del> <ins> stdenv python3 ruby perl gnused gnugrep coreutils libfaketime; </ins> ghostscript = ghostscriptX; # could be without X, probably, but we use X above };

Discussion:
Building this package twice does not produce the bit-by-bit identical result each time, making it harder to detect CI breaches. You can read more about this at https://reproducible- . nix-build '<nixpkgs' -A --check --keep-failed You can use to analyze the differences in the output of the two builds. To view the build log of the build that produced the artifact in the binary cache: nix-store --read-log $(nix-instantiate '<nixpkgs' -A ) Tested on nixpkgs Notably the ordering of the words in and similar seem nondeterministic, perhaps the other differences are effects of that.
That is an issue with , respectively the tools called by , so it should be solved upstream.
fmtutil here is coming from texlive-scripts in - but it's the output of that's not reproducible. I'm now sure it's in dumping out the hyphenation exception strings in the (random) order in which they appear in the lua hashtable. I guess we should sort them in dictionary order. There is already a qsort routine, so perhaps we should put the exceptions in an array, sort that array using qsort, and only produce the result from that.
I think this is already referring to .
Huh! Indeed that covers the same issue - I did search before digging into this problem, but not good enough apparently :laughing: .
Change:
checkPhase = '' runHook preCheck <del> python -m pytest -v -x -W always </del> <ins> python -m pytest -v -x -W always${stdenv.lib.optionalString stdenv.isDarwin " --deselect=Tests/test_file_icns.py::TestFileIcns::test_save --deselect=Tests/test_imagegrab.py::TestImageGrab::test_grab"} </ins> runHook postCheck '';

Discussion:
Updated channel and seeing build failures identical to those reported on hydra starting Jun 6: latest builds: first broken: tail of first broken: Dependency graph here is nixops- -python2.7-datadog- -python2.7-Pillow- Tagging those involved in the spate of recent pillow issues since neither of the listed maintainers were involved and I assume this is related:
I think this might be related to the changes I made, and it looks like froze at 6.2.2 after I changed the expression. Maybe if we replace the current (frozen) with the contents of the , this might be enough to resolve the issue.
Change:
</para> </listitem> <listitem> <ins> <para>Core version changes:</para> <para>gcc: 8.3.0 -&gt; 9.2.0</para> <para>glibc: 2.27 -&gt; 2.30</para> <para>linux: 4.19 -&gt; 5.4</para> <para>mesa: 19.1.5 -&gt; 19.3.3</para> <para>openssl: 1.0.2u -&gt; 1.1.1d</para> </listitem> <listitem> <para>Desktop version changes:</para> <para>plasma5: 5.16.5 -&gt; 5.17.5</para> <para>kdeApplications: 19.08.2 -&gt; 19.12.3</para> <para>gnome3: 3.32 -&gt; 3.34</para> <para>pantheon: 5.0 -&gt; 5.1.3</para> </listitem> <listitem> </ins> <para> Linux kernel is updated to branch 5.4 by default (from 4.19). Users of Intel GPUs may prefer to explicitly set branch to 4.19 to avoid some regressions.

Discussion:
I have read the release notes of 20.03, here are the things i noticed: Linux kernel is updated to branch 5.4 by default (from 4.19). Users of Intel GPUs may prefer to explicitly set branch to 4.19 to avoid some regressions. Can you add a link to an open issue to see when it is fixed? At least link to "more information" e.g.: Not all entries are services. Maybe "Modules" would be more accurate? If we decide to change it, apply it to all NixOS releases. Some services are listed here, but they where just moved. For example: Best would be to update the tooling to exclude moved files and update it. The services.dnscrypt-proxy module has been removed as it used the deprecated version of dnscrypt-proxy. We've services.dnscrypt- to use the supported version. can't it be a drop-in replacement? it would be more user friendly if the new version would just be used with services.dnscrypt-proxy (i don't know the software, so it might makes sense) Update: This seems fine since the options have changed completely. It has option now. Maybe mention that the options have changed. Like "options are now organized using a settings option" or something like that to make it really clear fixed small typo myself (backported in )
I was hoping to do/address all these things :+1:
Change:
<ins> { lib , appimageTools , fetchurl , makeWrapper , gtk3 , gsettings-desktop-schemas , pname , version , hash , metaCommon ? { } }: let pname = "losslesscut"; src = fetchurl { url = "https://github.com/mifi/lossless-cut/releases/download/v${version}/LosslessCut-linux-x86_64.AppImage"; inherit hash; }; extracted = appimageTools.extractType2 { inherit pname version src; }; in (appimageTools.wrapType2 { inherit pname version src; profile = '' export LC_ALL=C.UTF-8 ''; extraPkgs = ps: appimageTools.defaultFhsEnvArgs.multiPkgs ps; extraInstallCommands = '' mv $out/bin/{${pname}-${version},losslesscut} ( mkdir -p $out/share cd ${extracted}/usr find share -mindepth 1 -type d -exec mkdir -p $out/{} ; find share -mindepth 1 -type f,l -exec ln -s $PWD/{} $out/{} ; ) ln -s ${extracted}/losslesscut.png $out/share/icons/losslesscut.png mkdir $out/share/applications cp ${extracted}/losslesscut.desktop $out/share/applications substituteInPlace $out/share/applications/losslesscut.desktop  --replace AppRun losslesscut source "${makeWrapper}/nix-support/setup-hook" wrapProgram "$out/bin/losslesscut"  --add-flags "--disable-seccomp-filter-sandbox" ''; meta = metaCommon // { platforms = [ "x86_64-linux" ]; mainProgram = "losslesscut"; }; }) // { inherit pname version; } </ins>

Discussion:
Losslesscut crashes at startup due to missing Steps to reproduce the behavior: # crash # works Losslesscut works out-of-the-box. probably just needs a in .
It seems to come from a sandboxing feature of Chromium. (LosslessCut is an Electron app, and Electron uses Chromium, IIUC.) I'll add the flag when I'm available. Should it be to both the Linux and the Darwin binary, or just to the former?
I was only able to test on Linux. While you're at it: When bumping the version, filenames need a change (only tested for Linux): and is still open.
Thank you for reminding! After a quick test, 3.43.0 does run out-of-the-box on my machine Does it crash because the user namespaces is unavailable? Does the same problem happen to , it is another electron app packaged the same way. Does it happen to itself?
I can confirm that it works ootb on NixOS 21.11, but not on 22.05. Caprine crashes in a similar way on NixOS 22.05: Chromium works on both.
How about onlyoffice-bin? If does work, it might have something to do with .
works on 22.05
I'm working on it, but couldn't find a way to call in . To be exact, I don't know how to inject the dependency , a setup hook, into the builder. How should I do it? Thanks a lot for your patience.
Is this issue still relevant?
Last time I checked: Yes. I've got this still on my list and will close in case it is resolved.
It should now be fixed in .
Confirmed.
Change:
inherit sha256; }; <ins> cargoLock = { lockFile = ./Cargo.lock; outputHashes = { "crossbeam-epoch-0.9.5" = "sha256-Jf0RarsgJiXiZ+ddy0vp4jQ59J9m0k3sgXhWhCdhgws="; "ntapi-0.3.7" = "sha256-G6ZCsa3GWiI/FeGKiK9TWkmTxen7nwpXvm5FtjNtjWU="; }; }; patches = [ # Fix: https://github.com/solana-labs/solana/issues/34203 # From https://github.com/Homebrew/homebrew-core/pull/156930/files#diff-f27c55b86df31cd4935c956efee1be743eae0958e3850f3f9891d51bfea50b1cR76 ./account-info.patch ]; </ins> strictDeps = true; cargoBuildFlags = builtins.map (n: "--bin=${n}") solanaPkgs;

Discussion:
Package name: solana-cli Latest released version: 1.16.27 <!-- Search your package here: --- Current version on the unstable channel: 1.14.23 Current version on the stable/release channel: 1.14.23 <!-- 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]:
Hello I was able make the building script work so solana-cli is updated to 1.16.27 expect solana has bug in a which doesn't let me compile. The issue was already reported back back in 22 november 2023: solana-labs/solana So until is fixed I can't do anything more, as soon as it is fixed I will post my pr
Thanks , did you manage to build it for the current version? () On the master of nixpkgs I couldn't even build the existing version of Solana due a rocksdb issue I also found this commit on homebrew PRs. Seems like they patched this part in order to make the build work:
Hello I didn't test it and I don't think I need since I made it able to compile 1.16.27 I appreciate the citation, with the patch used by them I was able to fix it, appreciate your help
Change:
meta = with stdenv.lib; { description = "A command line tool for transferring files with URL syntax"; homepage    = https://curl.haxx.se/; <del> maintainers = with maintainers; [ lovek323 ]; </del> license = licenses.curl; <ins> maintainers = with maintainers; [ lovek323 ]; </ins> platforms = platforms.all; }; }

Discussion:
, CVSSv3=9.8 (nixos-20.03) Scanned versions: nixos-20.03: . May contain false positives.
Fixed in
Change:
<del> { stdenv, fetchurl, makeWrapper, autoPatchelfHook, dpkg </del> <ins> { stdenv, fetchurl, makeWrapper, wrapGAppsHook, autoPatchelfHook, dpkg </ins> , xorg, atk, glib, pango, gdk_pixbuf, cairo, freetype, fontconfig, gtk3 , gnome2, dbus, nss, nspr, alsaLib, cups, expat, udev, libnotify, xdg_utils }:

Discussion:
Seems to be related to and Try to open a folder with vscode. system: host os: multi-user?: sandbox: version: channels(root): channels(okina): nixpkgs:
VSCode still crashes for me when attempting to open a folder. I am using the unstable channel and I've uninstalled, collected garbage, reinstalled without any improvement.
The unstable channel hasn't really updated yet, or at least it hasn't for me.
Change:
callPackage ./generic.nix { } rec { pname = "signal-desktop"; dir = "Signal"; <del> version = "7.16.0"; </del> <ins> version = "7.17.0"; </ins> url = "https://updates.signal.org/desktop/apt/pool/s/signal-desktop/signal-desktop_${version}_amd64.deb"; <del> hash = "sha256-DfPQb3TGhVVZ7webNoMmyhjhRKKO3lWf12ZIpi7D7tc="; </del> <ins> hash = "sha256-4Yp81aBY01cVZ/KDSqPO3R3HglLup/+sczQ5XNtQn84="; </ins> }

Discussion:
Package name: signal-desktop Latest released version: <!-- Search your package here: --- Current version on the unstable channel: 7.16.0 Current version on the stable/release channel: 7.16.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:
makeWrapper ]; <ins> # See https://github.com/clojure/brew-install/blob/1.10.1/src/main/resources/clojure/install/linux-install.sh </ins> installPhase = let binPath = stdenv.lib.makeBinPath [ rlwrap jdk ]; in '' <del> mkdir -p $out/libexec cp clojure-tools-${version}.jar $out/libexec cp example-deps.edn $out cp deps.edn $out cp exec.jar $out </del> <ins> clojure_lib_dir=$out bin_dir=$out/bin echo "Installing libs into $clojure_lib_dir" install -Dm644 deps.edn "$clojure_lib_dir/deps.edn" install -Dm644 example-deps.edn "$clojure_lib_dir/example-deps.edn" install -Dm644 exec.jar "$clojure_lib_dir/libexec/exec.jar" install -Dm644 clojure-tools-${version}.jar "$clojure_lib_dir/libexec/clojure-tools-${version}.jar" echo "Installing clojure and clj into $bin_dir" </ins> substituteInPlace clojure --replace PREFIX $out <ins> install -Dm755 clojure "$bin_dir/clojure" install -Dm755 clj "$bin_dir/clj" </ins> <del> install -Dt $out/bin clj clojure wrapProgram $out/bin/clj --prefix PATH : $out/bin:${binPath} wrapProgram $out/bin/clojure --prefix PATH : $out/bin:${binPath} </del> <ins> wrapProgram $bin_dir/clojure --prefix PATH : $out/bin:${binPath} wrapProgram $bin_dir/clj --prefix PATH : $out/bin:${binPath} </ins> installManPage clj.1 clojure.1 '';

Discussion:
Describe the bug The nix install of clojure causes issues with certain workflows. For example Expected behavior I would expect clj new to complete successfully, as per the brew equivalent: Additional context I noticed that symlinked from to seemed to fix the issue; so I suspect something problematic around here: (maybe) Notify maintainers Metadata Please run and paste the result. Maintainer information:
Seems like (or as it was previously named) was never in the right location. Thanks for the spot and the fix!
Ah no problem. Thank you for the speedy response!
Change:
"-DCOMPILER_RT_DEFAULT_TARGET_ONLY=ON" "-DCMAKE_C_COMPILER_TARGET=${stdenv.hostPlatform.config}" "-DCMAKE_ASM_COMPILER_TARGET=${stdenv.hostPlatform.config}" <ins> ] ++ lib.optionals (useLLVM || bareMetal || isMusl || isAarch64) [ "-DCOMPILER_RT_BUILD_LIBFUZZER=OFF" </ins> ] ++ lib.optionals (useLLVM || bareMetal || isMusl) [ "-DCOMPILER_RT_BUILD_SANITIZERS=OFF" "-DCOMPILER_RT_BUILD_XRAY=OFF" <del> "-DCOMPILER_RT_BUILD_LIBFUZZER=OFF" </del> "-DCOMPILER_RT_BUILD_PROFILE=OFF" ] ++ lib.optionals ((useLLVM || bareMetal) && !haveLibc) [ "-DCMAKE_C_COMPILER_WORKS=ON"

Discussion:
Compile fails on aarch64 master . Steps to reproduce the behavior: to install ungoogled-chromium on aarch64 master compile <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --hardly relevant, as this is marked broken in master Maintainer information:
possible workaround is to disable building the libfuzzer, I'll check that now.
Sorry wrong patch, tested system build reboot chromium & firefox with this on aarch64
Change:
maintainers = with maintainers; [ vrthra ]; license = licenses.mit; platforms = with platforms; unix; <ins> knownVulnerabilities = [ "CVE-2020-11721" # https://github.com/saitoha/libsixel/issues/134 "CVE-2020-19668" # https://github.com/saitoha/libsixel/issues/136 ]; </ins> }; }

Discussion:
, CVSSv3=6.5 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc
See also:

, CVSSv3=6.5 (nixos-unstable) Scanned versions: nixos-unstable: . May contain false positives. Cc