{"query_id": "q-en-nixpkgs-003bea105d5e62a4e5664aa3d025ff21de944b47e29d4af2f24b517e09448b4d", "query": "stdenv.mkDerivation rec { pname = \"cinnamon-common\"; version = \"5.4.9\"; version = \"5.4.10\"; src = fetchFromGitHub { owner = \"linuxmint\"; repo = \"cinnamon\"; rev = version; hash = \"sha256-nM87NO/dwOd+hN5/3zX7XUjyKvXh4uDhLcGFcKE9ccA=\"; hash = \"sha256-yNjFP32+0LXqHfJUxm1A+CTuwny5/IxxT08689f7VlE=\"; }; patches = [ ./use-sane-install-dir.patch ./libdir.patch # Re-add libsoup 2.4 as dependency - needed by some applets. # Can be removed on next update. (fetchpatch { url = \"https://github.com/linuxmint/cinnamon/commit/76224fe409d074f8a44c70e4fd5e1289f92800b9.patch\"; sha256 = \"sha256-nDt4kkK1kVstxbij63XxTJ2L/TM9Q1P6feok3xlPQOM=\"; }) # keybindings.js: Use bindings.get(). # Can be removed on next update. # https://github.com/linuxmint/cinnamon/issues/11055 (fetchpatch { url = \"https://github.com/linuxmint/cinnamon/commit/7724e4146baf8431bc1fb55dce60984e77adef5a.patch\"; sha256 = \"sha256-idGtkBa13nmoEprtmAr6OssO16wJwBd16r2ZbbhrYDQ=\"; }) ]; buildInputs = [", "positive_passages": [{"docid": "doc-en-nixpkgs-451cab574cc9604bc25a466d5ad6197d77eaf3bdd7635fc351b5f0063a70ef0f", "text": "I am new to nixos... When I try to use printScr Key on keyboard. it not responding. non of the printScreen optins working.. Steps to reproduce the behavior: ... press Key PrintScr ... ... Should take a screen shot ask for location to save to. If applicable, add screenshots to help explain your problem. Add any other context about the problem here. ", "positive_passages": [{"docid": "doc-en-nixpkgs-a7079e198aca988098951b4fa76cc9c83dc618ebe0d3503c23f6bfa32d8f7208", "text": "Since May 10, .NET 5.0 is EOL (End Of Life), and should not be used. Should it be marked as EOF similar to dotnet 2.2 and 3.0? See All packages using dotnet 5.0 should be updated to use a newer, supported version. These packages still need updating: [x] - [x] - [x] - [x] pkgs/development/tools/build- - [x] -\nThere is at least one package, which currently uses dotnet 5 sdk - . So we will need to update it beforehand. Btw, I'm not sure if we have any policy regarding packages removal, for nixpkgs in general or specifically for it's dotnet part. , what do you think?\nThe package is also using .NET 5: . But this is because I made the PR upstream updating it from .NET 4 to 5. I suspect that the transition to 6 will be similarly easy.\nI think we should just mark it as depricated, as many projects do still use it upstream. Dotnet version 3 is also still commonly used, so I dont expect it would be realistic to remove version 5 any time soon. also uses dotnet 5 by default, I'll go ahead and switch that over now. See . That doesnt mark dotnet 5 as deprecated or change anything from a SDK perspective, just some preperation work.\nSee as well, it adds a warning whenever dotnet version 5 is used. Not using a throw for now since a few packages depend on it and I dont have the time to clean that all up at the moment.\nCan you provide a list of packages that need updating?\nBased on a quick grep: pkgs/development/tools/build-\nI believe that after all the above PRs are merged, we should be able to safely remove .NET 5 from nixpkgs :)", "commid": "nixpkgs_issue_173115", "tokennum": 405}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-0281b17aa287723f443aaf51f1a78812f3403589916a9582c9437b6fa1483036", "query": "version = \"0.24\"; src = pkgs.fetchurl { url = \"http://www.cython.org/release/${name}.tar.gz\"; url = \"mirror://pypi/C/Cython/${name}.tar.gz\"; sha256 = \"1wd3q97gia3zhsgcdlvxh26hkrf3m53i6r1l4g0yya119264vr3d\"; };", "positive_passages": [{"docid": "doc-en-nixpkgs-271cc78d174da36f32a4a2d69e23cae5ba269e47da0ad532cbc0947ea64afa0d", "text": "Source no longer apparently available from upstream website. They recommend using pypi. Attempt to build , as in :", "commid": "nixpkgs_issue_16218", "tokennum": 23}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-02a7dbac88516f27f589c6e89f1b02f0578769513fe753cf3eff810155c29882", "query": " import ./make-test.nix ({ pkgs, lib, ...} : { name = \"gotify-server\"; meta = with pkgs.stdenv.lib.maintainers; { maintainers = [ ma27 ]; }; machine = { pkgs, ... }: { environment.systemPackages = [ pkgs.jq ]; services.gotify = { enable = true; port = 3000; }; }; testScript = '' startAll; $machine->waitForUnit(\"gotify-server\"); $machine->waitForOpenPort(3000); my $token = $machine->succeed( \"curl --fail -sS -X POST localhost:3000/application -F name=nixos \" . '-H \"Authorization: Basic $(echo -ne \"admin:admin\" | base64 --wrap 0)\" ' . '| jq .token | xargs echo -n' ); my $usertoken = $machine->succeed( \"curl --fail -sS -X POST localhost:3000/client -F name=nixos \" . '-H \"Authorization: Basic $(echo -ne \"admin:admin\" | base64 --wrap 0)\" ' . '| jq .token | xargs echo -n' ); $machine->succeed( \"curl --fail -sS -X POST 'localhost:3000/message?token=$token' -H 'Accept: application/json' \" . '-F title=Gotify -F message=Works' ); my $title = $machine->succeed( \"curl --fail -sS 'localhost:3000/message?since=0&token=$usertoken' | jq '.messages|.[0]|.title' | xargs echo -n\" ); $title eq \"Gotify\" or die \"Wrong title ($title), expected 'Gotify'!\"; ''; }) ", "positive_passages": [{"docid": "doc-en-nixpkgs-a2208ba5659daaaabe5723e3ff15318bd4e1fbb7ac5c248ef8fbb4e919cf7b90", "text": "Project description A simple server for sending and receiving messages in real-time per WebSocket. Includes a web UI, also has an Android client for receiving notifications and an optional CLI program (distributed separately) for sending notifications. Metadata homepage URL: source URL: license: MIT platforms: anything Go runs on\nI started an attempt locally, however it failed due to some timeouts while fetching Go dependencies... will retry during this week :)\nI think the main difficulty is the UI, which needs to be compiled with NPM. In essence, I think the build is three-staged: fetch UI dependencies, fetch Go dependencies, do the actual build.\nYou may want to take a look at .", "commid": "nixpkgs_issue_67384", "tokennum": 153}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-02c4aab2e3c11dca7d9287028fad57e81efe402b18a869522bb148bf665ebf4d", "query": " { config, lib, pkgs, ... }: with lib; let cfg = config.programs.msmtp; in { meta.maintainers = with maintainers; [ pacien ]; options = { programs.msmtp = { enable = mkEnableOption \"msmtp - an SMTP client\"; setSendmail = mkOption { type = types.bool; default = true; description = '' Whether to set the system sendmail to msmtp's. ''; }; defaults = mkOption { type = types.attrs; default = {}; example = { aliases = \"/etc/aliases\"; port = 587; tls = true; }; description = '' Default values applied to all accounts. See msmtp(1) for the available options. ''; }; accounts = mkOption { type = with types; attrsOf attrs; default = {}; example = { \"default\" = { host = \"smtp.example\"; auth = true; user = \"someone\"; passwordeval = \"cat /secrets/password.txt\"; }; }; description = '' Named accounts and their respective configurations. The special name \"default\" allows a default account to be defined. See msmtp(1) for the available options. Use `programs.msmtp.extraConfig` instead of this attribute set-based option if ordered account inheritance is needed. It is advised to use the `passwordeval` setting to read the password from a secret file to avoid having it written in the world-readable nix store. The password file must end with a newline (`n`). ''; }; extraConfig = mkOption { type = types.lines; default = \"\"; description = '' Extra lines to add to the msmtp configuration verbatim. See msmtp(1) for the syntax and available options. ''; }; }; }; config = mkIf cfg.enable { environment.systemPackages = [ pkgs.msmtp ]; services.mail.sendmailSetuidWrapper = mkIf cfg.setSendmail { program = \"sendmail\"; source = \"${pkgs.msmtp}/bin/sendmail\"; setuid = false; setgid = false; }; environment.etc.\"msmtprc\".text = let mkValueString = v: if v == true then \"on\" else if v == false then \"off\" else generators.mkValueStringDefault {} v; mkKeyValueString = k: v: \"${k} ${mkValueString v}\"; mkInnerSectionString = attrs: concatStringsSep \"n\" (mapAttrsToList mkKeyValueString attrs); mkAccountString = name: attrs: '' account ${name} ${mkInnerSectionString attrs} ''; in '' defaults ${mkInnerSectionString cfg.defaults} ${concatStringsSep \"n\" (mapAttrsToList mkAccountString cfg.accounts)} ${cfg.extraConfig} ''; }; } ", "positive_passages": [{"docid": "doc-en-nixpkgs-9f8d973790633895f03ad38a4f631455a31557eec5a27e134b30bdf71fed07df", "text": "The ssmtp program is dead/unmaintained. The commonly suggested substitute is msmtp. While [home-manager has a module for msmtp][1], NixOS lacks one. [1]: Let's: [x] Done in We should probably also: [x] Remove the ssmtp NixOS module and add migration instructions to the release notes () [x] Remove the ssmtp package ()\nI marked this as stale due to inactivity. →\nThe module works really well. Thanks for the module", "commid": "nixpkgs_issue_105710", "tokennum": 118}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-02e09652b273599b6d6013367ec221812c07d170e0669295a4773ad0afcf4a49", "query": "# https://github.com/NixOS/nixpkgs/pull/161773#discussion_r820134708 zenKernels = callPackage ../os-specific/linux/kernel/zen-kernels.nix; linux_zen = (zenKernels { linux_zen = zenKernels { variant = \"zen\"; kernelPatches = [ kernelPatches.bridge_stp_helper kernelPatches.request_key_helper ]; }).zen; }; linux_lqx = (zenKernels { linux_lqx = zenKernels { variant = \"lqx\"; kernelPatches = [ kernelPatches.bridge_stp_helper kernelPatches.request_key_helper ]; }).lqx; }; # This contains the variants of the XanMod kernel xanmodKernels = callPackage ../os-specific/linux/kernel/xanmod-kernels.nix { xanmodKernels = callPackage ../os-specific/linux/kernel/xanmod-kernels.nix; linux_xanmod = xanmodKernels { variant = \"lts\"; kernelPatches = [ kernelPatches.bridge_stp_helper kernelPatches.request_key_helper ]; }; linux_xanmod_stable = xanmodKernels { variant = \"main\"; kernelPatches = [ kernelPatches.bridge_stp_helper kernelPatches.request_key_helper ]; }; linux_xanmod_latest = xanmodKernels { variant = \"main\"; kernelPatches = [ kernelPatches.bridge_stp_helper kernelPatches.request_key_helper ]; }; linux_xanmod = xanmodKernels.lts; linux_xanmod_stable = xanmodKernels.main; linux_xanmod_latest = xanmodKernels.main; linux_libre = deblobKernel packageAliases.linux_default.kernel;", "positive_passages": [{"docid": "doc-en-nixpkgs-777348a90017a07a7256e52c4e04bea8f69f252116fc335d27cb71f122cb95da", "text": "Mainline / hardened / testing / ... kernels can be painlessly modified via : Sadly, this does not work with a bunch of other kernel variants: All kernels should honor I am not entirely sure how dynamic binding is implemented in kernel stuff, however slightly changing xanmod parts this way seems to fix : zen and lqx look similar to xanmod, no idea about libre Pinging people who seem to update affected packages often Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nsame underlying issue as it seems\nCan confirm that this patch fix the issue for zen and lqx kernels:\nhave you submitted these changes as a PR that I can review?\nsorry for the late response. I created a new PR with this changes.\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:", "commid": "nixpkgs_issue_314591", "tokennum": 188}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-02fc1f5b18462a10a58e150e0ac36dcfac7061c63c9f8eb0eb87e74cc13215b4", "query": "\"-p:PublishTrimmed=true\" ]; dotnetInstallFlags = [ \"--framework=net7.0\" \"--framework=net8.0\" ]; selfContainedBuild = true;", "positive_passages": [{"docid": "doc-en-nixpkgs-8d5c740bdb78d6c578a989c0f7616fe42fbc3923340ef85ecdfc027a30955794", "text": "Looks like it now uses .NET 8 which probably made all existing plugins incompatible - Package name: ArchiSteamFarm Latest released version: 5.5.0.11 - [ownCloud Infinite Scale Stack](https://owncloud.com/infinite-scale-4-0/), a modern and scalable rewrite of ownCloud. - [Handheld Daemon](https://github.com/hhd-dev/hhd), support for gaming handhelds like the Legion Go, ROG Ally, and GPD Win. Available as [services.handheld-daemon](#opt-services.handheld-daemon.enable). - [Guix](https://guix.gnu.org), a functional package manager inspired by Nix. Available as [services.guix](#opt-services.guix.enable).", "positive_passages": [{"docid": "doc-en-nixpkgs-2273bc5198fe9d09243e56c93bfc55a3b191530a572f22968cb9eebf7a48c3ed", "text": "\"ownCloud Infinite Scale Stack\" or owncloud rewritten in Go. ``` The comments will not be rendered in the rendered HTML. #### Link reference definitions Links can reference a label, for example, to make the link target reusable: ```markdown ::: {.note} Reference links can also be used to [shorten URLs][url-id] and keep the markdown readable. ::: [url-id]: https://github.com/NixOS/nixpkgs/blob/19d4f7dc485f74109bd66ef74231285ff797a823/doc/README.md ``` This syntax is taken from [CommonMark](https://spec.commonmark.org/0.30/#link-reference-definitions). #### Typographic replacements Typographic replacements are enabled. Check the [list of possible replacement patterns check](https://github.com/executablebooks/markdown-it-py/blob/3613e8016ecafe21709471ee0032a90a4157c2d1/markdown_it/rules_core/replacements.py#L1-L15). ## Getting help If you need documentation-specific help or reviews, ping [@NixOS/documentation-reviewers](https://github.com/orgs/nixos/teams/documentation-reviewers) on your pull request.", "positive_passages": [{"docid": "doc-en-nixpkgs-b82978e60eecc691ae933eecb8185668502db649d652503be51f9fc63919a6c2", "text": "Contributors working on improving the nixpkgs manual would be redirected to the . This section is not up-to-date with all the syntax features supported by , forcing contributors to look for use examples over the whole manual. The same markdown syntax is used to write and generate the NixOS manual. However, this manual does not make any mention of the supported syntax. This makes it hard to contribute to the NixOS manual with relative isolation from the nixpkgs manual. Update in Nixpkgs manual to include reference material and examples on all the syntax features supported by . Link in Nixos manual for completion. [x] remove references to in the . : [x] remove references to in the . [x] add a redirecting to the syntax section in . [x] add reference to lack of support for [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support () () )", "commid": "nixpkgs_issue_246357", "tokennum": 232}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-76fa1362f279d5cf6dd3a4d502691a4fe92045f9b1fc6685ef6425343a0109a5", "query": "sha256 = \"sha256-0S7Dj6PMSbZkEAY6ZLUpKVfe/tFxsq60TTAFj0Qhtv0=\"; }; # See https://github.com/NixOS/nixpkgs/issues/156957. postPatch = '' substituteInPlace setup.py --replace \"dill>=0.3.1.1,<0.3.2\" \"dill\" --replace \"pyarrow>=0.15.1,<8.0.0\" \"pyarrow\" --replace \"numpy>=1.14.3,<1.23.0\" \"numpy\" --replace \"pymongo>=3.8.0,<4.0.0\" \"pymongo\" ''; pythonRelaxDeps = [ # See https://github.com/NixOS/nixpkgs/issues/156957 \"dill\" \"numpy\" \"pyarrow\" \"pymongo\" # See https://github.com/NixOS/nixpkgs/issues/193613 \"protobuf\" ]; sourceRoot = \"source/sdks/python\";", "positive_passages": [{"docid": "doc-en-nixpkgs-8865a2a0a97e111f30b92c2ba6d281111cd174fa4f5da241d3ef0dbb9eb72328", "text": "Build of failed on x86_64-linux as of . This is currently breaking . python39Packages.tensorflow-datasets maintainers cc: maintainers cc: Other cc: n/a nixpkgs at commit This issue was automatically generated by . that created this issue. Internal tags:", "commid": "nixpkgs_issue_193613", "tokennum": 64}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-7719c95207885042e2a2f2a5d67e6e5a22ac5b1104e77db540f86804e0c7279d", "query": ", gnome3 , libhandy , librsvg , rustc , cargo }: rustPlatform.buildRustPackage rec { stdenv.mkDerivation rec { pname = \"gnome-tour\"; version = \"3.38.0\";", "positive_passages": [{"docid": "doc-en-nixpkgs-4aeed9179222b372673755d35a25b3e27a19fcb59f06048305f8850fa6a86a74", "text": "Describe the bug fails to compile with Additional context See for a possible cause. Notify maintainers cc (sorry for notifying you here and in the PR!)\nGonna try to just switch it to . We should probably update gnome docs for Rust+Gnome packages\nYeah, I think that would be best. The idea of the hooks is that is not necessary anymore in mixed projects. I will also do a PR for cargoBuildHook, since it should not be used when is set explicitly.", "commid": "nixpkgs_issue_114659", "tokennum": 102}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-772b717a0ba2df2617f484158b3b0d4c8f6e4b16f471f9f351d0e2556b7cd1ad", "query": "''; installPhase = let pythonPath = python.pkgs.makePythonPath propagatedBuildInputs; pythonPath = python.pkgs.makePythonPath dependencies; in '' runHook preInstall", "positive_passages": [{"docid": "doc-en-nixpkgs-bf93bee584c302a717bc81f9efd5650c71aee4cb57a0d01cb56676001a226f14", "text": "Package name: paperless-ngx Latest released version: 2.12.1 - The `power.ups` module now generates `upsd.conf`, `upsd.users` and `upsmon.conf` automatically from a set of new configuration options. This breaks compatibility with existing `power.ups` setups where these files were created manually. Back up these files before upgrading NixOS. - `mkosi` was updated to v19. Parts of the user interface have changed. Consult the [release notes](https://github.com/systemd/mkosi/releases/tag/v19) for a list of changes.", "positive_passages": [{"docid": "doc-en-nixpkgs-7e3875ddf580eb79f3e4440df607bae8fb544f5dd780ae8e21ba1a72342cd3a6", "text": "Describe the bug I'm trying to use NixOS in a UPS client (not server). When , the and services shouldn't be running. There is a note that says that is not used currently. To Reproduce Steps to reproduce the behavior: Error: and fail. Expected behavior only upsmon should be running Notify maintainers - The `power.ups` module now generates `upsd.conf`, `upsd.users` and `upsmon.conf` automatically from a set of new configuration options. This breaks compatibility with existing `power.ups` setups where these files were created manually. Back up these files before upgrading NixOS. - `mkosi` was updated to v19. Parts of the user interface have changed. Consult the [release notes](https://github.com/systemd/mkosi/releases/tag/v19) for a list of changes.", "positive_passages": [{"docid": "doc-en-nixpkgs-f42455fa63faa260588e21bb0034eaf58f1498ea931b3c7b82da3096e74cc480", "text": "Describe the bug The following snippet: results in services failing to start due to missing config files etc. : : ( fails too, but that could be down to the fact that I haven't plugged the UPS in yet -- but for the record, it complains ) Expected behavior I'd expect the services to start successfully (and probably complain about the missing actual UPS). Notify maintainers (The UPS module appears to have received only drive-by changes for the last several years, so no idea who to bug personally). Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:\nOK, should've read the whole module: I'm supposed to supply the missing /etc/nut files myself because it's unwise to keep them in the store (they could contain passwords and whatnot, I guess?). Declaring (in the service definitions) the state directory to be but creating for the purpose appears to be a real bug, though :)\nAlso (sorry for the semi-off-topic) what are best practices for referencing hand-written config files without their contents winding up in the store? Double-symlinking? If this is documented somewhere, then I haven't found where.\nI was struggling with the same problem as until I noticed this bug report. After copying and editing , , and from to (and setting on all those files), I was able to get it to work. I think this should be more discoverable. If it's not appropriate to copy those sample files to on the users behalf, there should at least be detailed instructions on the option to explain what else needs to be done.\nI marked this as stale due to inactivity. →\nAgreed this should be more discoverable. Perhaps at least could be defaulted to empty and written, since I seem to be getting away without anything in there. In case it helps anyone, I got it working with something like this:\nI was hit this bug today, too. Maybe we can fix it by using a startup unit that handles the secrets and setup the state directories like nextcloud or syncthing do\nBeen working on today and wanted to put some notes here. Using version 2.7.4. First, isn't used by for PIDs and it will try to write to .", "commid": "nixpkgs_issue_91681", "tokennum": 498}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-d0b7f261d02663f82d993105dc3406bff78fa01c73a0f07c04dd7743f6b0ef25", "query": " - The `power.ups` module now generates `upsd.conf`, `upsd.users` and `upsmon.conf` automatically from a set of new configuration options. This breaks compatibility with existing `power.ups` setups where these files were created manually. Back up these files before upgrading NixOS. - `mkosi` was updated to v19. Parts of the user interface have changed. Consult the [release notes](https://github.com/systemd/mkosi/releases/tag/v19) for a list of changes.", "positive_passages": [{"docid": "doc-en-nixpkgs-b9aa03afc140411f7cb98b1a75ef1428e8e2733962d63403f6fbd21ed1ddfa08", "text": "flags , , may be needed instead of environment variables until a 2.7.5 release. Ref: Using for debug makes it non-forking, requiring a change to the systemd unit . I was able to get to run as non-root: I'm still working on understanding how to manage state directories in NixOS but this was needed:\nI set out to get my UPS (cyberpower CP1500 AVR UPS) working with NixOS today. This was the first issue I came across, I figured this was the best place to share my configuration. I probably made this more complex than it needed to be because I have no idea what I am doing, and it is definitely not secure; one problem at a time.\nNot stale; still relevant\nThanks for providing your standalone config! I learned a ton tweaking it into a netserver config! The below config creates a working NUT netserver that other machines on your local network can be connected to. The only thing I have yet to figure out is a secure way to include passwords in .nix files that won't show up if I push my local copy to github. Any ideas? If you want to tweak when NUT shuts down your computers you can modify the values of \" = NIX_LDFLAGS = lib.optionals (!atLeast24) [ # https://github.com/NixOS/nix/commit/3e85c57a6cbf46d5f0fe8a89b368a43abd26daba (lib.optionalString enableStatic \"-lssl -lbrotlicommon -lssh2 -lz -lnghttp2 -lcrypto\") # https://github.com/NixOS/nix/commits/74b4737d8f0e1922ef5314a158271acf81cd79f8 (lib.optionalString (stdenv.hostPlatform.system == \"armv5tel-linux\" || stdenv.hostPlatform.system == \"armv6l-linux\") \"-latomic\") ]; postPatch = '' patchShebangs --build tests '';", "positive_passages": [{"docid": "doc-en-nixpkgs-f8cff2a6b64a7d20c4d5fc35cd36f74c29031455ce1240673825fb3965e950d5", "text": "Package name: nix23 Latest released version: 2.3.17 (see ) Current version on the unstable channel: 2.3.16 Current version on the stable/release channel: 2.3.16 Notify maintainers Note for maintainers: Please tag this issue in your PR. See for context. The release script apparently doesn't upload source tarballs anymore, so 2.3.17 sources look more like the other ones. There's a bunch of expressions in that might need to be revisited.", "commid": "nixpkgs_issue_265916", "tokennum": 107}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-d0d6e0e3491ef41d2dd9a12f652cb0290a3ce2f4b1c8a9457982f61d0ec48ea9", "query": "desktop-file-utils glib wrapGAppsHook python3Packages.pip ]; buildInputs = [", "positive_passages": [{"docid": "doc-en-nixpkgs-be1dfc843eec01a09fa9b483d920f907317e286bf0f42506a8c8f53bafc01e6b", "text": "Steps to reproduce the behavior: package 'grapejuice' Fixed by adding to propagatedBuildInputs Please run and paste the result.", "commid": "nixpkgs_issue_252052", "tokennum": 31}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-d1995e56a88d430a0895831cedca7b01d96e87579a270f2d6fc0da1ac7b6a8bc", "query": "doCheck = (!stdenv.isDarwin); # examples.complex.xss_scanner doesn't import correctly with pytest5 checkPhase = '' export HOME=$(mktemp -d) export LC_CTYPE=en_US.UTF-8 pytest -k 'not test_find_unclaimed_URLs and not test_tcp' pytest --ignore test/examples -k 'not test_find_unclaimed_URLs and not test_tcp' ''; propagatedBuildInputs = [", "positive_passages": [{"docid": "doc-en-nixpkgs-b4fe243ce0686505f4b6df04586261d2a75b64ba551055e3adb36103aee5fbc4", "text": "Describe the bug A clear and concise description of what the bug is. mitmproxy tests broken on unstable. To Reproduce Steps to reproduce the behavior: nix-env -iA nixos-unstable.mitmproxy Additional context Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:\nthank you for submitting this, ill get it fixed", "commid": "nixpkgs_issue_73506", "tokennum": 86}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-d19b933a985134ff969eab37c4c488881b4b279b650b5cc2b069f7523be28aad", "query": "${optionalString cfg.caching.apcu \"'memcache.local' => 'OCMemcacheAPCu',\"} 'log_type' => 'syslog', 'log_level' => '${builtins.toString cfg.logLevel}', ${optionalString (cfg.config.overwriteProtocol != null) \"'overwriteprotocol' => '${cfg.config.overwriteProtocol}',\"} ${optionalString (c.overwriteProtocol != null) \"'overwriteprotocol' => '${c.overwriteProtocol}',\"} ${optionalString (c.dbname != null) \"'dbname' => '${c.dbname}',\"} ${optionalString (c.dbhost != null) \"'dbhost' => '${c.dbhost}',\"} ${optionalString (c.dbport != null) \"'dbport' => '${toString c.dbport}',\"} ${optionalString (c.dbuser != null) \"'dbuser' => '${c.dbuser}',\"} ${optionalString (c.dbtableprefix != null) \"'dbtableprefix' => '${toString c.dbtableprefix}',\"} ${optionalString (c.dbpass != null) \"'dbpassword' => '${c.dbpass}',\"} ${optionalString (c.dbpassFile != null) \"'dbpassword' => nix_read_pwd(),\"} 'dbtype' => '${c.dbtype}', 'trusted_domains' => ${writePhpArrary c.extraTrustedDomains}, ]; ''; occInstallCmd = let c = cfg.config; adminpass = if c.adminpassFile != null then ''\"$(<\"${toString c.adminpassFile}\")\"'' else ''\"${toString c.adminpass}\"''; dbpass = if c.dbpassFile != null then ''\"$(<\"${toString c.dbpassFile}\")\"'' else if c.dbpass != null then ''\"${toString c.dbpass}\"'' else null; adminpass = if c.adminpassFile != null then ''\"$(<\"${toString c.adminpassFile}\")\"'' else ''\"${toString c.adminpass}\"''; installFlags = concatStringsSep \" n \" (mapAttrsToList (k: v: \"${k} ${toString v}\") { \"--database\" = ''\"${c.dbtype}\"'';", "positive_passages": [{"docid": "doc-en-nixpkgs-92b14e6173137c0a37b55493ebed2edffc15393ffbe0c79634a221cfd529baf3", "text": "Data that was once config and recorded on doesn't get updated when the configuration changes. This is a violation of purity. And more than that, it's very surprising when trying to install, hesitating between pgsql and sqlite, and struggling before understanding that the configuration doesn't get used anyway :p cc\nthat's a bit tough. We have a unit, that's supposed to do the installation. We use the command to install nextcloud (passing the configured database and adminpass settings as command parameters). This CLI generates , and installs nextcloud. The script checks the presence of , and skips installation on following starts. If you now change configuration from the module, we won't run the install command again, as the config file already exists, and assumes nextcloud is already installed.\nHmm\u2026 Maybe it would be possible to generate the somewhere in the store, and symlink to it? This way the next time runs it can in addition check whether points to the correct store path. Now, I don't really know what exactly does, so maybe it's not actually possible to do this because eg. one would need to re-run on certain configuration changes? In which case it'd be hard :/ but at least we can maybe make fail or something like that, so that the issue is at least noisy?\nI don't recommend to do this, I just tried that (after upgrading one of my personal systems) and this tries to recreate a database schema which can end in very bad results. Unfortunately I doubt that this will work properly, nextcloud wants to merge this during the runtime. E.g. it adds a after a successful or adds trusted domains when running the corresponding command. I'm using this as well now and hitting these issues, unfortunately I don't have useful ideas either ATM, but I'm happy to discuss better solutions :)\nNextcloud edits it's in a lot of different places, so having it generated through Nix currently isn't possible. digs into that already, I a comments about our use case here too.\nto avoid other people running into the reconfiguration issue for now, what about documenting that, maybe in ?\nThat's certainly a good thing to do.", "commid": "nixpkgs_issue_49783", "tokennum": 484}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-d19b933a985134ff969eab37c4c488881b4b279b650b5cc2b069f7523be28aad", "query": "${optionalString cfg.caching.apcu \"'memcache.local' => 'OCMemcacheAPCu',\"} 'log_type' => 'syslog', 'log_level' => '${builtins.toString cfg.logLevel}', ${optionalString (cfg.config.overwriteProtocol != null) \"'overwriteprotocol' => '${cfg.config.overwriteProtocol}',\"} ${optionalString (c.overwriteProtocol != null) \"'overwriteprotocol' => '${c.overwriteProtocol}',\"} ${optionalString (c.dbname != null) \"'dbname' => '${c.dbname}',\"} ${optionalString (c.dbhost != null) \"'dbhost' => '${c.dbhost}',\"} ${optionalString (c.dbport != null) \"'dbport' => '${toString c.dbport}',\"} ${optionalString (c.dbuser != null) \"'dbuser' => '${c.dbuser}',\"} ${optionalString (c.dbtableprefix != null) \"'dbtableprefix' => '${toString c.dbtableprefix}',\"} ${optionalString (c.dbpass != null) \"'dbpassword' => '${c.dbpass}',\"} ${optionalString (c.dbpassFile != null) \"'dbpassword' => nix_read_pwd(),\"} 'dbtype' => '${c.dbtype}', 'trusted_domains' => ${writePhpArrary c.extraTrustedDomains}, ]; ''; occInstallCmd = let c = cfg.config; adminpass = if c.adminpassFile != null then ''\"$(<\"${toString c.adminpassFile}\")\"'' else ''\"${toString c.adminpass}\"''; dbpass = if c.dbpassFile != null then ''\"$(<\"${toString c.dbpassFile}\")\"'' else if c.dbpass != null then ''\"${toString c.dbpass}\"'' else null; adminpass = if c.adminpassFile != null then ''\"$(<\"${toString c.adminpassFile}\")\"'' else ''\"${toString c.adminpass}\"''; installFlags = concatStringsSep \" n \" (mapAttrsToList (k: v: \"${k} ${toString v}\") { \"--database\" = ''\"${c.dbtype}\"'';", "positive_passages": [{"docid": "doc-en-nixpkgs-c4e56eafb4795d6fe067848a15c32dddf2be7d2dfa8a8db4e6140162b43d60cc", "text": "If nobody else wants to take over, I'd volunteer to do this during the next week as investing time on improving the nextcloud module is one item on my todo list :) I was aware of being stateful, but thanks a lot for linking the corresponding ticket! I'll have a look at this as soon as I have sufficient time to :)\nIn the light of this issue, what's the correct way to upgrade nextcloud to a new major version? Do I just pull a newer , upgrade my system and hope that the systemd job will do the right thing?\nThe service runs an that should apply all changes like database migrations needed for the new Nextcloud version (beware, downgrades aren't possible). As long as you let Nextcloud do its job, you shouldn't get that much issues. IMHO the actual problem here is the configuration of the software within Nix(OS).\njust a simple question (could not come to a conclusion after the lengthy thread) but I recently updated my nextcloud via nixops deploy and the update disabled the calendar module. Did I mess up or is that expected ? any way to configure this from nix ?\nAssuming that you installed the calendar module via the UI, it is installed in . The beginning of my config reads: So in principle nextcloud can edit the apps installed via the web interface (otherwise you couldn't install them via the interface in the first place).\nI don't think there's anything actionable here - the nextcloud nixos module is limited by how Nextcloud (imperatively) manages its configuration. The current state is properly documented in , and we raised our concerns to upstream in - closing this issue, feel free to reopen if there's more to be done.\nI think one actionable item would be to have the nextcloud service fail with an explicit error if the configuration being used is not compatible with the configuration defined in the .nix. At least the user would be warned in practice that configuration is not really applied, and not only by the manual that they are relatively unlikely to actually read. Reopening for now, feel free to reclose if you think that's not a reasonable \u201csolution\u201d :)\nThe problem is we don't know whether the configuration on disk containing database connection information () differs from the one that would be generated through an installation via - we don't render the configuration on our own, but the installer writes it out as a side-effect.", "commid": "nixpkgs_issue_49783", "tokennum": 528}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-d19b933a985134ff969eab37c4c488881b4b279b650b5cc2b069f7523be28aad", "query": "${optionalString cfg.caching.apcu \"'memcache.local' => 'OCMemcacheAPCu',\"} 'log_type' => 'syslog', 'log_level' => '${builtins.toString cfg.logLevel}', ${optionalString (cfg.config.overwriteProtocol != null) \"'overwriteprotocol' => '${cfg.config.overwriteProtocol}',\"} ${optionalString (c.overwriteProtocol != null) \"'overwriteprotocol' => '${c.overwriteProtocol}',\"} ${optionalString (c.dbname != null) \"'dbname' => '${c.dbname}',\"} ${optionalString (c.dbhost != null) \"'dbhost' => '${c.dbhost}',\"} ${optionalString (c.dbport != null) \"'dbport' => '${toString c.dbport}',\"} ${optionalString (c.dbuser != null) \"'dbuser' => '${c.dbuser}',\"} ${optionalString (c.dbtableprefix != null) \"'dbtableprefix' => '${toString c.dbtableprefix}',\"} ${optionalString (c.dbpass != null) \"'dbpassword' => '${c.dbpass}',\"} ${optionalString (c.dbpassFile != null) \"'dbpassword' => nix_read_pwd(),\"} 'dbtype' => '${c.dbtype}', 'trusted_domains' => ${writePhpArrary c.extraTrustedDomains}, ]; ''; occInstallCmd = let c = cfg.config; adminpass = if c.adminpassFile != null then ''\"$(<\"${toString c.adminpassFile}\")\"'' else ''\"${toString c.adminpass}\"''; dbpass = if c.dbpassFile != null then ''\"$(<\"${toString c.dbpassFile}\")\"'' else if c.dbpass != null then ''\"${toString c.dbpass}\"'' else null; adminpass = if c.adminpassFile != null then ''\"$(<\"${toString c.adminpassFile}\")\"'' else ''\"${toString c.adminpass}\"''; installFlags = concatStringsSep \" n \" (mapAttrsToList (k: v: \"${k} ${toString v}\") { \"--database\" = ''\"${c.dbtype}\"'';", "positive_passages": [{"docid": "doc-en-nixpkgs-e4cf0a48ca0407b14e74a8a4d6172973ee0007ab7182b6a4f2414eba4f2b1982", "text": "If I'm not missing something obvious, checking configuration changes would translate to parsing/evaluating on every nextcloud startup as an , comparing every \"interesting\" key with the one provided through nixos configuration, and eventually then bailing out if they differ. I'm not sure if that's a road we'd like to go and keep up to date, while the underlying bug is a missing distinction between configuration and state upstream\u2026\nSince upstream mixes state and config it's questionable whether their configuration format is somehow supposed to be backwards-compatible (as it's only supposed to be used internally by Nextcloud). Hence I'm afraid that this will make i.e. upgrades even harder in case of configuration changes, so :-1: from me. As the issues are documented in the manual now, folks are warned and I think that this is a better option in contrast to adding more complexity to . I suggest we either close this for the reasons already stated or wait for an appropriate upstream fix.\nI really don't feel good having stuff in that's actually a disguised command line\u2026 :/ Something that would sound nicer to me would be an executable that the user would have to manually run, and a bare-bones module that does not handle setup or configuration and just makes sure that the systemd unit is setup. At least the error is obvious (enabling the module without having run the executable would fail), all module options actually mean something, and the impure operation is made explicit. Either that or, similar to , rename all the options so it's explicit that they're used only for initial configuration. Would one of these solutions make sense to you?\nMe neither, but currently we don't have much choice\u2026 I really like the fact that we can set up the Nextcloud instance in an unattended fashion, without having to worry about manual setting things up. I really don't want to end with more imperative setup steps than necessary. In theory, we could move some of the options in to to make it more obvious what isn't applied continuously. But TBH, I'd rather like to see the state/config mixing fixed upstream than having to introduce more mental complexity here, especially if this gets fixed and we end up with both incarnations. Really, this issue only occurs while a user changes nextcloud database parameters (mostly while tweaking his initial setup), and not having read the module documentation, where the behaviour is documented.", "commid": "nixpkgs_issue_49783", "tokennum": 521}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-d19b933a985134ff969eab37c4c488881b4b279b650b5cc2b069f7523be28aad", "query": "${optionalString cfg.caching.apcu \"'memcache.local' => 'OCMemcacheAPCu',\"} 'log_type' => 'syslog', 'log_level' => '${builtins.toString cfg.logLevel}', ${optionalString (cfg.config.overwriteProtocol != null) \"'overwriteprotocol' => '${cfg.config.overwriteProtocol}',\"} ${optionalString (c.overwriteProtocol != null) \"'overwriteprotocol' => '${c.overwriteProtocol}',\"} ${optionalString (c.dbname != null) \"'dbname' => '${c.dbname}',\"} ${optionalString (c.dbhost != null) \"'dbhost' => '${c.dbhost}',\"} ${optionalString (c.dbport != null) \"'dbport' => '${toString c.dbport}',\"} ${optionalString (c.dbuser != null) \"'dbuser' => '${c.dbuser}',\"} ${optionalString (c.dbtableprefix != null) \"'dbtableprefix' => '${toString c.dbtableprefix}',\"} ${optionalString (c.dbpass != null) \"'dbpassword' => '${c.dbpass}',\"} ${optionalString (c.dbpassFile != null) \"'dbpassword' => nix_read_pwd(),\"} 'dbtype' => '${c.dbtype}', 'trusted_domains' => ${writePhpArrary c.extraTrustedDomains}, ]; ''; occInstallCmd = let c = cfg.config; adminpass = if c.adminpassFile != null then ''\"$(<\"${toString c.adminpassFile}\")\"'' else ''\"${toString c.adminpass}\"''; dbpass = if c.dbpassFile != null then ''\"$(<\"${toString c.dbpassFile}\")\"'' else if c.dbpass != null then ''\"${toString c.dbpass}\"'' else null; adminpass = if c.adminpassFile != null then ''\"$(<\"${toString c.adminpassFile}\")\"'' else ''\"${toString c.adminpass}\"''; installFlags = concatStringsSep \" n \" (mapAttrsToList (k: v: \"${k} ${toString v}\") { \"--database\" = ''\"${c.dbtype}\"'';", "positive_passages": [{"docid": "doc-en-nixpkgs-c18de52bf5cfd2a2f4ec3e5fa95428d955562611c8e8ba19985e2786aaf847a4", "text": "What about adding the following (subtile) log statement, to point users to the docs when they peek into the logs while things are not working as expected?\nI agree that the log statement is the minimum we can do, and would at least give a hint about the way in which things are broken. Now, I guess the reason we're kind of disagreeing on the path forward is that you're much more hopeful than me that nextcloud will ever fix its stuff -- I'm assuming it'll get fixed in years at best (and even then\u2026) -- and if it's in years then I'd much rather live with for years then spend a year deprecating it by making it conflict with new options than try to live with from now on and have users fail to understand what is going on. Now urhm, I'm investigating the module a bit deeper, and\u2026 is there any reason we can't put the database configuration etc. in ? We could then refresh on each activation, and it should be enough? If we have a way to couple it with something that automatically runs iff the database is not ready yet then the setup would actually be\u2026 almost perfect?\nAfter having a deeper look at the sources ( at github, (6 commits ahead of v16.0.0RC1)) I guess that this should be possible (I didn't test it yet though). Configs will be loaded from using PHP's function[1] while all files ending with will be taken into account. Hence works as all config arrays will be merged together. This config will be loaded at [2] and is available as which is then used in the DI container[3]. If I understand the code correctly, I assume that it should be possible to render all config options in as config files found by glob will override values from [4]. [4]\nNice catch! This might indeed be possible - we should make very sure that config overrides work the way we think they will - seems to write the merged configuration, and not just the overrides (and merging this with other config in the wrong order can lead to wonderfully weird to debug issues) ;-) While I'd still prefer nextcloud splitting config and state properly, and being able to cope with read-only (base) config - it might be a direction worth exploring. What do you think?", "commid": "nixpkgs_issue_49783", "tokennum": 524}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-d19b933a985134ff969eab37c4c488881b4b279b650b5cc2b069f7523be28aad", "query": "${optionalString cfg.caching.apcu \"'memcache.local' => 'OCMemcacheAPCu',\"} 'log_type' => 'syslog', 'log_level' => '${builtins.toString cfg.logLevel}', ${optionalString (cfg.config.overwriteProtocol != null) \"'overwriteprotocol' => '${cfg.config.overwriteProtocol}',\"} ${optionalString (c.overwriteProtocol != null) \"'overwriteprotocol' => '${c.overwriteProtocol}',\"} ${optionalString (c.dbname != null) \"'dbname' => '${c.dbname}',\"} ${optionalString (c.dbhost != null) \"'dbhost' => '${c.dbhost}',\"} ${optionalString (c.dbport != null) \"'dbport' => '${toString c.dbport}',\"} ${optionalString (c.dbuser != null) \"'dbuser' => '${c.dbuser}',\"} ${optionalString (c.dbtableprefix != null) \"'dbtableprefix' => '${toString c.dbtableprefix}',\"} ${optionalString (c.dbpass != null) \"'dbpassword' => '${c.dbpass}',\"} ${optionalString (c.dbpassFile != null) \"'dbpassword' => nix_read_pwd(),\"} 'dbtype' => '${c.dbtype}', 'trusted_domains' => ${writePhpArrary c.extraTrustedDomains}, ]; ''; occInstallCmd = let c = cfg.config; adminpass = if c.adminpassFile != null then ''\"$(<\"${toString c.adminpassFile}\")\"'' else ''\"${toString c.adminpass}\"''; dbpass = if c.dbpassFile != null then ''\"$(<\"${toString c.dbpassFile}\")\"'' else if c.dbpass != null then ''\"${toString c.dbpass}\"'' else null; adminpass = if c.adminpassFile != null then ''\"$(<\"${toString c.adminpassFile}\")\"'' else ''\"${toString c.adminpass}\"''; installFlags = concatStringsSep \" n \" (mapAttrsToList (k: v: \"${k} ${toString v}\") { \"--database\" = ''\"${c.dbtype}\"'';", "positive_passages": [{"docid": "doc-en-nixpkgs-04af33963a42328dbf0c54ed988ae388dd41d8a53fa37fa4fce1f7fa5bd4d355", "text": "Well, for the record it was actually idea :sweat_smile: I guess so, all the stuff from is also in my at the moment. I'll probably have sufficient time next weekend to check if I can trigger such a case. I can't promise that, but unless anybody beats me, I can hopefully prepare a fix for this :)\nDid you gain some new insights on this?\nUnfortunately not... I was pretty busy back then. But as this only requires some fiddling in the module and no patching of the actual package, the change shouldn't be too painful, so if you'd like to take over... :sweat_smile:\nthere's with a fix now :)", "commid": "nixpkgs_issue_49783", "tokennum": 148}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-d1ac0ba9fb9ccecc93a3cda49e5f6f20962f648615c735f7f90eb1fd6bb96d80", "query": "# luarocks only looks for rockspecs in the default/system tree instead of all # configured trees) luarocks_config = \"luarocks-config.lua\"; luarocks_content = '' luarocks_content = let extraVariablesStr = lib.concatStringsSep \"n \" (lib.mapAttrsToList (k: v: \"${k}='${v}';\") extraVariables); in '' local_cache = \"\" -- To prevent collisions when creating environments, we install the rock -- files into per-package subdirectories", "positive_passages": [{"docid": "doc-en-nixpkgs-edcd0f50c03ab3337ffbc029daa7e11cc68bd7fcbd1d59d3396f9c4c0023e7de", "text": "Describe the bug neovim fails to build with missing , similar to , on . To Reproduce Steps to reproduce the behavior: to from master () Expected behavior The package should successfully build. Metadata On master () Maintainer information:\nvia in\nso you could do until a proper fix.\nReverting the luarocks bump doesn't work for me. That fix is also very surprising to me, since neovim broke (for me) after the latest nixos-unstable channel update.\nInteresting. It worked fine for me. Running the above revert command and then (inside my local nixpkgs with it reverted) let me build neovim properly. I don't think it's particularly surprising if updating a channel that happens to include the luarocks bump causes it to break, unless I'm misunderstanding you.\nI updated from a channel where the luarocks bump had already happened, and neovim worked on that channel. In fact, I reverted to the previous hydra evaluation to make my system evaluate again.\nThis was actually before and it was working without problems and then suddenly the problem appeared again. I can also report that I cam getting this in the same way described (updated latest nixos-unstable channel and then neovim stopped building again).\nI confirm this fixed by on master (channels may take a while). For now I'll assume that charvp's failure to resolve the issue with that revert was some kind of mistake; we can re-open otherwise, perhaps separately if it's a different kind of error.\nDoes anyone know why updating the luarocks dependency is so brittle? Is it possible to at least add a test so we don't regress again in the future?\nthe tool exists (nixpkgs-review) but it takes CPU and disk space to run plus some reviewer time (and was not run in this case). Also for this specific case, the luarocks update broke in subtle ways the build so I wouldn't call it . It is called unstable for a reason. The good thing about nixpkgs is you can pin neovim to an older version while keeping your system on unstable.\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nAre we sure this is fixed on Darwin? still shows failing with logs of: Or is this a different issue?", "commid": "nixpkgs_issue_81206", "tokennum": 494}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-d1ac0ba9fb9ccecc93a3cda49e5f6f20962f648615c735f7f90eb1fd6bb96d80", "query": "# luarocks only looks for rockspecs in the default/system tree instead of all # configured trees) luarocks_config = \"luarocks-config.lua\"; luarocks_content = '' luarocks_content = let extraVariablesStr = lib.concatStringsSep \"n \" (lib.mapAttrsToList (k: v: \"${k}='${v}';\") extraVariables); in '' local_cache = \"\" -- To prevent collisions when creating environments, we install the rock -- files into per-package subdirectories", "positive_passages": [{"docid": "doc-en-nixpkgs-e09767df0580761637b592fb601d32b1e74bbbe6be5426b230a286e2e7d01bcf", "text": "I think the root problem here is that luarocks has a poor implementation of \"move\". Combined with the build's behavior being affected by filesystem ordering the result is essentially random. The [implementation of move][] calls out to the operating system commands [][] and [][]. Building with will contain a sequence of , and . I've extracted the [relevant part of the log][]. The critical aspect here is that by default, unix will dereference symlinks and copy their contents. [implementation of move]: []: []: [relevant part of the log]: My theory: luarocks scans the directory for external libraries in filesystem order and attempts to move all shared libraries from to . At which point one of 3! things will happen, but the two main ones are: is copied and deleted and , now broken symlinks, fail to copy and are copied by dereferencing, and deleted is copied and deleted Either way is wrong to some degree, but one of them happens to work well enough for downstream packages to build. If I build locally, the filesystem order I get seems to work, so we can inspect the two results: I've been focusing on this for darwin since the failure case happens to be cached, but I believe it applies equally to linux.\nis that sthg you have already witnessed ?\nWhat LuaRocks version is this happening with? I have pushed fixes related to the file deployment stage in 3.3.1.\nI've tested 3.2.1 (current nixpkgs master) and 3.3.1 (hasty upgrade locally), they both have similar results, except on 3.3.1 the errors now propagate correctly. I've uploaded a [log of a failed build][] with 3.3.1. [log of a failed build]:\nI was hoping to find time to write a proper issue report and a test lua package for this, but haven't yet. My test case would have a directory structure made with , that looks like: In order to succeed the deployment stage would have to produce both the file and its symlink.", "commid": "nixpkgs_issue_81206", "tokennum": 462}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-d1ac0ba9fb9ccecc93a3cda49e5f6f20962f648615c735f7f90eb1fd6bb96d80", "query": "# luarocks only looks for rockspecs in the default/system tree instead of all # configured trees) luarocks_config = \"luarocks-config.lua\"; luarocks_content = '' luarocks_content = let extraVariablesStr = lib.concatStringsSep \"n \" (lib.mapAttrsToList (k: v: \"${k}='${v}';\") extraVariables); in '' local_cache = \"\" -- To prevent collisions when creating environments, we install the rock -- files into per-package subdirectories", "positive_passages": [{"docid": "doc-en-nixpkgs-1e4fcf1fb0aeb4c16221f034e0c294114b7fe3907c35f8218554cbb7771d9345", "text": "Describe the bug I have neovim in my systemPackages, I did and today and it stuck at building luajit: To Reproduce Steps to reproduce the behavior: to Expected behavior The system should upgrade properly. Additional context Output: Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(kj): nixpkgs: Maintainer information:\nPossible fix is in . There was already an open issue about it () but from an unclear reason people have reached the conclusion it was fixed on latest master.\nOh I meant , not .\nWell, I agree with that conclusion. For me, on the build is broken with the error above and on current master it isn't. EDIT: note that the channels lag behind, usually less than a couple days, but sometimes we get a week or two due to some harder regression.\nYea right. For me on NixOS I tried with the nixpkgs-unstable channel and could install successfully. The nixos-unstable still fails though.", "commid": "nixpkgs_issue_80704", "tokennum": 216}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-d1ad2586c8c0e2db07ca35351d036178d47d77f7373dd8b8c4324b412672378b", "query": "}; }; # Test OCSP Stapling specialisation.ocsp-stapling.configuration = { pkgs, ... }: { security.acme.certs.\"a.example.test\" = { ocspMustStaple = true; }; services.nginx.virtualHosts.\"a.example.com\" = { extraConfig = '' ssl_stapling on; ssl_stapling_verify on; ''; }; }; # Test using Apache HTTPD specialisation.httpd-aliases.configuration = { pkgs, config, lib, ... }: { services.nginx.enable = lib.mkForce false;", "positive_passages": [{"docid": "doc-en-nixpkgs-451a553fefb11d4deb83ca838f127929e126cb1973ab880b6d39513dad78038e", "text": "Describe the bug causes Lego to fail. To Reproduce Steps to reproduce the behavior: set on an enabled certificate. to this configuration. fail. Lego complains about an unrecognized (really misplaced) flag. Expected behavior The certificate will be successfully fetched, with Must-Staple enabled. Screenshots Additional context I think the problematic code is here: should not be in commonOpts, it should instead be in runOpts and renewOpts. Lego runs successfully when is to and . Notify maintainers (the acme team) Metadata Maintainer information:\nThanks for the report :) It appears that the --must-staple option is common to both \"run\" and \"renew\" modes, but is not actually a common option that can be specified before the mode. I'll get a PR ready for this.", "commid": "nixpkgs_issue_99584", "tokennum": 172}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-d1c1d19e52a05cd74ecda7b536f1dc1e713f768692a088b1403b1d3f09bc1035", "query": "\"test_album_from_string\" \"test_album_from_url\" \"test_album_length\" \"test_artist_from_url\" \"test_artist_from_string\" \"test_artist_from_url\" \"test_convert\" \"test_download_ffmpeg\" \"test_download_song\"", "positive_passages": [{"docid": "doc-en-nixpkgs-bf6324256752d407120d4555ef16bb5437e3f9b9e95de0aac3df18cb9f61dce3", "text": "Failure happens locally as well when trying to build spotdl on the nixos-23.05 branch. this the tail of the log: The last line is apparently unrelated: (maintainer) (recent bumps)\nThis test doesn't fail if spotdl is built using version from this nixpkgs commit , I'm not sure if this is an upstream issue with spotdl while using newer yt-dlp versions (newer than ).", "commid": "nixpkgs_issue_239733", "tokennum": 92}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-d1c9b8cbaf54a8ec8c076a1c5c1e598d175b3dd5d557ec119aa0ffd4f84217bf", "query": ", awscli }: python3.pkgs.buildPythonApplication rec { pname = \"awscli\"; version = \"1.32.101\"; # N.B: if you change this, change botocore and boto3 to a matching version too pyproject = true; let botocoreVersion = python3.pkgs.botocore.version; # awscli.version should be pinned to 2 minor versions less than the botocoreVersion versionMinor = toString (lib.toInt (lib.versions.minor botocoreVersion) - 2); versionPatch = lib.versions.patch botocoreVersion; self = python3.pkgs.buildPythonApplication rec { pname = \"awscli\"; version = \"1.${versionMinor}.${versionPatch}\"; # N.B: if you change this, change botocore and boto3 to a matching version too pyproject = true; src = fetchPypi { inherit pname version; hash = \"sha256-M4KzuQ+srPfk85P5QeQfVMorSKWhmNhdX4AY0AeRDTQ=\"; }; src = fetchPypi { inherit pname version; hash = \"sha256-GPcXkl2H0XNaeqt2/qD5+KvW23dRB0X+zLWo9hLigQM=\"; }; nativeBuildInputs = [ python3.pkgs.pythonRelaxDepsHook ]; nativeBuildInputs = [ python3.pkgs.pythonRelaxDepsHook ]; pythonRelaxDeps = [ \"botocore\" \"colorama\" \"docutils\" \"rsa\" ]; pythonRelaxDeps = [ # botocore must not be relaxed \"colorama\" \"docutils\" \"rsa\" ]; build-system = [ python3.pkgs.setuptools ]; build-system = [ python3.pkgs.setuptools ]; propagatedBuildInputs = with python3.pkgs; [ botocore s3transfer colorama docutils rsa pyyaml groff less ]; propagatedBuildInputs = with python3.pkgs; [ botocore s3transfer colorama docutils rsa pyyaml groff less ]; postInstall = '' mkdir -p $out/share/bash-completion/completions echo \"complete -C $out/bin/aws_completer aws\" > $out/share/bash-completion/completions/awscli postInstall = '' mkdir -p $out/share/bash-completion/completions echo \"complete -C $out/bin/aws_completer aws\" > $out/share/bash-completion/completions/awscli mkdir -p $out/share/zsh/site-functions mv $out/bin/aws_zsh_completer.sh $out/share/zsh/site-functions mkdir -p $out/share/zsh/site-functions mv $out/bin/aws_zsh_completer.sh $out/share/zsh/site-functions rm $out/bin/aws.cmd ''; rm $out/bin/aws.cmd ''; doInstallCheck = true; doInstallCheck = true; installCheckPhase = '' runHook preInstallCheck installCheckPhase = '' runHook preInstallCheck $out/bin/aws --version | grep \"${python3.pkgs.botocore.version}\" $out/bin/aws --version | grep \"${version}\" $out/bin/aws --version | grep \"${botocoreVersion}\" $out/bin/aws --version | grep \"${version}\" runHook postInstallCheck ''; runHook postInstallCheck ''; passthru = { python = python3; # for aws_shell updateScript = nix-update-script { # Excludes 1.x versions from the Github tags list extraArgs = [ \"--version-regex\" \"^(1.(.*))\" ]; }; tests.version = testers.testVersion { package = awscli; command = \"aws --version\"; inherit version; passthru = { python = python3; # for aws_shell updateScript = nix-update-script { extraArgs = [ \"--version=skip\" ]; }; tests.version = testers.testVersion { package = awscli; command = \"aws --version\"; inherit version; }; }; }; meta = with lib; { homepage = \"https://aws.amazon.com/cli/\"; changelog = \"https://github.com/aws/aws-cli/blob/${version}/CHANGELOG.rst\"; description = \"Unified tool to manage your AWS services\"; license = licenses.asl20; mainProgram = \"aws\"; maintainers = with maintainers; [ anthonyroussel ]; meta = with lib; { homepage = \"https://aws.amazon.com/cli/\"; changelog = \"https://github.com/aws/aws-cli/blob/${version}/CHANGELOG.rst\"; description = \"Unified tool to manage your AWS services\"; license = licenses.asl20; mainProgram = \"aws\"; maintainers = with maintainers; [ anthonyroussel ]; }; }; } in assert self ? pythonRelaxDeps -> !(lib.elem \"botocore\" self.pythonRelaxDeps); self ", "positive_passages": [{"docid": "doc-en-nixpkgs-54dc46d8a328c1010c9261d6b22417859632fdc7bec7ec0cc2e66d819c3f13b2", "text": "The version of AWSCLI in master is 1.32.58. This version requires botocore==1.34.58, however the version of botocore in master is 1.34.87 AWSCli botocore pin: This started happening after changing my to Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nThis should be fixed by , which syncs botocore, awscli, and boto3.", "commid": "nixpkgs_issue_310105", "tokennum": 116}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-d206892e7ea550eb7aad86e42c6d1b113c78591bec9060558d57549681ee157d", "query": "* Full encryption, DHT, and PEX support ''; homepage = \"http://www.transmissionbt.com/\"; license = lib.licenses.gpl2; # parts are under MIT license = lib.licenses.gpl2Plus; # parts are under MIT maintainers = with lib.maintainers; [ astsmtl vcunat wizeman ]; platforms = lib.platforms.unix; };", "positive_passages": [{"docid": "doc-en-nixpkgs-cc4a548fd0cfb6b7e7765f5cac6a6e74e30eed2a7adedf6e5777e59c7adef35f", "text": "Project description Fragments is a modern, responsive and graphical Gnome bittorrent client Metadata homepage URL: source URL: license: gpl3 platforms: linux The new version of Fragments depends on libutp which hopefully gets merged soon. I've opened a pull request for it . for Fragments.\nWe have transmission and torrential. Maybe that's something for you.\nThat's true but Fragments is a really neat, easy and modern looking torrent client. It has an adaptive interface which would also work quite well on mobile devices, for example NixOS mobile :+1:", "commid": "nixpkgs_issue_132316", "tokennum": 120}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-d20dbb51a41802b42065103c8e4c1b3bbbee594bfeb156661ebb6acd91423099", "query": " { lib , stdenv , fetchurl , pkg-config , lua , readline , ncurses , lz4 , tbox , xmake-core-sv }: stdenv.mkDerivation rec { pname = \"xmake\"; version = \"2.7.9\"; src = fetchurl { url = \"https://github.com/xmake-io/xmake/releases/download/v${version}/xmake-v${version}.tar.gz\"; hash = \"sha256-m0LYY0gz9IhbBbiUKd1gBE3KmSMvYJYyC42Ff7M9Ku8=\"; }; nativeBuildInputs = [ pkg-config ]; buildInputs = [ lua lua.pkgs.cjson readline ncurses lz4 tbox xmake-core-sv ]; configureFlags = [ \"--external=y\" ]; meta = with lib; { description = \"A cross-platform build utility based on Lua\"; homepage = \"https://xmake.io\"; license = licenses.asl20; platforms = lua.meta.platforms; maintainers = with maintainers; [ rewine ]; }; } ", "positive_passages": [{"docid": "doc-en-nixpkgs-74483d13e38d234ec30379799b7bb9778dc75bdffa75aaeee5d033fa45ac8604", "text": "Project description A lightweight cross-platform build utility based on Lua Metadata homepage URL: source URL: license: asl20 platforms: unix", "commid": "nixpkgs_issue_212231", "tokennum": 31}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-d21f846c53a3bbf3e7b59d60ff9541c322684e80d0f19c8635ee6000294d3841", "query": "are used internally to configure an HTTP server using PHP-FPM and nginx. The config attribute set is used for the config.php which is used for the application's configuration. Beware: this isn't entirely pure since the config is modified by the application's runtime! used by the imperative installer and all values are written to an additional file to ensure that changes can be applied by changing the module's options. In case the application serves multiple hosts (those are checked with In case the application serves multiple domains (those are checked with $_SERVER['HTTP_HOST']) those can be added using it's needed to add them to services.nextcloud.config.extraTrustedDomains. Auto updates for Nextcloud apps can be enabled using services.nextcloud.autoUpdateApps. Pitfalls", "positive_passages": [{"docid": "doc-en-nixpkgs-92b14e6173137c0a37b55493ebed2edffc15393ffbe0c79634a221cfd529baf3", "text": "Data that was once config and recorded on doesn't get updated when the configuration changes. This is a violation of purity. And more than that, it's very surprising when trying to install, hesitating between pgsql and sqlite, and struggling before understanding that the configuration doesn't get used anyway :p cc\nthat's a bit tough. We have a unit, that's supposed to do the installation. We use the command to install nextcloud (passing the configured database and adminpass settings as command parameters). This CLI generates , and installs nextcloud. The script checks the presence of , and skips installation on following starts. If you now change configuration from the module, we won't run the install command again, as the config file already exists, and assumes nextcloud is already installed.\nHmm\u2026 Maybe it would be possible to generate the somewhere in the store, and symlink to it? This way the next time runs it can in addition check whether points to the correct store path. Now, I don't really know what exactly does, so maybe it's not actually possible to do this because eg. one would need to re-run on certain configuration changes? In which case it'd be hard :/ but at least we can maybe make fail or something like that, so that the issue is at least noisy?\nI don't recommend to do this, I just tried that (after upgrading one of my personal systems) and this tries to recreate a database schema which can end in very bad results. Unfortunately I doubt that this will work properly, nextcloud wants to merge this during the runtime. E.g. it adds a after a successful or adds trusted domains when running the corresponding command. I'm using this as well now and hitting these issues, unfortunately I don't have useful ideas either ATM, but I'm happy to discuss better solutions :)\nNextcloud edits it's in a lot of different places, so having it generated through Nix currently isn't possible. digs into that already, I a comments about our use case here too.\nto avoid other people running into the reconfiguration issue for now, what about documenting that, maybe in ?\nThat's certainly a good thing to do.", "commid": "nixpkgs_issue_49783", "tokennum": 484}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-d21f846c53a3bbf3e7b59d60ff9541c322684e80d0f19c8635ee6000294d3841", "query": "are used internally to configure an HTTP server using PHP-FPM and nginx. The config attribute set is used for the config.php which is used for the application's configuration. Beware: this isn't entirely pure since the config is modified by the application's runtime! used by the imperative installer and all values are written to an additional file to ensure that changes can be applied by changing the module's options. In case the application serves multiple hosts (those are checked with In case the application serves multiple domains (those are checked with $_SERVER['HTTP_HOST']) those can be added using it's needed to add them to services.nextcloud.config.extraTrustedDomains. Auto updates for Nextcloud apps can be enabled using services.nextcloud.autoUpdateApps. Pitfalls", "positive_passages": [{"docid": "doc-en-nixpkgs-c4e56eafb4795d6fe067848a15c32dddf2be7d2dfa8a8db4e6140162b43d60cc", "text": "If nobody else wants to take over, I'd volunteer to do this during the next week as investing time on improving the nextcloud module is one item on my todo list :) I was aware of being stateful, but thanks a lot for linking the corresponding ticket! I'll have a look at this as soon as I have sufficient time to :)\nIn the light of this issue, what's the correct way to upgrade nextcloud to a new major version? Do I just pull a newer , upgrade my system and hope that the systemd job will do the right thing?\nThe service runs an that should apply all changes like database migrations needed for the new Nextcloud version (beware, downgrades aren't possible). As long as you let Nextcloud do its job, you shouldn't get that much issues. IMHO the actual problem here is the configuration of the software within Nix(OS).\njust a simple question (could not come to a conclusion after the lengthy thread) but I recently updated my nextcloud via nixops deploy and the update disabled the calendar module. Did I mess up or is that expected ? any way to configure this from nix ?\nAssuming that you installed the calendar module via the UI, it is installed in . The beginning of my config reads: So in principle nextcloud can edit the apps installed via the web interface (otherwise you couldn't install them via the interface in the first place).\nI don't think there's anything actionable here - the nextcloud nixos module is limited by how Nextcloud (imperatively) manages its configuration. The current state is properly documented in , and we raised our concerns to upstream in - closing this issue, feel free to reopen if there's more to be done.\nI think one actionable item would be to have the nextcloud service fail with an explicit error if the configuration being used is not compatible with the configuration defined in the .nix. At least the user would be warned in practice that configuration is not really applied, and not only by the manual that they are relatively unlikely to actually read. Reopening for now, feel free to reclose if you think that's not a reasonable \u201csolution\u201d :)\nThe problem is we don't know whether the configuration on disk containing database connection information () differs from the one that would be generated through an installation via - we don't render the configuration on our own, but the installer writes it out as a side-effect.", "commid": "nixpkgs_issue_49783", "tokennum": 528}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-d21f846c53a3bbf3e7b59d60ff9541c322684e80d0f19c8635ee6000294d3841", "query": "are used internally to configure an HTTP server using PHP-FPM and nginx. The config attribute set is used for the config.php which is used for the application's configuration. Beware: this isn't entirely pure since the config is modified by the application's runtime! used by the imperative installer and all values are written to an additional file to ensure that changes can be applied by changing the module's options. In case the application serves multiple hosts (those are checked with In case the application serves multiple domains (those are checked with $_SERVER['HTTP_HOST']) those can be added using it's needed to add them to services.nextcloud.config.extraTrustedDomains. Auto updates for Nextcloud apps can be enabled using services.nextcloud.autoUpdateApps. Pitfalls", "positive_passages": [{"docid": "doc-en-nixpkgs-e4cf0a48ca0407b14e74a8a4d6172973ee0007ab7182b6a4f2414eba4f2b1982", "text": "If I'm not missing something obvious, checking configuration changes would translate to parsing/evaluating on every nextcloud startup as an , comparing every \"interesting\" key with the one provided through nixos configuration, and eventually then bailing out if they differ. I'm not sure if that's a road we'd like to go and keep up to date, while the underlying bug is a missing distinction between configuration and state upstream\u2026\nSince upstream mixes state and config it's questionable whether their configuration format is somehow supposed to be backwards-compatible (as it's only supposed to be used internally by Nextcloud). Hence I'm afraid that this will make i.e. upgrades even harder in case of configuration changes, so :-1: from me. As the issues are documented in the manual now, folks are warned and I think that this is a better option in contrast to adding more complexity to . I suggest we either close this for the reasons already stated or wait for an appropriate upstream fix.\nI really don't feel good having stuff in that's actually a disguised command line\u2026 :/ Something that would sound nicer to me would be an executable that the user would have to manually run, and a bare-bones module that does not handle setup or configuration and just makes sure that the systemd unit is setup. At least the error is obvious (enabling the module without having run the executable would fail), all module options actually mean something, and the impure operation is made explicit. Either that or, similar to , rename all the options so it's explicit that they're used only for initial configuration. Would one of these solutions make sense to you?\nMe neither, but currently we don't have much choice\u2026 I really like the fact that we can set up the Nextcloud instance in an unattended fashion, without having to worry about manual setting things up. I really don't want to end with more imperative setup steps than necessary. In theory, we could move some of the options in to to make it more obvious what isn't applied continuously. But TBH, I'd rather like to see the state/config mixing fixed upstream than having to introduce more mental complexity here, especially if this gets fixed and we end up with both incarnations. Really, this issue only occurs while a user changes nextcloud database parameters (mostly while tweaking his initial setup), and not having read the module documentation, where the behaviour is documented.", "commid": "nixpkgs_issue_49783", "tokennum": 521}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-d21f846c53a3bbf3e7b59d60ff9541c322684e80d0f19c8635ee6000294d3841", "query": "are used internally to configure an HTTP server using PHP-FPM and nginx. The config attribute set is used for the config.php which is used for the application's configuration. Beware: this isn't entirely pure since the config is modified by the application's runtime! used by the imperative installer and all values are written to an additional file to ensure that changes can be applied by changing the module's options. In case the application serves multiple hosts (those are checked with In case the application serves multiple domains (those are checked with $_SERVER['HTTP_HOST']) those can be added using it's needed to add them to services.nextcloud.config.extraTrustedDomains. Auto updates for Nextcloud apps can be enabled using services.nextcloud.autoUpdateApps. Pitfalls", "positive_passages": [{"docid": "doc-en-nixpkgs-c18de52bf5cfd2a2f4ec3e5fa95428d955562611c8e8ba19985e2786aaf847a4", "text": "What about adding the following (subtile) log statement, to point users to the docs when they peek into the logs while things are not working as expected?\nI agree that the log statement is the minimum we can do, and would at least give a hint about the way in which things are broken. Now, I guess the reason we're kind of disagreeing on the path forward is that you're much more hopeful than me that nextcloud will ever fix its stuff -- I'm assuming it'll get fixed in years at best (and even then\u2026) -- and if it's in years then I'd much rather live with for years then spend a year deprecating it by making it conflict with new options than try to live with from now on and have users fail to understand what is going on. Now urhm, I'm investigating the module a bit deeper, and\u2026 is there any reason we can't put the database configuration etc. in ? We could then refresh on each activation, and it should be enough? If we have a way to couple it with something that automatically runs iff the database is not ready yet then the setup would actually be\u2026 almost perfect?\nAfter having a deeper look at the sources ( at github, (6 commits ahead of v16.0.0RC1)) I guess that this should be possible (I didn't test it yet though). Configs will be loaded from using PHP's function[1] while all files ending with will be taken into account. Hence works as all config arrays will be merged together. This config will be loaded at [2] and is available as which is then used in the DI container[3]. If I understand the code correctly, I assume that it should be possible to render all config options in as config files found by glob will override values from [4]. [4]\nNice catch! This might indeed be possible - we should make very sure that config overrides work the way we think they will - seems to write the merged configuration, and not just the overrides (and merging this with other config in the wrong order can lead to wonderfully weird to debug issues) ;-) While I'd still prefer nextcloud splitting config and state properly, and being able to cope with read-only (base) config - it might be a direction worth exploring. What do you think?", "commid": "nixpkgs_issue_49783", "tokennum": 524}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-d21f846c53a3bbf3e7b59d60ff9541c322684e80d0f19c8635ee6000294d3841", "query": "are used internally to configure an HTTP server using PHP-FPM and nginx. The config attribute set is used for the config.php which is used for the application's configuration. Beware: this isn't entirely pure since the config is modified by the application's runtime! used by the imperative installer and all values are written to an additional file to ensure that changes can be applied by changing the module's options. In case the application serves multiple hosts (those are checked with In case the application serves multiple domains (those are checked with $_SERVER['HTTP_HOST']) those can be added using it's needed to add them to services.nextcloud.config.extraTrustedDomains. Auto updates for Nextcloud apps can be enabled using services.nextcloud.autoUpdateApps. Pitfalls", "positive_passages": [{"docid": "doc-en-nixpkgs-04af33963a42328dbf0c54ed988ae388dd41d8a53fa37fa4fce1f7fa5bd4d355", "text": "Well, for the record it was actually idea :sweat_smile: I guess so, all the stuff from is also in my at the moment. I'll probably have sufficient time next weekend to check if I can trigger such a case. I can't promise that, but unless anybody beats me, I can hopefully prepare a fix for this :)\nDid you gain some new insights on this?\nUnfortunately not... I was pretty busy back then. But as this only requires some fiddling in the module and no patching of the actual package, the change shouldn't be too painful, so if you'd like to take over... :sweat_smile:\nthere's with a fix now :)", "commid": "nixpkgs_issue_49783", "tokennum": 148}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-d2304b3fad600f4c98d93fa0651b42d9378dc0672c55c2ff3d3868ff7dcd46ad", "query": "libsoup gnome3.gnome-settings-daemon gnome3.nautilus gnome3.mutter gnome3.gnome-desktop gobjectIntrospection gnome3.nautilus # Makes it possible to select user themes through the `user-theme` extension gnome3.gnome-shell-extensions ]; postPatch = ''", "positive_passages": [{"docid": "doc-en-nixpkgs-acfb4e7feefdedf68da4361d4a01cd78f525067b5e91d9c69377e196d25df0ff", "text": "The meson build doesn't compile the schemas, opting to do it instead in a package shell script. Unfortunately it seems that compiling the schemas aren't enough to make all the extensions work. In particular at least and still won't work (seems to fix though). With the schemas installed Tweaks simply complains that the extension is incorrectly installed. complains about lacking any typelib file for . I'm not sure how well these extensions worked before 3.28, but a report on irc indicated that at least worked before. cc Run Tweaks on nixos-unstable, try to enable eg. the extension under or . Running a schema fix on top of system: host os: multi-user?: sandbox: version: channels(hed): channels(root): nixpkgs:\nThe extension works for me when I manually change the directory structure to: As for the , I removed from dependencies so that might explain this failure. The extension should probably be fixed like .\nYou're able to switch switch themes in in Tweaks? Might be something wrong on my end. I'll submit a PR fixing the schemas at least.\nTesting out a fix for .\nHmm, I can enable it but the theme switching does not work. I seems to require the extension schemas in when running Tweaks. Maybe it got picked up from global for bash users, but the option was always disabled for me with fish.\nWe might want to add as a dependency to Tweaks so that it could work for non-bash users. Then we will need to fix the schemas: the schemas in and find a hack similar to to add the schemas path to the extension. like the following to put the schemas where extensions can find them and add symlink for Tweaks. same thing as the second point but accomplished by patching files.\nYour suggested fix worked for at least :) I went with basically adding the code from to to fix the schema problem. Generating the directory structure you quoted above seems the most sane and keeping with upstream. Tested things out in a vm with bash, and didn't seem to work there either. So not sure if the problem is non bash. Anyway, adding to fixes , so I think that's appropriate. I should've got everything now, will submit a PR :)\nI think it only works in bash and globally installed packages or something.", "commid": "nixpkgs_issue_38377", "tokennum": 520}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-d2304b3fad600f4c98d93fa0651b42d9378dc0672c55c2ff3d3868ff7dcd46ad", "query": "libsoup gnome3.gnome-settings-daemon gnome3.nautilus gnome3.mutter gnome3.gnome-desktop gobjectIntrospection gnome3.nautilus # Makes it possible to select user themes through the `user-theme` extension gnome3.gnome-shell-extensions ]; postPatch = ''", "positive_passages": [{"docid": "doc-en-nixpkgs-b66ac587919c34b68d8e55f748fd939f288f4863add5c49462c8ba286d9db67d", "text": "I would not rely on it since I consider it an ugly impurity. I would prefer the first solution since it will be the cleanest and could be possibly automated in the future, but number two is fine too.", "commid": "nixpkgs_issue_38377", "tokennum": 44}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-d238150087e1437124025c89029bb30a07b276d8f8c39f8d2a9a42b0f84a8f51", "query": "EOF cat ${certdata2pem} > certdata2pem.py patch -p1 < ${./fix-unicode-ca-names.patch} ${optionalString includeEmail '' # Disable CAs used for mail signing substituteInPlace certdata2pem.py --replace ['CKA_TRUST_EMAIL_PROTECTION'] ''' ''} ''; buildPhase = ''", "positive_passages": [{"docid": "doc-en-nixpkgs-ff7b26f229ec22629feef5d8d699a8c2aea5ff26ba56eb87047b30f330d230f9", "text": "Describe the bug Putting a valid certificate name in will cause nixos-rebuild to fail. To Reproduce Steps to reproduce the behavior: this line in . This command will fail. Expected behavior finishes sucessfully. Additional context This error message is related to : I guess this error is caused by switching to python 3. Notify maintainers