jiebi/CodeConvo huggingface dataset:
Change:
mkDerivation rec { pname = "kaidan"; <del> version = "0.8.0"; </del> <ins> version = "0.9.1"; </ins> src = fetchFromGitLab { domain = "invent.kde.org"; owner = "network"; repo = pname; rev = "v${version}"; <del> sha256 = "070njci5zyzahmz3nqyp660chxnqx1mxp31w17syfllvrw403qmg"; </del> <ins> hash = "sha256-F5GhN9hAF2e8b0T3peUnLk8CVd+nq4YR8k52x6ZOoLM="; </ins> }; nativeBuildInputs = [ cmake extra-cmake-modules pkg-config ];

Discussion:
Steps to reproduce the behavior: kaidan <!-- 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]:
Thanks for notifying me!
Change:
}); let snapshotHash = if stdenv.system == "i686-linux" <del> then "g2h9l35123r72hqdwayd9h79kspfb4y9" </del> <ins> then "7e2f9c82e1af5aa43ef3ee2692b985a5f2398f0a" </ins> else if stdenv.system == "x86_64-linux" <del> then "fnx2rf1j8zvrplcc7xzf89czn0hf3397" </del> <ins> then "4c03a3fd2474133c7ad6d8bb5f6af9915ca5292a" </ins> else if stdenv.system == "i686-darwin" <del> then "3viz3fi2jx18qjwrc90nfhm9cik59my6" </del> <ins> then "4d84d31449a5926f9e7ceb344540d6e5ea530b88" </ins> else if stdenv.system == "x86_64-darwin" <del> then "h2bf3db4vwz5cjjkn98lxayivdc6dflp" </del> <ins> then "f8baef5b0b3e6f9825be1f1709594695ac0f0abc" </ins> else throw "no snapshot for platform ${stdenv.system}"; snapshotName = "cargo-nightly-${platform}.tar.gz"; in

Discussion:
To make sure that we are on the same page: Kernel: (run ) 4.5.0 System: (NixOS: , Ubuntu/Fedora: , ...) (Flounder) Nix version: (run ) 1.11.2 Nixpkgs version: (run ) During testing of I managed to get at least two different hashes for . After some discussion with it seems that this derivation can produce non-deterministic output. Hashes of outputs are always the same. They are not. Build several times.
How would one work around that? It basically means the system cannot be rebuild :cry:
cc
You can work around it by updating SHA checksum in the affected package locally.
:confused: Is there any documentation you could point me too. I know how I would to it for packages that I install as a user: out nixpkgs repo the last commit that build for unstable on hydra that out the exa's file 5 run But I think it's also possible to override it in a nix expression, like the one in , since I installed it as a systems package. The thing is that all ressources I find either explain how to do it for that they link to
I changed my to include that: but to no avail :confused:
Sadly we don't have a mechanism to override (it needs to be supported). However, you can rebuild your whole NixOS from a modified repository:
Another way to do it is to call patched nixpkgs from your :
Thanks for your help! I really appreciate it. I tried your last suggestions, but that leads to: It looks like some network hick up, but I tried it multiple times and I opened the github repository from the same machine and it loads fine. Maybe it has something to do with this line: ?
Hm, unfortunately I have no idea what's going on -- you've fixed the hash, so it seems like another problem in .
Still thanks for the help. I learned a lot!
depends on a git repository in which doesn't work with
maybe fetchcargo could take an argument to pin git-based dependencies on a certain commit?
I can confirm that this is still an issue when building : through AUR/exa-git. cc
Are there any updates on this issue, please?
Should be fixed.
Change:
, colorama , fetchFromGitHub , funcparserlib <ins> , hy </ins> , pytestCheckHook <ins> , python </ins> , pythonOlder , rply <ins> , testers , toPythonApplication , hyDefinedPythonPackages ? python-packages: [ ] /* Packages like with python.withPackages */ </ins> }: buildPythonPackage rec { pname = "hy"; <del> version = "1.0a3"; </del> <ins> version = "1.0a4"; format = "setuptools"; </ins> <del> disabled = pythonOlder "3.6"; </del> <ins> disabled = pythonOlder "3.7"; </ins> src = fetchFromGitHub { owner = "hylang"; repo = pname; rev = version; <del> sha256 = "1dqw24rvsps2nab1pbjjm1c81vrs34r4kkk691h3xdyxnv9hb84b"; </del> <ins> sha256 = "sha256-MBzp3jqBg/kH233wcgYYHc+Yg9GuOaBsXIfjFDihD1E="; </ins> }; <ins> # https://github.com/hylang/hy/blob/1.0a4/get_version.py#L9-L10 HY_VERSION = version; </ins> propagatedBuildInputs = [ colorama funcparserlib <del> rply ] ++ lib.optionals (pythonOlder "3.9") [ </del> <ins> rply # TODO: remove on the next release ] ++ lib.optionals (pythonOlder "3.9") [ </ins> astor <del> ]; </del> <ins> ] # for backwards compatibility with removed pkgs/development/interpreters/hy # See: https://github.com/NixOS/nixpkgs/issues/171428 ++ (hyDefinedPythonPackages python.pkgs); </ins> checkInputs = [ pytestCheckHook

Discussion:
The one in is more up-to-date (1.0a3 vs 1.0a1, current version is 1.0a4 though), . The second one is the oldest though. Not sure what is the best solution here. It doesn't seem to make much sense to have Hy being considered a interpreter instead of a Python package (it even has attribute that AFAIK isn't any different from simply from using with and other dependencies as ). But I don't have sufficient context here. We probably need to merge one in another and delete the other derivation. Steps to reproduce the behavior: We should only have one Hy package. N/A N/A <!-- 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.
Created a PR removing and keeping , while also making has the same parameter for backwards compatibility:
Change:
sha256 = "0f2wzdw2a3ac581322b2y79rlj3c9f33ddrq9allj97r1si6v5xk"; }; <del> patches = [ ./clean-env.patch ]; </del> enableParallelBuilding = true; nativeBuildInputs = [ pkg-config autoconf automake ];

Discussion:
Describe the bug In NixOS 20.09, Emacs now has the output of gtk+ in its closure, which in turn causes it to pull in stuff like mesa-drivers (424 MiB): This caused the closure size of Emacs to increase from 339 MiB in NixOS 20.03 to 1324 MiB in 20.09. Metadata NixOS 20.09..
cc
This was reverted in
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
<ins> From 5574aba60ed76f2bae947722122ac4d71ab8ed5a Mon Sep 17 00:00:00 2001 From: Takeshi KOMIYA <i.tkomiya@gmail.com> Date: Mon, 18 Jan 2016 12:38:02 +0900 Subject: [PATCH] Fix tests are broken with pygments-2.1 --- tests/test_build_html.py |  2 +- tests/test_intl.py       | 10 ++++++---- 2 files changed, 7 insertions(+), 5 deletions(-) diff --git a/tests/test_build_html.py b/tests/test_build_html.py index e330761..17ea089 100644 --- a/tests/test_build_html.py +++ b/tests/test_build_html.py @@ -82,7 +82,7 @@ def checker(nodes): (".//a[@href='_downloads/img1.png']", ''), (".//pre", u'"quotes"'), (".//pre", u"'included'"), -        (".//pre/span[@class='s']", u'üöä'), +        (".//pre/span[@class='s2']", u'üöä'), (".//div[@class='inc-pyobj1 highlight-text']//pre", r'^class Foo:n    passns*$'), (".//div[@class='inc-pyobj2 highlight-text']//pre", diff --git a/tests/test_intl.py b/tests/test_intl.py index 4c665d4..b24ec65 100644 --- a/tests/test_intl.py +++ b/tests/test_intl.py @@ -694,14 +694,15 @@ def test_additional_targets_should_not_be_translated(app, status, warning): yield assert_count(expected_expr, result, 1) # C code block with lang should not be translated but be *C* highlighted -    expected_expr = """<span class="cp">#include &lt;stdio.h&gt;</span>""" +    expected_expr = ("""<span class="cp">#include</span> """ +                     """<span class="cpf">&lt;stdio.h&gt;</span>""") yield assert_count(expected_expr, result, 1) # doctest block should not be translated but be highlighted expected_expr = ( """<span class="gp">&gt;&gt;&gt; </span>""" """<span class="kn">import</span> <span class="nn">sys</span>  """ -        """<span class="c"># sys importing</span>""") +        """<span class="c1"># sys importing</span>""") yield assert_count(expected_expr, result, 1) ## raw.txt @@ -754,14 +755,15 @@ def test_additional_targets_should_be_translated(app, status, warning): yield assert_count(expected_expr, result, 1) # C code block with lang should be translated and be *C* highlighted -    expected_expr = """<span class="cp">#include &lt;STDIO.H&gt;</span>""" +    expected_expr = ("""<span class="cp">#include</span> """ +                     """<span class="cpf">&lt;STDIO.H&gt;</span>""") yield assert_count(expected_expr, result, 1) # doctest block should not be translated but be highlighted expected_expr = ( """<span class="gp">&gt;&gt;&gt; </span>""" """<span class="kn">import</span> <span class="nn">sys</span>  """ -        """<span class="c"># SYS IMPORTING</span>""") +        """<span class="c1"># SYS IMPORTING</span>""") yield assert_count(expected_expr, result, 1) ## raw.txt </ins>

Discussion:
fails its test suite, which in turn breaks various other packages like and . According to the issue was caused by commit from
just needs a bump
1.3.4 fails with the same test failure
Change:
msieve = callPackage ../applications/science/math/msieve { }; <del> weka = callPackage ../applications/science/math/weka { }; </del> <ins> weka = callPackage ../applications/science/math/weka { jre = openjdk11; }; </ins> yad = callPackage ../tools/misc/yad { };

Discussion:
Weka crashes if using the nixpkgs version Steps to reproduce the behavior: weka from nixpkgs at (nixos-unstable) weka Weka opening that main window and working properly. It neither opens the main window nor works properly. If applicable, add screenshots to help explain your problem. Downloading the zip from and running by using from works as expected. <!-- 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.
Change:
postInstall = '' install -Dm444 $src/res/oculante.png -t $out/share/icons/hicolor/128x128/apps/ install -Dm444 $src/res/oculante.desktop -t $out/share/applications <del> ''; postFixup = lib.optionalString stdenv.isLinux '' patchelf $out/bin/oculante --add-rpath ${lib.makeLibraryPath [ libxkbcommon libX11 ]} </del> <ins> wrapProgram $out/bin/oculante  --prefix LD_LIBRARY_PATH : ${lib.makeLibraryPath [libGL]} </ins> ''; meta = with lib; {

Discussion:
Fails to run due to error: Steps to reproduce the behavior: It runs. Running it with NixGL works. Using an Intel GPU. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Running on NixOS 24.05pre, current nixpkgs revision is . Bumping the version on master to 0.8.6 and building has the same result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Same here. Using nVidia GPU.

Package name: oculante Latest released version: 0.8.6 <!-- Search your package here: --- Current version on the unstable channel: 0.7.7 Current version on the stable/release channel: 0.7.7 <!-- 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:
rkflashtool = callPackage ../tools/misc/rkflashtool { }; <ins> rkvm = callPackage ../tools/misc/rkvm { }; </ins> rkrlv2 = callPackage ../applications/audio/rkrlv2 { }; rmlint = callPackage ../tools/misc/rmlint {

Discussion:
Project description It's like synergy or barrier, but supports wayland and windows as well. I started packaging it , but it doesn't build yet ( fails to find the evdev files it wants). Metadata homepage URL: source URL: license: mit platforms: linux
here's the build log so far:
well, this is probably the issue: I'll file an issue.
If this is the only issue you can probably patch it like this: And during phrase you can use or to substitute with . Should work.
Good idea. Another weird one popped out though: Not sure what's up, since libevdev does not seem to actually come with that header file included... and from what I can tell ubuntu's libevdev-dev packages don't either??
Weird, debian's libevdev-dev pkg:
Looks like I misunderstood. I think they bundle their input.h for building their lib, but expect to be providing , so I'm adding that to the clang_args too...
Okay, update: error:
I marked this as stale due to inactivity. &rarr;
build: please see:
What's the status on this, doesn't look like it's made it into the binary cache yet. Is it a 23.11 addition?
the PR is still being reviewed:
Change:
, callPackage , fetchFromGitHub , fetchpatch <ins> , fetchurl </ins> , rocmUpdateScript , makeWrapper , cmake

Discussion:
The build for a lot of ROCm components broke with , which updated CMake from 3.29.0 to 3.29.1, basically breaking all of ROCm. This commit was merged via and recently made its way from staging into unstable in the last few days. Steps to reproduce the behavior: The builds for a number of ROCm components now fail with error messages like the following: This is possible related to how ROCm uses of CMake incorrectly. See , , and I have posted about this issue on the CMake discourse to verify if this is considered a bug in CMake, as suggested by <!-- 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 first recommendation we got from CMake was updating to 3.29.2, which has already been merged to staging:
I was able to confirm that with that commit that updates CMake to 3.29.2 builds again. I will leave this issue open until the relevant changes make it into unstable.
is there an easy way to temporarily use the cmake version from staging in my configuration for a specific package, without using staging for every dependency of that package?
A workaround could be to apply this as patch:
One possible fix would be overriding the CMake version that is used inside of ROCm to update to the newer version, and merging that with a PR to master. The advantage of this compared to would be that we do not need to worry about the fix actually breaking the build once the version update lands (I have not tested that this happens, but I could imagine it does). It might be a good idea to do this by making the overridden version of a part of , and removing extra dependency on elsewhere in ROCm. Also ROCm 5.7 and 6.0 are both broken, so if we want to merge a fix before the CMake version update lands in unstable, we should fix both. I am not working on a fix for this, and I couldn't merge one, but I'm happy to review PRs.
Change:
<ins> { lib, stdenv, fetchFromGitHub, gtk3, meson, ninja, json_c, pkg-config, gtk-layer-shell, libpulseaudio, libmpdclient, libxkbcommon, alsa-lib, makeWrapper, }: let version = "1.0_beta14"; in stdenv.mkDerivation { pname = "sfwbar"; inherit version; src = fetchFromGitHub { owner = "LBCrion"; repo = "sfwbar"; rev = "v${version}"; hash = "sha256-4brP1SXaWq/L0D87rvlrWhLU1oFPSwNNxBSzRr4jsTM="; }; buildInputs = [ gtk3 json_c gtk-layer-shell libpulseaudio libmpdclient libxkbcommon alsa-lib ]; nativeBuildInputs = [ meson ninja pkg-config makeWrapper ]; postFixup = '' wrapProgram $out/bin/sfwbar  --suffix XDG_DATA_DIRS : $out/share ''; meta = { homepage = "https://github.com/LBCrion/sfwbar"; description = "Flexible taskbar application for wayland compositors, designed with a stacking layout in mind"; changelog = "https://github.com/LBCrion/sfwbar/releases/tag/v${version}"; mainProgram = "sfwbar"; platforms = lib.platforms.linux; maintainers = with lib.maintainers; [ luftmensch-luftmensch NotAShelf ]; license = lib.licenses.gpl3Only; }; } </ins>

Discussion:
Package name: sfwbar Latest released version: 1.0beta14 <!-- Search your package here: --- Current version on the unstable channel: 1.0beta13 Current version on the stable/release channel: 1.0_beta13 <!-- 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 NotAShelf <!-- 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:
description = "John the Ripper password cracker"; license = licenses.gpl2Plus; homepage = "https://github.com/openwall/john/"; <del> maintainers = with maintainers; [ offline matthewbauer cherrykitten ]; </del> <ins> maintainers = with maintainers; [ offline matthewbauer cherrykitten ]; </ins> platforms = platforms.unix; }; }

Discussion:
Project description Is it possible to add OpenCL support to ? Details can be found by link below: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I tried but I'm getting a weird linker error: I have no idea what causes it. Looking at the source, it looks perfectly fine.
CC
Worked around it with . PR:
Change:
sha256 = "0621njipng32x43lw8n49mapq10lnvibg8vlvgciqsfvrbpz1yp5"; } { <del> url = "https://api.pulumi.com/releases/plugins/pulumi-resource-postgresql-v3.1.0-darwin-amd64.tar.gz"; sha256 = "1x5fm72v9h3lrqcyyq2xm14bc14rsqhjmc4mwa2wgbk4pvjgawyv"; </del> <ins> url = "https://api.pulumi.com/releases/plugins/pulumi-resource-postgresql-v3.2.0-darwin-amd64.tar.gz"; sha256 = "1j7z5dbqzsdq1q8ks9g5pwzyc3ml6avhhp6xj94dzdhskl6pd8w5"; </ins> } { url = "https://api.pulumi.com/releases/plugins/pulumi-resource-random-v4.2.0-darwin-amd64.tar.gz"; sha256 = "0gd3xnl31892qp8ilz9lc1zdps77nf07jgvh0k37mink8f0ppy2z"; } { <del> url = "https://api.pulumi.com/releases/plugins/pulumi-resource-vault-v4.3.0-darwin-amd64.tar.gz"; sha256 = "0ay8d84fc1hr1n4fpy1a4nj7bmhxzp86p0x68gz4rr9iwrd7xfgl"; </del> <ins> url = "https://api.pulumi.com/releases/plugins/pulumi-resource-vault-v4.4.0-darwin-amd64.tar.gz"; sha256 = "01rrmj95lhvwxi8f338f50l2zspnin41j8hi2j9pjsjwfayhpq93"; </ins> } { url = "https://api.pulumi.com/releases/plugins/pulumi-resource-vsphere-v4.0.1-darwin-amd64.tar.gz";

Discussion:
<!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on github to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the 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: pulumi-bin <!-- 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: 3.10.0 desired version: 3.12.0 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Please tag this issue in your PR.
Change:
stdenv.mkDerivation rec { pname = "libssh"; <del> version = "0.10.6"; </del> <ins> version = "0.11.1"; </ins> src = fetchurl { url = "https://www.libssh.org/files/${lib.versions.majorMinor version}/libssh-${version}.tar.xz"; <del> hash = "sha256-GGHUmPW28XQbarxz5ghHhJHtz5ydS2Yw7vbnRZbencE="; </del> <ins> hash = "sha256-FLfcxy6R4IFRxYuYGntXCrJmP2MOfSg3ZF1anGEsG3k="; </ins> }; <del> # Do not split 'dev' output until lib/cmake/libssh/libssh-config.cmake # is fixed to point INTERFACE_INCLUDE_DIRECTORIES to .dev output. # Otherwise it breaks `plasma5Packages.kio-extras`: #   https://hydra.nixos.org/build/221540008/nixlog/3/tail #outputs = [ "out" "dev" ]; </del> <ins> outputs = [ "out" "dev" ]; </ins> postPatch = '' # Fix headers to use libsodium instead of NaCl

Discussion:
Package name: libssh Latest released version: 0.11.1 <!-- Search your package here: --- Current version on the unstable channel: 0.10.6 Current version on the stable/release channel: 0.10.6 <!-- 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 Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
rote = callPackage ../development/libraries/rote { }; <ins> round = callPackage ../applications/graphics/round { }; </ins> ronn = callPackage ../development/tools/ronn { }; rshell = python3.pkgs.callPackage ../development/tools/rshell { };

Discussion:
Project description Generate architecture diagrams with python code. Allows for rapid iteration. Metadata homepage URL: source URL: license: mit platforms: linux, darwin This library requires graphviz (both native and the python library).
Change:
nativeBuildInputs = [ pkgconfig intltool ]; <del> configureFlags = [ "--with-systemdsystemunitdir=$(out)/lib/systemd/system" "--localstatedir=/var" ]; </del> <ins> configureFlags = [ "--with-systemdsystemunitdir=${placeholder "out"}/lib/systemd/system" "--localstatedir=/var" "--sysconfdir=${placeholder "out"}/etc" ]; </ins> meta = with stdenv.lib; { homepage = https://fprint.freedesktop.org/;

Discussion:
After fixing Stracing reveals that it is trying to open (yes, literal ) which is nonsense. Looks like somehow is misconfigured during the build? system: host os: multi-user?: sandbox: version: channels(michael): channels(root): nixpkgs:
Change:
pytest ]; <del> pythonImportsCheck = [ "hypothesis_auto" ]; </del> <ins> pythonImportsCheck = [ "hypothesis_auto" ]; </ins> meta = with lib; { description = "Enables fully automatic tests for type annotated functions";

Discussion:
Steps to reproduce the behavior: streamdeck-ui I'm unsure why this happens and how to fix it so I would need help on this Please run and paste the result. (unstable - )
Looks like broke with That PR is full of mines that make it challenging to bisect fully.