jiebi/CodeConvo huggingface dataset:
Change:
I discovered today that overriding torchvision with does not work. At least not without making corresponding changes to torch. For example, We should either remove this argument and pull from torch or improve the ergonomics here somehow. cc Checkout nixpkgs at a relatively recent master commit, eg , and then run
can you test if fixes the problem? To be honest, including the argument for was a mistake in the first place -- it should (must?) use whatever was built with, so it should be inherit directly.
Maybe assert torch.cudaSupport is more explicit? Idk
I'm not super comfortable with asserts in the derivation because (afaik) they can't be overridden. Thoughts on me updating to ensure either both are compiled with CUDA, or neither are?
I understand it's a compromise. IIRC if we set here, we'll just exclude the broken package from ofborg and nixpkgs-review, contrary to the purpose.
Why do we need to be asserting or marking things as broken depending on ? shouldn't it build fine either way?
So the question is, should use , or should it accept as an argument and then possibly . I think that silently using may be surprising to people, but then again we're discussing some furnish while the thing is broken xD
ohhh i see, yeah that's tricky. i could envision someone creating a nix-shell with both and and then being very surprised to learn that is not built with CUDA support

Discussion:
requiredSystemFeatures = [ "big-parallel" ]; passthru = { <del> inherit cudaSupport cudaPackages gpuTargetString; cudaCapabilities = supportedCudaCapabilities; </del> <ins> inherit cudaSupport cudaPackages; </ins> # At least for 1.10.2 `torch.fft` is unavailable unless BLAS provider is MKL. This attribute allows for easy detection of its availability. blasProvider = blas.provider; <ins> } // lib.optionalAttrs cudaSupport { # NOTE: supportedCudaCapabilities isn't computed unless cudaSupport is true, so we can't use #   it in the passthru set above because a downstream package might try to access it even #   when cudaSupport is false. Better to have it missing than null or an empty list by default. cudaCapabilities = supportedCudaCapabilities; </ins> }; meta = with lib; {

{ buildPythonPackage <del> , cudaSupport ? torch.cudaSupport or false # by default uses the value from torch </del> , fetchFromGitHub , lib , libjpeg_turbo

}: let <del> inherit (torch) cudaPackages gpuTargetString; </del> <ins> inherit (torch) cudaCapabilities cudaPackages cudaSupport; </ins> inherit (cudaPackages) cudatoolkit cudaFlags cudaVersion; # NOTE: torchvision doesn't use cudnn; torch does!

+ lib.optionalString cudaSupport '' export CC=${cudatoolkit.cc}/bin/cc export CXX=${cudatoolkit.cc}/bin/c++ <del> export TORCH_CUDA_ARCH_LIST="${gpuTargetString}" </del> <ins> export TORCH_CUDA_ARCH_LIST="${lib.concatStringsSep ";" cudaCapabilities}" </ins> export FORCE_CUDA=1 '';
Change:
Package name: Latest released version: Current version on the unstable channel: Current version on the stable/release channel: Notify maintainers I attempted to update the version myself, but encountered an issue: Unfortunately, I don't have the time to investigate further at the moment. Therefore, I would appreciate it if someone else could take it from here. Note for maintainers: Please tag this issue in your PR.
I've updated the issue to reflect that the same error persists even with version .

Discussion:
stdenv.mkDerivation rec { pname = "calibre"; <del> version = "6.11.0"; </del> <ins> version = "6.15.1"; </ins> src = fetchurl { url = "https://download.calibre-ebook.com/${version}/${pname}-${version}.tar.xz"; <del> hash = "sha256-ylOZ5ljA5uBb2bX/qFhsmPQW6dJVEH9jxQaR2u8C4Wc="; </del> <ins> hash = "sha256-t9fG1hBlQmDh0i5ezBoqk9C9oliNNF0peKDz1YH7RBo="; </ins> }; # https://sources.debian.org/patches/calibre/${version}+dfsg-1

#  allow for plugin update check, but no calibre version check (fetchpatch { name = "0001-only-plugin-update.patch"; <del> url = "https://raw.githubusercontent.com/debian-calibre/calibre/debian/${version}%2Bdfsg-1/debian/patches/0001-only-plugin-update.patch"; </del> <ins> url = "https://raw.githubusercontent.com/debian-calibre/calibre/debian/${version}-1/debian/patches/0001-only-plugin-update.patch"; </ins> hash = "sha256-uL1mSjgCl5ZRLbSuKxJM6XTfvVwog70F7vgKtQzQNEQ="; }) (fetchpatch { <del> name = "0007-Hardening-Qt-code.patch"; url = "https://raw.githubusercontent.com/debian-calibre/calibre/debian/${version}%2Bdfsg-1/debian/patches/0007-Hardening-Qt-code.patch"; hash = "sha256-CutVTb7K4tjewq1xAjHEGUHFcuuP/Z4FFtj4xQb4zKQ="; </del> <ins> name = "0006-Hardening-Qt-code.patch"; url = "https://raw.githubusercontent.com/debian-calibre/calibre/debian/${version}-1/debian/patches/0006-Hardening-Qt-code.patch"; hash = "sha256-9P1kGrQbWAWDzu5EUiQr7TiCPHRWUA8hxPpEvFpK20k="; </ins> }) ] ++ lib.optional (!unrarSupport) ./dont_build_unrar_plugin.patch;
Change:
Steps to reproduce the behavior: from 22.11 live image (plasma) -shell -p dduper Fails directly. <!-- 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. Thanks!
i'm on it!
many thanks for update, but current 22.11 still doesn't build (local channels updated to current): I think the might be this strange sha256 crc: For comparsion: Thanks!
Oh, this specific hash format is nix-specific -- it's not just of the file, and most unimportant info about the patch is discarded before hashing (like the date it was created). Also there's no message about mismatched hashes, which there would be if the hash indeed did not match (Nix ABSOLUTELY DOESN'T mess around with hashes, that's what makes it so good!) You'll have to wait a bit until my back port is released on the official Hydra channel (what you're using). In the mean time you can make a direct-from-Git build using

Discussion:
patches = [ (fetchpatch { name = "0001-Print-csum-for-a-given-file-on-stdout.patch"; <del> url = "https://raw.githubusercontent.com/Lakshmipathi/dduper/f45d04854a40cb52ae0e6736916d5955cb68b8ee/patch/btrfs-progs-v5.12.1/0001-Print-csum-for-a-given-file-on-stdout.patch"; sha256 = "0c7dd44q2ww6k9nk5dh6m0f0wbd8x84vb2m61fk6a44nsv2fwz1x"; </del> <ins> url = "https://raw.githubusercontent.com/Lakshmipathi/dduper/5416ebd5b98ed0b1e463fc088408770e51a74f9c/patch/btrfs-progs-v5.18/0001-Print-csum-for-a-given-file-on-stdout.patch"; sha256 = "sha256-SnDiIAI/TInhAZqK+8RGDwF8ikcAHWueYaygNBO8dAc="; </ins> }) ]; });
Change:
I never really noticed this until today, but apparently the discord task bar icon (if you have one, I am on KDE) is supposed to have a notification badge, I have included a screenshot. The discord task bar icon should include a badge for the number of unread notifications ! Today I was setting up a system for someone else who was new to Linux, I installed Discord via flatpak, and then they asked me about the badge (since it is present on Windows but not on the ). From a little searching, it seems that Discord needs to ba available in the system, so on Kubuntu this was fixed by doing . Since is already in , it might just be a matter of adding it to the ?
Huh. I don't think I ever knew one was supposed to be there either. I see an unread indicator (red circle in the top corner, no number), so that works fine, but I don't think I've ever seen a number. Assuming that would be all it would take, sounds like a pretty simple PR that would be a good addition.
I have made a clone of and it does seem that all that was need was to add the library to . I found it to be a bit ugly myself since I had over 1000 unread notifications, and it seems disabling it is only possible outside the application. On for example, you have to go to and tick off "Show notification badges". Running the current from afterwords does not remove the badges, it only freezes them in place, as in marking notifications as read will not update the number, so this is also cached somewhere outside , meaning this couldn't be a toggleable functionality via an .

Discussion:
, libXScrnSaver, libXcomposite, libXcursor, libXdamage, libXext, libXfixes , libXi, libXrandr, libXrender, libXtst, libxcb, libxshmfence, mesa, nspr, nss , pango, systemd, libappindicator-gtk3, libdbusmenu, writeScript, python3, runCommand <ins> , libunity </ins> , wayland , branch , common-updater-scripts, withOpenASAR ? false }:

libnotify libX11 libXcomposite <ins> libunity </ins> libuuid libXcursor libXdamage
Change:
Steps to reproduce the behavior: Run I'm running Nix from the provided VirtualBox demo appliance, updated to the unstable channel. It also failed to build for OfBorg <!-- --Please run and paste the result.

Discussion:
buildPythonPackage rec { pname = "dash"; <del> version = "2.7.0"; </del> <ins> version = "2.8.1"; </ins> format = "setuptools"; disabled = pythonOlder "3.6";

owner = "plotly"; repo = pname; rev = "refs/tags/v${version}"; <del> hash = "sha256-kxat6CjX4xPEtlhRiYJF5wN2Luds7DduZyiUA9/kKWY="; </del> <ins> hash = "sha256-6FsLvLsqnkSt/i27q/JJGfNh2zxKeA0t6VYNPCzhR0w="; </ins> }; propagatedBuildInputs = [ <del> plotly flask flask-compress </del> dash-core-components dash-html-components dash-table <ins> flask flask-compress plotly </ins> ]; passthru.optional-dependencies = {

}; nativeCheckInputs = [ <del> pytestCheckHook pytest-mock </del> mock <ins> pytest-mock pytestCheckHook </ins> pyyaml ];

"tests/integration" ]; <ins> disabledTests = [ # Failed: DID NOT RAISE <class 'ImportError'> "test_missing_flask_compress_raises" ]; </ins> pythonImportsCheck = [ "dash" ];

meta = with lib; { description = "Python framework for building analytical web applications"; homepage = "https://dash.plot.ly/"; <ins> changelog = "https://github.com/plotly/dash/blob/v${version}/CHANGELOG.md"; </ins> license = licenses.mit; maintainers = with maintainers; [ antoinerg ]; };
Change:
I can't update my system when itch should be installed: error: Package ‘electron-11.5.0’ in /nix/store/5wja3wj4lq4gijjgg2lx3966pf6lzijc-nixos- is marked as insecure, refusing to evaluate. Steps to reproduce the behavior: in no error also reproducible on unstable i guess electron needs an update or use a later electron version, if possible system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
It's an upstream issue, trying to use a newer Electron version makes Itch straight up not work (it gets stuck at the initial loading). unfortunately seems to be abandoned. There technically is a new version (25.6.1-canary), but it hasn't been distributed as a binary on , and looking at the commits it doesn't change much. There is really nothing that can be done here. You can do this on your if you don't care about the security risks:
Upstream issue:

Discussion:
, fetchzip , fetchFromGitHub , butler <del> , electron_11 </del> <ins> , electron </ins> , steam-run , makeWrapper , copyDesktopItems

}: stdenvNoCC.mkDerivation rec { pname = "itch"; <del> version = "25.6.2"; </del> <ins> version = "26.1.2"; # TODO: Using kitch instead of itch, revert when possible </ins> src = fetchzip { <del> url = "https://broth.itch.ovh/${pname}/linux-amd64/${version}/itch.zip"; </del> <ins> url = "https://broth.itch.ovh/k${pname}/linux-amd64/${version}/archive/default#.zip"; </ins> stripRoot = false; <del> sha256 = "sha256-F/vaYBHCygseiKNMJ+jBy31YDIFqYToAETGUl/pkHII="; </del> <ins> sha256 = "sha256-thXe+glpltSiKNGIRgvOZQZPJWfDHWo3dLdziyp2BM4="; </ins> }; itch-setup = fetchzip {

fetchFromGitHub { owner = "itchio"; repo = pname; <del> rev = "v25.6.1-canary"; # Use ${version} if possible hash = "sha256-iBp7K7AW97SOlRa8N8TW2LcVtmUi9JU00fYUuPwKORc="; </del> <ins> rev = "v${version}-canary"; sha256 = "sha256-veZiKs9qHge+gCEpJ119bAT56ssXJAH3HBcYkEHqBFg="; </ins> sparseCheckout = [ sparseCheckout ]; } + sparseCheckout;

installPhase = '' runHook preInstall <ins> # TODO: Remove when the next stable Itch is stabilized substituteInPlace ./resources/app/package.json  --replace "kitch" "itch" </ins> mkdir -p $out/bin $out/share/${pname}/resources/app cp -r resources/app "$out/share/${pname}/resources/"

postFixup = '' makeWrapper ${steam-run}/bin/steam-run $out/bin/${pname}  <del> --add-flags ${electron_11}/bin/electron  </del> <ins> --add-flags ${electron}/bin/electron  </ins> --add-flags $out/share/${pname}/resources/app  --set BROTH_USE_LOCAL butler,itch-setup  --prefix PATH : ${butler}/bin/:${itch-setup}
Change:
Package name: darktile Latest released version: 0.0.11 <!-- Search your package here: --- Current version on the unstable channel: 0.0.10 Current version on the stable/release channel: 0.0.10 <!-- 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.
Hi! Unfortunately, I'm no longer using NixOS. It should still be pretty trivial to create a PR, but I won't be able to test it. If I create a draft PR for this, will you be willing to download it and test whether it works?
Also, I'd appreciate it if you became the maintainer of this package instead of me (only if you want to, of course). There are pretty much no updates to it, so you'll rarely have to do anything
Sure, I would be happy to test the draft PR and become the maintainer of the package. Please let me know if there's anything else you need from me to proceed.
ok, well, foremost, it seems like the hash of the package can't get obtained on systems without Nix. Could you please run and post the output here?
Sure. Here:
I opened a draft PR which updates the package and makes you the maintainer. Please test if the updated package works.

Discussion:
{ stdenv , fetchFromGitHub , lib <del> , go </del> , pkg-config , libX11 , libXcursor

, libXxf86vm , libGL , nixosTests <ins> , buildGoModule </ins> }: <del> stdenv.mkDerivation rec { </del> <ins> buildGoModule rec { </ins> pname = "darktile"; <del> version = "0.0.10"; </del> <ins> version = "0.0.11"; </ins> src = fetchFromGitHub { owner = "liamg"; repo = "darktile"; rev = "v${version}"; <del> sha256 = "0pdj4yv3qrq56gb67p85ara3g8qrzw5ha787bl2ls4vcx85q7303"; </del> <ins> hash = "sha256-M3vySAyYwqscR9n0GGXp1ttO/mhdSCponZNYJRBBI18="; </ins> }; <del> nativeBuildInputs = [ go pkg-config ]; </del> <ins> vendorHash = null; nativeBuildInputs = [ pkg-config ]; </ins> buildInputs = [ libX11

libGL ]; <del> postPatch = '' substituteInPlace scripts/build.sh  --replace "bash" "sh" ''; postConfigure = '' export GOPATH=$TMP/go ''; makeFlags = [ "HOME=$TMP" ]; installPhase = '' runHook preInstall install -Dm755 darktile -t $out/bin runHook postInstall ''; </del> passthru.tests.test = nixosTests.terminal-emulators.darktile; meta = with lib; {

downloadPage = "https://github.com/liamg/darktile/releases"; changelog = "https://github.com/liamg/darktile/releases/tag/v${version}"; license = licenses.mit; <del> maintainers = with maintainers; [ flexagoon ]; </del> <ins> platforms = platforms.linux; badPlatforms = [ "aarch64-linux" ]; maintainers = with maintainers; [ mikaelfangel ]; </ins> mainProgram = "darktile"; }; }
Change:
I'm trying to build the netboot files for a raspberry pi, I tried both on an Ampere aarch64 and on the rRPI itself, I alwasy get this error sometimes it happens directly in the , sometimes in replace-initrd- Steps to reproduce the behavior: -build '' -A netboot tried -A netboot.aarch64-linux and adding --option system aarch64-linux, same results. error: a 'x8664-linux' with features {} is required to build '/nix/store/jbyl55lz04dmfv6blcc47zqsn38568rh-', but I am a 'aarch64-linux' with features {benchmark, big-parallel, gccarch-armv8-a, kvm, nixos-test} I altro tried cross compiling on a x8664 machine but I get the same error when it gets to replace-initrd- Please run and paste the result. this path will be fetched (0.06 MiB download, 0.30 MiB unpacked): /nix/store/x1q75v4ysr72w4x6c713cpf1dmfg18cq-bash-interactive-5.1-p16-dev copying path '/nix/store/x1q75v4ysr72w4x6c713cpf1dmfg18cq-bash-interactive-5.1-p16-dev' from ''... system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
sorry i dont have any expirience in this area but it looks like neboot builds on aarch64-linux, please test this PR
Thanks for the answer, I'll try applying the fix, I'll let you know how it goes.

Discussion:
meta = with lib; { description = "Mini PXE server"; maintainers = [ maintainers.raskin ]; <del> platforms = ["x86_64-linux"]; </del> <ins> platforms = [ "x86_64-linux" "aarch64-linux" ]; </ins> license = lib.licenses.free; }; }
Change:
Package name: hypr Latest commit: <!-- Search your package here: --- Current version on the unstable channel: 2022-05-25 Current version on the stable/release channel: 2022-05-25 <!-- 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.
Commit includes various fixes and fixes build on macos. Updating to the latest revision is essential.

Discussion:
, xmodmap }: <del> stdenv.mkDerivation (finalAttrs: { </del> <ins> stdenv.mkDerivation (self: { </ins> pname = "hypr"; <del> version = "unstable-2022-05-25"; </del> <ins> version = "unstable-2023-01-26"; </ins> src = fetchFromGitHub { owner = "hyprwm"; repo = "Hypr"; <del> rev = "3e3d943c446ae77c289611a1a875c8dff8883c1e"; hash = "sha256-lyaGGm53qxg7WVoFxZ7kerLe12P1N3JbN8nut6oZS50="; </del> <ins> rev = "af4641847b578b233a6f06806f575b3f320d74da"; hash = "sha256-FUKR5nceEhm9GWa61hHO8+y4GBz7LYKXPB0OpQcQ674="; </ins> }; patches = [ ./000-dont-set-compiler.diff <del> # TODO: remove on next release (fetchpatch { url = "https://github.com/hyprwm/Hypr/commit/08d6af2caf882247943f0e8518ad782f35d1aba4.patch"; sha256 = "sha256-WjR12ZH8CE+l9xSeQUAPYW5r5HzoPpod5YqDPJTdTY8="; }) (fetchpatch { url = "https://github.com/hyprwm/Hypr/commit/7512a3ab91865b1e11b8c4a9dfdffb25c2b153de.patch"; sha256 = "sha256-0Hq5n115z0U44op7A1FO9tUOeMEPV0QgD5E5zcmend0="; }) </del> ]; nativeBuildInputs = [

''; meta = with lib; { <del> inherit (finalAttrs.src.meta) homepage; </del> <ins> inherit (self.src.meta) homepage; </ins> description = "A tiling X11 window manager written in modern C++"; license = licenses.bsd3; maintainers = with maintainers; [ AndersonTorres ];
Change:
Package name: electron-mail Latest released version: 5.1.6 <!-- Search your package here: --- Current version on the unstable channel: 5.1.2 Current version on the stable/release channel: 5.1.2 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR.

Discussion:
let pname = "electron-mail"; <del> version = "5.1.2"; </del> <ins> version = "5.1.6"; </ins> name = "ElectronMail-${version}"; src = fetchurl { url = "https://github.com/vladimiry/ElectronMail/releases/download/v${version}/electron-mail-${version}-linux-x86_64.AppImage"; <del> sha256 = "sha256-PLDzAtH7T7QMrLavvcF3zOVTayCqEA1IghIUAAxkbEE="; </del> <ins> sha256 = "sha256-lsXVsx7U43czWFWxAgwTUYTnUXSL4KPFnXLzUklieAo="; </ins> }; appimageContents = appimageTools.extract { inherit name src; };
Change:
Package name: i3lock-fancy-rapid Latest released version: 2021-04-21 (commit: ) <!-- Search your package here: --- Current version on the unstable channel: 2019-10-09 Current version on the stable/release channel: 2019-10-09 <!-- 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.
Commit: has performance improvements.

Discussion:
{ lib, stdenv, fetchFromGitHub, xorg, i3lock }: <del> stdenv.mkDerivation rec { </del> <ins> stdenv.mkDerivation { </ins> pname = "i3lock-fancy-rapid"; <del> version = "2019-10-09"; </del> <ins> version = "unstable-2021-04-21"; </ins> src = fetchFromGitHub { owner = "yvbbrjdr"; repo = "i3lock-fancy-rapid"; <del> rev = "c67f09bc8a48798c7c820d7d4749240b10865ce0"; sha256 = "0jhvlj6v6wx70239pgkjxd42z1s2bzfg886ra6n1rzsdclf4rkc6"; </del> <ins> rev = "6eeebd4caa177b82fa5010b5e8828cce3f89fb97"; hash = "sha256-EoX8ts0yV/zkb4wgEh4P8noU+UraRS4w9pp+76v+Nm0="; </ins> }; buildInputs = [ xorg.libX11 ]; propagatedBuildInputs = [ i3lock ]; postPatch = ''

''; installPhase = '' <ins> runHook preInstall </ins> install -D i3lock-fancy-rapid $out/bin/i3lock-fancy-rapid ln -s $out/bin/i3lock-fancy-rapid $out/bin/i3lock <ins> runHook postInstall </ins> ''; meta = with lib; {
Change:
Steps to reproduce the behavior: on latest Nixpkgs master (See ). Tracked upstream:
Oh nice catch! I'll try a git bisect on the to try to narrow down the cause.
Forgot I was running this in the background :sweat_smile: - tracked it down to the :
debugpy doesn't depend on etils
Oh yep, it was probably just a bad automatic bisect then, I'll try manually.
Ok, I just ran it again and it just looks like there was just an unrelated error in one of the commits it sampled before: If this wasn't going to work I was thinking of adding failing inputDrvs as a skip condition. Didn't need to, but it'll be helpful for next time!

Discussion:
, buildPythonPackage , pythonOlder , fetchFromGitHub <ins> , fetchpatch </ins> , substituteAll , gdb , django

inherit version; }) <ins> # https://github.com/microsoft/debugpy/issues/1230 (fetchpatch { url = "https://patch-diff.githubusercontent.com/raw/microsoft/debugpy/pull/1232.patch"; sha256 = "sha256-m5p+xYiJ4w4GcaFIaPmlnErp/7WLwcvJmaCqa2SeSxU="; }) </ins> # Fix importing debugpy in: # - test_nodebug[module-launch(externalTerminal)] # - test_nodebug[module-launch(integratedTerminal)]

pytestFlagsArray = [ "--timeout=0" ]; # Fixes hanging tests on Darwin __darwinAllowLocalNetworking = true; <ins> disabledTests = [ # https://github.com/microsoft/debugpy/issues/1241 "test_flask_breakpoint_multiproc" ]; </ins> pythonImportsCheck = [ "debugpy" ];
Change:
Steps to reproduce the behavior: colima on darwin or aarch64-linux Seems to still build successfully on x86_64-linux (). Please run and paste the result.
Thanks for reporting. The seems to be flaky. I opened a pr to disable it so that the hydra build should succeed again.

Discussion:
vendorHash = "sha256-bEgC7j8WvCgrJ2Ahye4mfWVEmo6Y/OO64mDIJXvtaiE="; <ins> # disable flaky Test_extractZones # https://hydra.nixos.org/build/212378003/log excludedPackages = "gvproxy"; </ins> CGO_ENABLED = 1; preConfigure = ''