jiebi/CodeConvo huggingface dataset:
Change:
<del> { lib , symlinkJoin , buildPythonPackage </del> <ins> { buildPythonPackage , cudaSupport ? torch.cudaSupport or false # by default uses the value from torch </ins> , fetchFromGitHub <del> , ninja , which </del> <ins> , lib </ins> , libjpeg_turbo , libpng <ins> , ninja </ins> , numpy <del> , scipy </del> , pillow <del> , torch </del> , pytest <del> , cudaSupport ? torch.cudaSupport or false # by default uses the value from torch </del> <ins> , scipy , symlinkJoin , torch , which </ins> }: let <del> inherit (torch) gpuTargetString; inherit (torch.cudaPackages) cudatoolkit cudnn; </del> <ins> inherit (torch) cudaPackages gpuTargetString; inherit (cudaPackages) cudatoolkit cudaFlags cudaVersion; # NOTE: torchvision doesn't use cudnn; torch does! #   For this reason it is not included. cuda-common-redist = with cudaPackages; [ cuda_cccl # <thrust/*> libcublas # cublas_v2.h libcusolver # cusolverDn.h libcusparse # cusparse.h ]; </ins> <del> cudatoolkit_joined = symlinkJoin { name = "${cudatoolkit.name}-unsplit"; paths = [ cudatoolkit.out cudatoolkit.lib ]; </del> <ins> cuda-native-redist = symlinkJoin { name = "cuda-native-redist-${cudaVersion}"; paths = with cudaPackages; [ cuda_cudart # cuda_runtime.h cuda_nvcc ] ++ cuda-common-redist; </ins> }; <del> in buildPythonPackage rec { </del> <ins> cuda-redist = symlinkJoin { name = "cuda-redist-${cudaVersion}"; paths = cuda-common-redist; }; </ins> pname = "torchvision"; version = "0.14.1"; <ins> in buildPythonPackage { inherit pname version; </ins> src = fetchFromGitHub { owner = "pytorch";

Discussion:
As per the title, the current CUDA and stdenv versions used to build are seemingly incompatible and can lead to build failures stating this (specifically - see below - but likely others as well). ~Likely introduced in ~ [of course it was the actual stdenv bump], but as it's a dynamic failure it's not a triviality to add an assert to to catch similar errors in future. with CUDA-enabled (e.g. in or override in ). Observe the build fails with the following output:
cc
This should be fixed when is merged.
Change:
<ins> { lib , stdenv , fetchFromGitHub , gtk3 , meson , ninja , json_c , pkg-config , gtk-layer-shell , libpulseaudio , libmpdclient , libxkbcommon , }: stdenv.mkDerivation rec { pname = "sfwbar"; version = "1.0_beta11"; src = fetchFromGitHub { owner = "LBCrion"; repo = pname; rev = "v${version}"; sha256 = "PmpiO5gvurpaFpoq8bQdZ53FYSVDnyjN8MxDpelMnAU="; }; buildInputs = [ gtk3 json_c gtk-layer-shell libpulseaudio libmpdclient libxkbcommon ]; nativeBuildInputs = [ meson ninja pkg-config ]; meta = with lib; { homepage = "https://github.com/LBCrion/sfwbar"; description = "A flexible taskbar application for wayland compositors, designed with a stacking layout in mind"; platforms = platforms.linux; maintainers = with maintainers; [ NotAShelf ]; license = licenses.gpl3Only; }; } </ins>

Discussion:
Project description SFWBar (S Floating Window Bar) is a flexible taskbar application for wayland compositors, designed with a stacking layout in mind. Metadata homepage source license: GPL-3.0 platforms: unix, linux
I'll take a look at this.
Would it be possible to get this updated to version 1.0_beta14 Beta 14 has been out since Jan 2, unstable still only has beta 13 Thanks
Please don't bump closed threads for update requests, the correct way would be to open an out of date package report in
Change:
sha256 = "1klq8j70q8r8hyqv1wi6jcx8g76yh46bh8614y82zzggn4cx6y3r"; }; <ins> patches = [ (fetchpatch { name = "CVE-2019-11459.patch"; url = "https://gitlab.gnome.org/GNOME/evince/commit/3e38d5ad724a042eebadcba8c2d57b0f48b7a8c7.patch"; sha256 = "1ds6iwr2r9i86nwrly8cx7p1kbvf1gljjplcffa67znxqmwx4n74"; }) ]; </ins> postPatch = '' chmod +x meson_post_install.py patchShebangs meson_post_install.py

Discussion:
, (nixos-unstable) Scanned versions: nixos-unstable: . May contain false positives.
Change:
{ puppet-lint = { <ins> groups = ["default"]; platforms = []; </ins> source = { remotes = ["https://rubygems.org"]; <del> sha256 = "1wyk2l440d96ps3x127r52n51kqpqi2nzb3xlg92qn6aksqhnkis"; </del> <ins> sha256 = "1rcj3cb6lf90g6vvhh3c9p8yn7pgibglf9k5878bzd6pn5ag0h9v"; </ins> type = "gem"; }; <del> version = "2.3.6"; </del> <ins> version = "2.5.2"; </ins> }; }

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: puppet-lint <!-- 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: 2.3.6 desired version: 2.5.2 <!-- 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:
ghdl-llvm = callPackage ../development/compilers/ghdl { backend = "llvm"; <ins> inherit (llvmPackages_15) llvm; </ins> }; gcl_2_6_13_pre = callPackage ../development/compilers/gcl/2.6.13-pre.nix { };

Discussion:
Steps to reproduce the behavior: type: I have none. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Context: caused because last supported version for 3.0.0 is llvm 15: Should be easy enough to fix, thanks for reporting.
Change:
singularity-overriden-nixos ; <del> sfwbar = callPackage ../applications/misc/sfwbar { }; </del> skate = callPackage ../applications/misc/skate { }; slack = callPackage ../applications/networking/instant-messengers/slack { };

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:
githubId = 75371; name = "Stig Palmquist"; }; <ins> sg-qwt = { email = "hello@edgerunners.eu.org"; matrix = "@dhl:edgerunners.eu.org"; github = "sg-qwt"; name = "sg-qwt"; githubId = 115715554; }; </ins> sgraf = { email = "sgraf1337@gmail.com"; github = "sgraf812";

Discussion:
Project description A tool for formatting Clojure code, used by many editor plugins <!-- Describe the project a little: --Metadata homepage URL: source URL: license: EPL-1.0 platforms: linux, darwin
Change:
fontconfig-ultimate has been removed. The repository has been archived upstream and activity has ceased for several years. https://github.com/bohoomil/fontconfig-ultimate/issues/171. ''; <ins> # 2020-07-21 fontconfig_210 = throw '' fontconfig 2.10.x hasn't had a release in years, is vulnerable to CVE-2016-5384 and has only been used for old fontconfig caches. ''; </ins> font-droid = throw "font-droid has been deprecated by noto-fonts"; # 2019-04-12 foomatic_filters = foomatic-filters;  # 2016-08 fuse_exfat = exfat;                   # 2015-09-11

Discussion:
, CVSSv3=7.8 (nixos-20.03) Scanned versions: nixos-20.03: . May contain false positives.
See also:
PR for unstable: PR for 20.03:
This is still an issue.
oops, sorry
We only use config files. We could probably just delete everything but from the derivation, or remove it from top-level.
Yeah, but we still ship the fontconfig binary in nixpkgs. Is there any reason we still need to provide config files parse-able by 2.10.x fontconfig implementations?
I doubt there is much of a reason these days, nobody will be running programs compiled against fontconfig 2.10. I just do not want to remove it now so that possible breakage caused by is not mixed with potential downfall from removing the unversioned path.
is a new attempt to address this.
Change:
lxvst_path = "/usr/local/lib64/lxvst:/usr/local/lib/lxvst:/usr/lib64/lxvst:/usr/lib/lxvst:" "/usr/local/lib64/linux_vst:/usr/local/lib/linux_vst:/usr/lib64/linux_vst:/usr/lib/linux_vst:" -			"/usr/lib/vst:/usr/local/lib/vst"; <del> +			"/usr/lib/vst:/usr/local/lib/vst:" </del> <ins> +			"/usr/lib/vst:/usr/local/lib/vst:$HOME/.nix-profile/lib/vst:" </ins> +			"$HOME/.lxvst:$HOME/.nix-profile/lib/lxvst:/run/current-system/sw/lib/lxvst:/etc/profiles/per-user/$USER/lib/lxvst"; }

Discussion:
The patched version of Ardour in nixpkgs is not able to open VST2 audio plugins also installed from nixpkgs. All VST2 plugins are detected, but say they can’t be opened by Ardour. For example, having installed the ardour and lsp-plugins nixpkgs packages, the Ardour plugin manager shows the status “Error”: ! The error given for one of the VST2 plugins is: Steps to reproduce the behavior: Ardour and some VST2 plugins from nixpkgs (e.g. "ardour" and "lsp-plugins" packages) Ardour and scan for plugins The plugins are detected and can be used. I'm running NixOS 23.11 and installing these things declaratively with home-manager. i.e.: <!-- 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]:
I suspect is not actually a plugin, but a shared library used by the plugins in the same directory like which loads fine for me: Are you sure the actual plugins are affected? !
I tested with and and I was able to see both of those, but I'm able to reproduce other vst2 plugins (like LSP) not showing. Could it be that they're not in ardour's vst2 scan path? !
nixpkgs patches Ardour to find other plugin types, but I think i've to the plugin search path manually.
Hi guys, thanks for taking the time to look into this issue. You're right about the shared library not being a plugin - this was a red herring that was stopping me from understanding the problem. I just to my plugin search path and everything I was missing has now loaded in successfully. Thank you! To prevent other users from experiencing this problem (and possibly me if I change systems and forget this fix), can this path be to the list that the nixpkgs patch adds to ardour?
Change:
}; nativeBuildInputs = [ cmake makeWrapper pkgconfig ]; <del> buildInputs = [ libusb ncurses numpy python swig2 ]; </del> <ins> buildInputs = [ libusb ncurses ] ++ lib.optionals usePython [ python swig2 ]; propagatedBuildInputs = lib.optional usePython python.pkgs.numpy; </ins> cmakeFlags = [ "-DCMAKE_BUILD_TYPE=Release" <del> "-DUSE_PYTHON_CONFIG=ON" ]; </del> <ins> ] ++ lib.optional usePython "-DUSE_PYTHON_CONFIG=ON"; </ins> postFixup = lib.optionalString (lib.length extraPackages != 0) '' # Join all plugins via symlinking

Discussion:
The soapysdr package contains a Python binding, but it is not possible to use it normally (e.g. via ) because it is not registered as a Python package in nixpkgs. I am not sure what is the proper way of handling this case, since soapysdr is both a regular library and a Python package, and nixpkgs makes a distinction between the two. A workaround is to add. Cc
See the section "15.17.2.2.4. toPythonModule function" in the Nixpkgs manual.
Change:
, gtkSupport ? stdenv.isLinux , cairo , glib <ins> , gtk2 </ins> , gtk3 <ins> # runtime dependencies for JavaFX , ffmpeg </ins> }: let dist = dists.${stdenv.hostPlatform.system}

Discussion:
Attempt to build with JavaFX: . The build fails due to being unable to satisfy dependencies. The issue seems to occur for other versions of as well. Build was attempted in a flake with Nixpkgs pinned to , <!-- 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]:
I remember encountering this during a last bump, but eventually abandoned it because something like point to obsolete versions of ffmpeg that no longer exist in Nixpkgs. I'll probably mark with on Linux as broken at some time this week.
Oh, there's actually for that. Would you please test if works?
Change:
meta = with lib; { description = "Ticketing software that cares about your event—all the way"; <del> mainProgram = "pretix-manage"; </del> homepage = "https://github.com/pretix/pretix"; license = with licenses; [ agpl3Only

Discussion:
The pretix package does not contain generated locales for , causing internal server errors when trying to select this language (concretely when clients try to access ). Steps to reproduce the behavior: the pretix module with an organizer and select german-informal in the localisation settings. the organiser profile, be greeted by an "Internal Server Error" page. Be present with the actual requested page instead of an http/500 one. The E-Mail sent out to the admin contains more details: This seems to be related to the of django. Looking in the requested is missing. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
The pypi wheel is missing it as well, but the hosted version does have it. :thinking:
The locale is seen by , but not by , which originates in Happens to as well.
It's also noteworthy that is compiling e.g. , which is not in the output of :thinking:
This list seems more reasonable, no? :laughing:
I do have the feeling, that this happens because there is not pretix configuration at build time. From checking just a couple of languages, the ones showing up in appear to match the ones in And whilst pretix has it's own , they do not set defaults for . To my understanding (based on heavy use of ;)), pretix only sets based on the user-provided settings (see ).
Yep, that's why. I'm preparing a patch.
Indeed, that looks purrfect!
Change:
spacy-loggers = callPackage ../development/python-modules/spacy-loggers { }; <del> spacy_models = callPackage ../development/python-modules/spacy/models.nix { }; </del> <ins> spacy_models = callPackage ../development/python-modules/spacy/models.nix { inherit (pkgs) jq; }; </ins> spacy-pkuseg = callPackage ../development/python-modules/spacy-pkuseg { };

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 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: python310Packages.spacy_models (not found in nix search, but available in REPL) <!-- The current version can be found easily with the same process as 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.3.0 desired version: 3.4.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 (finalAttrs: { pname = "mutter"; <del> version = "44.1"; </del> <ins> version = "44.2"; </ins> outputs = [ "out" "dev" "man" "devdoc" ]; src = fetchurl { url = "mirror://gnome/sources/mutter/${lib.versions.major finalAttrs.version}/mutter-${finalAttrs.version}.tar.xz"; <del> sha256 = "lzrq+rQvBvk0oJlPyEh4lYzbTSdmpMhnpczcVH3VcFY="; </del> <ins> sha256 = "N1ZtflXJPciJTpx/I6e6WHmoswuvZVWCIwCdK0Z0AqE="; </ins> }; mesonFlags = [

Discussion:
Package name: gnome-shell Latest released version: 44.2 <!-- Search your package here: --- Current version on the unstable channel: 44.1 Current version on the stable/release channel: 44.1 <!-- 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.

Since the Gnome 44 (under wayland) update, on multiple devices reproducible errors with Qt based applications. nextcloud-client: The application does not show itself after first start, it is only visible in Activities as an empty frame. You have to restart the application and it works. keepassxc: The Drag-and-Drop functionality does not work. This are only two errors that I found, but I think many Qt-applications are affected. The solution is to set inside a shell and start the application. The errors vanish. Currently, my workaround is setting it global with Perhaps, can you add the variable as a default setting for each gnome under wayland session? Thank you <!-- 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.
Could you please try if fixes it?
Does not solve the problem.
QT has also issue with wireshark (QTSTYLEOVERRIDE)
strawberry player is also affected. Outputs: When running: drag and drop works, without that env variable drag and drop does not work. Did not found a way that works on X11.
I am also experiencing this issue, under x11. 's drag and drop does not work, which renders the program almost unusable.
Also experiencing this issue with QGIS.
has possible fix for
Will this get backported to stable?
Already happened
Change:
''; postFixup = '' <del> for autostart in $(grep -rl "OnlyShowIn=GNOME;" $out/etc/xdg/autostart) do echo "Patching OnlyShowIn to Pantheon in: $autostart" sed -i "s,OnlyShowIn=GNOME;,OnlyShowIn=Pantheon;," $autostart done # This breaks lightlocker https://github.com/elementary/session-settings/commit/b0e7a2867608c3a3916f9e4e21a68264a20e44f8 # TODO: shouldn't be neeed for the 5.1 greeter (awaiting release) rm $out/etc/xdg/autostart/org.gnome.SettingsDaemon.ScreensaverProxy.desktop </del> # So the polkit policy can reference /run/current-system/sw/bin/elementary-settings-daemon/gsd-backlight-helper mkdir -p $out/bin/elementary-settings-daemon ln -s $out/libexec/gsd-backlight-helper $out/bin/elementary-settings-daemon/gsd-backlight-helper

Discussion:
Describe the bug Open indicator and see the following in journal The error at the top comes from now depending on settings schema (provided by ibus). This situation is annoyingly complex, because we cannot wrap . So what we try to do is create a wrapper with all the transitive dependencies of the plugins and call it day. We used to do patches to hardcode the gsettings, but this was far to much work to maintain and could be prone to developer error sometimes. I'm thinking the easiest solution would be to add all the transitive dependencies of to , and then wingpanel's can pick up all the proper dependencies. I think the only ideal request I could make to Pantheon upstream is to make use of SearchProviders from GNOME I believe this basically should be the very thing they want. They currently have a forked version of synapse's plugins system which IMHO appears to be inferior. To Reproduce Steps to reproduce the behavior: wingpanel-with-indicators the switchboard-plugin process get killed Expected behavior The switchboard-plugin process doesn't die. Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
Change:
''; }; <del> nginx.recommendedHttpHeaders = mkOption { type = types.bool; default = true; description = "Enable additional recommended HTTP response headers"; </del> <ins> nginx = { recommendedHttpHeaders = mkOption { type = types.bool; default = true; description = "Enable additional recommended HTTP response headers"; }; hstsMaxAge = mkOption { type = types.ints.positive; default = 15552000; description = '' Value for the <code>max-age</code> directive of the HTTP <code>Strict-Transport-Security</code> header. See section 6.1.1 of IETF RFC 6797 for detailed information on this directive and header. ''; }; </ins> }; };

Discussion:
The header should only be if is enabled, right?
I don't think so. The description for that option says "Use https for generated links." The commit you linked is from last Feburary (which may be the version in NixOS 21.11 – I'm not sure), and on , that header is controlled by the boolean option . The upstream project recommendes this header, as far as I can tell, and the Nextcloud admin panel warns you if this is not set, so I think it is semantically correct for this header to be if the "recommended HTTP headers" flag is set, but it does get in the way if you are trying to serve Nextcloud as a Tor .onion service, where you don't want to be using SSL/TLS.
Good to hear that it is different in master, but it is not just onion services, many internal services lack tls because the vpn or tls termination is done downstream and nextcloud only speaks http. I would expect we want a single boolean to turn on/off tls, no?
I had not thought of that use case. I would say that is a good reason to have this controlled by the same flag.
Change:
<ins> { lib, buildGoModule, fetchFromGitHub, }: buildGoModule rec { pname = "c3-lsp"; version = "0.3.2"; src = fetchFromGitHub { owner = "pherrymason"; repo = "c3-lsp"; rev = "v${version}"; hash = "sha256-HD3NE2L1ge0pf8vtrKkYh4GIZg6lSPTZGFQ+LPbDup4="; }; sourceRoot = "${src.name}/server"; vendorHash = "sha256-y+Qs3zuvTq/KRc1ziH0R7E10et+MaQW9xOsFmSdI7PM="; postInstall = '' mv $out/bin/lsp $out/bin/c3-lsp ''; meta = { description = "Language Server for C3 Language"; homepage = "https://github.com/pherrymason/c3-lsp"; changelog = "https://github.com/pherrymason/c3-lsp/blob/${src.rev}/changelog.md"; license = lib.licenses.gpl3Only; maintainers = with lib.maintainers; [ arthsmn ]; mainProgram = "c3-lsp"; platforms = lib.platforms.all; }; } </ins>

Discussion:
Project description c3-lsp is language server for Metadata homepage URL: source URL: - license: gpl3 platforms: linux Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I am not a professional in nix packaging so sorry for not providing .nix file (
Change:
, mesonEmulatorHook , fetchurl , python3 <ins> , python3Packages </ins> , pkg-config , gtk3 , gtk-mac-integration

Discussion:
Gedit is missing the pycairo dependency (python311Packages.pycairo specifically in my case) I'm on the unstable channel I'm new to nix, so maybe an indirect dependency is missing the pycairo dependency instead a terminal will periodically (~1 per second) print the error message see no errors with: . No error message should be printed. I'm using the Nix package manager on Manjaro Linux. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]: