jiebi/CodeConvo huggingface dataset:
Change:
environment = env; }; <del> # Reading the user-provided password file requires root access systemd.services.paperless-copy-password = mkIf (cfg.passwordFile != null) { requiredBy = [ "paperless-scheduler.service" ]; before = [ "paperless-scheduler.service" ]; serviceConfig = { ExecStart = '' ${pkgs.coreutils}/bin/install --mode 600 --owner '${cfg.user}' --compare  '${cfg.passwordFile}' '${cfg.dataDir}/superuser-password' ''; Type = "oneshot"; }; }; </del> systemd.services.paperless-consumer = { description = "Paperless document consumer"; # Bind to `paperless-scheduler` so that the consumer never runs

Discussion:
I want to use but with and residing on an NFS mounted path. My NFS server is secured to only allow access from . I also have enabled on my NFS server, as is the recommended best practice. But the paperless module uses tmpfiles to ensure those directories are created, but root does not have permission to create files in the nfs share. Result: To be clear the nfs mounted path is so and are inside the mount. Notably the paperless service still works, if I ensure those directories exist myself. But the tmpfiles rules setup service still errors out. One workaround I thought might work would be to set and to and then set those env vars myself. However the NixOS module requires those two options to be set. Possible fixes: sub-directories could be created inside a systemd service that is running as the user. this wouldn't work without some shenangiams because if the dir is something like the user won't have permissions to make and optional so the admin can manage setting them this isn't ideal because then the user also has to muck with a flag to bypass the and let the admin manage it themselves. this my favored option I'm happy to open a PR if the maintainers like one of those options. Steps to reproduce the behavior: with and on nfs monts those directories don't exist in the nfs mount should work without error. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
GEM remote: https://rubygems.org/ specs: <del> puppet-lint (2.3.6) </del> <ins> puppet-lint (2.5.2) </ins> PLATFORMS ruby

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:
buildPythonPackage rec { pname = "youtube-search-python"; <del> version = "1.5.2"; </del> <ins> version = "1.5.3"; </ins> disabled = pythonOlder "3.6"; src = fetchPypi { inherit pname version; <del> sha256 = "33f0d58f4803b0b2badf860cd31fb83d3f7edecdd2c01dd09cd6511abbf0e6b9"; </del> <ins> sha256 = "4bc39224d1f0915692101a7739289c41173de2eb88b445aabc7be284802b7489"; </ins> }; propagatedBuildInputs = [ httpx ];

Discussion:
Upgrading fails, seemingly because the existing systemd version is newer in 21.11 than unstable. Steps to reproduce the behavior: NixOS 21.11 21.11 channel, add unstable channel NixOS upgrades from 21.11 to unstable. is the commit upgrading systemd to 249.7, cherry picks it to 21.11. Adding the flag to the invocation would also solve this issue, albeit leaving the newer EFI files in place. <!-- 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.
I think the corresponding PR is
As pointed out above by this will be fixed when staging-next gets merged ().
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
nativeBuildInputs = [ autoPatchelfHook makeWrapper ]; buildInputs = [ <del> dbus glib libGL libX11 libXfixes libuuid libxcb qtbase qtdeclarative qtlocation qtquickcontrols2 qtscript qtwebchannel qtwebengine libjpeg_turbo ]; </del> <ins> dbus glib libGL libX11 libXfixes libuuid libxcb qtEnv libjpeg_turbo ] ++ qtDeps; </ins> runtimeDependencies = optional pulseaudioSupport libpulseaudio;

Discussion:
Zoom GUI is not shown on current master () This started to happen after package refactoring (, , ), and not due to package upgrade (I've checked that). I've documented some findings already ping and other Zoom users. Am I alone with this issue? At this moment no GUI (no greeting window) is shown. system: host os: multi-user?: sandbox: version: channels(root): channels(danbst): nixpkgs:
I at least cannot reproduce this with on nixpkgs
I installed to a profile using your reproduction steps, and it works fine here. What is in your in your shell? At least here it's:
I was able to reproduce this via: So there's some piece of the environment missing in the package.
This also reproduces the issue: Currently investigating what needs on the $PATH.
Thanks for your efforts, but when writing a command can you (and everyone else) please be complete? I had time to quickly confirm what you wanted to say, but here I am telling you that it is not a valid test case. I wrote an example of a complete command in closed thread with zoom in the title started by myself, so it's not like I don't practice this myself.
Sorry about that. As the package is unfree, you'll need in or in your environment. So a complete standalone test case would be:
does this reproduce issue too? I've checked that commit (last revision of old zoom-us expression) launches fine for me with this bash command.
It sounds like it was caused by using autoPatchelf? It could be that there is some incompatibility between what zoom-us is built with and what we have locally. Maybe we should just revert that part (but leave the version updates). I would much prefer to use Nixpkgs Qt here but there is a lot of unknown in how zoom-us is built. It might just be safest to revert to the old expression.
Turns out the issue was missing QML2 imports. This was discovered by comparing: to and looking for libraries loaded by the latter but not the former. One fix was to add a environment variable to the wrapper, but I found it simpler to re-use to build an environment with all the Qt dependencies symlinked in place and using its . The package should be easier to maintain as a result since you don't have to know what feature each qt5 package is meant to provide.
Change:
github = "pennae"; githubId = 82953136; }; <ins> perchun = { name = "Perchun Pak"; email = "nixpkgs@perchun.it"; github = "PerchunPak"; githubId = 68118654; }; </ins> peret = { name = "Peter Retzlaff"; github = "peret";

Discussion:
Project description <!-- Describe the project a little: --Metadata homepage URL: source URL: license: Not sure platforms: macOS - not sure about others Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Don't know if you got a notification, but I created a PR for this request - .
Change:
buildGoModule = buildGo112Module; }; <del> inherit (callPackage ../applications/networking/cluster/terraform {}) </del> <ins> inherit (callPackage ../applications/networking/cluster/terraform { # terraform 0.12 crashes with go1.14 on darwin https://github.com/hashicorp/terraform/issues/24287 buildGoPackage = if stdenv.isDarwin then buildGo113Package else buildGoPackage; }) </ins> terraform_0_11 terraform_0_11-full terraform_0_12

Discussion:
Describe the bug terraform012 crashes on macos 10.14.6 mojave To Reproduce Steps to reproduce the behavior: terraform012 from (I also built locally on ) : Expected behavior A the version number should be printed. Additional context terraform011 does not crash. I was able to work around the problem by building building terraform012 using go 1.12 (this patch against nixpkgs): Metadata Please run and paste the result. Maintainer information:
upstream issue would you mind creating a PR with your patch but with ?
Looks like you beat me to it, thank you.
Change:
paperless = 315; #mailman = 316;  # removed 2019-08-30 zigbee2mqtt = 317; <ins> # shadow = 318; # unused </ins> # When adding a uid, make sure it doesn't match an existing gid. And don't use uids above 399!

Discussion:
Describe the bug Currently, /etc/shadow belongs to the root group. For many use cases, this poses no problems, but when some program needs to use PAM to authenticate on the behalf of multiple users, the program needs to be executed as root (which seems generally unacceptable security-wise). One example is PAM authentication in Nginx, where the (see discussion on this). Expected behavior I think it's reasonable for /etc/shadow to belong to a group called "shadow" so users can make the decision on letting some programs/users read /etc/shadow. . If maintainers agree this is a reasonable thing to do, and if someone can confirm if this change is as simple as adding a group called shadow and adding a line in update-users- chown-ing /etc/shadow to root:shadow, then I'll create a PR. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
I've tackled this in PTAL.
Just as a reminder, the 20.09 release is scheduled to happen this monday, the 28th. If this is still relevant to blocking the release, then there should be some forward movement. A blocker meeting has still yet to be scheduled. But, if you consider this item to still warrant blocking the entirety of the nixos-20.09 release, the please do so on the . A template for proposing an item can be found
As soon as the above PR is merged (), it can be backported to 20.09, and this issue won't be blocking 20.09 anymore.
Change:
# The unwrapped libreoffice derivation , unwrapped , makeWrapper <ins> , xorg # for lndir </ins> , runCommand , substituteAll # For Emulating wrapGAppsHook

Discussion:
i can no longer use libreoffice headlessly i suspect this is due to the rewrite of the wrapper additionally, the binary is no longer provided, only etc, which are supposed to be usable headlessly too and maybe more impactful, attempting to launch the GUI with doesn't work either Steps to reproduce the behavior: -, -for a known working .odt file or project using the headless feature, see (already amended to attempt to use instead of ) to open libreoffice with the appropriate sub-app with that file open to open libreoffice writer with that file open to yield to yield error window on ! due to , the wrapper rewrite which seems to have introduced this issue
Aish... didn't realize this usage would break when I the flag to ... As a workaround, you can run the unwrapped executables in the meantime, this should work (works for me): I'm a bit confused though, which revision are you evaluating exactly? which is used in your report is before the wrapper rewrite.
I don't experience other issues you mention on current branch .
oh right, i had this issue on up-to-date yesterday on my laptop i filed the issue on my desktop
i'm unclear about what issues you don't experience on current on the branch, there's no
My bad :sweat_smile: My wasn't updated at all! Adding won't be that hard, but fixing the issue is harder...
Change:
cachecontrol numpy lxml <ins> packaging </ins> pillow scour pyserial

Discussion:
inkscape requires for "save as optimized svg" draw something, save as optimized svg error same error with fixed by i have not-yet found a cheap solution for (cheap as in: avoid rebuilding inkscape) Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(user): channels(root): nixpkgs: inkscape maintainer
Change:
{ stdenv, fetchurl, makeWrapper, makeDesktopItem, zlib, glib, libpng, freetype, openssl , xorg, fontconfig, qtbase, qtwebengine, qtwebchannel, qtsvg, xkeyboard_config, alsaLib <del> , libpulseaudio ? null, libredirect, quazip, less, which, unzip, llvmPackages </del> <ins> , libpulseaudio ? null, libredirect, quazip, which, unzip, llvmPackages, writeShellScriptBin </ins> }: let

Discussion:
Describe the bug When adding to and then running , at some point the license agreement of teamspeak shows up in the console and I couldn't find a way to accept it. Because of this, the installation is stuck forever at this point with no instructions how to continue. To Reproduce add to run Expected behavior The last command should complete and teamspeak should be installed on my system. Screenshots ! Additional context I've tried both stable and unstable, but got the same result for both. Metadata Maintainer information:
I can reproduce this. Seem like the sandbox changed lately and the command doesn't get the from . I will submit a PR with a fix.
Change:
<ins> { lib , stdenv , fetchFromGitLab , rustPlatform , meson , ninja , pkg-config , rustc , cargo , wrapGAppsHook4 , desktop-file-utils , libxml2 , libadwaita , openssl , libsoup_3 , webkitgtk_6_0 , sqlite }: stdenv.mkDerivation rec { pname = "read-it-later"; version = "0.5.0"; src = fetchFromGitLab { domain = "gitlab.gnome.org"; owner = "World"; repo = pname; rev = version; hash = "sha256-A8u1fecJAsVlordgZmUJt/KZWxx6EWMhfdayKWHTTFY="; }; cargoDeps = rustPlatform.fetchCargoTarball { inherit src; name = "${pname}-${version}"; hash = "sha256-wK7cegcjiu8i1Grey6ELoqAn2BrvElDXlCwafTLuFv0="; }; nativeBuildInputs = [ meson ninja pkg-config rustPlatform.cargoSetupHook rustc cargo wrapGAppsHook4 desktop-file-utils libxml2.bin #xmllint ]; buildInputs = [ libadwaita openssl libsoup_3 webkitgtk_6_0 sqlite ]; meta = with lib; { description = "A simple Wallabag client with basic features to manage articles"; homepage = "https://gitlab.gnome.org/World/read-it-later"; license = licenses.gpl3Plus; mainProgram = "read-it-later"; maintainers = with maintainers; [ aleksana ]; platforms = platforms.unix; }; } </ins>

Discussion:
Project description Wallabag Client for desktop. Metadata homepage URL: source URL: license: gpl3 platforms: linux
Change:
, pkg-config , openssl , Security <ins> , SystemConfiguration </ins> }: rustPlatform.buildRustPackage rec { pname = "lychee"; <del> version = "0.13.0"; </del> <ins> version = "0.14.2"; </ins> src = fetchFromGitHub { owner = "lycheeverse"; repo = pname; rev = "v${version}"; <del> hash = "sha256-JUyoOtlypDWK6HxsonVzbfQAdcXk728a8gVI/5GI2fs="; </del> <ins> hash = "sha256-6ePL76qoRDJvicMF8Hp5SDLDIyYJfgDsZyK47/DmC6U="; </ins> }; <del> cargoLock = { lockFile = ./Cargo.lock; outputHashes = { "criterion-0.4.0" = "sha256-0EKLRdxbH2czkZjmuaYLzkTBU687y6Iw9yqNV2TbsDw="; }; }; </del> <ins> cargoHash = "sha256-OMs2/s+jHaOXf7GnVpEgF9Ev+mmSgTZcVpgYx1BISRc="; </ins> nativeBuildInputs = [ pkg-config ]; buildInputs = [ openssl ] <del> ++ lib.optionals stdenv.isDarwin [ Security ]; </del> <ins> ++ lib.optionals stdenv.isDarwin [ Security SystemConfiguration ]; </ins> checkFlags = [ #  Network errors for all of these tests

Discussion:
Package name: Latest released version: 0.14.2 <!-- Search your package here: --- Current version on the unstable channel: 0.13.0 Current version on the stable/release channel: 0.13.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]:
Change:
url = "https://salsa.debian.org/debian/xneur/-/raw/da38ad9c8e1bf4e349f5ed4ad909f810fdea44c9/debian/patches/gcc-10.patch"; sha256 = "0pc17a4sdrnrc4z7gz28889b9ywqsm5mzm6m41h67j2f5zh9k3fy"; }) <ins> (fetchpatch { name = "enchant2.patch"; url = "https://salsa.debian.org/debian/xneur/-/raw/695b0fea56cde4ff6cf0f3988218c5cb9d7ff5ae/debian/patches/enchant2.patch"; sha256 = "02a3kkfzdvs5f8dfm6j5x3jcn5j8qah9ykfymp6ffqsf4fijp65n"; }) </ins> ]; postPatch = '' <del> sed -e 's@for xosd_dir in@for xosd_dir in ${xosd} @' -i configure </del> <ins> sed -e 's@for xosd_dir in@for xosd_dir in ${xosd} @' -i configure.ac </ins> ''; meta = with lib; {

Discussion:
Enchant 2 (now the default) is long supported by most packages. The following packages need to be updated or removed: [x] gtkspell2 (dead): [x] xiphos: [x] subtitleeditor: [x] xneur: (contains the removal of enchant1) [x] gnome2.gtkhtml (dead): [x] gnome2.gtkhtml4 (dead): [x] gnome.gtkhtml (dead?): [x] php.extensions.enchant:
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 .
This issue is still relevant.
the list from is not up-to-date. e.g. is already fixed maybe we can also close it, because defaults to version 2 and to version 1.
I marked this as stale due to inactivity. &rarr;
Updated the list.
Now with xiphos merged You can thick both xiphos and gnome2.gtkhtml4 off the checklist
Pushed the enchant1 removal commit to
Change:
outputHashMode = if (recursiveHash || executable) then "recursive" else "flat"; <del> inherit curlOpts showURLs mirrorsFile postFetch downloadToTemp executable; </del> <ins> curlOpts = lib.warnIf (lib.isList curlOpts) '' fetchurl for ${toString (builtins.head urls_)}: curlOpts is a list (${lib.generators.toPretty { multiline = false; } curlOpts}), which is not supported anymore. - If you wish to get the same effect as before, for elements with spaces (even if escaped) to expand to multiple curl arguments, use a string argument instead: curlOpts = ${lib.strings.escapeNixString (toString curlOpts)}; - If you wish for each list element to be passed as a separate curl argument, allowing arguments to contain spaces, use curlOptsList instead: curlOptsList = [ ${lib.concatMapStringsSep " " lib.strings.escapeNixString curlOpts} ];'' curlOpts; curlOptsList = lib.escapeShellArgs curlOptsList; inherit showURLs mirrorsFile postFetch downloadToTemp executable; </ins> impureEnvVars = impureEnvVars ++ netrcImpureEnvVars;

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:
<ins> diff -ru a/app/app_procs.c b/app/app_procs.c --- a/app/app_procs.c	2021-01-30 11:09:52.000000000 -0500 +++ b/app/app_procs.c	2021-01-30 11:11:05.000000000 -0500 @@ -785,6 +785,7 @@ if (!filename) { g_print (_("Filename conversion failed: %sn"), filenames[i]); +	  ++i; continue; } </ins>

Discussion:
, CVSSv3=5.5 (nixos-20.03, nixos-unstable) Scanned versions: nixos-20.03: ; nixos-unstable: . May contain false positives.
cc
Change:
, makeWrapper , netperf , nixosTests <del> , python3 </del> <ins> , python3Packages </ins> , stdenv , zip }: <del> python3.pkgs.buildPythonApplication rec { </del> <ins> python3Packages.buildPythonApplication rec { </ins> pname = "bcc"; version = "0.31.0";

Discussion:
Mentioned in , the bcc package can also be used as from python. This currently doesn't seem to work? If applicable, add screenshots to help explain your problem. Add any other context about the problem here. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
bcc doesn't depend on kernel anymore, so the second half of the comment you linked at isn't required and we can just move the package & add a compat alias. Technically you should already be able to use bcc as by magic'ing the correct site path, but I agree it's better to move it - patch welcome!
Change:
comixcursors = callPackage ../data/icons/comixcursors { }; <del> corefonts = callPackage ../data/fonts/corefonts { }; </del> courier-prime = callPackage ../data/fonts/courier-prime { }; cozette = callPackage ../data/fonts/cozette { };

Discussion:
Steps to reproduce the behavior: corefonts This package fails to build because all of the sourceforge mirrors all return "429 Too Many Requests" after making a certain number of requests. I'm not sure if the package needs to add a delay, find a different download host, or something else entirely. <!-- 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]:
Change:
ninja meson pkg-config <del> # needed for glib-compile-resources glib </del> ]; buildInputs = [ systemd libgudev <ins> glib </ins> ]; propagatedBuildInputs = [ <del> python3.pkgs.pygobject3 </del> <ins> python3Packages.pygobject3 </ins> ]; mesonFlags = [

Discussion:
Steps to reproduce the behavior: update nixpkgs-unstable - -rebuild switch Package switcheroo-control-2.6 cannot find dependencies: cmake & glib-2.0 = 2.56.0 on nixos-unstable channel. <!-- 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]: