jiebi/CodeConvo huggingface dataset:
Change:
services.dbus.packages = [ pkgs.gnome3.gnome-keyring pkgs.gcr ]; <ins> security.pam.services.login.enableGnomeKeyring = true; </ins> }; }

Discussion:
GDM's PAM modules are currently built so that the password stack of the keyring PAM module get loaded before a password input module is loaded, which results in the keyring never being unlocked automatically. in with GDM to use an application that has its password stored in GNOME keyring will ask you for the unlock password System: (Flounder) Nix version: nix-env (Nix) 1.11.4 Nixpkgs version: 16.09.1465.
Relevant discussion on unified PAM settings
Same with LightDM.
Automatic GNOME keyring unlocking with LightDM is fixed in NixOS 18.03, but GDM still does not unlock the keyring...
I wonder if this is resolved after
If it is a PAM thing, I do not thinks so. We did not touch PAM.

GDM currently uses custom PAM configuration that doesn't cover all items that are generated when is used, especially for sessions. As a result, logging in via GDM doesn't apply custom limits set via . custom limits that apply to the current user via out and back in again (via GDM) output output again, compare System: 16.09.1066. (Flounder) Nix version: nix-env (Nix) 1.11.4 Nixpkgs version: 16.09.1066.
Also facing this issue.
Closing in favor of open PR.
Change:
''; }; <del> pruneBindMounts = mkOption { type = bool; </del> <ins> pruneBindMounts = lib.mkOption { type = lib.types.bool; </ins> default = false; description = '' Whether not to index bind mounts

Discussion:
Using more-or-less the default configuration for (with ), the list of results is printed twice whenever running . For example: Steps to reproduce the behavior: the module like so: the job with some file name that exists on the system Matching files should each be printed once. The issue is fixed if I unset the environment variable. plocate deliberately reads from both and the hard coded default path, even if they are the same: The comment claims that this is also the behavior of mlocate, but I do not have an mlocate database installed and haven't wanted to change my running system to use mlocate. It looks like recently started being set in NixOS in . Please run and paste the result.
Sounds to me like an upstream issue. Can you write a mail to the upstream maintainer? ;a=blob;f=README;h=;hb=HEAD#l40
Sure, I have done so. I'll follow up when I get a response.
The plocate maintainer says they do not consider this to be a bug in plocate, and is intentional behavior. Rather than setting the environment variable, could we just make a wrapper script for that uses the NixOS-configured dbpath, if we don't want to re-build itself when the path is changed?
I would be personally fine to just drop support for a custom place for the db. If people really want to have it somewhere else they could symlink it. Then we don't need a wrapper or to worry about the env.
I can confirm the behaviour with .
Could we just take out the variable setting? It isn't needed for or , and just causes this annoying behaviour. If it's needed for , maybe the setting could be made conditional. It would be nice to get something done about it sooner rather than later. This issue has been open for 4 months now.
Please take a look at
I've reviewed the PR and it LGTM. Thanks for doing this! It will be great to have this fixed.
Change:
# nixos-prepare-root doesn't currently do anything with file ownership, so we set it up here instead chown @root_uid@:@nixbld_gid@ $mountPoint/nix/store <del> mount --rbind /dev $mountPoint/dev mount --rbind /proc $mountPoint/proc mount --rbind /sys $mountPoint/sys </del> # Grub needs an mtab. ln -sfn /proc/mounts $mountPoint/etc/mtab

Discussion:
the runChroot code in nixos-install was removed in it will now try to do a full install if you run cc
I'll try to restore before 17.09 branch point, sorry!
Okay I'm looking at this now. I'm not entirely clear on the flag's purpose, so it's hard for me to add it back (even looking at the old code), and it doesn't really appear to be documented except that it gets mentioned in the manual once in passing. Can someone elaborate on what it's for and what it's guarding against? That'll make it much easier for me to add it back. Edit: the commit message clarifies some of it. I guess it's chroot + some bind mounts to make the chroot usable? It feels a little odd to stick that under but I guess I should replicate that behavior.
Okay, I get what it's supposed to do. is just "set up a few bind mounts like /proc to make it look legit, and then chroot", right? It has nothing to do with installation except that one might want to use it to test a fresh install (but one might also want to use it to test an unfresh install mounted on another machine, or something).
Also useful to fix a broken installation, e.g. when you broke your boot loader or something similar severe. Then you can boot from usb, run and then do a rebuild, and everything works again.
Cool! do you have a good test setup for my PR addressing this? My access to physical NixOS boxes for testing is limited right now.
the hardware's here, but did not manage to get your PR version running on my NixOS live usb key to try it, or somehow mount a snapshot of my actual installation and trick nixos-install into chrooting into that.
Note that on Arch Linux, and are two separate tools, and , which would at least make it easier to test this skipping all that mount point checking, as well as more flexible. And it would also prevent the confusion on what does in the first place.
ping We only have a few days left until the release. :)
I've updated the PR, sorry!
Change:
description = "A fully non-destructive photo retouching program providing a complete RAW image editing workflow"; homepage = "https://aferrero2707.github.io/PhotoFlow/"; license = licenses.gpl3Plus; <del> maintainers = [ maintainers.MtP ]; platforms = platforms.linux; # sse3 is not supported on aarch64 badPlatforms = [ "aarch64-linux" ]; # added 2021-09-30 # upstream seems pretty dead #/build/source/src/operations/denoise.cc:30:10: fatal error: vips/cimg_funcs.h: No such file or directory broken = true; </del> <ins> maintainers = with maintainers; [ MtP wegank ]; platforms = platforms.unix; </ins> }; }

Discussion:
Steps to reproduce the behavior: Adding fixes the issue. <!-- 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.
Change:
<ins> { lib , aiohttp , beautifulsoup4 , buildPythonPackage , fetchFromGitHub , pkce , poetry-core , pythonOlder }: buildPythonPackage rec { pname = "python-myq"; version = "3.1.13"; pyproject = true; disabled = pythonOlder "3.8"; src = fetchFromGitHub { owner = "Python-MyQ"; repo = "Python-MyQ"; rev = "refs/tags/v${version}"; hash = "sha256-kW03swRXZdkh45I/up/FIxv0WGBRqTlDt1X71Ow/hrg="; }; nativeBuildInputs = [ poetry-core ]; propagatedBuildInputs = [ aiohttp beautifulsoup4 pkce ]; # Project has no tests doCheck = false; pythonImportsCheck = [ "pymyq" ]; meta = with lib; { description = "Python wrapper for MyQ API"; homepage = "https://github.com/Python-MyQ/Python-MyQ"; changelog = "https://github.com/Python-MyQ/Python-MyQ/releases/tag/v${version}"; license = with licenses; [ mit ]; maintainers = with maintainers; [ fab ]; }; } </ins>

Discussion:
The home-assistant component currently declares that it's missing the input However the package actually exists, it's just called . This appears to be the old name of the package, it looks as though it got renamed at some point, although the nixpkgs packge for it wasn't updated for the name change.
Note that merely setting restores the component's functionality.
Change:
exit 1 '' else configText; <del> environment.systemPackages = [ cfg.package ]; </del> } (mkIf cfg.enable { networking.resolvconf.package = pkgs.openresolv; <ins> environment.systemPackages = [ cfg.package ]; </ins> systemd.services.resolvconf = { description = "resolvconf update";

Discussion:
Changes introduced in forcing package (or whatever the option is set to) installation even if the set to . This is because the module is unconditionally adding the package to the : Steps to reproduce the behavior: both and to in order to avoid enabling the service or systemd overriding the package with . installed packages, for example using the command. An package is installed into the system: An package should not be installed into the system. I am on a quest to build a minimal NixOS system for usage in LXC containers and trying to trim things down to the minimum, without having to resort to forking, overriding, patching and maintaining individual modules. I am happy to open up a PR to move the package assignment to the block: but would like to check if anyone has any objections or reasons why I shouldn't be doing so. appreciate any insights ‍ Please run and paste the result.
As the author of that PR I have no objections to restoring the old behaviour.
Change:
<ins> #! @bash@/bin/bash # shellcheck shell=bash exec @buildobjdump@ -p "$@" </ins>

Discussion:
Steps to reproduce the behavior: , , and itself is effectively abandoned by the upstream (yocto project). I think we may as well drop it rather than fix it. However now relies on it as a runtime linker for use in cross compilation, we have to find an alternative. Please run and paste the result.
openembedded replaced prelink with objdump will test
Change:
fingerprint = "8BC7 74E4 A2EC 7507 3B61  A647 0BBB 1C8B 1C36 39EE"; }]; }; <ins> carloscraveiro = { email = "carlos.craveiro@usp.br"; github = "CarlosCraveiro"; githubId = 85318248; name = "Carlos Henrique Craveiro Aquino Veras"; }; </ins> carlosdagos = { email = "m@cdagostino.io"; github = "carlosdagos";

Discussion:
Project description SimulIDE Circuit Simulator is a simple real time electronic circuit simulator, intended for hobbyist or students to learn and experiment with analog and digital electronic circuits and microcontrollers. It supports PIC, AVR , Arduino and other MCUs and MPUs. <!-- Describe the project a little: --Metadata homepage URL: source URL: license: gpl3 platforms: linux
Change:
repmgr = super.callPackage ./ext/repmgr.nix { }; rum = super.callPackage ./ext/rum.nix { }; <ins> wal2json = super.callPackage ./ext/wal2json.nix { }; </ins> }

Discussion:
Project description is a PostgreSQL extension. The extension is a JSON output plugin for changeset extraction. Metadata homepage URL: source URL: license: platforms: unix, linux, darwin
Just curious why you need it? These days most tools support the builtin pgoutput...
I am using it in an event-driven architecture to publish events to GCP pubsub. JSON is easier to parse for my use case since I am using it in the application, and not just for replication.
I marked this as stale due to inactivity. &rarr;
I packaged this up over in It worked for my minimal testing, but I haven't done anything more involved with it yet.
Change:
freeglut libjpeg wxGTK32 <del> sqlite </del> gtk3 libXScrnSaver libnotify <del> patchelf </del> libX11 libxcb xcbutil ]; <del> NIX_LDFLAGS = "-lX11"; </del> <ins> NIX_LDFLAGS = lib.optionalString (!headless) "-lX11"; </ins> preConfigure = '' ./_autosetup

Discussion:
Project description Currently there is a package for boinc, but it comes with a GUI manager. For a headless server it would be nice to have a package without graphical dependencies as an option. Unfortunately, I have no experience in creating packages myself, but I found these links that might be useful: General build instructions: Arch Package: Metadata homepage URL: source URL: license: gpl3, lgpl3 platforms: unix, linux, darwin
Change:
hash = "sha256-M1CnB1adk02lJuFsm0zzjSx/l9hKHJMt1Wh2a5Xtdyg="; }; <del> python = python3; </del> <ins> # subpath installation is broken with uvicorn >= 0.26 # https://github.com/NixOS/nixpkgs/issues/298719 # https://github.com/paperless-ngx/paperless-ngx/issues/5494 python = python3.override { packageOverrides = self: super: { uvicorn = super.uvicorn.overridePythonAttrs (oldAttrs: { version = "0.25.0"; src = fetchFromGitHub { owner = "encode"; repo = "uvicorn"; rev = "0.25.0"; hash = "sha256-ng98DTw49zyFjrPnEwfnPfONyjKKZYuLl0qduxSppYk="; }; }); }; }; </ins> path = lib.makeBinPath [ ghostscript

Discussion:
When running paperless-ngx with a location like , current unstable and master will cause it to break. See also this upstream issue: Steps to reproduce the behavior: paperless to use as location: to access The login screen should be shown The client is redirected infinitely. This can be solved by using uvicorn <= 0.25, which doesn't include the yet, to match the . Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
fixes it for me, but I feel like this quick hack isn't good enough for a PR - feel free to take it from here.
Thanks for the report! I will open a PR for that
Can't we fix this in our NixOS module? And maybe a NixOS test for this would be good.
I agree a NixOS test would be good. What do you mean with a fix in the module? The module doesn't configure nginx (and I think it shouldn't) and then I see no other way than pinning uvicorn?
I didn't read the upstream issue carefully but it sounded like setting some environment variables also fixes this.
I tests in Feel free to integrate them & improve when needed.
As best as I can tell, what happened is that Uvicorn now prefixes all requests made to Paperless with the (previously, would be rewritten to but now it's not), this rewriting is now supposed to be done on Paperless's end (for spec reasons I guess). Which means that you can't fix this with an environment variable, and they are going to be pinning Uvicorn to 0.25 until they do a (potentially) sizeable rewrite.
Mind opening a PR for them?
Change:
<del> { lib , fetchFromGitHub , stdenv , substituteAll , bison , boost , cmake , double-conversion , fmt , fuse3 , glog , gtest , jemalloc , libarchive , libevent , libunwind , lz4 , openssl , pkg-config , ronn , xxHash , utf8cpp , zstd </del> <ins> { lib, fetchFromGitHub, stdenv, substituteAll, bison, boost, cmake, double-conversion, fmt, fuse3, glog, gtest, jemalloc, libarchive, libevent, libunwind, lz4, openssl, pkg-config, ronn, xxHash, utf8cpp, zstd, </ins> }: <del> stdenv.mkDerivation rec { </del> <ins> let </ins> pname = "dwarfs"; <del> version = "0.7.5"; </del> <ins> version = "0.9.9"; in stdenv.mkDerivation { inherit pname version; </ins> src = fetchFromGitHub { owner = "mhx"; repo = "dwarfs"; <del> rev = "v${version}"; </del> <ins> rev = "refs/tags/v${version}"; </ins> fetchSubmodules = true; hash = "sha256-Zzm2SaFR31TBBMDfgJulVbqsJBh1He2wBFzHRC/c5vg="; }; patches = [ <del> (with lib.versions; substituteAll { src = ./version_info.patch; </del> <ins> ( with lib.versions; substituteAll { src = ./version_info.patch; </ins> <del> versionFull = version; # displayed as version number (with v prepended) versionMajor = major version; versionMinor = minor version; versionPatch = patch version; }) </del> <ins> versionFull = version; # displayed as version number (with v prepended) versionMajor = major version; versionMinor = minor version; versionPatch = patch version; } ) </ins> ]; cmakeFlags = [

Discussion:
Package name: dwarfs Latest released version: 0.9.8 <!-- Search your package here: --- Current version on the unstable channel: 0.7.5 Current version on the stable/release channel: 0.7.2 <!-- 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:
(fetchNuGet { pname = "HarfBuzzSharp.NativeAssets.Win32"; version = "2.8.2.1-preview.108"; sha256 = "0n6ymn9jqms3mk5hg0ar4y9jmh96myl6q0jimn7ahb1a8viq55k1"; }) (fetchNuGet { pname = "JetBrains.Annotations"; version = "10.3.0"; sha256 = "1grdx28ga9fp4hwwpwv354rizm8anfq4lp045q4ss41gvhggr3z8"; }) (fetchNuGet { pname = "libsodium"; version = "1.0.18.2"; sha256 = "02xd4phd6wfixhdq48ma92c166absqw41vdq5kvjch8p0vc9cdl2"; }) <del> (fetchNuGet { pname = "Microsoft.AspNetCore.App.Ref"; version = "6.0.19"; sha256 = "1r41m93kacyyhgjxmhx84n9wv9c2ckwa8295qa4kj8rn73gg4x28"; }) (fetchNuGet { pname = "Microsoft.AspNetCore.App.Runtime.linux-x64"; version = "6.0.19"; sha256 = "1izm1kx4rwi6cp6r6qzjn9h1lmqdcx87yj4gnf291gnabgwpdg9i"; }) </del> (fetchNuGet { pname = "Microsoft.CodeAnalysis.Analyzers"; version = "2.9.6"; sha256 = "18mr1f0wpq0fir8vjnq0a8pz50zpnblr7sabff0yqx37c975934a"; }) (fetchNuGet { pname = "Microsoft.CodeAnalysis.Common"; version = "3.4.0"; sha256 = "12rn6gl4viycwk3pz5hp5df63g66zvba4hnkwr3f0876jj5ivmsw"; }) (fetchNuGet { pname = "Microsoft.CodeAnalysis.CSharp"; version = "3.4.0"; sha256 = "0rhylcwa95bxawcgixk64knv7p7xrykdjcabmx3gknk8hvj1ai9y"; })

Discussion:
Some .NET packages depend on SDK-specific nugets, requiring updates when the SDK is updates, as seen in [x] - should be fixed by [x] - SDK-specific nugets should not be included in
Change:
<del> { lib , stdenv , fetchFromGitLab , bash , btrfs-progs , cmake , coreutils , git , pkg-config , qt6 , snapper , util-linux , enableSnapper ? true , nix-update-script </del> <ins> { lib, stdenv, fetchFromGitLab, bash, btrfs-progs, cmake, coreutils, git, pkg-config, qt6, snapper, util-linux, enableSnapper ? true, nix-update-script, </ins> }: stdenv.mkDerivation (finalAttrs: {

Discussion:
btrfs-assistant failed to use in nix-shell Steps to reproduce the behavior: A clear and concise description of what you expected to happen. nix-shell should success <!-- 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 fixed the nix-shell -p error but the application doesn't run properly. Looking into if we need to do some env variable nonsense because of the way the application works.
Change:
}: stdenvNoCC.mkDerivation rec { pname = "itch"; <del> version = "25.6.2"; </del> <ins> version = "26.1.2"; # TODO: Using kitch instead of itch, revert when possible </ins> src = fetchzip { <del> url = "https://broth.itch.ovh/${pname}/linux-amd64/${version}/itch.zip"; </del> <ins> url = "https://broth.itch.ovh/k${pname}/linux-amd64/${version}/archive/default#.zip"; </ins> stripRoot = false; <del> sha256 = "sha256-F/vaYBHCygseiKNMJ+jBy31YDIFqYToAETGUl/pkHII="; </del> <ins> sha256 = "sha256-thXe+glpltSiKNGIRgvOZQZPJWfDHWo3dLdziyp2BM4="; </ins> }; itch-setup = fetchzip {

Discussion:
Steps to reproduce the behavior: itch system: host os: multi-user?: sandbox: version: channels(root): channels(username): nixpkgs:
Looks like there is an issue already posted for this package NixOS/nixpkgs and there was a PR (NixOS/nixpkgs which uses a canary build instead) posted. Since there is no stable update (the canary builds uses a separate config directory, which is also explained here ) this is still a upstream issue.

I can't update my system when itch should be installed: error: Package ‘electron-11.5.0’ in /nix/store/5wja3wj4lq4gijjgg2lx3966pf6lzijc-nixos- is marked as insecure, refusing to evaluate. Steps to reproduce the behavior: in no error also reproducible on unstable i guess electron needs an update or use a later electron version, if possible system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
It's an upstream issue, trying to use a newer Electron version makes Itch straight up not work (it gets stuck at the initial loading). unfortunately seems to be abandoned. There technically is a new version (25.6.1-canary), but it hasn't been distributed as a binary on , and looking at the commits it doesn't change much. There is really nothing that can be done here. You can do this on your if you don't care about the security risks:
Upstream issue:
Change:
patches = [ ./osvi.patch ]; meta = { <del> platforms = stdenv.lib.platforms.windows; </del> <ins> platforms = stdenv.lib.platforms.all; </ins> }; }

Discussion:
Cross compiling any package with or results in an infinite recursion error. The same error when just evaluating I get the same results with A resulted into this commit: By removing the part from that commit already fixes this issue. Please run and paste the results. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
should fix this, hopefully. /cc
Change:
, fetchurl , meson , ninja <del> , pkgconfig </del> <ins> , pkg-config </ins> , SDL2 , alsaLib , bullet

Discussion:
Describe the bug Setting the variable to , as suggested , does nothing. Unsetting results in this error: Expected behavior There are two issues. First, the Enlightenment Foundation Libraries are not complied with Wayland support. Secondly, the variable needs to be set correctly a Wayland environment. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Maintainer information:
PR fixes this issue. Tested terminology with sway. The environment variable should not be set. In my test it was not needed to set . !
Change:
sha256 = "1i8bwi83qcqvi8zrkjn4mp2v8v7y11fd520wpg2jgy5hqyz34chg"; }; <del> buildInputs = optionals (stdenv.isDarwin) [ pkgs.makeWrapper ]; </del> <ins> buildInputs = [ pkgs.makeWrapper ]; </ins> preBuild = '' makeFlagsArray+=(prefix="$out") ''; <del> postInstall = optional (stdenv.isDarwin) '' </del> <ins> postInstall = '' </ins> wrapProgram $out/bin/git-flow  <del> --set FLAGS_GETOPT_CMD ${pkgs.getopt}/bin/getopt </del> <ins> --set FLAGS_GETOPT_CMD ${pkgs.getopt}/bin/getopt  --suffix PATH : ${pkgs.git}/bin </ins> ''; meta = with stdenv.lib; {

Discussion:
I'm not sure whether purely runtime dependencies should be defined or not. Anyway, isn't specifying git and getopt as its propagated build inputs although those packages are required for gitfow to work properly. So should they be ?
Hmm.. Perhaps this is just related to the fact that I'm using FHS user environment. It works in normal nix shell if I run .
Actually it turned out that with pure nix shell, it doesn't work. So here's a more comprehensive bug(?) report. I'm not sure if this is a bug or is this just how it's supposed to be. To me, this seems weird. doesn't work without manually adding build time dependencies and to the environment. Let's create some playground: Gitflow doesn't install git so it cannot be used: Also, getopt is missing: With both git and getopt given, it gitflow works: System: (NixOS: , Ubuntu/Fedora: , ...) Nix version: (run ) Nixpkgs version: (run )
How does find extra commands defined in other packages?
Edit: Ignore this and see the next comment instead. I guess dependency can be fixed by wrapping all necessary executables in similarly as only is currently wrapped. I can do that if that is the correct way. But I don't know how to fix dependency.
Actually, I think I got it now. Replaced with Replaced with Now, one can use successfully. If the user wants and use instead of , (s)he needs to install . Makes sense. Any thoughts? I don't know why there were conditionings on . Should I remove the conditioning or add ?
Seems like a good fix to me. Open a PR I'd say.