jiebi/CodeConvo huggingface dataset:
Change:
<ins> { lib , stdenv , fetchFromGitHub , glib , gnome-themes-extra , libxml2 , sassc , util-linux }: stdenv.mkDerivation rec { pname = "whitesur-gtk-theme"; version = "2021-06-23"; src = fetchFromGitHub { owner = "vinceliuice"; repo = pname; rev = version; sha256 = "075fw57mv6zadq4dryn8bg2b3vq8inmisq18s758cv53pprxh9hw"; }; nativeBuildInputs = [ glib libxml2 sassc util-linux ]; buildInputs = [ gnome-themes-extra # adwaita engine for Gtk2 ]; postPatch = '' find -name "*.sh" -print0 | while IFS= read -r -d ''' file; do patchShebangs "$file"; done # Do not provide `sudo`, as it is not needed in our use case of the install script substituteInPlace lib-core.sh --replace '$(which sudo)' false ''; dontBuild = true; installPhase = '' runHook preInstall mkdir -p $out/share/themes ./install.sh --dest $out/share/themes --alt all --theme all runHook postInstall ''; meta = with lib; { description = "MacOS Big Sur like theme for Gnome desktops"; homepage = "https://github.com/vinceliuice/WhiteSur-gtk-theme"; license = licenses.mit; platforms = platforms.unix; maintainers = [ maintainers.romildo ]; }; } </ins>

Discussion:
Project description Create a package for the WhiteSur GTK theme. Metadata homepage URL: source URL: license: mit platforms: linux By the same author as the Mojave GTK theme that there is already a package for: This project uses a new build process though so I was unable to adapt the old package for the new theme. Additionally the install script supports a large number of parameters to customize the theme. The readme details how this works. It would be nice if the package supported setting those parameters.
Change:
- The `services.fwupd` module now allows arbitrary daemon settings to be configured in a structured manner ([`services.fwupd.daemonSettings`](#opt-services.fwupd.daemonSettings)). - The `unifi-poller` package and corresponding NixOS module have been renamed to `unpoller` to match upstream. <ins> - The new option `services.tailscale.useRoutingFeatures` controls various settings for using Tailscale features like exit nodes and subnet routers. If you wish to use your machine as an exit node, you can set this setting to `server`, otherwise if you wish to use an exit node you can set this setting to `client`. The strict RPF warning has been removed as the RPF will be loosened automatically based on the value of this setting. </ins>

Discussion:
I really appreciate this message, but also would like to be able to disable it. Most of my Tailscale machines are not exit nodes, nor do they act as subnet routers, hence I would prefer to leave strict filtering enabled and also not have these warnings. It seems like a small thing, but these warnings tend to make me blind to other new, more relevant warnings. I'm hacking on something here:
Thanks for raising this, have been ignoring this issue for ages and meaning to try to do something about it but never got around to it :sweat_smile:
Hah now I'm going to ask you for feedback - how does sound for the option name? It's wordy but I can't think of anything much better. ? but then that hits the issue where it removes the chance for users to see / opt-out of future warnings.
sounds fine, not aware of any existing convention for options to silence warnings.
Change:
ln -s ${libcef}/lib/* $out/lib/obs-plugins/ ''; <ins> passthru.updateScript = nix-update-script { }; </ins> meta = with lib; { description = "Free and open source software for video recording and live streaming"; longDescription = ''

Discussion:
Package name: obs-studio Latest released version: 30.1 <!-- Search your package here: --- Current version on the unstable channel: 30.0.2 Current version on the stable/release channel: 29.1.3 <!-- 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]:
Change:
buildPythonPackage rec { pname = "sounddevice"; <del> version = "0.3.12"; </del> <ins> version = "0.3.13"; </ins> src = fetchPypi { inherit pname version; <del> sha256 = "f59ae4e2ec12cb1e5940f06f08804ecca855d959de25ca45a3938de45d0f81a2"; </del> <ins> sha256 = "01x2hm3xxzhxrjcj21si4ggmvkwmy5hag7f6yabqlhwskws721cd"; </ins> }; propagatedBuildInputs = [ cffi numpy portaudio ];

Discussion:
sounddevice patching fails on unstable
I upgraded it to version 0.3.13 which and also fixed the outdated patch in
Change:
ln -sf $out/lib/libssl.so $out/lib/libssl.so.1.0.0 ''; }; <ins> opencv4' = symlinkJoin { name = "opencv4-compat"; nativeBuildInputs = [ makeWrapper ]; paths = [ opencv4 ]; postBuild = '' for so in ${opencv4}/lib/*.so; do ln -s "$so" $out/lib/$(basename "$so").407 done ''; }; </ins> in stdenv.mkDerivation rec {

Discussion:
Steps to reproduce the behavior: out current unstable: citrix-workspace: This also affects citrixworkspace23090 and citrixworkspace23070. system: host os: multi-user?: sandbox: version: channels(root): channels(username): nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Yeah, I ran into the same, unfortunately opencv is a massive expression, and the diff for the recent change was also massive, so inlining and overriding are IMO out. I ended up pulling opencv from a working commit ().
I observed the same issue yesterday and reached the same conclusion as Unfortunately, there is no newer version of Citrix Workspace available, leaving us with the November 2023 release that requires OpenCV 4.7. I attempted to use to enable compatibility with OpenCV 4.9, but alas without success. For now, it seems I will have to mark these packages as broken.
for anyone who has not had to mix nixpkgs versions before.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
</listitem> <listitem> <para> <ins> The WireGuard module gained a new option <option>networking.wireguard.interfaces.&lt;name&gt;.peers.*.dynamicEndpointRefreshSeconds</option> that implements refreshing the IP of DNS-based endpoints periodically (which WireGuard itself <link xlink:href="https://lists.zx2c4.com/pipermail/wireguard/2017-November/002028.html">cannot do</link>). </para> </listitem> <listitem> <para> </ins> MariaDB has been updated to 10.5. Before you upgrade, it would be best to take a backup of your database and read <link xlink:href="https://mariadb.com/kb/en/upgrading-from-mariadb-104-to-mariadb-105/#incompatible-changes-between-104-and-105">

Discussion:
On NixOS 20.09, steps to reproduce the behavior: setting up wireguard, change to another port still shows the old port:
This seems to be fixed by my PR
Change:
preFixup = '' wrapProgram "$out/bin/shotwell"  --set GDK_PIXBUF_MODULE_FILE "$GDK_PIXBUF_MODULE_FILE"  <del> --prefix XDG_DATA_DIRS : "$XDG_ICON_DIRS:${gtk3}/share:$out/share:$GSETTINGS_SCHEMAS_PATH" </del> <ins> --prefix XDG_DATA_DIRS : "$XDG_ICON_DIRS:${gtk3}/share:$out/share:$GSETTINGS_SCHEMAS_PATH"  --prefix GIO_EXTRA_MODULES : "${gnome3.dconf}/lib/gio/modules" </ins> rm $out/share/icons/hicolor/icon-theme.cache '';

Discussion:
Shotwell does not store its configuration when running under nix. Specifically, on startup, it says: Is there a standard way of fixing such issue in nix? In case it's relevant, I'm not running nixos, but the nixpkgs unstable channel on a Fedora box.
Try wrapping the binary with . Also on your non-nixos system you should have dconf installed at least.
Many thanks for the tip - I can confirm that this fixes the problem. I will submit a pull request later today.
Reopening, close when the fix is committed.
Sorry for closing prematurely; closing now. Thanks again for being so helpful!
Reopening, let's make sure this one is documented.
document what? This issue is closed, we can open another one for documentation. There's already an issue for documenting GNOME stuff iirc. Mostly because the commit refers to this issue.
"Documentation for Gnome3 packaging".
Change:
defaultText = literalExpression "pkgs.tailscale"; description = lib.mdDoc "The package to use for tailscale"; }; <ins> useRoutingFeatures = mkOption { type = types.enum [ "none" "client" "server" "both" ]; default = "none"; example = "server"; description = lib.mdDoc '' Enables settings required for Tailscale's routing features like subnet routers and exit nodes. To use these these features, you will still need to call `sudo tailscale up` with the relevant flags like `--advertise-exit-node` and `--exit-node`. When set to `client` or `both`, reverse path filtering will be set to loose instead of strict. When set to `server` or `both`, IP forwarding will be enabled. ''; }; </ins> }; config = mkIf cfg.enable { <del> warnings = optional (firewallOn && rpfIsStrict) '' Strict reverse path filtering breaks Tailscale exit node use and some subnet routing setups. Consider setting: networking.firewall.checkReversePath = "loose"; ''; </del> environment.systemPackages = [ cfg.package ]; # for the CLI systemd.packages = [ cfg.package ]; systemd.services.tailscaled = {

Discussion:
I really appreciate this message, but also would like to be able to disable it. Most of my Tailscale machines are not exit nodes, nor do they act as subnet routers, hence I would prefer to leave strict filtering enabled and also not have these warnings. It seems like a small thing, but these warnings tend to make me blind to other new, more relevant warnings. I'm hacking on something here:
Thanks for raising this, have been ignoring this issue for ages and meaning to try to do something about it but never got around to it :sweat_smile:
Hah now I'm going to ask you for feedback - how does sound for the option name? It's wordy but I can't think of anything much better. ? but then that hits the issue where it removes the chance for users to see / opt-out of future warnings.
sounds fine, not aware of any existing convention for options to silence warnings.
Change:
, util-linux , rsync , makeWrapper <ins> , wrapGAppsNoGuiHook </ins> , gettext , getconf , testers

Discussion:
Upon attempting to start the backup process, the following error is shown, resulting in the backup failing to start: Steps to reproduce the behavior: deja-dup (Backups) to create a backup Backup run properly without issues ! Similar to , but with a different Python library (Gio) Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I have located the derivation files for both the working and non-working version. working: non-working:
Thanks for reporting. probably needs I opened , could you please test it?
The fix works!
Change:
, dejavu_fonts , SDL2 , SDL2_ttf <ins> , SDL2_image </ins> }: let pname = "freenukum";

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: freenukum <!-- 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: 0.3.5 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. Homepage: Project's URL has to:
Thanks a lot, (all of you).
Change:
, gitUpdater }: <del> let </del> <ins> mkDerivation rec { </ins> pname = "gitqlient"; <del> version = "1.5.0"; </del> <ins> version = "1.6.2"; </ins> <del> main_src = fetchFromGitHub { </del> <ins> src = fetchFromGitHub { </ins> owner = "francescmm"; <del> repo = pname; </del> <ins> repo = "gitqlient"; </ins> rev = "v${version}"; <del> sha256 = "sha256-Mq29HbmPABrRIJjWC5AAKIOKbGngeJdkZkWeJw8BFuw="; }; aux_src = fetchFromGitHub rec { owner = "francescmm"; repo = "AuxiliarCustomWidgets"; rev = "835f538b4a79e4d6bb70eef37a32103e7b2a1fd1"; sha256 = "sha256-b1gb/7UcLS6lI92dBfTenGXA064t4dZufs3S9lu/lQA="; name = repo; }; qlogger_src = fetchFromGitHub rec { owner = "francescmm"; repo = "QLogger"; rev = "d1ed24e080521a239d5d5e2c2347fe211f0f3e4f"; sha256 = "sha256-NVlFYmm7IIkf8LhQrAYXil9kH6DFq1XjOEHQiIWmER4="; name = repo; }; qpinnabletab_src = fetchFromGitHub rec { owner = "francescmm"; repo = "QPinnableTabWidget"; rev = "cc937794e910d0452f0c07b4961c6014a7358831"; sha256 = "sha256-2KzzBv/s2t665axeBxWrn8aCMQQArQLlUBOAlVhU+wE="; name = repo; </del> <ins> fetchSubmodules = true; hash = "sha256-fHrsDEHEUgQYkZdnSzJ/+gTsV0eX8tOqSlr7vNH6LVs="; </ins> }; <del> git_src = fetchFromGitHub rec { owner = "francescmm"; repo = "git"; rev = "b62750f4da4b133faff49e6f53950d659b18c948"; sha256 = "sha256-4FqA+kkHd0TqD6ZuB4CbJ+IhOtQG9uWN+qhSAT0dXGs="; name = repo; }; in mkDerivation rec { inherit pname version; srcs = [ main_src aux_src qlogger_src qpinnabletab_src git_src ]; sourceRoot = main_src.name; </del> nativeBuildInputs = [ qmake

Discussion:
Package name: gitqlient Latest released version: 1.6.2 Current version on the unstable channel: 1.5.0 Current version on the stable/release channel: 1.5.0 Notify maintainers 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:
markdown-macros = callPackage ../development/python-modules/markdown-macros { }; <del> mathics = callPackage ../development/python-modules/mathics { }; </del> matplotlib = let path = if isPy3k then ../development/python-modules/matplotlib/default.nix else ../development/python-modules/matplotlib/2.nix;

Discussion:
The mathics test does not work because: /cc (commit history)
I see the same error with on the 20.03 beta channel. I think it also happens on Master. It used to work (maybe a few weeks ago? if I have time I'll bisect).
I removing mathics.
Change:
{ lib, <ins> stdenv, </ins> buildPythonPackage, pythonOlder, fetchFromGitHub,

Discussion:
Symptoms practically identical to . Steps to reproduce the behavior: (e.g. on ) when is enabled. Relevant section (): Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I dont know anything about cuda unfortunately. If anyone else has knowledge, im happy to help merge a PR though.
try passing to , thanks
looks like that worked.
Change:
# Required so as to avoid adding libspotify as a build dependency (as it is # unfree and thus would prevent us from having a free package). ./clementine-spotify-blob-remove-from-build.patch <ins> (fetchpatch { # Fix w/gcc7 url = "https://github.com/clementine-player/Clementine/pull/5630.patch"; sha256 = "0px7xp1m4nvrncx8sga1qlxppk562wrk2qqk19iiry84nxg20mk4"; }) </ins> ]; nativeBuildInputs = [ cmake pkgconfig ];

Discussion:
Clementine fails to build with latest nixpkgs, crashing with the following error: to install clementine. (Using modified version of nixpkgs )
Change:
# "--enable-foo" flags here configureFlags = [ "--with-kde-solid=$out/share/apps/solid/actions" <del> ] ++ optional onlyLibVLC "--disable-vlc"; </del> <ins> ] ++ optional onlyLibVLC "--disable-vlc" ++ optionals chromecastSupport [ "--enable-sout" "--enable-chromecast" "--enable-microdns" ]; </ins> # Remove runtime dependencies on libraries postConfigure = ''

Discussion:
The current vlc derivation does not include chromecast support. I believe we need to add the flags during the configuration step to enable it by default, which I think is a reasonable thing to do. I tried to do the minimal change myself, but looks like we need some new dependencies that don't exist in nixpkg yet: I'm still fairly new so it will take some learning to figure out what needs to be done to package protobuf-lite (not sure I'll get around to it anytime soon). If anyone else is into making these changes, it would be much appreciated. Or please let me know if I'm off-track here and there's a better way to do this.
You're on the right track. This should work:
Ah, now it builds, and I can see the relevant chromecast features, but it's still not finding the chromecast. Thank you! Sounds like that happens when microdns is not available. I tried adding nssmdns to the derivation but that didn't do the trick. is enabled. Hmmmm.
FWIW (mostly because I like linking things together), but sounds like you're past what is useful from that :). I frequently find chromecast programs on NixOS don't work... especially scanning support... with the firewall enabled. . Should only need mdns support for discovery/scanning, I think :).
Yea I did see that. I don't think it's the firewall, as google-chrome chromecasts fine. Even VLC via flatpak manages to connect to the chromecast (but fails to encode due to some other error). I believe mdns is used to find the chromecast automagically.
Make sure avahi is running and that mdns is set in resolvconf
Avahi is running and nssmdns is enabled, if that's what you mean. Is it working for you? Reading an older VLC PR: Sounds like we need VLC's own libmicrodns packaged before this will work: Edit: Indeed building with :
I managed to package up libmicrodns and it's working now! I'll clean up and send a PR. :) Thanks for the help everyone.
Change:
in stdenv.mkDerivation (finalAttrs: { pname = "kodi"; <del> version = "21.0"; </del> <ins> version = "21.1"; </ins> kodiReleaseName = "Omega"; src = fetchFromGitHub { owner = "xbmc"; repo  = "xbmc"; rev   = "${finalAttrs.version}-${finalAttrs.kodiReleaseName}"; <del> hash  = "sha256-xrFWqgwTkurEwt3/+/e4SCM6Uk9nxuW62SrCFWWqZO0="; </del> <ins> hash  = "sha256-NjId1T1cw9dl0Fx1QDsijiN1VUpuQ/EFl1kxWSESCR4="; </ins> }; patches = [

Discussion:
Package name: kodi Latest released version: 21.1 Current version on the unstable channel: 21.0 Current version on the stable/release channel: 21.0 Notify maintainers Release: Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
thanks for the ping! i am on it in the next day or two
Change:
}; }; <del> xen-vanilla = xen_4_5-vanilla; xen-slim = xen_4_5-slim; xen-light = xen_4_5-light; </del> <ins> xen-vanilla = xen_4_8-vanilla; xen-slim = xen_4_8-slim; xen-light = xen_4_8-light; </ins> }

Discussion:
Security support for Xen 4.5 (our current default version) ended January 2018, so we should change the default to 4.8 in 18.03 (and remove 4.5 in the future).
what's your opinion on this?
See .
Change:
./services/mail/dovecot.nix ./services/mail/dspam.nix ./services/mail/exim.nix <ins> ./services/mail/maddy.nix </ins> ./services/mail/mail.nix ./services/mail/mailcatcher.nix ./services/mail/mailhog.nix

Discussion:
Maddy, a small and compact mail server written in Go, was merged as a package with by . Having a NixOS module to enable and configure it would be really great! If someone is interested in creating a PR, I will be happy to help and test it :+1: Best regards Jonas
Hi, I dont have any sort of way to properly test this within the actual nixos repo but I've got a personal working module/service you can try
I did something very similar to the above, but based my serviceConfig on the example . It contains quite a bit more of the systemd security features, so if you want to make something to include in nixpkgs I think all these things should be on! I also hooked it up to Dovecot, hence the waiting script, not sure if that's the best way of doing it.
How about this: Nice and simple.
Have you tried this? Somehow it doesn't work for me:
- it looks like the units aren't included in the nixpkgs package :man_shrugging:, but I created a PR to fix this in Please review, test, and approve PR. I have never used so I wouldn't want to merge that PR without you (or someone else) testing. Thanks!
Change:
# error: unsafe buffer access env.NIX_CFLAGS_COMPILE = lib.optionalString stdenv.cc.isClang "-Wno-unsafe-buffer-usage"; <ins> patches = [ # nvcc doesn't recognize the "gsl" attribute namespace (microsoft/onnxruntime#13573) # only affects nvcc (fetchpatch { url = "https://raw.githubusercontent.com/microsoft/onnxruntime/4bfa69def85476b33ccfaf68cf070f3fb65d39f7/cmake/patches/gsl/1064.patch"; hash = "sha256-0jESA+VENWQms9HGE0jRiZZuWLJehBlbArxSaQbYOrM="; }) ]; </ins> doCheck = true; meta = with lib; {

Discussion:
Project description ONNX Runtime: cross-platform, high performance ML inferencing and training accelerator . Onnxruntime is already packaged. I would like to have the version with gpu support to be able to package obs-backgroundremoval with gpu support (). Related: Metadata homepage URL: source URL: license: mit platforms: linux
Obs-backgroundremoval includes tensorrtproviderfactory.h to build
need it, too
Is it possible to add gpu support to the obs-backgroundremoval as this issue is closed?
It may be possible. If anyone wants to open a PR for that, please base it on the current update PR
Change:
*/ { stdenv, lib, fetchurl, runCommand, writeText, buildEnv , callPackage, ghostscript_headless, harfbuzz <del> , makeWrapper </del> <ins> , makeWrapper, installShellFiles </ins> , python3, ruby, perl, tk, jdk, bash, snobol4 , coreutils, findutils, gawk, getopt, gnugrep, gnumake, gnupg, gnused, gzip, ncurses, zip , libfaketime, asymptote, biber-ms, makeFontsConf

Discussion:
texlive's texdoc has imported a . Maybe we can support it. can work, will search to get the package names but So there is still something needed to be done :cry:
Change:
"test_downloader_getter" "test_general" "test_get_config_dirs" <ins> "test_get_configuration" </ins> "test_get_data" "test_valid_dblp_key" "test_validate_arxivid"

Discussion:
Steps to reproduce the behavior: papis Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Seems to be a issue, I think?
I guess it fails [here][1]. Trying from the latest revision via following overlay doesn't help either Maybe this all is related to [this issue][2]. [1]: [2]:
Since the problem looks wider than the papis derivation, I disabled the problematic test temporarily: With this overlay the build succeeds.
Change:
"--skip serialize_test2_report" "--skip serialize_test3_report" "--skip serialize_test6_report" <del> "--skip test_package::case_2" "--skip test_package::case_3" "--skip test_package::case_6" </del> <ins> # multiple test cases that time-out or cause memory leaks "--skip test_package" </ins> "--skip test_package_update_readme::case_2" "--skip test_package_update_readme::case_3" "--skip test_package_update_readme::case_5"

Discussion:
Steps to reproduce the behavior: It takes a while to compile, but when finished the memory usage goes really high in the testphase, during in the step . I have to keyboard interrupt before oom-killer nukes my GUI. I have 16 GiB of RAM, so low memory shouldn't be the problem. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- I'm on a flake based system, so no channels.
Thanks for raising. It's probably case 4 & 7: Have you tried building the upstream project, both as is & in a nix sandbox? I'm thinking this isn't a nixpkgs specific issue. If you could raise an issue on the upstream repo I'll update and disable all tests under for now
yep i just set up a registry for the master branch and build the new version with and no memory overload, so that fixed it gonna try to build 0.11.5 and 6 without nix now
building "as is" means just cloning the project and using right? or do i have to build on a different distro?
Yeah thats it. Im guessing it will work fine but building the normal project with no networking causes the issue.