jiebi/CodeConvo huggingface dataset:
Change:
curl+=(--insecure) fi <ins> eval "curl+=($curlOptsList)" </ins> curl+=( $curlOpts $NIX_CURL_FLAGS

Discussion:
I was trying to download something that required that I put a token to the header. That has to be quoted mind you. Then I got these errors: Then it tries to download what's in the url, but It can't because that token authorizes it. Clearly not what I wanted :) Please run and paste the results. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: cc
This seems difficult to support. You could use or (e.g. ) instead.
I honestly think someone would expect this to just work like that. Perhaps there should be a note somewhere, if no one is interested in supporting this, that you cannot use quoted args here. Either of those are a workaround for me at least :+1: . But there could be more complex times when this isn't enough.
Actually you can use such quoted args only in scripts (e.g. or ). This could be made to work with Nix 2 and its structured attributes feature (even while maintaining compatibility with Nix 1):
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . on the on .
I believe this can still be implemented, and would be better than the current solution of writeText.
I just had this need in svanderburg/node2nix. The file workaround worked, but it took a very very long time to find this issue.
I marked this as stale due to inactivity. &rarr;
still an issue and why it is difficult to support? looks like a trivial bug
I marked this as stale due to inactivity. &rarr;
Change:
stdenv.mkDerivation (finalAttrs: { pname = "xorriso"; <del> version = "1.5.7"; </del> <ins> version = "1.5.7-unstable-2023-12-06"; </ins> src = fetchurl { <del> url = "https://www.gnu.org/software/xorriso/xorriso-${finalAttrs.version}.tar.gz"; hash = "sha256-hnV3w4f2tKmjIk60Qd7Y+xY432y8Bg+NGh5dAPMY9QI="; </del> <ins> url = "https://web.archive.org/web/20231206123448/https://www.gnu.org/software/xorriso/xorriso-1.5.7.tar.gz"; hash = "sha256-B7lV3n3e1aF7yJsLxwi8C8m3sBmUUePpCV9KfWRuTm0="; </ins> }; buildInputs = [

Discussion:
Steps to reproduce the behavior: without substituters. was replaced upstream: see . I had to it because GH was refusing to accept the upload for some reason. The calls 1.5.7 a "development snapshot", so I suppose from their perspective it's possible for it to change. Current source archive hashes:
Change:
fuse2fs # Mount ext3 filesystems go mount # mount <del> privileged-un-utils </del> squashfsTools # mksquashfs unsquashfs # Make / unpack squashfs image squashfuse # squashfuse_ll squashfuse # Mount (without unpacking) a squashfs image without privileges ] ++ lib.optional enableNvidiaContainerCli nvidia-docker;

Discussion:
Nixpkgs's package of Sylabs SingularityCE () now fails to execute image. After initial examination, the known cause is the failure to substitute default FHS s for some files, but the fix is WIP. Steps to reproduce the behavior: error. should succeed. If applicable, add screenshots to help explain your problem. Add any other context about the problem here. <!-- 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]:
singularity isn't supposed to work without setuid?
Yup. The error seems to result from failure to replace all the default paths after source file hierarchy changes.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
]; # Adapt from https://gitlab.gnome.org/GNOME/gnome-build-meta/blob/gnome-3-38/elements/core/meta-gnome-core-shell.bst <del> environment.systemPackages = with pkgs.gnome; [ adwaita-icon-theme nixos-background-info gnome-backgrounds gnome-bluetooth gnome-color-manager gnome-control-center gnome-shell gnome-shell-extensions gnome-themes-extra pkgs.gnome-tour # GNOME Shell detects the .desktop file on first log-in. pkgs.gnome-user-docs pkgs.orca pkgs.glib # for gsettings pkgs.gnome-menus pkgs.gtk3.out # for gtk-launch pkgs.hicolor-icon-theme pkgs.shared-mime-info # for update-mime-database pkgs.xdg-user-dirs # Update user dirs as described in http://freedesktop.org/wiki/Software/xdg-user-dirs/ ]; </del> <ins> environment.systemPackages = let mandatoryPackages = with pkgs.gnome; [ gnome-shell ]; optionalPackages = with pkgs.gnome; [ adwaita-icon-theme nixos-background-info gnome-backgrounds gnome-bluetooth gnome-color-manager gnome-control-center gnome-shell-extensions gnome-themes-extra pkgs.gnome-tour # GNOME Shell detects the .desktop file on first log-in. pkgs.gnome-user-docs pkgs.orca pkgs.glib # for gsettings program pkgs.gnome-menus pkgs.gtk3.out # for gtk-launch program pkgs.xdg-user-dirs # Update user dirs as described in http://freedesktop.org/wiki/Software/xdg-user-dirs/ ]; in mandatoryPackages ++ utils.removePackagesByName optionalPackages config.environment.gnome.excludePackages; </ins> }) # Adapt from https://gitlab.gnome.org/GNOME/gnome-build-meta/blob/gnome-3-38/elements/core/meta-gnome-core-utilities.bst

Discussion:
A clear and concise description of what the bug is. Steps to reproduce the behavior: install Nixos enabling Gnome An option to Exclude Gnome-Tour package or to exclude some Gnome-shell packages I would like to exclude some useless Gnome-shell packages that if i exclude them will not break my whole system. You can not exclude packages from Gnome-shell with this option and this not work because is required by this <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
This should be resolved in , but it is not part of 22.05, Edit:
How do I do a backport ? Thank you for your fast response.
It works. = with pkgs; [ gnome-tour ];
After doing this commands gnome tour still in my system. Do i need to do something more ? ! Maybe that ballon is not Gnome tour but i think it is.
It works in unstable channel, you need waitting for Backport 22.05 merge.
Thank you
I merged , not sure why the issue is not auto-closed. You should get the fix when the backport reaches the channel you uses, feel free to re-open this if the issue persists.
After waiting for being in Nixos 22.05, Writing this in And executing. That deleted Gnome-tour from my system. Thank you for your support.
Change:
]; buildInputs = [ dbus <ins> fftwFloat </ins> freetype jansson libGL

Discussion:
Package name: cardinal Latest released version: Current version on the unstable channel: v22.12 Current version on the stable/release channel: v22.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 Note for maintainers: Please tag this issue in your PR.
Change:
in stdenv'.mkDerivation rec { pname = "sunshine"; <del> version = "0.22.0"; </del> <ins> version = "0.22.2"; </ins> src = fetchFromGitHub { owner = "LizardByte"; repo = "Sunshine"; rev = "v${version}"; <del> sha256 = "sha256-O9U4zP1o6yWtzk+2DW7ueimvsTuajLY8IETlvCT4jTE="; </del> <ins> sha256 = "sha256-So8fX0XQoW2cdTWWENoE07EU6e8vvjeTpizLoaDTjeg="; </ins> fetchSubmodules = true; }; patches = [ # remove npm install as it needs internet access -- handled separately below ./dont-build-webui.patch <del> # revert https://github.com/LizardByte/Sunshine/pull/2046 - let cmake install handle udev and systemd files (fetchpatch { url = "https://github.com/LizardByte/Sunshine/commit/0d4dfcd708c0027b7d8827a03163858800fa79fa.patch"; hash = "sha256-77NtfX0zB7ty92AyFOz9wJoa1jHshlNbPQ7NOpqUuYo="; revert = true; }) </del> ]; # build webui ui = buildNpmPackage { inherit src version; pname = "sunshine-ui"; <del> npmDepsHash = "sha256-jAZUu2CfcqhC2xMiZYpY7KPCRVFQgT/kgUvSI+5Cpkc="; </del> <ins> npmDepsHash = "sha256-0487ntbJZ20MZHezQ+Z3EJkidF3Dgoh/mynYwR7k/+I="; </ins> # use generated package-lock.json as upstream does not provide one postPatch = ''

Discussion:
Package name: sunshine Latest released version: 0.22.2 <!-- Search your package here: --- Current version on the unstable channel: 0.22.0 Current version on the stable/release channel: 0.21.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: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
rustPlatform.buildRustPackage rec { pname = "topgrade"; <del> version = "14.0.0"; </del> <ins> version = "14.0.1"; </ins> src = fetchFromGitHub { owner = "topgrade-rs"; repo = "topgrade"; rev = "v${version}"; <del> hash = "sha256-sZUJMbFQiGw1Qqdtv+yExSnmaKd02+qIEgE3SHKYP6s="; </del> <ins> hash = "sha256-opTMV+OH8PR9SxBWj1o8xSngK0QdindDcXyd6TRjdvI="; </ins> }; <del> cargoHash = "sha256-XRVxPjvQT0XfhMMa+M4yLtTIpUl6Mtq9eM9wG2pkug8="; </del> <ins> cargoHash = "sha256-pgYrUZAxoyllQp1HuVhbLR3za+Gx0l8Z2/Zq/KCOKZg="; </ins> nativeBuildInputs = [ installShellFiles

Discussion:
Package name: Topgrade Latest released version: 14.0.1 <!-- Search your package here: --- Current version on the unstable channel: 13.0.0 Current version on the stable/release channel: 13.0.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]:
Maintainers:
Please search PRs before opening a new issue
I am sorry about this, I will close this issue
Change:
sampler = callPackage ../applications/misc/sampler { }; <ins> scalr-cli = callPackage ../tools/admin/scalr-cli { }; </ins> shairplay = callPackage ../servers/shairplay { avahi = avahi-compat; }; shairport-sync = callPackage ../servers/shairport-sync { };

Discussion:
Project description CLI for interacting with Scalr. Metadata homepage URL: source URL: license: apache 2 platforms: windows, linux, darwin
Change:
in rustPlatform.buildRustPackage rec { pname = "rio"; <del> version = "0.1.8"; </del> <ins> version = "0.1.10"; </ins> src = fetchFromGitHub { owner = "raphamorim"; repo = "rio"; rev = "refs/tags/v${version}"; <del> hash = "sha256-NLvCLyIts3NoSqbR9PIhXj3GCeURrBXXv/zVgZecfNQ="; </del> <ins> hash = "sha256-S42is3wqjBvYgysQ6yDUAn7ZEy9xJBmQD/emYAQfCkw="; </ins> }; <del> cargoHash = "sha256-TvNmTI3At2ezsdEOd5mAc6uUQXgGP47d0AMVVUUJr/A="; </del> <ins> cargoHash = "sha256-ILX3xrcz3tMnl7mUrwUAXv9ffaZKjSoSf8cZVQB10zk="; </ins> nativeBuildInputs = [ ncurses

Discussion:
Package name: rio Latest released version: 0.1.10 <!-- Search your package here: --- Current version on the unstable channel: 0.1.7 Current version on the stable/release channel: 0.0.39 <!-- 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]:
will do a PR this evening
Change:
linux_5_15 = recurseIntoAttrs (packagesFor kernels.linux_5_15); linux_5_16 = throw "linux 5.16 was removed because it reached its end of life upstream"; # Added 2022-04-23 linux_5_17 = recurseIntoAttrs (packagesFor kernels.linux_5_17); <ins> linux_5_18 = recurseIntoAttrs (packagesFor kernels.linux_5_18); </ins> }; rtPackages = {

Discussion:
Steps to reproduce the behavior: Tail of the build log The build failure seems related to these unused options. I tried removing the corresponding lines (in a local directory - so I changed my url to the filesystem path). in but it didn't fix anything. It seems that kernel 5.18 phased out some options. Instead of warning us, there's an explicit error. I have no idea how to fix this since is great for adding lines to the kernel config, but not great at removing them. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- (I'm not exactly sure who to notify about this so I just kind of scanned s of and . Please let me know if there's someone more appropriate to notify.) Please run and paste the result. Not sure how to do this for this specific package (no ).
Can you check if fixes this?
. But, it still fails:
Should be fixed by
I can confirm that fixes this! Thanks !
Change:
<del> { stdenv, fetchurl, makeWrapper }: </del> <ins> { stdenv, fetchurl, makeWrapper, ocl-icd, vulkan-loader, linuxPackages }: </ins> stdenv.mkDerivation rec { pname = "geekbench";

Discussion:
Describe the bug don't list compute devices Expected behavior I have a Radeon RX 480 and use PR to have OpenCL support in Mesa. BOINC and detects the GPU as OpenCL device. And even Vulkan seems to work: Same with Nvidia: Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
My next step would be to add as dependency and to the PATH. It works in BOINC.
That would be too easy... further debugging. So we need , , , and in the PATH. I figured it out!
Change:
nativeBuildInputs = [ jdk gradle <del> makeWrapper </del> <ins> wrapGAppsHook </ins> copyDesktopItems unzip ]; <ins> buildInputs = [ gtk3 ]; </ins> buildPhase = '' runHook preBuild

Discussion:
File open dialog results in crash due to missing GSettings schema path. This seems similar to Steps to reproduce the behavior: on "Open library" icon File open dialog opens. Please run and paste the result.
I can't reproduce it on a clean NixOS VM.
to reproduce these issues do to empty XDGDATADIRS
Great! Now I can reproduce it without a VM.
Please test
Thanks for the quick fix, works for me.
Would be nice if this could be backported (let's try with issue label on the PR again after it is merged, if you would be so kind to 22.05 as well.
I'll add the label. :ok_hand:
I am not sure whether this label should only be applied after the PR is successfully merged, i.e. only then does the action trigger, but let's see about that assumption.
Unfornately there is confilctions so the auto backport failed.
Thanks, yes, already saw it. Will open a manual backport PR.
Change:
<ins> { lib , buildGoModule , fetchFromGitHub , android-tools }: buildGoModule rec { pname = "fdroidcl"; version = "0.7.0"; src = fetchFromGitHub { owner = "mvdan"; repo = "fdroidcl"; rev = "v${version}"; hash = "sha256-tqhs3b/DHfnGOm9qcM56NSzt1GJflJfbemkp7+nXbug="; }; patches = [ ./go_mod_version_update.patch ]; vendorHash = "sha256-BWbwhHjfmMjiRurrZfW/YgIzJUH/hn+7qonD0BcTLxs="; postPatch = '' substituteInPlace adb/{server,device}.go  --replace 'exec.Command("adb"' 'exec.Command("${android-tools}/bin/adb"' ''; # TestScript/search attempts to connect to fdroid doCheck = false; meta = with lib; { description = "F-Droid command line interface written in Go"; homepage = "https://github.com/mvdan/fdroidcl"; license = licenses.bsd3; maintainers = with maintainers; [ aleksana ]; }; } </ins>

Discussion:
Project description <!-- Describe the project a little: --Command-line tool for managing and installing F-Droid APKs on an Android device via ADB. Metadata homepage URL: source URL: license: BSD 3-Clause platforms: unix, linux, darwin
Change:
"bigtable_read_sync_vs_async_benchmark", "bigtable_scan_throughput_benchmark", "bigtable_table_sample_rows_integration_test", <ins> "common_grpc_utils_internal_grpc_impersonate_service_account_integration_test", </ins> "iam_iam_credentials_integration_test", "iam_iam_integration_test", "logging_quickstart",

Discussion:
name: google-cloud-cpp current version: 1.38.0 desired version: 1.42.0 maintainers: who did the last update Please tag this issue in your PR.
I don't have time to work on this at the moment.
Change:
buildDotnetModule rec { pname = "osu-lazer"; <del> version = "2023.1026.0"; </del> <ins> version = "2023.1218.1"; </ins> src = fetchFromGitHub { owner = "ppy"; repo = "osu"; rev = version; <del> sha256 = "sha256-kbi4Um1MRctpwD7ndlcB+K7AxDbWHqAHmkJbEI0fNzI="; </del> <ins> sha256 = "sha256-VUnILNH5Ng1mx/UmlBGu6/yYXUOf1t3ofl0AiRHNsRc="; </ins> }; projectFile = "osu.Desktop/osu.Desktop.csproj";

Discussion:
Package name: osu-lazer Latest released version: <!-- Search your package here: --- Current version on the unstable channel: 2023.815.0 Current version on the stable/release channel: 2023.511.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 Note for maintainers: Please tag this issue in your PR.
Change:
patches = [ ./fix-cmake-config-includedir.patch <ins> (fetchpatch { name = "fix-pkgconfig-paths.patch"; url = "https://github.com/google/googletest/commit/5126ff48d9ac54828d1947d1423a5ef2a8efee3b.patch"; sha256 = "sha256-TBvECU/9nuvwjsCjWJP2b6DNy+FYnHIFZeuVW7g++JE="; }) </ins> ]; nativeBuildInputs = [ cmake ninja ];

Discussion:
Describe the bug The in contains the store path twice: To Reproduce Notify maintainers Metadata system: host os: multi-user?: sandbox: version:
Occasionally we have issues with pkg-config files and patching. implemented the start of a validatePkgConfig hook in I'm not sure if it'd catch this particular error, but it'd be great to add and enhance it so we have automation preventing regressions like this in the future.
This should be fixed in the next release: In the meanwhile, we should apply that as patches.
Thanks! I've opened I've also tried adding to the but I got this error:
Change:
gettext wrapGAppsHook ]; <ins> # Workaround for https://dev.gajim.org/gajim/gajim/-/issues/10719. # We don't use plugin release URL because it's updated in place. plugins = fetchFromGitLab { domain = "dev.gajim.org"; owner = "gajim"; repo = "gajim-plugins"; rev = "fea522e4360cec6ceacbf1df92644ab3343d4b99"; sha256 = "sha256-CmwEiLsdldoOfgHfWL/5hf/dp0HEDNAIlc5N0Np20KE="; }; postPatch = '' mkdir -p gajim/data/plugins cp -r $plugins/plugin_installer gajim/data/plugins ''; </ins> dontWrapGApps = true; preFixup = ''

Discussion:
does not build in nixpkgs-unstable, nixos-21.11 and master. The test phase fails with python import errors for emoji data. Thus gajim seems broken in current NixOS and branches. Steps to reproduce the behavior: (current head of nixos-21.11) Gajim builds without any errors. Possibly introduced by Please run and paste the result. Maintainer information:
Looks like it builds now in and
I confirm that after updating I got Gajim back.
Yup, can confirm. Works again, now.
Change:
<ins> { src, meta, version, stdenv, nodejs, pnpm, }: stdenv.mkDerivation (finalAttrs: { inherit version src meta; pname = "overlayed-webui"; pnpmDeps = pnpm.fetchDeps { inherit (finalAttrs) src pname version; hash = "sha256-FBJrVXTgKh8Op7TiZjA/i2LY2OOIKmqGR+GwGUecqVI="; }; nativeBuildInputs = [ nodejs pnpm.configHook ]; buildPhase = '' runHook preBuild cd apps/desktop node --max_old_space_size=1024000 ./node_modules/vite/bin/vite.js build runHook postBuild ''; installPhase = '' runHook preInstall cp -r dist $out runHook postInstall ''; }) </ins>

Discussion:
Project description Overlayed is a modern discord voice chat overlay. Metadata homepage URL: source URL: license: AGPL-3.0 platforms: unix, linux, darwin, windows Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
mv devilutionx.app $out/Applications '' else '' install -Dm755 -t $out/bin devilutionx <del> install -Dt $out/share/fonts/truetype ../Packaging/resources/CharisSILB.ttf install -Dt $out/share/diasurgical/devilutionx ../Packaging/resources/devilutionx.mpq # TODO: icons and .desktop (see Packages/{debian,fedora}/*) </del> <ins> install -Dm755 -t $out/share/diasurgical/devilutionx devilutionx.mpq install -Dm755 -t $out/share/applications ../Packaging/nix/devilutionx-hellfire.desktop ../Packaging/nix/devilutionx.desktop install -Dm755 ../Packaging/resources/icon.png $out/share/icons/hicolor/512x512/apps/devilution.png install -Dm755 ../Packaging/resources/hellfire.png $out/share/icons/hicolor/512x512/apps/devilution-hellfire.png </ins> '') + '' runHook postInstall

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: devilutionx <!-- 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: 1.2.1 desired version: 1.3.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. There are a number of changes in the new version, many of which make it difficult to package for nixpkgs.
Change:
hash = "sha256-hs71bIoByh5S1ncsku+y4X2i0yU65FknJE05lEmnru4="; }; <ins> nativeBuildInputs = [ pythonRelaxDepsHook ]; pythonRelaxDeps = [ # FIXME: Remove when >= 2.111.0 "attrs" "protobuf" ]; </ins> propagatedBuildInputs = [ attrs boto3

Discussion:
Steps to reproduce the behavior: nixpkgs electrum was recently updated 4.3.1 -4.3.2: previously built fine on nixpkgs 2022-09-28 () <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --<!-- attempting ti bisect, but on a slow machine, and it looks like there's miscellaneous failures over this duration so not sure it'll bisect cleanly: --
bisected to: good: bad: that's the staging-next merge though, so a lot of surface area. however, we appear to address a very similar build failure over in pkgs/development/python- by doing: i'm not sure how to test this same patch on electrum since it doesn't have any file.
oh just kidding, Electrum just places its in a different location. the patch below fixes the build when applied to master, and the application starts but i didn't test any functionality that i know touches protobuf. not sure how concerned i should be about overriding a pinned dep (i'm not a python dev):
Fix in