jiebi/CodeConvo huggingface dataset:
Change:
assert !(nativeOnly && runtimeOnly); <del> let </del> <ins> let </ins> runtimePkgs = with pkgs; [ # Required glib

Discussion:
I have just updated to NixOS 17.09 commit . After the update I found out that all browser based tabs in steam don't work. This error message is printed: A quick grep in nixpkgs shows that steam runtime is using libnss 3.19.2. So that might be the cause of the problem. Install NixOS commit . Run steam. Open STORE or COMMUNITY tab. system: host os:
The solution is in I'll open a PR. Thanks for filing that.
I tried your patch and can confirm that it fixes the issue. Thank you!
Change:
<del> { lib, fetchFromGitHub, makeDesktopItem, prusa-slicer }: </del> <ins> { lib, fetchFromGitHub, makeDesktopItem, prusa-slicer, wxGTK31-gtk3 }: </ins> let appname = "SuperSlicer"; pname = "super-slicer";

Discussion:
prusa-slicer crashes, maybe related to our wxWidgets version. See for now. cc
Maybe caused by Maybe backport that change, or use the prusa-slicer wxWidget fork.
I can reproduce it with nixpkgs rev Using the wxWidgets fork from prusa3d fixes the issue. Will try to write a PR soon.
Change:
<ins> { lib, stdenv, fetchFromGitHub, makeWrapper, coreutils, gawk }: stdenv.mkDerivation rec { pname = "theme-sh"; version = "1.1.5"; src = fetchFromGitHub { owner = "lemnos"; repo = "theme.sh"; rev = "v${version}"; sha256 = "sha256-zDw8WGBzO4/HRCgN7yoUxT49ibTz+QkRa5WpBQbl1nI="; }; nativeBuildInputs = [ makeWrapper ]; dontBuild = true; installPhase = '' runHook preInstall mkdir -p $out/bin install -Dm755 bin/theme.sh $out/bin wrapProgram $out/bin/theme.sh  --prefix PATH : ${lib.makeBinPath [ coreutils gawk ]} runHook postInstall ''; meta = with lib; { description = "A script which lets you set your $terminal theme"; homepage = "https://github.com/lemnos/theme.sh"; license = licenses.mit; platforms = platforms.all; maintainers = with maintainers; [ figsoda ]; mainProgram = "theme.sh"; }; } </ins>

Discussion:
Project description A program that allows you to set the terminal theme from the command line and scripts. ! Metadata homepage URL: source URL: license: MIT platforms: linux, macos
Change:
<del> { lib , buildPythonApplication , fetchPypi , appdirs , attrs , beautifulsoup4 , click-plugins , elasticsearch , flask-compress , flask_login , flask_wtf , html2text , python-dotenv , python-frontmatter , requests , tinydb , validators , werkzeug , wtforms }: </del> <ins> { lib, stdenv, python3, fetchPypi }: let defaultOverrides = [ (self: super: { flask = super.flask.overridePythonAttrs (oldAttrs: rec { version = "1.1.2"; pname = "Flask"; src = super.fetchPypi { inherit pname version; sha256 = "sha256-Tvoa4tfJhlr0iYbeiuuFBL8yx/PW/ck1PTSyH0sScGA="; }; checkInputs = [ self.pytest ]; propagatedBuildInputs = with self; [ itsdangerous click werkzeug jinja2 ]; doCheck = false; }); }) (self: super: { flask_login = super.flask_login.overridePythonAttrs (oldAttrs: rec { pname = "Flask"; version = "0.5.0"; src = fetchPypi { inherit pname version; sha256 = "6d33aef15b5bcead780acc339464aae8a6e28f13c90d8b1cf9de8b549d1c0b4b"; }; doCheck = false; }); }) ]; mkOverride = attrname: version: sha256: self: super: { ${attrname} = super.${attrname}.overridePythonAttrs (oldAttrs: { inherit version; src = oldAttrs.src.override { inherit version sha256; }; }); }; py = python3.override { # Put packageOverrides at the start so they are applied after defaultOverrides packageOverrides = lib.foldr lib.composeExtensions (self: super: { }) (defaultOverrides); }; in with py.pkgs; </ins> buildPythonApplication rec { pname = "archivy";

Discussion:
Looks like it is missing python3Packages.setuptools...
works for me - please provide output from
fixes that, but then you will be running into
I have informed the author of archivy, and he's looking into it.
This is because in the version requirements are loosened and an incompatible new version of flask is used to run archivy. Removing this change to the version constraints for flask would fix the problem.
Change:
pkgs ? import ../../.. { inherit system config; } }: { fpm = import ./fpm.nix { inherit system pkgs; }; <ins> httpd = import ./httpd.nix { inherit system pkgs; }; </ins> pcre = import ./pcre.nix { inherit system pkgs; }; }

Discussion:
Describe the bug When I enable PHP in httpd using , the file when visited can only see 11 extensions instead of the 52 I get when I run it through php CLI command. To Reproduce A failing NixOS test: Additional context Likely caused by the great refactor: Notify maintainers
Yep, the refactor relies on a configuration file with all the extensions to load being present and specified. For the binary, we have a wrapper that just tells PHP to look in the right folder for the config, but with the module, it looks like that's not used, since it loads PHP as an extension. The solution would probably be to inherit the config from the package as the first thing put into the it already generates; it should be accessible as .
Change:
caddy.gid = config.ids.gids.caddy; }; <ins> security.acme.certs = let eachACMEHost = unique (catAttrs "useACMEHost" acmeVHosts); reloads = map (useACMEHost: nameValuePair useACMEHost { reloadServices = [ "caddy.service" ]; }) eachACMEHost; in listToAttrs reloads; </ins> }; }

Discussion:
Describe the bug When i try to import a config file, i get an error: When i copy the exact same text in , it does work. The file does exist and i can read it, even with the caddy user! So this seem to be a bug. To Reproduce Steps to reproduce the behavior: ... ... ... Expected behavior A clear and concise description of what you expected to happen. Additional context Add any other context about the problem here. Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
Without knowing anything about my first guess would be this: Is it possible this command is evaluating your configuration? If so, the issue is that the command is being run sandboxed so has no access outside the sandbox to your file. Build time commands can be tough.
That would make sense. So NixOS brakes the import feature.
Out of curiosity can you please paste your relevant config?
what exactly do you want to see? For a workaround, i just copied everything into the NixOS option: But in some cases, it's nice to have the webserver config. together with the website sourcecode:
Thanks for posting. The context helps. I think this is what you want:
It could make sense to add an off-by-default option to opt-out build-time configuration check.
Given my above solution, I'm not sure what value it would offer in this scenario. What scenario did you have in mind Can this config file hold secrets maybe?
Then you don't have to use such a workaround on NixOS and can just use it as described in it's documentation. There can be secrets in it, but i don't see how that's relevant here:
Hi, module maintainer here. I was the person who made the original PR for adapting s for Caddy 2, and I had no idea about the directive at the time. The motivation was to generate TLS settings from the module options and merge them with JSON-ified . Please use as suggested for now, and I'll see how I can make this easier in the future.
I marked this as stale due to inactivity. &rarr;
Change:
in optionalString ((length devices) > 0) "linux-dev (${devicesString})"; <del> mkConfig = name: keyboard: pkgs.writeText "${mkName name}-config.kdb" '' (defcfg ${keyboard.extraDefCfg} ${mkDevices keyboard.devices} linux-continue-if-no-devs-found yes) ${keyboard.config} ''; </del> <ins> mkConfig = name: keyboard: pkgs.writeTextFile { name = "${mkName name}-config.kdb"; text = '' (defcfg ${keyboard.extraDefCfg} ${mkDevices keyboard.devices} linux-continue-if-no-devs-found yes) ${keyboard.config} ''; checkPhase = '' ${getExe cfg.package} --cfg "$target" --check --debug ''; }; </ins> mkService = name: keyboard: nameValuePair (mkName name) { wantedBy = [ "multi-user.target" ];

Discussion:
I've successfully setup kanata but it was not easy, mostly because this was my first time using this kind of software. I thought it would help to reference an external kanata configuration, such that I can just send a reload signal to kanata instead of having the slow this fails because the systemd service is highly-secure (kudos to maintainers) I wonder what are the implications of allowing the service to read files in my $HOME ? seems like I had to remove to make it work. kanata is by default compiled without "cmd" so it should not be able to run a command. It looks ok to me ? I am not asking for nixpkgs to support this necessarily, I could override the service settings with mkForce but I wonder if it puts me at some crazy risk ? I suppose is not going to be changed. on nixos-unstable
It is indeed time-consuming to run repeatedly to get a stable and usable config. My workaround for this is to view as a deployment tool instead of a development/testing tool, i.e., I only add a stable config to my NixOS config and using to deploy it. For kanata, one way to get a stable config without is to run it directly, such as . Since kanata's NixOS module defines it as a systemd service, your approach of opening a hole from those hardening options is also viable. To open a smallest hole, the following snippet is enough. Whether this hole is a security issue to you depends on your threat model. In general, it is fine to expose a read-only file to a service.
thanks a lot, that answers my concern. I've opened to ask for author's feedback as well.
Change:
<del> { lib, buildPythonApplication, fetchPypi, matplotlib, numpy, pymavlink, pyserial , setuptools, wxPython_4_0 }: </del> <ins> { stdenv, lib, buildPythonApplication, fetchPypi, matplotlib, numpy, pymavlink, pyserial , setuptools, wxPython_4_0, billiard, gnureadline }: </ins> buildPythonApplication rec { pname = "MAVProxy";

Discussion:
Describe the bug wxPython40, , does not build there likely because it uses wxGTK rather than this prevents kicad from being built on darwin To Reproduce Steps to reproduce the behavior: darwin, Expected behavior wxPython40 to build on darwin and be usable by kicad there Additional context i maintain the kicad package and Notify maintainers while there are no listed maintainers for this package it was initially contributed by (if you already investigated after the kicad PR ping, nothing relevant changed since) and has a fair amount of contributions by Maintainer information:
Hi I don't have/use mac but happy to answer any wxPython questions as I can
I'm experiencing the same issue with Linux, using .
likely a different issue. Stacktrace? What nixpkgs version / commit?
The as of this writing. Here's the output I'm seeing. <details<summarybuild log</summary</detailsIt looks like pkg-config is giving an old version of GTK+?
please use your failure seems the same as which i closed because it's fixed in the branch by and i can confirm at least starts building there (it's still going...) i'm not sure when this fix will get to ...
nice! didn't know about the details tag. Ok yeah that looks like my issue, thanks for pointing me in that direction.
I can reproduce this on 10.14.6. My best take so far was to use and adapt other Darwin requirements. <details<summarydiff against master</summary</detailsUnfortunately it does not build with the same errors as for the .
Bumped to 3.0.5.1, to its , and it builds! was set, but no dependency specified. That's what caused the missing symbols. <details<summaryworking diff</summary</detailsI'm not even sure why this works at all. claims they build from a submodule, but obviously in this setup we take whatever is supplied through . To be pedantic, 4.0.7 is supposed use some specific instead of a release, as you can . That commit is after* 3.0.4 and shortly before 3.0.5. I only skimmed the , but it sounds and looks like backwards-compatible bug fixes. Opinions on how to proceed?

If we follow upstream and choose the intermediate revision, what to specify as the package version?
i've kinda given up on stuff, at least until the next release which i hope will either be built based on a release or be compatible with the latest release (i have no reason to believe this would be the case though) if you have a diff that fixes a package, i recommend you make a PR 4.0.7 seems to work with the 3.0.4, it seems reasonable to assume the same would be true for 3.0.4
Change:
, unzip, libsecret, libXScrnSaver, libxshmfence, buildPackages , atomEnv, at-spi2-atk, autoPatchelfHook , systemd, fontconfig, libdbusmenu, glib, buildFHSEnv, wayland <ins> , libglvnd </ins> # Populate passthru.tests , tests

Discussion:
I've been trying to see why vscode had rather laggy scrolling and high cpu usage when scrolling on wayland with set to 1, and upon discovering and , I saw that the library isn't found by it, causing the app to fall back to software rendering. Disabling the env variable and starting vscode like that shows that on xwayland it does start up with gpu acceleration. Doing the same thing described , VScode does start with GPU acceleration working. and no longer complains about the library Steps to reproduce the behavior: VScode with set and with the flag, so it starts with wayland support and outputs details about the startup and other stuff how it complains about the library. to see check that it's indeed using software rendering. The library is found, there are no complaints, and GPU acceleration is enabled. I am on an Intel laptop. Please run and paste the result.
Whats the exact log? vscode vendors that library and it is located in our package at
Relevant lines from [(44)] Failed to load GLES library: cannot open shared object file: No such file or directory [(186)] Exiting GPU process due to errors during initialization [(44)] Failed to load GLES library: cannot open shared object file: No such file or directory [(186)] Exiting GPU process due to errors during initialization
Same error happens on VSCodium where running with on Wayland frequently crashes on startup. ing yields a lot of lines before the logged error, including this particularly interesting one: The file doesn't actually exist, only does, so apparently VSCodium is looking for while only is vendored. If is to the , is found as a symlink to the actual library and ing again confirms that this library is loaded by VSCodium. Edit: Adding to fails with different error messages, so probably there's something broken with the vendored library:
I would guess that's because the drivers to not abi match. I would recommend to rm the vendored shared object and symlink libglvnd to the correct location. Also we should investigate if we can remove/replace the other vendored libraries.
Adding to the library path did the trick for me, thanks!
I can't get it to work with vscode sadly. vscode = (super: { libPath = lib.makeLibraryPath [pkgs.libglvnd]; });
How soon will the changes get into nixos-unstable?

2 days max ?
You can follow the PR here:
This is still broken for me: In fact, that file is missing. is missing too. As expected, due to last PR merged. I can confirm that the wrapper script contains: So what gives? How did this work for others but not me?
I'm guessing the last PR fixed it for wayland/ but broke it for others? Edit: I can confirm that I have gpu acceleration when I pin vscode nixpkgs to which is the parent commit of . I also tried the following, linking libglvnd's libGLESv2 into vscode directory. The error changed and terminal rendering completely broke with a black screen:
please open a bug !
Change:
mainProgram = "qemu-kvm"; maintainers = with maintainers; [ eelco qyliss ]; platforms = platforms.unix; <ins> priority = 10; # Prefer virtiofsd from the virtiofsd package. </ins> }; }

Discussion:
Describe the bug libvirt can't find I'm unsure how to reference virtiofsd via libvirt xml without it being garbage collected. I'm currently hard coding nix store: Expected behavior A consistent reference to virtiofsd either via a link in or putting it on the $PATH. Additional context Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
It's not perfect, but adding the following snippet to does the trick for me. I have the following line in my virtual machine XML to make use of it:
I marked this as stale due to inactivity. &rarr;
Still important to me.
Sorry about the spam, I had to push to my fork in order to test it and I managed to have this crappy typo that I missed for a while.. Anyway, that PR should fix it.
That's what and are for. To have stable links in xml files which survive upgrades of and , hibernation of guests, reboots of host, GCs and all of those interleaved. Maintaining through all XML's seems ugly
Change:
postPatch = '' substituteInPlace scripts/mosh.pl  --subst-var-by ssh "${openssh}/bin/ssh" <ins> substituteInPlace scripts/mosh.pl  --subst-var-by mosh-client "$out/bin/mosh-client" </ins> ''; configureFlags = [ "--enable-completion" ] ++ lib.optional withUtempter "--with-utempter";

Discussion:
Describe the bug When running the program in a context where is not set up perfectly for nix usage, running fails to run, saying it can not count colors. To Reproduce Steps to reproduce the behavior: mosh in a "clean" env without any nix paths on it: that it's unable to exec : Expected behavior An attempt to connect to Additional context I suspect this could easily be fixed by making the wrapper that mosh installs prefix the mosh bin to . Notify maintainers Metadata Please run and paste the result. Maintainer information:
As a workaround, I currently run mosh like this in iTerm: That seems not ideal, but it works for now (:
Change:
hostSuffix = lib.optionalString (stdenv.hostPlatform != stdenv.buildPlatform && !dontAddHostSuffix) "-${stdenv.hostPlatform.config}"; # Disambiguate statically built packages. This was originally # introduce as a means to prevent nix-env to get confused between # nix and nixStatic. This should be also achieved by moving the

Discussion:
Describe the bug I'm getting from some Nix packages. /nix/store/8br3hnwahahpi4m3s9xjd34xn18bf1l4-source/pkgs/stdenv/generic/make- Here -Originated from: Is it because it should be Expected behavior No error nix-env version is 2.11.0 Additional context Add any other context about the problem here.
I ran into the same issue when I tried to use nix-darwin with flakes. The example was using an old version of nixpkgs-darwin. Changing it to use the latest version seemed to fix it. I made a PR to update the readme: LnL7/nix-darwin .
Same problem on OpenBSD The trace
Can be reproduced on linux with: ` Edit: The problem is in cc-native which seems to be rotted over time because we didn't add a new system for a longer time. The problem is that cc-native has not version attr. Trying to find a fix for that right now.
can you move this to nixpkgs?
Change:
default = configFile; defaultText = "A Caddyfile automatically generated by values from services.caddy.*"; example = literalExpression '' <del> pkgs.writeTextDir "Caddyfile" ''' </del> <ins> pkgs.writeText "Caddyfile" ''' </ins> example.com root * /var/www/wordpress

Discussion:
I wanted to configure caddy with my own config file, setting as documented in the option. Steps to reproduce the behavior: above snippet how caddy does not start, as does not exist. at the filesystem, observe there's a directory with a inside, while sets Possibly introduced in Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Looks like a regression to me. Will investigate further. Thanks for your report and the commit you suggested that might have introduced it :)
I don't think it's that commit. Can you try ?
I am pretty sure this documentation error has been introduced all the way back in . The option docs simply switched from to , but forgot to wrap add a at the end. And now we are somewhat stuck with behavior that expects it that way... sigh.
I think this in combination with introduced the breaking change, since we now always pass as the arg, but expect a basename of to enable the adapter.
It works if you do as demonstrated here: But it's ugly.
Alternatively do and explicitly set .
I tried with too, it doesn't work. I extended with an example (at least I think I did), and it fails. It's pushed to , if someone does a PR fixing the issue feel free to cherry-pick it in ;-)
With you also need to explicitly set .
Fixed it in (when using )
Can you also fix the writeTextDir case? That's what the documentation recommends to use...
I adjusted the documentation to use (which it used to be before )
I could also instead fix the case, if you have strong opinions, but this was a bit easier.
I think fixing the writeTextDir case makes more sense. That's what people might have in their configs, and getting everyone to notice they now need to write it like this, and update configs is worse UX than fixing the usage that was documented. Assuming it worked with 23.05 for example, but regressed with 23.11 again. That is, if this ever worked like this before. If it was broken all the time, no one could have a working config so it doesn't matter much :laughing:
Both and (without ) have been broken since , which landed in .
Ok, in that case, it's been broken for an entire release, so this is not just a regression when upgrading to 23.11. then it's probably ok.
Change:
ki18n, xcb-util-cursor, kconfig, kcoreaddons, kdbusaddons, kdeclarative, kio, kipi-plugins, knotifications, kscreen, kwidgetsaddons, kwindowsystem, kxmlgui, libkipi, <del> qtx11extras, knewstuff, kwayland, qttools </del> <ins> qtbase, qtx11extras, knewstuff, kwayland, qttools, kcolorpicker, kimageannotator </ins> }: mkDerivation { pname = "spectacle"; <del> meta = with lib; { maintainers = with maintainers; [ ttuegel ]; }; </del> <ins> meta = with lib; { maintainers = with maintainers; [ ttuegel ]; broken = versionOlder qtbase.version "5.15"; }; </ins> nativeBuildInputs = [ extra-cmake-modules kdoctools ]; buildInputs = [ kconfig kcoreaddons kdbusaddons kdeclarative ki18n kio knotifications kscreen kwidgetsaddons kwindowsystem kxmlgui libkipi qtx11extras xcb-util-cursor <del> knewstuff kwayland </del> <ins> knewstuff kwayland kcolorpicker kimageannotator </ins> ]; postPatch = '' substituteInPlace desktop/org.kde.spectacle.desktop.cmake 

Discussion:
Describe the bug Starting with version 20.12, Spectacle has annotation support, utilizing . Most big distributions already ship Spectacle with the feature enabled. I assume kImageAnnotator needs to be packaged and integrated with the existing Spectacle package. Screenshots Screenshot of the functionality from the official KDE docs: ! Additional context 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:
Change:
<del> { qemu, fetchFromGitHub, lib }: let src = fetchFromGitHub { owner  = "riscv"; repo   = "riscv-qemu"; rev    = "f733c7b5f86147216e14aff90c03ccdd76056bef"; sha256 = "1ppr9qqwi7qqh8m6dgk1hrzg8zri240il27l67vfayd8ijagb9zq"; fetchSubmodules = true; }; version = "2.11.92"; revCount = "60378"; shortRev = builtins.substring 0 9 src.rev; targets = [ "riscv32-linux-user" "riscv32-softmmu" "riscv64-linux-user" "riscv64-softmmu" ]; in lib.overrideDerivation qemu (orig: { name = "${(builtins.parseDrvName qemu.name).name}-${version}pre${revCount}_${shortRev}"; inherit src; # <<<<<<< HEAD #   # https://github.com/riscv/riscv-qemu/pull/109 #   patches = [ ./no-etc-install.patch ./statfs-flags.patch ./riscv-initrd.patch ]; # ======= # The pulseaudio and statfs patches are in 2.12.0+, which this is based on patches = [ ./force-uid0-on-9p.patch ./no-etc-install.patch ]; configureFlags = orig.configureFlags ++ [ "--target-list=${lib.concatStringsSep "," targets}" ]; postInstall = null; }) </del>

Discussion:
Qemu 2.12.0 has released today. We need to update package. Please run and paste the results.