jiebi/CodeConvo huggingface dataset:
Change:
inherit version; src = fetchurl { url = "https://icl.cs.utk.edu/projectsfiles/magma/downloads/magma-${version}.tar.gz"; <del> sha256 = "0rrvd21hczxlm8awc9z54fj7iqpjmsb518fy32s6ghz0g90znd3p"; </del> <ins> hash = "sha256-dbVU2rAJA+LRC5cskT5Q5/iMvGLzrkMrWghsfk7aCnE="; </ins> name = "magma-${version}.tar.gz"; };

Discussion:
Build of failed on x86_64-linux as of . This is currently breaking . python3Packages.pytorchWithCuda maintainers cc: magma maintainers cc: Other cc: n/a nixpkgs at commit This issue was automatically generated by . that created this issue. Internal tag:
This looks like another gcc11 failure. could you take a look?
Sure thing
Going to attempt to bump from 2.5.4 (2020) to 2.6.2 (2022)
Change:
kwidgetsaddons kxmlgui <ins> breeze-icons </ins> marble oxygen threadweaver

Discussion:
Main problem: no icons in digikam. Digikam requires breeze icons. I've noticed in other bug reports that I need to do something like this: But when I run , there are no icon themes available to choose. Thanks!
Using: And searching for I see it looking in these two locations: But not in the nix store path where the icons reside. I can link that and see the icons in digikam: How is the icon location intended to be communicated?
Those links in my previous comment were created in the directory.
should look in each entry of for icon themes. Does your include ? That is where icon themes installed with will go. If that entry is not present in , then I think your shell is probably not configured correctly. If that entry is present, then there is probably a bug in if it isn't respecting that variable.
Indeed, does allow to see the icons. Next I'll investigate the setup. Thank you.
How should nixpkgs users know to include in ? isn't mentioned in , and it isn't configured automatically when sources . A carefully reading of suggests writing to create a derivation to fix up missing manual/info pages. I guess this would work for the missing icons too. In the short term, maybe XDGDATADIRS should be mentioned in one of these sections of the manuals. Am I overlooking a better mechanism?
Hello, I'm a bot and I thank you in the name of the community for opening this issue. To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human. The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use or on the relevant files to find them. Lastly, you can always ask for help at or at .
Change:
# https://downloads.haskell.org/~ghc/8.10.2/ src = fetchurl ({ i686-linux = { <del> url = "http://haskell.org/ghc/dist/${version}/ghc-${version}-i386-deb9-linux.tar.xz"; </del> <ins> url = "${downloadsUrl}/${version}/ghc-${version}-i386-deb9-linux.tar.xz"; </ins> sha256 = "0bvwisl4w0z5z8z0da10m9sv0mhm9na2qm43qxr8zl23mn32mblx"; }; x86_64-linux = { <del> url = "http://haskell.org/ghc/dist/${version}/ghc-${version}-x86_64-deb10-linux.tar.xz"; </del> <ins> url = "${downloadsUrl}/${version}/ghc-${version}-x86_64-deb10-linux.tar.xz"; </ins> sha256 = "0chnzy9j23b2wa8clx5arwz8wnjfxyjmz9qkj548z14cqf13slcl"; }; armv7l-linux = { <del> url = "http://haskell.org/ghc/dist/${version}/ghc-${version}-armv7-deb10-linux.tar.xz"; </del> <ins> url = "${downloadsUrl}/${version}/ghc-${version}-armv7-deb10-linux.tar.xz"; </ins> sha256 = "1j41cq5d3rmlgz7hzw8f908fs79gc5mn3q5wz277lk8zdf19g75v"; }; aarch64-linux = { <del> url = "http://haskell.org/ghc/dist/${version}/ghc-${version}-aarch64-deb10-linux.tar.xz"; </del> <ins> url = "${downloadsUrl}/${version}/ghc-${version}-aarch64-deb10-linux.tar.xz"; </ins> sha256 = "14smwl3741ixnbgi0l51a7kh7xjkiannfqx15b72svky0y4l3wjw"; }; x86_64-darwin = { <del> url = "http://haskell.org/ghc/dist/${version}/ghc-${version}-x86_64-apple-darwin.tar.xz"; </del> <ins> url = "${downloadsUrl}/${version}/ghc-${version}-x86_64-apple-darwin.tar.xz"; </ins> sha256 = "1hngyq14l4f950hzhh2d204ca2gfc98pc9xdasxihzqd1jq75dzd"; }; }.${stdenv.hostPlatform.system}

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: ghc <!-- 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: Please tag this issue in your PR.
Today I tried to install , but it failed at downloading : complained about hash mismatch. It seems like URL has changed.
I used the following overlay as a workaround:
Should work with .
Change:
DirectoryIndex index.php Require all granted <del> Options +FollowSymLinks </del> <ins> Options +FollowSymLinks -Indexes </ins> </Directory> # https://wordpress.org/support/article/hardening-wordpress/#securing-wp-config-php

Discussion:
Hello there, I recently installed a wordpress theme named nebula on my wordpress site, using the the nixos options in services.wordpress. Anyways, when I tried to activate the nebula plugin it threw a bunch of errors, which I fixed with the extraConfig option: define('FS_METHOD', 'direct'); but, I keep on getting another error message: [Nebula] Directory indexing not disabled (at the time last checked). Visitors may be able to see file listings of directories such as the Includes URL or Content URL (and/or others)! Run an audit to re-scan » In order to try and fix this I tried some wordpress plugins that automatically disable directory indexing, but they can't find the .htaccess file in the /nix/store/ ? Any tips on how to fix this issue declaratively using the nixos options? Note, when other plugins are activate this directory indexing error is not thrown, so I'm not even sure if this is a security issue or not? Activate the Nebula plugin. Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
I think we should set this in the module by default. Because then as far as I remember the FTP upload dialog doesn't show and as it's readonly anyways that's just more logical for the user. Would need to test if it actually does directory indexes currently but we should probably set It's readonly anyways so that doesn't work. Most plugins probably don't check that. P.S.: The wordpress module is really broken see
Reviewing the module it looks like you want something like this: Please try that and let me know how it goes. But also keep in mind...
, Thanks! I tried out the configuration you mentioned and no error is being thrown anymore, which is great.

But, that also caused another error to be thrown: Fatal error: Uncaught Error: arraydiff(): Argument ($array) must be of type array, bool given in /nix/store/7rip1dbvilj25rf4j9hn3az9q6mscfj3-wordpress- on line 197, Call stack: arraydiff() wp-content/themes/nebula- Nebula::dashboardnebulaataglance() wp- dometaboxes() wp- wp_dashboard() wp- I'm not sure if this error has to do with the configuration to disable directory indexing, or if it's an issue with the Nebula theme itself? Anyways, at least some good progress has been made with this issue. Thanks again for the help!
blind guess but maybe the plugin is not compatible with php8 yet
are we good to close this issue?
I think we should disable directory indexing in our module by default
are you able to make a PR for that?
Change:
xed = callPackage ../development/libraries/xed { }; <ins> xedit = callPackage ../applications/editors/xedit { }; </ins> xine-lib = callPackage ../development/libraries/xine-lib { }; xautolock = callPackage ../misc/screensavers/xautolock { };

Discussion:
Project description On some installations this simple text editor even has syntax highlightning, but it might require non-trivial amounts of work to get that part to work. Metadata homepage URL: source URL: Gitlab, , tag = or alternatively: latest current version: 1.2.2 license: MIT (according to the ebuild in the Gentoo repository) platforms: at least linux, but might also support other platforms with X11 support
I marked this as stale due to inactivity. &rarr;
I still need this.
Change:
githubId = 993484; name = "Greg Hale"; }; <ins> imlonghao = { email = "nixos@esd.cc"; github = "imlonghao"; githubId = 4951333; name = "Hao Long"; }; </ins> immae = { email = "ismael@bouya.org"; github = "immae";

Discussion:
borgmatic is simple, configuration-driven backup software for servers and workstations. Protect your files with client-side encryption. Backup your databases too. Monitor it all with integrated third-party services. Homepage: Source: License: GPL v3 () Platforms: UNIX, Linux, Darwin (I guess anywhere Python is supported)
I marked this as stale due to inactivity. &rarr;
Up!
Change:
<ins> diff --git a/test/run b/test/run index 43a57312..398be8d8 100755 --- a/test/run +++ b/test/run @@ -148,21 +148,17 @@ file_size() { objdump_cmd() { local file="$1" -    if $HOST_OS_APPLE; then -        xcrun dwarfdump -r 0 "$file" -    elif $HOST_OS_WINDOWS || $HOST_OS_CYGWIN; then +    if $HOST_OS_WINDOWS || $HOST_OS_CYGWIN; then # For some reason objdump only shows the basename of the file, so fall # back to brute force and ignorance. strings "$1" else -        objdump -W "$file" +        @objdump@ -W "$file" fi } objdump_grep_cmd() { -    if $HOST_OS_APPLE; then -        grep -Fq ""$1"" -    elif $HOST_OS_WINDOWS || $HOST_OS_CYGWIN; then +    if $HOST_OS_WINDOWS || $HOST_OS_CYGWIN; then grep -Fq "$1" else grep -Fq ": $1" </ins>

Discussion:
fails to build while cross-compiling on a host from . Steps to reproduce the behavior: from on a host Maintainer information:
I don't have any problems building , the tests are disabled in a cross compilation build. Are you doing anything extra to enable them? It seems like the failure can be fixed by replacing with , but I'm not sure how you've enabled the tests, so I can't verify if it works.
Yes, I'm surprised the tests are running at all in a cross-compilation scenario. Maybe you are already on a 32-bit build machine, but forcing the cross-compilation pathway with pkgsCross? Also, unrelated to this specific issue, if you are trying to build 32-bit binaries on an x86 host you may have better luck with , which tends to be more reliable as it builds natively.
Well, I did a quick test using in this configuration. I am not using it anymore and, as you mentioned, it probably was some kind of misconfiguration on my side. I will re-open the issue in case this is actually an issue. As a side note, that's what I was doing but I had to cross-compile in the end. Thanks for the suggestion! Sorry for bothering you and thank you for your prompt response!
I've encountered the same issue - not with , but with , more precisely (ccache wrapper correctly uses buildPackages). Edit: fixed
Change:
}: # Type aliases <del> # Gpu = { #   archName: String, # e.g., "Hopper" #   computeCapability: String, # e.g., "9.0" #   minCudaVersion: String, # e.g., "11.8" #   maxCudaVersion: String, # e.g., "12.0" # } </del> <ins> # Gpu :: AttrSet #   - See the documentation in ./gpus.nix. </ins> let inherit (lib) attrsets lists strings trivial versions;

Discussion:
Steps to reproduce the behavior: magma From : Also may be interested.
Is this related to the race condition error you saw before?
can you tell me more about what hardware you're using, and what your looks like? For reference, runs without issue for me with using a 4090 and an i9 13900k: EDIT: Would you also try building with I made some changes there that moved the CUDA runtime stub and NVCC into . I'm curious if that helps at all.
I don't think so -- closest I can remember to this was the linking error AMD HIP had with 2.7.x (which is why its stuck on magma 2.6.x), but that was a different inscrutable error from .
CPU is a Xeon Gold 5218 with Quadro RTX 8000 GPUs. I haven't set any configuration other than and .
I don't know why this issue isn't affecting your builds but most likely the fix is to set :
Haven't tried yet either, sorry.
Any idea when this failure started occurring?
magma 2.6.2 I believe works but 2.7.1 fails. I can try to bisect at some point if needed.
What channel were you building from by the way? I'm gonna try to find a way to match your setup but I need to know exactly which version of nixpkgs you're using to build.
Okay, I was able to reproduce it. It happened while a Nixpkgs-review for that magma PR I linked earlier. I suspect it has something to do with either my disabling or restricting . Time to investigate ‍
Something for me to look at later tonight; if it is the case that the increased number of cuda capabilities being targeted is causing the binary to bloat, check that we're using , like PyTorch : IIRC Magma doesn't set that flag. Also, I remember being unable to find specifically in the NVCC docs. Since PyTorch also ships binaries targeting a bunch of different CUDA capabilities, their configs are a goldmine of flags we might need to look into. EDIT: Haven't built with it yet, but it seems like it should fix it.

Apache MXNet had the same issue: EDIT2: Reminder to self: if that is the fix, add here: and here:
I know it's still a draft but can you try building again with I think it should fix your issue. Unrelated, but if you're building anything from source and you want faster builds I highly recommend specifying the single compute capability you need to build for (like I do here ) because it results in massively faster builds. HEAD right now builds for 14 different capabilities and that PR gets it down to 8, but it's much faster to build for just one.
is building for me from that branch (without any configuring compute capabilities yet), thanks.
Change:
cjdns = callPackage ../tools/networking/cjdns { }; <ins> cjson = callPackage ../development/libraries/cjson { }; </ins> cksfv = callPackage ../tools/networking/cksfv { }; clementine = libsForQt514.callPackage ../applications/audio/clementine {

Discussion:
Project description cJSON aims to be the dumbest possible parser that you can get your job done with. It's a single file of C, and a single header file. This is a new for mosquitto 2.0.0. There is a possible name clash as there is already a Lua and a Python implementation which are using as part of their name. Metadata homepage URL: source URL: license: MIT and ASL 2.0 platforms: Unix, unsure about the the others
PR for mosquitto update to 2.0.0 -
Change:
version = source.version; patches = (source.patches or []) <del> ++ optional jackSupport ./mumble-jack-support.patch </del> ++ [ ./fix-rnnoise-argument.patch ]; nativeBuildInputs = [ pkgconfig python qt5.qmake ]

Discussion:
I'm not entirely sure what's going on here yet but the mumble jack patch can probably / should probably be removed once lands in an upstream release.
Actually, the patch fails.
Actually I'm not sure what's going on here. Is this already in 1.3.0?
JACK works with , therefore the patch can be removed.
Change:
owner = "influxdata"; repo = "flux"; rev = "v${libflux_version}"; <del> hash = "sha256-gx6vnGOFu35wasLl7X/73eDsE0/50cAzjmBjZ+H2Ne4="; </del> <ins> hash = "sha256-XHT/+JMu5q1cPjZT2x/OKEPgxFJcnjrQKqn8w9/Mb3s="; </ins> }; patches = [ <del> # Fix build with recent rust versions </del> <ins> # Fix build on Rust 1.78 (included after v0.195.0) </ins> (fetchpatch { <del> url = "https://github.com/influxdata/flux/commit/6dc8054cfeec4b65b5c7ae786d633240868b8589.patch"; </del> <ins> name = "fix-build-on-rust-1.78.patch"; url = "https://github.com/influxdata/flux/commit/68c831c40b396f0274f6a9f97d77707c39970b02.patch"; </ins> stripLen = 2; extraPrefix = ""; <del> excludes = [ "rust-toolchain.toml" ]; hash = "sha256-w3z+Z26Xhy9TNICyNhc8XiWNSpdLA23ADI4K/AOMYhg="; </del> <ins> excludes = [ ]; hash = "sha256-6LOTgbOCfETNTmshyXgtDZf9y4t/2iqRuVPkz9dYPHc="; </ins> }) <del> ./no-deny-warnings.patch </del> <ins> ./fix-unsigned-char.patch </ins> ]; sourceRoot = "${src.name}/libflux"; <del> cargoSha256 = "sha256-MoI5nxLGA/3pduZ+vgmSG3lm3Nx58SP+6WXQl2pX9Lc="; </del> <ins> cargoHash = "sha256-O+t4f4P5291BuyARH6Xf3LejMFEQEBv+qKtyjHRhclA="; </ins> nativeBuildInputs = [ rustPlatform.bindgenHook ]; buildInputs = lib.optional stdenv.isDarwin libiconv; pkgcfg = ''

Discussion:
Steps to reproduce the behavior: There appears to be a cache miss, because starts to be compiled, but it fails. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
the maintainers to tag would be for v2 and and for v1 (all share the same build failure). v2 will be addressed via
Apologies. Thank you.
Change:
<ins> { lib, bash, buildGoModule, fetchFromGitHub, getent, stdenv }: buildGoModule rec { pname = "otel-cli"; version = "0.0.20"; src = fetchFromGitHub { owner = "equinix-labs"; repo = pname; rev = "v${version}"; hash = "sha256-bWdkuw0uEE75l9YCo2Dq1NpWXuMH61RQ6p7m65P1QCE="; }; vendorHash = "sha256-IJ2Gq5z1oNvcpWPh+BMs46VZMN1lHyE+M7kUinTSRr8="; preCheck = '' ln -s $GOPATH/bin/otel-cli . '' + lib.optionalString (!stdenv.isDarwin) '' substituteInPlace main_test.go  --replace 'const minimumPath = `/bin:/usr/bin`' 'const minimumPath = `${lib.makeBinPath [ getent ]}`' ''; meta = with lib; { homepage = "https://github.com/equinix-labs/otel-cli"; description = "A command-line tool for sending OpenTelemetry traces"; changelog = "https://github.com/equinix-labs/otel-cli/releases/tag/v${version}"; license = licenses.asl20; maintainers = with lib.maintainers; [ emattiza urandom ]; }; } </ins>

Discussion:
Project description OTel-CLI is a command-line application to enhance existing shell based applications with instrumentation and observability via OTLP and OpenTelemetry Metadata homepage URL: source URL: license: ASL2.0 platforms: linux
I marked this as stale due to inactivity. &rarr;
not stale, pr
Change:
license = licenses.lgpl2Plus; platforms = platforms.all; repositories.git = "git://git.gnupg.org/libgcrypt.git"; <ins> knownVulnerabilities = [ "CVE-2014-3591" "CVE-2015-0837" "CVE-2015-7511" "CVE-2017-0379" "CVE-2017-7526" "CVE-2017-9526" "CVE-2018-0495" "CVE-2018-6829" "CVE-2018-12437" ]; </ins> }; }

Discussion:
, CVSSv3=4.9 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: .
See also:
Spotify is using this.
What exactly needs to be done here? I'm not familiar with these vulnerability roundups.
We should remove from nixpkgs. Spotify is one of the packages preventing us from doing so. It would be nice if someone could look into using for Spotify.
Based on my understanding we're only using : though I could be mistaken.

, CVSSv3=7.5 (nixos-20.03, nixos-unstable) CVSSv3=7.5 (nixos-20.03, nixos-unstable) CVSSv3=6.8 (nixos-20.03, nixos-unstable) CVSSv3=5.9 (nixos-20.03, nixos-unstable) CVSSv3=5.9 (nixos-20.03, nixos-unstable) CVSSv3=4.7 (nixos-20.03, nixos-unstable) CVSSv3=4.2 (nixos-20.03, nixos-unstable) CVSSv3=2.0 (nixos-20.03, nixos-unstable) Scanned versions: nixos-20.03: ; nixos-unstable: . May contain false positives.
Change:
<del> { stdenv, fetchzip, fetchFromGitHub, file, libxslt, docbook_xml_dtd_412, docbook_xsl, xmlto </del> <ins> { stdenv, fetchurl, fetchFromGitHub , file, libxslt, docbook_xml_dtd_412, docbook_xsl, xmlto </ins> , w3m, which, gnugrep, gnused, coreutils , mimiSupport ? false, gawk ? null }:

Discussion:
To make sure that we are on the same page: Kernel: System: Nix version: Nixpkgs version: leads to error: should correctly recognize file type (as through command), but it fails with error 4 should return for pdf-file as command. Described above. I noticed that for installed xdg-utility is just a bash script and there is command inside funtion. gives May be this is the reason.
Change:
] }: let <del> version = "1.14.23"; sha256 = "sha256-NUkkLzLNh8P7PFh/SVtd9JM18w3egDaaK80urGw1SSs="; cargoSha256 = "sha256-7t8Quh6T2MzJWEM5Y50CgCyFfx2ZJRAdCpZyyYvJrt4="; </del> <ins> version = "1.16.27"; sha256 = "sha256-xd0FCSlpPJDVWOlt9rIlnSbjksmvlXJWHkvlZONd2dM="; </ins> inherit (darwin.apple_sdk_11_0) Libsystem; inherit (darwin.apple_sdk_11_0.frameworks) System IOKit AppKit Security; in rustPlatform.buildRustPackage rec { pname = "solana-cli"; <del> inherit version cargoSha256; </del> <ins> inherit version; </ins> src = fetchFromGitHub { owner = "solana-labs";

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:
postFetch = '' rm $out/mutagen # Keep only mutagen-agents.tar.gz. ''; <del> sha256 = "sha256-kQdlwNsZd/YrH5XagtQRA/1WFhw4fLmqQW+kZ4ykxfc="; </del> <ins> hash = "sha256-RFB1/gzLjs9w8mebEd4M9Ldv3BrLIj2RsN/QAIJi45E="; </ins> }; doCheck = false; subPackages = [ "cmd/mutagen" "cmd/mutagen-agent" ]; <ins> tags = [ "mutagencli" "mutagenagent" ]; </ins> postInstall = '' install -d $out/libexec ln -s ${agents}/mutagen-agents.tar.gz $out/libexec/

Discussion:
Mutagen crashes: Steps to reproduce the behavior: No crash Please run and paste the result.