jiebi/CodeConvo huggingface dataset:
Code change:
rm -rf $out/include rm -rf $out/lib/*.a mv $out/bin/chat $out/bin/${finalAttrs.meta.mainProgram} <ins> install -D ${finalAttrs.embed_model} $out/resources/nomic-embed-text-v1.5.f16.gguf </ins> install -m 444 -D $src/gpt4all-chat/flatpak-manifest/io.gpt4all.gpt4all.desktop $out/share/applications/io.gpt4all.gpt4all.desktop <del> install -m 444 -D $src/gpt4all-chat/icons/logo.svg $out/share/icons/hicolor/scalable/apps/io.gpt4all.gpt4all.svg </del> <ins> install -m 444 -D $src/gpt4all-chat/icons/nomic_logo.svg $out/share/icons/hicolor/scalable/apps/io.gpt4all.gpt4all.svg </ins> substituteInPlace $out/share/applications/io.gpt4all.gpt4all.desktop  --replace-fail 'Exec=chat' 'Exec=${finalAttrs.meta.mainProgram}' '';

Related discussion:
text: Package name: gpt4all Latest released version: 3.2.1 <!-- Search your package here: --- Current version on the unstable channel: 2.8.0 Current version on the stable/release channel: 2.7.5 <!-- 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]:
Hi, I don't maintain GPT4All any longer, I switched to some other technologies (Open-WebUI).
haha, maybe i'll give that one a try then :) ty for all your hard work
Code change:
inherit (python2Packages) mutagen python wrapPython; }; <ins> dsp = callPackage ../tools/audio/dsp { }; </ins> dirdiff = callPackage ../tools/text/dirdiff { tcl = tcl-8_5; tk = tk-8_5;

Related discussion:
text: Project description is an audio processing program with an interactive mode. Also has a LADSPA frontend. Metadata homepage URL: source URL: license: isc platforms: linux
Code change:
<ins> { lib , buildPythonPackage , fetchFromGitHub , pythonOlder , setuptools , setuptools-scm , libxcrypt , numpy , qt6 , qtpy , pyqt6 , pytestCheckHook , pytest-cov }: buildPythonPackage rec { pname = "echo"; version = "0.8.0"; disabled = pythonOlder "3.6"; src = fetchFromGitHub { owner = "glue-viz"; repo = pname; rev = "v${version}"; sha256 = "sha256-0FmUA7kOFSRZXwbj8d7asujBPOjE2pFhu6TDNSGD4r0="; }; nativeBuildInputs = [ setuptools setuptools-scm qt6.wrapQtAppsHook ]; buildInputs = lib.optionals (pythonOlder "3.9") [ libxcrypt ]; propagatedBuildInputs = [ qt6.qtconnectivity qt6.qtbase qt6.qttools pyqt6 numpy qtpy ]; env.SETUPTOOLS_SCM_PRETEND_VERSION = version; # collecting ... qt.qpa.xcb: could not connect to display # qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. doCheck = false; nativeCheckInputs = [ pytestCheckHook pytest-cov ]; pythonImportsCheck = [ "echo" ]; meta = with lib; { homepage = "https://github.com/glue-viz/echo"; description = "Callback Properties in Python"; license = licenses.mit; maintainers = with maintainers; [ ifurther ]; }; } </ins>

Related discussion:
text: Project description Glue is a python project to link visualizations of scientific datasets across many files. Click on the image for a quick demo: ! Metadata homepage URL: source URL: license: BSD Linux, BSD
Code change:
"--outfile", pubcert ) except: <del> rmtree(basedir) </del> <ins> rmtree(userdir) </ins> raise

Related discussion:
text: So I today I spawned a machine with and satisfyingly the directory was generated with all of the certificates etc that taskwarrior needs, including the clients' certificates. I noticed that the users' keys located at are owned by root with read only permissions for the root user alone. No matter what are and . I'd like to enable the group read those client keys, as well as the file so that I can configure a client easily. Thankfully the group can read the file, but not the client keys. The manual indeed explains that the command: Could be used to get those keys, but I'd like to use syncthing for that to automate the process even further. I got a bit lost while reading the . Specifically, I'm not sure why does always works in the following umask: I mean, ~why not~ - a solution is suggested in . A word of comment will be appreciated. cc .
Code change:
pushover-complete = callPackage ../development/python-modules/pushover-complete { }; <ins> pvextractor = callPackage ../development/python-modules/pvextractor { }; </ins> pvlib = callPackage ../development/python-modules/pvlib { }; pvo = callPackage ../development/python-modules/pvo { };

Related discussion:
text: Project description Glue is a python project to link visualizations of scientific datasets across many files. Click on the image for a quick demo: ! Metadata homepage URL: source URL: license: BSD Linux, BSD
Code change:
<ins> { gnome3, fetchFromGitHub, autoconf, automake, gtk_doc, gettext, libtool, gperf }: gnome3.vte.overrideAttrs (oldAttrs: rec { name = "vte-ng-${version}"; version = "0.46.1.a"; src = fetchFromGitHub { owner = "thestinger"; repo = "vte-ng"; rev = version; sha256 = "125fpibid1liz50d7vbxy71pnm8b01x90xnkr4z3419b90lybr0a"; }; # The patches apply the changes from https://github.com/GNOME/vte/pull/7 and # can be removed once the commits are merged into vte-ng. patches = [ ./fix_g_test_init_calls.patch ./fix_vteseq_n_lookup_declaration.patch ]; preConfigure = oldAttrs.preConfigure + "; ./autogen.sh"; nativeBuildInputs = [ gtk_doc autoconf automake gettext libtool ]; buildInputs = oldAttrs.buildInputs ++ [ gperf ]; }) </ins>

Related discussion:
text: The package has been . Trying to install results in the following error: Why was the package marked as broken? Is there a way to help fix it? System: Nix version: Nixpkgs version:
According to the project homepage it requires a different version of the vte library: If you package this one and add it as a dependency the package should work again.
Thanks for the response . Could you help understand the reasoning behind the commit that marked it as broken? Was the problem that was being packaged with the wrong dependency?
The dependency it needs is not in NixPkgs, so it has to be packaged and nobody cared enough to do it.
We had the patched vte under gnome-3.20, but 3.20 was now removed whole without porting that to the vte in 3.22. EDIT: refs and .
I've wasted hours trying to fix building the special vte library, you may try to continue: This fails with: I don't see marking one package broken preferable to keeping the whole gnome-3.20 in tree, sadly. Please open a pull request if you manage to succeed, but I don't see myself wasting more time on this otherwise soon.
I fixed the errors you found during compilation and submitted a PR to upstream VTE. As the changes may take a while to propagate down into vte-ng, I them as patches to the vte-ng package, which is now used to compile termite.
Code change:
```ShellSession $ cd /path/to/nixpkgs/doc $ nix-shell <del> [nix-shell]$ make $makeFlags </del> <ins> [nix-shell]$ make </ins> ``` If you experience problems, run `make debug` to help understand the docbook errors.

Related discussion:
text: Describe the bug To contribute to the nixpkgs documentation I followed the instructions in the nixpkgs manual "Chapter 21. Contributing to this documentation" and I followed the code snippet Firstly I was greeted with some warnings: But moving on to I saw a large number of errors. It looks like is set up inside the nix-shell but it's not picked up by ? Running the command does work. To Reproduce Expected behavior No warnings, no errors. Metadata Please run and paste the result. Maintainer information:
nix-shell has a specific setup to allow running stdenv phases such as
That also gives me a bunch of errors as well, but different ones: For a bunch of files. I managed to write some updates to the docs and validated them just using the command, but it's a bit unfortunate that just following the instructions literally doesn't work.
Sorry about that. should fix it.
Thanks, that fixes it for me (tested by setting the env variable manually). Great to see these steps towards making it easier to contribute to the docs.
Code change:
configureFlags = [ "--localstatedir=/var" "--sysconfdir=/etc" <ins> ] ++ optionals withCloud [ "--enable-cloud" "--with-aclk-ng" </ins> ]; postFixup = ''

Related discussion:
text: Project description Netdata agent plugin Metadata homepage URL: source URL: license: GPL 3.0 platforms: unix, linux, darwin We already do have netdata, however it seems to be built without support for the cloud agent that allows it to stream to the cloud or other netdata servers.
I have a local checkout with some edits that allow me to build netdata with cloud support. Unfortunately they also require a change in the libwebsockets build expression. Should I open a PR to integrate my changes into nixpkgs?
A PR would be great! I'm not a maintainer, but if they decide it's out of scope for nixpkgs, perhaps one on NUR might work - I'd try for a PR here first though
Great, I think having a configuration option that is per default would make sense. Maybe ?
Yeah, that seems to fall in line with the various flags present in other packages
I marked this as stale due to inactivity. &rarr;
Upstream has incorporated some of the suggestions in this thread, I intend to pick up on it again soon
what would be needed to make this work? Perhaps I can help?
The newest major release of Netdata (1.30.0) includes a cloud link implementation without the need for vendored dependencies. Unfortunately, it is not currently in a reliable state because of a bug in the custom HTTPS implementation. The has already been merged into Netdata master and will be included in the next release. I plan to make a PR that enables cloud support as soon as that release is available.
v1.31.0 dropped 12 minutes ago :) Anything I can do to help?
Thanks, I've already gotten a notification for that. Planning to make a PR when I get off work today. When my PR is done, it would be helpful if you could test my changes on your machines.
Just FYI, I have opened the PR that enables cloud support a few days ago. If you are still interested it would be greatly appreciated if you could test if everything works for you and maybe drop a comment.
Sorry, missed this but the pr looks good! I propose we backport this to stable?
Code change:
grep -l -r '/bin/bash' --null | xargs -0 sed -i -e "s!/bin/bash!${bash}/bin/bash!g" ''; <del> nativeBuildInputs = [ makeWrapper python3 jdk11 ant watchman ]; </del> <ins> nativeBuildInputs = [ makeWrapper python3 jdk8 ant watchman ]; </ins> buildPhase = '' # Set correct version, see https://github.com/facebook/buck/issues/2607

Related discussion:
text: Buck build system is packaged with the wrong JDK it seems PR introduced a bump in JDK version, see (). Metadata Please run and paste the result. Maintainer information:
I guess the most recent version should support java 11:
Until they make a stable release with those changes included, we will just use jdk8
Code change:
<del> { lib , stdenv , fetchFromGitHub , alsa-lib , cmake , ffmpeg , fribidi , game-music-emu , libXdmcp , libXv , libass , libcddb , libcdio , libpulseaudio , libsidplayfp , libva , libxcb , pkg-config , qtbase , qttools , taglib , vulkan-headers , vulkan-tools , wrapQtAppsHook }: stdenv.mkDerivation (finalAttrs: { pname = "qmplay2"; version = "24.04.07"; src = fetchFromGitHub { owner = "zaps166"; repo = "QMPlay2"; rev = finalAttrs.version; fetchSubmodules = true; hash = "sha256-WIDGApvl+aaB3Vdv0sHY+FHWqzreWWd3/xOLV11YfxM="; }; nativeBuildInputs = [ cmake pkg-config wrapQtAppsHook ]; buildInputs = [ alsa-lib ffmpeg fribidi game-music-emu libXdmcp libXv libass libcddb libcdio libpulseaudio libsidplayfp libva libxcb qtbase qttools taglib vulkan-headers vulkan-tools ]; postInstall = '' # Because we think it is better to use only lowercase letters! ln -s $out/bin/QMPlay2 $out/bin/qmplay2 ''; meta = { homepage = "https://github.com/zaps166/QMPlay2/"; description = "Qt-based Multimedia player"; longDescription = '' QMPlay2 is a video and audio player. It can play all formats supported by FFmpeg, libmodplug (including J2B and SFX). It also supports Audio CD, raw files, Rayman 2 music and chiptunes. It contains YouTube and MyFreeMP3 browser. ''; changelog = "https://github.com/zaps166/QMPlay2/releases/tag/${finalAttrs.version}"; license = lib.licenses.lgpl3Plus; maintainers = with lib.maintainers; [ AndersonTorres kashw2 ]; platforms = lib.platforms.linux; }; }) </del>

Related discussion:
text: Package name: Latest released version: <!-- Search your package here: --- Current version on the unstable channel: Current version on the stable/release channel: <!-- 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.
Code change:
<del> { lib, stdenv, fetchurl, pkg-config, freeglut, libGLU, libGL, libcdio, libjack2 , libsamplerate, libsndfile, libX11, SDL2, SDL2_net, zlib, alsa-lib }: </del> <ins> { lib , stdenv , fetchurl , SDL2 , SDL2_net , alsa-lib , flac , freeglut , libGL , libGLU , libX11 , libcdio , libjack2 , libsamplerate , libsndfile , pkg-config , zlib }: </ins> stdenv.mkDerivation rec { pname = "mednafen"; <del> version = "1.26.1"; </del> <ins> version = "1.29.0"; </ins> src = fetchurl { url = "https://mednafen.github.io/releases/files/${pname}-${version}.tar.xz"; <del> sha256 = "1x7xhxjhwsdbak8l0iyb497f043xkhibk73w96xck4j2bk10fac4"; </del> <ins> hash = "sha256-2j+88Ch3+b4PAov6XRy1npU6QEm5D+fjk4ijOG2fNi4="; </ins> }; nativeBuildInputs = [ pkg-config ]; buildInputs = [ <ins> SDL2 SDL2_net alsa-lib flac </ins> freeglut <del> libGLU libGL </del> <ins> libGL libGLU libX11 </ins> libcdio libjack2 <del> alsa-lib </del> libsamplerate libsndfile <del> libX11 SDL2 SDL2_net </del> zlib ];

Related discussion:
text: <!-- 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: mednafen <!-- 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: 1.26.1 (dated November 10, 2020) desired version: 1.29.0 (dated January 19, 2022) <!-- 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.
Code change:
<del> { lib, buildNpmPackage, fetchFromGitHub, vscode }: </del> <ins> { lib, stdenv, buildNpmPackage, fetchFromGitHub, vscode }: </ins> buildNpmPackage rec { pname = "vscode-langservers-extracted";

Related discussion:
text: Steps to reproduce the behavior: nixos-unstable to home.packages -rebuild build Please run and paste the result.
Code change:
umurmur = callPackage ../applications/networking/umurmur { }; <del> udocker = pythonPackages.callPackage ../tools/virtualization/udocker { }; </del> <ins> udocker = callPackage ../tools/virtualization/udocker { }; </ins> uefitoolPackages = recurseIntoAttrs (callPackage ../tools/system/uefitool/variants.nix {}); uefitool = uefitoolPackages.new-engine;

Related discussion:
text: I just discovered and i can't use it on NixOS Pulling image seems good Trying to run image fail because it try to mount some specials folders The : Trying without mounting folder fail because it can't find Start a shell with still fail because it can't find Please run and paste the results. system: host os: multi-user?: sandbox: version: channels(pinage404): channels(root): nixpkgs:
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 .
It could still be important.
I marked this as stale due to inactivity. &rarr;
Code change:
<ins> diff --git a/MathMod.pro b/MathMod.pro index 2e2fbf1..bb8f8bd 100644 --- a/MathMod.pro +++ b/MathMod.pro @@ -63,7 +63,5 @@ OTHER_FILES     +=  mathmodcollection.js  mathmodconfig.js # install -target.path    = $TARGET -sources.files  = $$SOURCES $$HEADERS $$RESOURCES $$FORMS mathmod.pro -sources.path   = $TARGET -INSTALLS      += target sources +target.path    = @out@/bin +INSTALLS      += target </ins>

Related discussion:
text: Project description Mathematical modelling software Metadata homepage URL: source URL: license: gpl2 platforms: cross-platform
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 . 3. Ask on the on .
I marked this as stale due to inactivity. &rarr;
Code change:
}; }; <ins> disableImagemagick = mkOption { type = types.bool; default = false; description = '' Whether to not load the ImageMagick module into PHP. This is used by the theming app and for generating previews of certain images (e.g. SVG and HEIF). You may want to disable it for increased security. In that case, previews will still be available for some images (e.g. JPEG and PNG). See https://github.com/nextcloud/server/issues/13099 ''; }; </ins> caching = { apcu = mkOption { type = types.bool;

Related discussion:
text: There is about the use of imagemagick in NextCloud due to . Admins may want to disable it unless they are certain that users won't upload untrusted files (which can easily happen by accident if folder sync is active). NextCloud is only passing certain file types to imagemagick but it is doing so based on the file extension. Therefore, an attacker can pass any file type to imagemagick. I have tested this with a PNM image (not supported by NextCloud) that I have renamed to . doesn't get a preview image but does, i.e. NextCloud thinks it is HEIF and passes it to ImageMagick, which processes it as PNM. There are several ways to disable imagick: in the NextCloud config. This will not only disable imagick but also previews for PNG and JPEG (which do not use imagick). in the NextCloud config. This may need manual adjustment after a NextCloud update. the extension for PHP. This also disables it for NextCloud plugins. Option 1 and 2 can already be used by an admin if the drawbacks are acceptable. However, I think 3 is the best option in most cases. has options that disable the other PHP extensions that used to be by default. I think we should do the same for imagick. If imagick is disabled, NextCloud will automatically disable the preview generators that need it. It will also show a warning about that (which is subject to debate in the issue linked above) and there may be some implications for the themes app (which I don't use). Therefore, I think we should keep imagick enabled by default and leave the decision to the admin. We could also add a suitable policy for ImageMagick and thereby disable any file formats or features that are considered insecure. I don't think I could write such a policy and be sure that it is secure (or even "secure enough"). In addition, we will have to keep it up-to-date with newer versions and CVEs. That is why I recommend that we only add a simple off switch. The above information is based on NextCloud 20. I will wait until and NextCloud 21 have landed in nixos-unstable (and on my server) and then test again and create a PR if there is any interest in having this upstream.
Code change:
}; }; <ins> disableImagemagick = mkOption { type = types.bool; default = false; description = '' Whether to not load the ImageMagick module into PHP. This is used by the theming app and for generating previews of certain images (e.g. SVG and HEIF). You may want to disable it for increased security. In that case, previews will still be available for some images (e.g. JPEG and PNG). See https://github.com/nextcloud/server/issues/13099 ''; }; </ins> caching = { apcu = mkOption { type = types.bool;

Related discussion:
text: Ouch, decisions based purely on a file ext is a behavior that sounds pretty broken to me :/ Optiobally disabling imagemagick and adjusting the config accordingly sounds reasonable to me, so feel free to file a PR. You can ping me for a review or if you need assistance with modifying the module :)
It's ok for what they do with it. It won't do double duty as a mitigation but I guess that was never intended. Thanks. Any suggestions on a name for the new option? Simply ? Should I add any tests for that? The existing tests only test three different configurations so adding one just for imagick seems like overkill. It should be quite easy though. If we want to test that previews actually aren't generated... Well, that's a different story. We would have to automate the web interface, for that. I think the existing tests are only testing the service, CLI and WebDAV.
As imagemagick enabled will remain the default, I'd suggest . Yes, adding a fourth VM test just for imagemagick is indeed an overkill IMHO since those tend to be fairly expensive. I'd suggest to write a testcase in , other integrations such as are also tested there. Right that could be a non-trivial thing to solve. Maybe check if there's a REST API or a way to implement this with the CLI of . But I don't think it'd be worth spending too much time on this if there's no reasonable way to test :)
I think we still want to test the default option in so we will need a second configuration that disables imagick. We don't have to start that VM if we only want to check whether imagick is in its closure. As there isn't any test helper for that, we probably don't want to do that though ;-) see Unfortunately, qemu on ARM is too unreliable for the automatic tests because qemu crashes when started on one of the little cores (i.e. 4 out of 6 times). I have done some interactive testing of the above commit but not an automated run. I will have to find some system that is not ARM, not high-security, not already virtualized...
Qemu/KVM does work if a kernel build or stress-ng is hogging the big cores :) is ready for review.