{"query_id": "q-en-nixpkgs-2d32e27ece3b2564aa7527c9d0ede4c0cc9c646d3b77d997ebfa6469cb756e88", "query": "Describe the bug Open indicator and see the following in journal The error at the top comes from now depending on settings schema (provided by ibus). This situation is annoyingly complex, because we cannot wrap . So what we try to do is create a wrapper with all the transitive dependencies of the plugins and call it day. We used to do patches to hardcode the gsettings, but this was far to much work to maintain and could be prone to developer error sometimes. I'm thinking the easiest solution would be to add all the transitive dependencies of to , and then wingpanel's can pick up all the proper dependencies. I think the only ideal request I could make to Pantheon upstream is to make use of SearchProviders from GNOME I believe this basically should be the very thing they want. They currently have a forked version of synapse's plugins system which IMHO appears to be inferior. To Reproduce Steps to reproduce the behavior: wingpanel-with-indicators the switchboard-plugin process get killed Expected behavior The switchboard-plugin process doesn't die. Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:", "positive_passages": [{"docid": "doc-en-nixpkgs-ac8f601c8855002bcc8fe6ccbc6fa715bc060511f22c54eb12d0499ab6ffbed5", "text": "''; executable = writeScript \"pantheon\" '' export XDG_CONFIG_DIRS=${elementary-settings-daemon}/etc/xdg:${elementary-default-settings}/etc:$XDG_CONFIG_DIRS # gnome-session can find RequiredComponents for `pantheon` session (notably pantheon's patched g-s-d autostarts) export XDG_CONFIG_DIRS=@out@/etc/xdg:$XDG_CONFIG_DIRS # Make sure we use our gtk-3.0/settings.ini export XDG_CONFIG_DIRS=${elementary-default-settings}/etc:$XDG_CONFIG_DIRS # * gnome-session can find the `pantheon' session # * use pantheon-mimeapps.list export XDG_DATA_DIRS=@out@/share:$XDG_DATA_DIRS exec ${gnome-session}/bin/gnome-session --session=pantheon \"$@\" # Start pantheon session. Keep in sync with upstream exec ${gnome-session}/bin/gnome-session --builtin --session=pantheon \"$@\" ''; # Absolute path patched version of the upstream xsession xsession = writeText \"pantheon.desktop\" '' [Desktop Entry] Name=Pantheon Comment=This session provides elementary experience Exec=@out@/libexec/pantheon TryExec=${wingpanel}/bin/wingpanel Icon= DesktopNames=Pantheon Type=Application ''; in stdenv.mkDerivation rec { pname = \"elementary-session-settings-unstable\"; version = \"2020-06-11\"; version = \"2020-07-06\"; repoName = \"session-settings\"; src = fetchFromGitHub { owner = \"elementary\"; repo = repoName; rev = \"130c9ae221913032ed18bcf6d21e3dcdba3c4209\"; sha256 = \"0bzg9vbq0ssnxgcb2vxpx6x9zv8ngkm9r3ki5q83m9al9919n0pr\"; rev = \"fa15cbd83fba0ba30e9a302db880350bff5ace52\"; hash = \"sha256-26H791c7OAjFYtjVChIatICSocMt0uTej1TKBOvw+6w=\"; }; nativeBuildInputs = [", "commid": "nixpkgs_pr_100116"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-2d32e27ece3b2564aa7527c9d0ede4c0cc9c646d3b77d997ebfa6469cb756e88", "query": "Describe the bug Open indicator and see the following in journal The error at the top comes from now depending on settings schema (provided by ibus). This situation is annoyingly complex, because we cannot wrap . So what we try to do is create a wrapper with all the transitive dependencies of the plugins and call it day. We used to do patches to hardcode the gsettings, but this was far to much work to maintain and could be prone to developer error sometimes. I'm thinking the easiest solution would be to add all the transitive dependencies of to , and then wingpanel's can pick up all the proper dependencies. I think the only ideal request I could make to Pantheon upstream is to make use of SearchProviders from GNOME I believe this basically should be the very thing they want. They currently have a forked version of synapse's plugins system which IMHO appears to be inferior. To Reproduce Steps to reproduce the behavior: wingpanel-with-indicators the switchboard-plugin process get killed Expected behavior The switchboard-plugin process doesn't die. Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:", "positive_passages": [{"docid": "doc-en-nixpkgs-5ff16e87232898f16c5888496e82986016f2100b22de0d8252e7c6147feb8a45", "text": "]; postInstall = '' # our mimeapps patched from upstream to exclude: # * pantheon-mail -> geary # * evince.desktop -> org.gnome.Evince.desktop mkdir -p $out/share/applications cp -av ${./pantheon-mimeapps.list} $out/share/applications/pantheon-mimeapps.list # instantiates pantheon's dockitems cp \"${dockitemAutostart}\" $out/etc/xdg/autostart/default-elementary-dockitems.desktop # script `Exec` to start pantheon mkdir -p $out/libexec substitute ${executable} $out/libexec/pantheon --subst-var out chmod +x $out/libexec/pantheon ''; postFixup = '' substituteInPlace $out/share/xsessions/pantheon.desktop --replace \"gnome-session --session=pantheon\" \"$out/libexec/pantheon\" --replace \"wingpanel\" \"${wingpanel}/bin/wingpanel\" # absolute path patched xsession substitute ${xsession} $out/share/xsessions/pantheon.desktop --subst-var out ''; passthru = {", "commid": "nixpkgs_pr_100116"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-2d32e27ece3b2564aa7527c9d0ede4c0cc9c646d3b77d997ebfa6469cb756e88", "query": "Describe the bug Open indicator and see the following in journal The error at the top comes from now depending on settings schema (provided by ibus). This situation is annoyingly complex, because we cannot wrap . So what we try to do is create a wrapper with all the transitive dependencies of the plugins and call it day. We used to do patches to hardcode the gsettings, but this was far to much work to maintain and could be prone to developer error sometimes. I'm thinking the easiest solution would be to add all the transitive dependencies of to , and then wingpanel's can pick up all the proper dependencies. I think the only ideal request I could make to Pantheon upstream is to make use of SearchProviders from GNOME I believe this basically should be the very thing they want. They currently have a forked version of synapse's plugins system which IMHO appears to be inferior. To Reproduce Steps to reproduce the behavior: wingpanel-with-indicators the switchboard-plugin process get killed Expected behavior The switchboard-plugin process doesn't die. Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:", "positive_passages": [{"docid": "doc-en-nixpkgs-f9cc2e1b73b287fee9c1319d9c4a6a10f083cfbd7cafbc10e90e418c029bee44", "text": ", json-glib , elementary-dock , bamf , switchboard , switchboard-with-plugs , libunity , libsoup , wingpanel", "commid": "nixpkgs_pr_100116"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-2d32e27ece3b2564aa7527c9d0ede4c0cc9c646d3b77d997ebfa6469cb756e88", "query": "Describe the bug Open indicator and see the following in journal The error at the top comes from now depending on settings schema (provided by ibus). This situation is annoyingly complex, because we cannot wrap . So what we try to do is create a wrapper with all the transitive dependencies of the plugins and call it day. We used to do patches to hardcode the gsettings, but this was far to much work to maintain and could be prone to developer error sometimes. I'm thinking the easiest solution would be to add all the transitive dependencies of to , and then wingpanel's can pick up all the proper dependencies. I think the only ideal request I could make to Pantheon upstream is to make use of SearchProviders from GNOME I believe this basically should be the very thing they want. They currently have a forked version of synapse's plugins system which IMHO appears to be inferior. To Reproduce Steps to reproduce the behavior: wingpanel-with-indicators the switchboard-plugin process get killed Expected behavior The switchboard-plugin process doesn't die. Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:", "positive_passages": [{"docid": "doc-en-nixpkgs-82d44155d4689fb77fe42800ed102c8d43cdaec507436c5e295553ae56b78d7e", "text": "pkgconfig python3 vala ]; ]; buildInputs = [ bamf", "commid": "nixpkgs_pr_100116"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-2d32e27ece3b2564aa7527c9d0ede4c0cc9c646d3b77d997ebfa6469cb756e88", "query": "Describe the bug Open indicator and see the following in journal The error at the top comes from now depending on settings schema (provided by ibus). This situation is annoyingly complex, because we cannot wrap . So what we try to do is create a wrapper with all the transitive dependencies of the plugins and call it day. We used to do patches to hardcode the gsettings, but this was far to much work to maintain and could be prone to developer error sometimes. I'm thinking the easiest solution would be to add all the transitive dependencies of to , and then wingpanel's can pick up all the proper dependencies. I think the only ideal request I could make to Pantheon upstream is to make use of SearchProviders from GNOME I believe this basically should be the very thing they want. They currently have a forked version of synapse's plugins system which IMHO appears to be inferior. To Reproduce Steps to reproduce the behavior: wingpanel-with-indicators the switchboard-plugin process get killed Expected behavior The switchboard-plugin process doesn't die. Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:", "positive_passages": [{"docid": "doc-en-nixpkgs-655df2f60667a7cf59c17179b6ef34ed9e0bb47409c6a9362755ebe0aec3e336", "text": "libhandy libsoup libunity switchboard switchboard-with-plugs wingpanel zeitgeist ]; ] ++ # applications-menu has a plugin to search switchboard plugins # see https://github.com/NixOS/nixpkgs/issues/100209 # wingpanel's wrapper will need to pick up the fact that # applications-menu needs a version of switchboard with all # its plugins for search. switchboard-with-plugs.buildInputs; mesonFlags = [ \"--sysconfdir=${placeholder \"out\"}/etc\"", "commid": "nixpkgs_pr_100116"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-2d32e27ece3b2564aa7527c9d0ede4c0cc9c646d3b77d997ebfa6469cb756e88", "query": "Describe the bug Open indicator and see the following in journal The error at the top comes from now depending on settings schema (provided by ibus). This situation is annoyingly complex, because we cannot wrap . So what we try to do is create a wrapper with all the transitive dependencies of the plugins and call it day. We used to do patches to hardcode the gsettings, but this was far to much work to maintain and could be prone to developer error sometimes. I'm thinking the easiest solution would be to add all the transitive dependencies of to , and then wingpanel's can pick up all the proper dependencies. I think the only ideal request I could make to Pantheon upstream is to make use of SearchProviders from GNOME I believe this basically should be the very thing they want. They currently have a forked version of synapse's plugins system which IMHO appears to be inferior. To Reproduce Steps to reproduce the behavior: wingpanel-with-indicators the switchboard-plugin process get killed Expected behavior The switchboard-plugin process doesn't die. Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:", "positive_passages": [{"docid": "doc-en-nixpkgs-4903952818a91f5b8417b6c5a7342308c4facc7747f72fd9eeda87689d592168", "text": "''; postFixup = '' for autostart in $(grep -rl \"OnlyShowIn=GNOME;\" $out/etc/xdg/autostart) do echo \"Patching OnlyShowIn to Pantheon in: $autostart\" sed -i \"s,OnlyShowIn=GNOME;,OnlyShowIn=Pantheon;,\" $autostart done # This breaks lightlocker https://github.com/elementary/session-settings/commit/b0e7a2867608c3a3916f9e4e21a68264a20e44f8 # TODO: shouldn't be neeed for the 5.1 greeter (awaiting release) rm $out/etc/xdg/autostart/org.gnome.SettingsDaemon.ScreensaverProxy.desktop # So the polkit policy can reference /run/current-system/sw/bin/elementary-settings-daemon/gsd-backlight-helper mkdir -p $out/bin/elementary-settings-daemon ln -s $out/libexec/gsd-backlight-helper $out/bin/elementary-settings-daemon/gsd-backlight-helper", "commid": "nixpkgs_pr_100116"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-2d32e27ece3b2564aa7527c9d0ede4c0cc9c646d3b77d997ebfa6469cb756e88", "query": "Describe the bug Open indicator and see the following in journal The error at the top comes from now depending on settings schema (provided by ibus). This situation is annoyingly complex, because we cannot wrap . So what we try to do is create a wrapper with all the transitive dependencies of the plugins and call it day. We used to do patches to hardcode the gsettings, but this was far to much work to maintain and could be prone to developer error sometimes. I'm thinking the easiest solution would be to add all the transitive dependencies of to , and then wingpanel's can pick up all the proper dependencies. I think the only ideal request I could make to Pantheon upstream is to make use of SearchProviders from GNOME I believe this basically should be the very thing they want. They currently have a forked version of synapse's plugins system which IMHO appears to be inferior. To Reproduce Steps to reproduce the behavior: wingpanel-with-indicators the switchboard-plugin process get killed Expected behavior The switchboard-plugin process doesn't die. Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:", "positive_passages": [{"docid": "doc-en-nixpkgs-ac8f601c8855002bcc8fe6ccbc6fa715bc060511f22c54eb12d0499ab6ffbed5", "text": "''; executable = writeScript \"pantheon\" '' export XDG_CONFIG_DIRS=${elementary-settings-daemon}/etc/xdg:${elementary-default-settings}/etc:$XDG_CONFIG_DIRS # gnome-session can find RequiredComponents for `pantheon` session (notably pantheon's patched g-s-d autostarts) export XDG_CONFIG_DIRS=@out@/etc/xdg:$XDG_CONFIG_DIRS # Make sure we use our gtk-3.0/settings.ini export XDG_CONFIG_DIRS=${elementary-default-settings}/etc:$XDG_CONFIG_DIRS # * gnome-session can find the `pantheon' session # * use pantheon-mimeapps.list export XDG_DATA_DIRS=@out@/share:$XDG_DATA_DIRS exec ${gnome-session}/bin/gnome-session --session=pantheon \"$@\" # Start pantheon session. Keep in sync with upstream exec ${gnome-session}/bin/gnome-session --builtin --session=pantheon \"$@\" ''; # Absolute path patched version of the upstream xsession xsession = writeText \"pantheon.desktop\" '' [Desktop Entry] Name=Pantheon Comment=This session provides elementary experience Exec=@out@/libexec/pantheon TryExec=${wingpanel}/bin/wingpanel Icon= DesktopNames=Pantheon Type=Application ''; in stdenv.mkDerivation rec { pname = \"elementary-session-settings-unstable\"; version = \"2020-06-11\"; version = \"2020-07-06\"; repoName = \"session-settings\"; src = fetchFromGitHub { owner = \"elementary\"; repo = repoName; rev = \"130c9ae221913032ed18bcf6d21e3dcdba3c4209\"; sha256 = \"0bzg9vbq0ssnxgcb2vxpx6x9zv8ngkm9r3ki5q83m9al9919n0pr\"; rev = \"fa15cbd83fba0ba30e9a302db880350bff5ace52\"; hash = \"sha256-26H791c7OAjFYtjVChIatICSocMt0uTej1TKBOvw+6w=\"; }; nativeBuildInputs = [", "commid": "nixpkgs_pr_100224"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-2d32e27ece3b2564aa7527c9d0ede4c0cc9c646d3b77d997ebfa6469cb756e88", "query": "Describe the bug Open indicator and see the following in journal The error at the top comes from now depending on settings schema (provided by ibus). This situation is annoyingly complex, because we cannot wrap . So what we try to do is create a wrapper with all the transitive dependencies of the plugins and call it day. We used to do patches to hardcode the gsettings, but this was far to much work to maintain and could be prone to developer error sometimes. I'm thinking the easiest solution would be to add all the transitive dependencies of to , and then wingpanel's can pick up all the proper dependencies. I think the only ideal request I could make to Pantheon upstream is to make use of SearchProviders from GNOME I believe this basically should be the very thing they want. They currently have a forked version of synapse's plugins system which IMHO appears to be inferior. To Reproduce Steps to reproduce the behavior: wingpanel-with-indicators the switchboard-plugin process get killed Expected behavior The switchboard-plugin process doesn't die. Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:", "positive_passages": [{"docid": "doc-en-nixpkgs-5ff16e87232898f16c5888496e82986016f2100b22de0d8252e7c6147feb8a45", "text": "]; postInstall = '' # our mimeapps patched from upstream to exclude: # * pantheon-mail -> geary # * evince.desktop -> org.gnome.Evince.desktop mkdir -p $out/share/applications cp -av ${./pantheon-mimeapps.list} $out/share/applications/pantheon-mimeapps.list # instantiates pantheon's dockitems cp \"${dockitemAutostart}\" $out/etc/xdg/autostart/default-elementary-dockitems.desktop # script `Exec` to start pantheon mkdir -p $out/libexec substitute ${executable} $out/libexec/pantheon --subst-var out chmod +x $out/libexec/pantheon ''; postFixup = '' substituteInPlace $out/share/xsessions/pantheon.desktop --replace \"gnome-session --session=pantheon\" \"$out/libexec/pantheon\" --replace \"wingpanel\" \"${wingpanel}/bin/wingpanel\" # absolute path patched xsession substitute ${xsession} $out/share/xsessions/pantheon.desktop --subst-var out ''; passthru = {", "commid": "nixpkgs_pr_100224"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-2d32e27ece3b2564aa7527c9d0ede4c0cc9c646d3b77d997ebfa6469cb756e88", "query": "Describe the bug Open indicator and see the following in journal The error at the top comes from now depending on settings schema (provided by ibus). This situation is annoyingly complex, because we cannot wrap . So what we try to do is create a wrapper with all the transitive dependencies of the plugins and call it day. We used to do patches to hardcode the gsettings, but this was far to much work to maintain and could be prone to developer error sometimes. I'm thinking the easiest solution would be to add all the transitive dependencies of to , and then wingpanel's can pick up all the proper dependencies. I think the only ideal request I could make to Pantheon upstream is to make use of SearchProviders from GNOME I believe this basically should be the very thing they want. They currently have a forked version of synapse's plugins system which IMHO appears to be inferior. To Reproduce Steps to reproduce the behavior: wingpanel-with-indicators the switchboard-plugin process get killed Expected behavior The switchboard-plugin process doesn't die. Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:", "positive_passages": [{"docid": "doc-en-nixpkgs-f9cc2e1b73b287fee9c1319d9c4a6a10f083cfbd7cafbc10e90e418c029bee44", "text": ", json-glib , elementary-dock , bamf , switchboard , switchboard-with-plugs , libunity , libsoup , wingpanel", "commid": "nixpkgs_pr_100224"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-2d32e27ece3b2564aa7527c9d0ede4c0cc9c646d3b77d997ebfa6469cb756e88", "query": "Describe the bug Open indicator and see the following in journal The error at the top comes from now depending on settings schema (provided by ibus). This situation is annoyingly complex, because we cannot wrap . So what we try to do is create a wrapper with all the transitive dependencies of the plugins and call it day. We used to do patches to hardcode the gsettings, but this was far to much work to maintain and could be prone to developer error sometimes. I'm thinking the easiest solution would be to add all the transitive dependencies of to , and then wingpanel's can pick up all the proper dependencies. I think the only ideal request I could make to Pantheon upstream is to make use of SearchProviders from GNOME I believe this basically should be the very thing they want. They currently have a forked version of synapse's plugins system which IMHO appears to be inferior. To Reproduce Steps to reproduce the behavior: wingpanel-with-indicators the switchboard-plugin process get killed Expected behavior The switchboard-plugin process doesn't die. Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:", "positive_passages": [{"docid": "doc-en-nixpkgs-82d44155d4689fb77fe42800ed102c8d43cdaec507436c5e295553ae56b78d7e", "text": "pkgconfig python3 vala ]; ]; buildInputs = [ bamf", "commid": "nixpkgs_pr_100224"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-2d32e27ece3b2564aa7527c9d0ede4c0cc9c646d3b77d997ebfa6469cb756e88", "query": "Describe the bug Open indicator and see the following in journal The error at the top comes from now depending on settings schema (provided by ibus). This situation is annoyingly complex, because we cannot wrap . So what we try to do is create a wrapper with all the transitive dependencies of the plugins and call it day. We used to do patches to hardcode the gsettings, but this was far to much work to maintain and could be prone to developer error sometimes. I'm thinking the easiest solution would be to add all the transitive dependencies of to , and then wingpanel's can pick up all the proper dependencies. I think the only ideal request I could make to Pantheon upstream is to make use of SearchProviders from GNOME I believe this basically should be the very thing they want. They currently have a forked version of synapse's plugins system which IMHO appears to be inferior. To Reproduce Steps to reproduce the behavior: wingpanel-with-indicators the switchboard-plugin process get killed Expected behavior The switchboard-plugin process doesn't die. Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:", "positive_passages": [{"docid": "doc-en-nixpkgs-655df2f60667a7cf59c17179b6ef34ed9e0bb47409c6a9362755ebe0aec3e336", "text": "libhandy libsoup libunity switchboard switchboard-with-plugs wingpanel zeitgeist ]; ] ++ # applications-menu has a plugin to search switchboard plugins # see https://github.com/NixOS/nixpkgs/issues/100209 # wingpanel's wrapper will need to pick up the fact that # applications-menu needs a version of switchboard with all # its plugins for search. switchboard-with-plugs.buildInputs; mesonFlags = [ \"--sysconfdir=${placeholder \"out\"}/etc\"", "commid": "nixpkgs_pr_100224"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-2d32e27ece3b2564aa7527c9d0ede4c0cc9c646d3b77d997ebfa6469cb756e88", "query": "Describe the bug Open indicator and see the following in journal The error at the top comes from now depending on settings schema (provided by ibus). This situation is annoyingly complex, because we cannot wrap . So what we try to do is create a wrapper with all the transitive dependencies of the plugins and call it day. We used to do patches to hardcode the gsettings, but this was far to much work to maintain and could be prone to developer error sometimes. I'm thinking the easiest solution would be to add all the transitive dependencies of to , and then wingpanel's can pick up all the proper dependencies. I think the only ideal request I could make to Pantheon upstream is to make use of SearchProviders from GNOME I believe this basically should be the very thing they want. They currently have a forked version of synapse's plugins system which IMHO appears to be inferior. To Reproduce Steps to reproduce the behavior: wingpanel-with-indicators the switchboard-plugin process get killed Expected behavior The switchboard-plugin process doesn't die. Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:", "positive_passages": [{"docid": "doc-en-nixpkgs-4903952818a91f5b8417b6c5a7342308c4facc7747f72fd9eeda87689d592168", "text": "''; postFixup = '' for autostart in $(grep -rl \"OnlyShowIn=GNOME;\" $out/etc/xdg/autostart) do echo \"Patching OnlyShowIn to Pantheon in: $autostart\" sed -i \"s,OnlyShowIn=GNOME;,OnlyShowIn=Pantheon;,\" $autostart done # This breaks lightlocker https://github.com/elementary/session-settings/commit/b0e7a2867608c3a3916f9e4e21a68264a20e44f8 # TODO: shouldn't be neeed for the 5.1 greeter (awaiting release) rm $out/etc/xdg/autostart/org.gnome.SettingsDaemon.ScreensaverProxy.desktop # So the polkit policy can reference /run/current-system/sw/bin/elementary-settings-daemon/gsd-backlight-helper mkdir -p $out/bin/elementary-settings-daemon ln -s $out/libexec/gsd-backlight-helper $out/bin/elementary-settings-daemon/gsd-backlight-helper", "commid": "nixpkgs_pr_100224"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-8cdce653c42a871c4a6c41d51353d7b9b46f577216a03e4a0bb4ea8e4297091e", "query": "Describe the bug Installing the latest SBT is not possible. To Reproduce Expected behavior Install is successful Notify maintainers ", "commid": "nixpkgs_pr_18798"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-2f461e8b78cd53278ce8593c9cd1891910ae3f17b6c0103a8b3ae494ed769416", "query": "Right now, we have sections covering Perl, Python, Ruby, Go, and more. is another popular language and we have an easy/automated way to add new packages to nixpkgs. We should make this easier for people who don't already know how! I plan on tackling this based on instructions I received over at\ncc\nSome of the entries in the document have a comment like Should I enhance the in and then generate the XML file? Can anyone clue me in to how they're generated?\nThey are generated in (using pandoc).\nOnce I've it to , how can I actually generate the XML?\nThe XML is generated during the build. To have it in the manual you need to include it with in . The confusing part is that refers some files that exists only at build-time (the files generated by ). It is also possible to keep the build directory with to inspect the generated files.", "positive_passages": [{"docid": "doc-en-nixpkgs-0b3c2d76ebe906ff7c5ebc3c88d42c811e76f2e6e3b5e81a31cacdf4fc405e30", "text": " NPM packages =========== Node.js packages =============== To add a package from [NPM](https://www.npmjs.com/) to nixpkgs: 1. Install node2nix: `nix-env -f '' -iA node2nix`. 2. Modify `pkgs/development/node-packages/node-packages.json`, to add, update, or remove package entries.", "commid": "nixpkgs_pr_18798"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-7d23bca2afabe244e001ea1f5ff411bdf8a2bece327125c5e4df1a0119e16fcc", "query": "glslc binary in shaderc has invalid signature Steps to reproduce the behavior: to compile shader on aarch64-darwin to SPIR-V should not be killed", "positive_passages": [{"docid": "doc-en-nixpkgs-9e05da579d570893104efcea89ddcc3f369860c95b1aca15c7dff86a65ecd7b6", "text": " { lib, stdenv, fetchFromGitHub, cmake, darwin, python3 }: { lib, stdenv, fetchFromGitHub, cmake, python3, autoSignDarwinBinariesHook, cctools }: # Like many google projects, shaderc doesn't gracefully support separately compiled dependencies, so we can't easily use # the versions of glslang and spirv-tools used by vulkan-loader. Exact revisions are taken from # https://github.com/google/shaderc/blob/known-good/known_good.json", "commid": "nixpkgs_pr_195466"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-7d23bca2afabe244e001ea1f5ff411bdf8a2bece327125c5e4df1a0119e16fcc", "query": "glslc binary in shaderc has invalid signature Steps to reproduce the behavior: to compile shader on aarch64-darwin to SPIR-V should not be killed", "positive_passages": [{"docid": "doc-en-nixpkgs-418ba47ca70d2d51a2a99b355b227e0a50e9b6caef412a63ae002051e8dcda85", "text": "rev = \"0c28b6451d77774912e52949c1e57fa726edf113\"; sha256 = \"sha256-KpCMceTV/BRaoJe1qeXhKYQNQqdGaM6Q9nklpJKzHFY=\"; }; in stdenv.mkDerivation rec { in stdenv.mkDerivation rec { pname = \"shaderc\"; version = \"2021.0\";", "commid": "nixpkgs_pr_195466"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-7d23bca2afabe244e001ea1f5ff411bdf8a2bece327125c5e4df1a0119e16fcc", "query": "glslc binary in shaderc has invalid signature Steps to reproduce the behavior: to compile shader on aarch64-darwin to SPIR-V should not be killed", "positive_passages": [{"docid": "doc-en-nixpkgs-62f5ce13a22873f5d66a4bd85c3412e73ceaff56b1808b8545cb3e93b6629b01", "text": "ln -s ${spirv-headers} third_party/spirv-tools/external/spirv-headers ''; nativeBuildInputs = [ cmake python3 ] ++ lib.optionals stdenv.isDarwin [ darwin.cctools ]; nativeBuildInputs = [ cmake python3 ] ++ lib.optionals stdenv.isDarwin [ cctools ] ++ lib.optionals (stdenv.isDarwin && stdenv.isAarch64) [ autoSignDarwinBinariesHook ]; postInstall = '' moveToOutput \"lib/*.a\" $static", "commid": "nixpkgs_pr_195466"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-7d23bca2afabe244e001ea1f5ff411bdf8a2bece327125c5e4df1a0119e16fcc", "query": "glslc binary in shaderc has invalid signature Steps to reproduce the behavior: to compile shader on aarch64-darwin to SPIR-V should not be killed", "positive_passages": [{"docid": "doc-en-nixpkgs-260bebb229887f9a20d1d44babf6a301acd7acf68ec72c3ca07ee54fe2d0f24e", "text": "session-desktop = callPackage ../applications/networking/instant-messengers/session-desktop { }; shaderc = callPackage ../development/compilers/shaderc { }; shaderc = callPackage ../development/compilers/shaderc { inherit (darwin) autoSignDarwinBinariesHook cctools; }; shades-of-gray-theme = callPackage ../data/themes/shades-of-gray { };", "commid": "nixpkgs_pr_195466"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-dd749394ca6f9ef8dec044c1f97ed1031c2283da667ca4fc89f0ac2387af4dc8", "query": "Easyeffects crashes when Echo Canceller is used (at least when applied on input). I've been told that it works fine on arch linux. Though it might be my hardware that somehow makes it crash. Steps to reproduce the behavior: Echo Canceller module to the Input Easy Effects to one of recording apps It doesn't crash It doesn't write anything useful in the logs, just exits with code 137. Please run and paste the result.\nI can reproduce it but it is not a regular crash \u2013 there is not core dump. It appears to be killed. Weirdly when I run it with: The termination is not caught.\nFor me it reproduced with gdb: Maybe it's terminated when child process is crashed?\nhmm, it seems to be something wrong with speex when configured to use the fftw library... not sure what, but this doesn't crash:\nThe same also happens in Speech Processor effect now:\nUnfortunately this didn't seem to do the trick for me, it still crashes with the Echo Canceller.\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nI have the same problem. The thing is, used to work OK on my system. Then I tried the module, after which this issue appeared. However, now it's persisting. I undid the change, even tried booting into old generation, but is still getting killed with the echo canceller on. For reference, this is what I used to try to enable the echo cancel module (not sure if it ever worked):", "positive_passages": [{"docid": "doc-en-nixpkgs-d7951879e8976efaca11ad8494b33aa1b5a3b003abe8f91d90aa846a2bd78b72", "text": " { lib, stdenv, fetchurl, autoreconfHook, pkg-config, fftw }: { lib , stdenv , fetchurl , autoreconfHook , pkg-config , fftw , withFftw3 ? true }: stdenv.mkDerivation rec { pname = \"speexdsp\";", "commid": "nixpkgs_pr_257996"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-dd749394ca6f9ef8dec044c1f97ed1031c2283da667ca4fc89f0ac2387af4dc8", "query": "Easyeffects crashes when Echo Canceller is used (at least when applied on input). I've been told that it works fine on arch linux. Though it might be my hardware that somehow makes it crash. Steps to reproduce the behavior: Echo Canceller module to the Input Easy Effects to one of recording apps It doesn't crash It doesn't write anything useful in the logs, just exits with code 137. Please run and paste the result.\nI can reproduce it but it is not a regular crash \u2013 there is not core dump. It appears to be killed. Weirdly when I run it with: The termination is not caught.\nFor me it reproduced with gdb: Maybe it's terminated when child process is crashed?\nhmm, it seems to be something wrong with speex when configured to use the fftw library... not sure what, but this doesn't crash:\nThe same also happens in Speech Processor effect now:\nUnfortunately this didn't seem to do the trick for me, it still crashes with the Echo Canceller.\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nI have the same problem. The thing is, used to work OK on my system. Then I tried the module, after which this issue appeared. However, now it's persisting. I undid the change, even tried booting into old generation, but is still getting killed with the echo canceller on. For reference, this is what I used to try to enable the echo cancel module (not sure if it ever worked):", "positive_passages": [{"docid": "doc-en-nixpkgs-091777d43e89c932ec316dd30e45630c8e67e89c63d5fdc28f3b1901dd548836", "text": "outputs = [ \"out\" \"dev\" \"doc\" ]; nativeBuildInputs = [ autoreconfHook pkg-config ]; buildInputs = [ fftw ]; buildInputs = lib.optionals withFftw3 [ fftw ]; configureFlags = [ \"--with-fft=gpl-fftw3\" ] ++ lib.optional stdenv.isAarch64 \"--disable-neon\"; configureFlags = lib.optionals withFftw3 [ \"--with-fft=gpl-fftw3\" ] ++ lib.optional stdenv.isAarch64 \"--disable-neon\"; meta = with lib; { homepage = \"https://www.speex.org/\";", "commid": "nixpkgs_pr_257996"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-dd749394ca6f9ef8dec044c1f97ed1031c2283da667ca4fc89f0ac2387af4dc8", "query": "Easyeffects crashes when Echo Canceller is used (at least when applied on input). I've been told that it works fine on arch linux. Though it might be my hardware that somehow makes it crash. Steps to reproduce the behavior: Echo Canceller module to the Input Easy Effects to one of recording apps It doesn't crash It doesn't write anything useful in the logs, just exits with code 137. Please run and paste the result.\nI can reproduce it but it is not a regular crash \u2013 there is not core dump. It appears to be killed. Weirdly when I run it with: The termination is not caught.\nFor me it reproduced with gdb: Maybe it's terminated when child process is crashed?\nhmm, it seems to be something wrong with speex when configured to use the fftw library... not sure what, but this doesn't crash:\nThe same also happens in Speech Processor effect now:\nUnfortunately this didn't seem to do the trick for me, it still crashes with the Echo Canceller.\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nI have the same problem. The thing is, used to work OK on my system. Then I tried the module, after which this issue appeared. However, now it's persisting. I undid the change, even tried booting into old generation, but is still getting killed with the echo canceller on. For reference, this is what I used to try to enable the echo cancel module (not sure if it ever worked):", "positive_passages": [{"docid": "doc-en-nixpkgs-2f93ca4cb4bde067800b715b8511af9f3148cc95d9cd63050681b76ba6852db9", "text": "libcardiacarrest = callPackage ../misc/libcardiacarrest { }; easyeffects = callPackage ../applications/audio/easyeffects { }; easyeffects = callPackage ../applications/audio/easyeffects { # Fix crashes with speexdsp effects speexdsp = speexdsp.override { withFftw3 = false; }; }; pulseeffects-legacy = callPackage ../applications/audio/pulseeffects-legacy { };", "commid": "nixpkgs_pr_257996"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-8975aa5250159fe5f6e08ff39cfabfabd478ac819ca4dfa560eb6fe4ae0bfd97", "query": "When using as a root user the following error is produced: . This needs to be included, see = \"source ${}/share/zsh-\"; Please run and paste the result.", "positive_passages": [{"docid": "doc-en-nixpkgs-bffa7d5990d4009d7738fdc2c695a8dc908d0449d3202576bdb13e3725a8145b", "text": "installPhase = '' install -D powerlevel10k.zsh-theme --target-directory=$out/share/zsh-powerlevel10k install -D powerlevel9k.zsh-theme --target-directory=$out/share/zsh-powerlevel10k install -D config/* --target-directory=$out/share/zsh-powerlevel10k/config install -D internal/* --target-directory=$out/share/zsh-powerlevel10k/internal cp -R gitstatus $out/share/zsh-powerlevel10k/gitstatus", "commid": "nixpkgs_pr_190123"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-4282c34f0d9a0257061fb3ef2ce242e23b512dbf587d15b10181118645268527", "query": "consists mostly of syscalls (including ). There are even Ruby-specific workarounds. C/C++ would be a better language for the task. This should also reduce closure size and startup time of FHS-sandboxed apps (Ruby needs to load itself and its libraries from disk).\nCan't we just use to setup the chroot?\nI'm not sure if it's capable of doing all things that we need for this, but it should be worth checking. Can it run a container as a process (not as a systemd service), and can it be used not by a superuser?\nneeds root privileges. btw has C code to set them up, the rest is probably bash only?\nD: A pity. Well, let's continue with the old plan then. Unfortunately we can't do much more in Bash than we already do because we need to do mounts in the same process we set the namespaces, in children necessary privileges are already gone. I'm not completely sure about this but I remember that when I tried to write this in Bash completely long time ago (using for setting up namespaces mounts and chroot were a problem.\nHow about using this one?\nbind mounts, sysfs, tmpfs and procfs should be\nI can confirm that these mounts are possible from using unprivileged lxc containers. But you cannot bind mount something from the host this way, because it needs to be done after . UPDATE: ok even that should be possible if the correct order is maintained: unshare -mount -chroot.\nOh, I should look at it! cc in case he's interested in this thread. I think that checks if the user is root -- that's why this doesn't work. This means that we need to call by ourselves... (I was going to hit \"Comment\" but you were faster ~_^) I expect that LXC containers do user maps such that you have UID 0 in new userns -- we, however, need to retain user uid.\nwhy do we have to retain user id?\nMultiple user apps use uid and username for their purposes -- we don't want to lie to them. I can't give a complete example (I remember that Steam breaks) but for example we have directories which apps can find based on uid.\nI have another suggestion: the Go programming language. Bear in mind that I'm generally not a super big fan of Go (in fact, while I use Go extensively at work, I generally use Haskell for my personal projects); however, I think that a higher level, simple (in terms of specification) language would be conducive to maintenance and further development. The binaries should be pretty small, and the closure should be pretty small, too. I might give that a go (no pun intended) and see what we think.\nSeveral possible issues: need native and then before any calls to pthreads (or you'll get or something close); I remember that Go has a runtime so there may be problems; need several syscalls which may not be readily available, namely , and others. In Ruby I import them from libc dynamically and redefine constants from C by hand, but doing this (especially redefining constants) is one of the reasons I want to move from Ruby in the first place. However these are only potential problems -- I don't know if they actually exist! I'm actually interested in how this turns out.\nYou cannot use clone() properly because of the language runtime. That's why docker uses a little C for that job.\nAh, you must be referring to this from : I'll need to give that a thorough reading before I understand why the runtime gets in the way (unless, perhaps, you have an explanation of why/how pthreads mucks things up).\nOh, I'm guessing that's probably stuff like this: Though, if there are other details, I'd love to hear them :smile:.\nIf you refer to my remark about fork and pthreads, it's actually 's limitation. You can look at how I workaround this in Ruby by calling imported instead of Ruby's builtin. You will know if you encounter it -- will just fail. I think the best way to find out is with an experiment. (notice that I don't know about Go runtime and haven't even used Go before, so, as I underline again, those might be non-issues)\nInteresting. I referred to the , but I don't see any mention of failure when used with pthreads. I don't doubt you; I'd just like to know how all this stuff works.\nNo problem even if these were doubts ~^. From man page:\nAh, dunno why I didn't try reading the man page -- thanks for pointing that out :wink:.\nAnybody done any more work on this? Also, this should probably be tagged with security, due to\na rewrite in a different language will not solve your grsecurity problems. I also do not see how the rewrite discussed here is related to security.\nAnything related to grsecurity is security-related. A rewrite into a compiled language means that a setuid wrapper can be created, which means I don't have to run shit as root.\nYou can drop your privileges via right after you enter the environment as -- it's less convenient but you get roughly what you want.", "positive_passages": [{"docid": "doc-en-nixpkgs-49aebe32dc448a0e79002887fc3778557aa752140df75fe714e03d9f08d6c2c7", "text": " #!/usr/bin/env ruby # Bind mounts hierarchy: from => to (relative) # If 'to' is nil, path will be the same mounts = { '/' => 'host', '/proc' => nil, '/sys' => nil, '/nix' => nil, '/tmp' => nil, '/var' => nil, '/run' => nil, '/dev' => nil, '/home' => nil, } # Propagate environment variables envvars = [ 'TERM', 'DISPLAY', 'XAUTHORITY', 'HOME', 'XDG_RUNTIME_DIR', 'LANG', 'SSL_CERT_FILE', 'DBUS_SESSION_BUS_ADDRESS', ] require 'tmpdir' require 'fileutils' require 'pathname' require 'set' require 'fiddle' def write_file(path, str) File.open(path, 'w') { |file| file.write str } end # Import C standard library and several needed calls $libc = Fiddle.dlopen nil def make_fcall(name, args, output) c = Fiddle::Function.new $libc[name], args, output lambda do |*args| ret = c.call *args raise SystemCallError.new Fiddle.last_error if ret < 0 return ret end end $fork = make_fcall 'fork', [], Fiddle::TYPE_INT CLONE_NEWNS = 0x00020000 CLONE_NEWUSER = 0x10000000 $unshare = make_fcall 'unshare', [Fiddle::TYPE_INT], Fiddle::TYPE_INT MS_BIND = 0x1000 MS_REC = 0x4000 MS_SLAVE = 0x80000 $mount = make_fcall 'mount', [Fiddle::TYPE_VOIDP, Fiddle::TYPE_VOIDP, Fiddle::TYPE_VOIDP, Fiddle::TYPE_LONG, Fiddle::TYPE_VOIDP], Fiddle::TYPE_INT # Read command line args abort \"Usage: chrootenv program args...\" unless ARGV.length >= 1 execp = ARGV # Populate extra mounts if not ENV[\"CHROOTENV_EXTRA_BINDS\"].nil? $stderr.puts \"CHROOTENV_EXTRA_BINDS is discussed for deprecation.\" $stderr.puts \"If you have a usecase, please drop a note in issue #16030.\" $stderr.puts \"Notice that we now bind-mount host FS to '/host' and symlink all directories from it to '/' by default.\" for extra in ENV[\"CHROOTENV_EXTRA_BINDS\"].split(':') paths = extra.split('=') if not paths.empty? if paths.size <= 2 mounts[paths[0]] = paths[1] else $stderr.puts \"Ignoring invalid entry in CHROOTENV_EXTRA_BINDS: #{extra}\" end end end end # Set destination paths for mounts mounts = mounts.map { |k, v| [k, v.nil? ? k.sub(/^/*/, '') : v] }.to_h # Create temporary directory for root and chdir root = Dir.mktmpdir 'chrootenv' # Fork process; we need this to do a proper cleanup because # child process will chroot into temporary directory. # We use imported 'fork' instead of native to overcome # CRuby's meddling with threads; this should be safe because # we don't use threads at all. $cpid = $fork.call if $cpid == 0 # If we are root, no need to create new user namespace. if Process.uid == 0 $unshare.call CLONE_NEWNS # Mark all mounted filesystems as slave so changes # don't propagate to the parent mount namespace. $mount.call nil, '/', nil, MS_REC | MS_SLAVE, nil else # Save user UID and GID uid = Process.uid gid = Process.gid # Create new mount and user namespaces # CLONE_NEWUSER requires a program to be non-threaded, hence # native fork above. $unshare.call CLONE_NEWNS | CLONE_NEWUSER # Map users and groups to the parent namespace begin # setgroups is only available since Linux 3.19 write_file '/proc/self/setgroups', 'deny' rescue end write_file '/proc/self/uid_map', \"#{uid} #{uid} 1\" write_file '/proc/self/gid_map', \"#{gid} #{gid} 1\" end # Do rbind mounts. mounts.each do |from, rto| to = \"#{root}/#{rto}\" FileUtils.mkdir_p to $mount.call from, to, nil, MS_BIND | MS_REC, nil end # Don't make root private so privilege drops inside chroot are possible File.chmod(0755, root) # Chroot! Dir.chroot root Dir.chdir '/' # New environment new_env = Hash[ envvars.map { |x| [x, ENV[x]] } ] # Finally, exec! exec(new_env, *execp, close_others: true, unsetenv_others: true) end # Wait for a child. If we catch a signal, resend it to child and continue # waiting. def wait_child begin Process.wait # Return child's exit code if $?.exited? exit $?.exitstatus else exit 1 end rescue SignalException => e Process.kill e.signo, $cpid wait_child end end begin wait_child ensure # Cleanup FileUtils.rm_rf root, secure: true end ", "commid": "nixpkgs_pr_31182"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-4282c34f0d9a0257061fb3ef2ce242e23b512dbf587d15b10181118645268527", "query": "consists mostly of syscalls (including ). There are even Ruby-specific workarounds. C/C++ would be a better language for the task. This should also reduce closure size and startup time of FHS-sandboxed apps (Ruby needs to load itself and its libraries from disk).\nCan't we just use to setup the chroot?\nI'm not sure if it's capable of doing all things that we need for this, but it should be worth checking. Can it run a container as a process (not as a systemd service), and can it be used not by a superuser?\nneeds root privileges. btw has C code to set them up, the rest is probably bash only?\nD: A pity. Well, let's continue with the old plan then. Unfortunately we can't do much more in Bash than we already do because we need to do mounts in the same process we set the namespaces, in children necessary privileges are already gone. I'm not completely sure about this but I remember that when I tried to write this in Bash completely long time ago (using for setting up namespaces mounts and chroot were a problem.\nHow about using this one?\nbind mounts, sysfs, tmpfs and procfs should be\nI can confirm that these mounts are possible from using unprivileged lxc containers. But you cannot bind mount something from the host this way, because it needs to be done after . UPDATE: ok even that should be possible if the correct order is maintained: unshare -mount -chroot.\nOh, I should look at it! cc in case he's interested in this thread. I think that checks if the user is root -- that's why this doesn't work. This means that we need to call by ourselves... (I was going to hit \"Comment\" but you were faster ~_^) I expect that LXC containers do user maps such that you have UID 0 in new userns -- we, however, need to retain user uid.\nwhy do we have to retain user id?\nMultiple user apps use uid and username for their purposes -- we don't want to lie to them. I can't give a complete example (I remember that Steam breaks) but for example we have directories which apps can find based on uid.\nI have another suggestion: the Go programming language. Bear in mind that I'm generally not a super big fan of Go (in fact, while I use Go extensively at work, I generally use Haskell for my personal projects); however, I think that a higher level, simple (in terms of specification) language would be conducive to maintenance and further development. The binaries should be pretty small, and the closure should be pretty small, too. I might give that a go (no pun intended) and see what we think.\nSeveral possible issues: need native and then before any calls to pthreads (or you'll get or something close); I remember that Go has a runtime so there may be problems; need several syscalls which may not be readily available, namely , and others. In Ruby I import them from libc dynamically and redefine constants from C by hand, but doing this (especially redefining constants) is one of the reasons I want to move from Ruby in the first place. However these are only potential problems -- I don't know if they actually exist! I'm actually interested in how this turns out.\nYou cannot use clone() properly because of the language runtime. That's why docker uses a little C for that job.\nAh, you must be referring to this from : I'll need to give that a thorough reading before I understand why the runtime gets in the way (unless, perhaps, you have an explanation of why/how pthreads mucks things up).\nOh, I'm guessing that's probably stuff like this: Though, if there are other details, I'd love to hear them :smile:.\nIf you refer to my remark about fork and pthreads, it's actually 's limitation. You can look at how I workaround this in Ruby by calling imported instead of Ruby's builtin. You will know if you encounter it -- will just fail. I think the best way to find out is with an experiment. (notice that I don't know about Go runtime and haven't even used Go before, so, as I underline again, those might be non-issues)\nInteresting. I referred to the , but I don't see any mention of failure when used with pthreads. I don't doubt you; I'd just like to know how all this stuff works.\nNo problem even if these were doubts ~^. From man page:\nAh, dunno why I didn't try reading the man page -- thanks for pointing that out :wink:.\nAnybody done any more work on this? Also, this should probably be tagged with security, due to\na rewrite in a different language will not solve your grsecurity problems. I also do not see how the rewrite discussed here is related to security.\nAnything related to grsecurity is security-related. A rewrite into a compiled language means that a setuid wrapper can be created, which means I don't have to run shit as root.\nYou can drop your privileges via right after you enter the environment as -- it's less convenient but you get roughly what you want.", "positive_passages": [{"docid": "doc-en-nixpkgs-520f91cc10a3fff55edf843dd0d4e2ab61e9a64004955ae295343a52b1126fc2", "text": " #define _GNU_SOURCE #include #include #define errorf(status, fmt, ...) error_at_line(status, errno, __FILE__, __LINE__, fmt, ##__VA_ARGS__) #include #include #include #include #include #include #include #include #include #include #include #include char *env_whitelist[] = {\"TERM\", \"DISPLAY\", \"XAUTHORITY\", \"HOME\", \"XDG_RUNTIME_DIR\", \"LANG\", \"SSL_CERT_FILE\", \"DBUS_SESSION_BUS_ADDRESS\"}; char **env_build(char *names[], size_t len) { char *env, **ret = malloc((len + 1) * sizeof(char *)), **ptr = ret; for (size_t i = 0; i < len; i++) { if ((env = getenv(names[i]))) { if (asprintf(ptr++, \"%s=%s\", names[i], env) < 0) errorf(EX_OSERR, \"asprintf\"); } } *ptr = NULL; return ret; } struct bind { char *from; char *to; }; struct bind binds[] = {{\"/\", \"host\"}, {\"/proc\", \"proc\"}, {\"/sys\", \"sys\"}, {\"/nix\", \"nix\"}, {\"/tmp\", \"tmp\"}, {\"/var\", \"var\"}, {\"/run\", \"run\"}, {\"/dev\", \"dev\"}, {\"/home\", \"home\"}}; void bind(struct bind *bind) { DIR *src = opendir(bind->from); if (src) { if (closedir(src) < 0) errorf(EX_IOERR, \"closedir\"); if (mkdir(bind->to, 0755) < 0) errorf(EX_IOERR, \"mkdir\"); if (mount(bind->from, bind->to, \"bind\", MS_BIND | MS_REC, NULL) < 0) errorf(EX_OSERR, \"mount\"); } else { // https://github.com/NixOS/nixpkgs/issues/31104 if (errno != ENOENT) errorf(EX_OSERR, \"opendir\"); } } void spitf(char *path, char *fmt, ...) { va_list args; va_start(args, fmt); FILE *f = fopen(path, \"w\"); if (f == NULL) errorf(EX_IOERR, \"spitf(%s): fopen\", path); if (vfprintf(f, fmt, args) < 0) errorf(EX_IOERR, \"spitf(%s): vfprintf\", path); if (fclose(f) < 0) errorf(EX_IOERR, \"spitf(%s): fclose\", path); } int nftw_rm(const char *path, const struct stat *sb, int type, struct FTW *ftw) { if (remove(path) < 0) errorf(EX_IOERR, \"nftw_rm\"); return 0; } #define LEN(x) sizeof(x) / sizeof(*x) int main(int argc, char *argv[]) { if (argc < 2) { fprintf(stderr, \"Usage: %s command [arguments...]n\" \"Requires Linux kernel >= 3.19 with CONFIG_USER_NS.n\", argv[0]); exit(EX_USAGE); } char tmpl[] = \"/tmp/chrootenvXXXXXX\"; char *root = mkdtemp(tmpl); if (root == NULL) errorf(EX_IOERR, \"mkdtemp\"); // Don't make root private so that privilege drops inside chroot are possible: if (chmod(root, 0755) < 0) errorf(EX_IOERR, \"chmod\"); pid_t cpid = fork(); if (cpid < 0) errorf(EX_OSERR, \"fork\"); if (cpid == 0) { uid_t uid = getuid(); gid_t gid = getgid(); // If we are root, no need to create new user namespace. if (uid == 0) { if (unshare(CLONE_NEWNS) < 0) errorf(EX_OSERR, \"unshare() failed: You may have an old kernel or have CLONE_NEWUSER disabled by your distribution security settings.\"); // Mark all mounted filesystems as slave so changes // don't propagate to the parent mount namespace. if (mount(NULL, \"/\", NULL, MS_REC | MS_SLAVE, NULL) < 0) errorf(EX_OSERR, \"mount\"); } else { // Create new mount and user namespaces. CLONE_NEWUSER // requires a program to be non-threaded. if (unshare(CLONE_NEWNS | CLONE_NEWUSER) < 0) errorf(EX_OSERR, \"unshare\"); // Map users and groups to the parent namespace. // setgroups is only available since Linux 3.19: spitf(\"/proc/self/setgroups\", \"deny\"); spitf(\"/proc/self/uid_map\", \"%d %d 1\", uid, uid); spitf(\"/proc/self/gid_map\", \"%d %d 1\", gid, gid); } if (chdir(root) < 0) errorf(EX_IOERR, \"chdir\"); for (size_t i = 0; i < LEN(binds); i++) bind(&binds[i]); if (chroot(root) < 0) errorf(EX_OSERR, \"chroot\"); if (chdir(\"/\") < 0) errorf(EX_OSERR, \"chdir\"); argv++; if (execvpe(*argv, argv, env_build(env_whitelist, LEN(env_whitelist))) < 0) errorf(EX_OSERR, \"execvpe\"); } int status; if (waitpid(cpid, &status, 0) < 0) errorf(EX_OSERR, \"waitpid\"); if (nftw(root, nftw_rm, getdtablesize(), FTW_DEPTH | FTW_MOUNT | FTW_PHYS) < 0) errorf(EX_IOERR, \"nftw\"); if (WIFEXITED(status)) return WEXITSTATUS(status); else if (WIFSIGNALED(status)) kill(getpid(), WTERMSIG(status)); return EX_OSERR; } ", "commid": "nixpkgs_pr_31182"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-4282c34f0d9a0257061fb3ef2ce242e23b512dbf587d15b10181118645268527", "query": "consists mostly of syscalls (including ). There are even Ruby-specific workarounds. C/C++ would be a better language for the task. This should also reduce closure size and startup time of FHS-sandboxed apps (Ruby needs to load itself and its libraries from disk).\nCan't we just use to setup the chroot?\nI'm not sure if it's capable of doing all things that we need for this, but it should be worth checking. Can it run a container as a process (not as a systemd service), and can it be used not by a superuser?\nneeds root privileges. btw has C code to set them up, the rest is probably bash only?\nD: A pity. Well, let's continue with the old plan then. Unfortunately we can't do much more in Bash than we already do because we need to do mounts in the same process we set the namespaces, in children necessary privileges are already gone. I'm not completely sure about this but I remember that when I tried to write this in Bash completely long time ago (using for setting up namespaces mounts and chroot were a problem.\nHow about using this one?\nbind mounts, sysfs, tmpfs and procfs should be\nI can confirm that these mounts are possible from using unprivileged lxc containers. But you cannot bind mount something from the host this way, because it needs to be done after . UPDATE: ok even that should be possible if the correct order is maintained: unshare -mount -chroot.\nOh, I should look at it! cc in case he's interested in this thread. I think that checks if the user is root -- that's why this doesn't work. This means that we need to call by ourselves... (I was going to hit \"Comment\" but you were faster ~_^) I expect that LXC containers do user maps such that you have UID 0 in new userns -- we, however, need to retain user uid.\nwhy do we have to retain user id?\nMultiple user apps use uid and username for their purposes -- we don't want to lie to them. I can't give a complete example (I remember that Steam breaks) but for example we have directories which apps can find based on uid.\nI have another suggestion: the Go programming language. Bear in mind that I'm generally not a super big fan of Go (in fact, while I use Go extensively at work, I generally use Haskell for my personal projects); however, I think that a higher level, simple (in terms of specification) language would be conducive to maintenance and further development. The binaries should be pretty small, and the closure should be pretty small, too. I might give that a go (no pun intended) and see what we think.\nSeveral possible issues: need native and then before any calls to pthreads (or you'll get or something close); I remember that Go has a runtime so there may be problems; need several syscalls which may not be readily available, namely , and others. In Ruby I import them from libc dynamically and redefine constants from C by hand, but doing this (especially redefining constants) is one of the reasons I want to move from Ruby in the first place. However these are only potential problems -- I don't know if they actually exist! I'm actually interested in how this turns out.\nYou cannot use clone() properly because of the language runtime. That's why docker uses a little C for that job.\nAh, you must be referring to this from : I'll need to give that a thorough reading before I understand why the runtime gets in the way (unless, perhaps, you have an explanation of why/how pthreads mucks things up).\nOh, I'm guessing that's probably stuff like this: Though, if there are other details, I'd love to hear them :smile:.\nIf you refer to my remark about fork and pthreads, it's actually 's limitation. You can look at how I workaround this in Ruby by calling imported instead of Ruby's builtin. You will know if you encounter it -- will just fail. I think the best way to find out is with an experiment. (notice that I don't know about Go runtime and haven't even used Go before, so, as I underline again, those might be non-issues)\nInteresting. I referred to the , but I don't see any mention of failure when used with pthreads. I don't doubt you; I'd just like to know how all this stuff works.\nNo problem even if these were doubts ~^. From man page:\nAh, dunno why I didn't try reading the man page -- thanks for pointing that out :wink:.\nAnybody done any more work on this? Also, this should probably be tagged with security, due to\na rewrite in a different language will not solve your grsecurity problems. I also do not see how the rewrite discussed here is related to security.\nAnything related to grsecurity is security-related. A rewrite into a compiled language means that a setuid wrapper can be created, which means I don't have to run shit as root.\nYou can drop your privileges via right after you enter the environment as -- it's less convenient but you get roughly what you want.", "positive_passages": [{"docid": "doc-en-nixpkgs-94d0957930db4781d343587eece952e66fe4c564ebad50e48b28c8758b6cd1ab", "text": "let buildFHSEnv = callPackage ./env.nix { }; in args@{ name, runScript ? \"bash\", extraBindMounts ? [], extraInstallCommands ? \"\", meta ? {}, passthru ? {}, ... }: args@{ name, runScript ? \"bash\", extraInstallCommands ? \"\", meta ? {}, passthru ? {}, ... }: let env = buildFHSEnv (removeAttrs args [ \"runScript\" \"extraBindMounts\" \"extraInstallCommands\" \"meta\" \"passthru\" ]); env = buildFHSEnv (removeAttrs args [ \"runScript\" \"extraInstallCommands\" \"meta\" \"passthru\" ]); # Sandboxing script chroot-user = writeScript \"chroot-user\" '' #! ${ruby}/bin/ruby ${builtins.readFile ./chroot-user.rb} ''; chrootenv = stdenv.mkDerivation { name = \"chrootenv\"; unpackPhase = \"cp ${./chrootenv.c} chrootenv.c\"; installPhase = \"cp chrootenv $out\"; makeFlags = [ \"chrootenv\" ]; }; init = run: writeScript \"${name}-init\" '' #! ${stdenv.shell}", "commid": "nixpkgs_pr_31182"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-4282c34f0d9a0257061fb3ef2ce242e23b512dbf587d15b10181118645268527", "query": "consists mostly of syscalls (including ). There are even Ruby-specific workarounds. C/C++ would be a better language for the task. This should also reduce closure size and startup time of FHS-sandboxed apps (Ruby needs to load itself and its libraries from disk).\nCan't we just use to setup the chroot?\nI'm not sure if it's capable of doing all things that we need for this, but it should be worth checking. Can it run a container as a process (not as a systemd service), and can it be used not by a superuser?\nneeds root privileges. btw has C code to set them up, the rest is probably bash only?\nD: A pity. Well, let's continue with the old plan then. Unfortunately we can't do much more in Bash than we already do because we need to do mounts in the same process we set the namespaces, in children necessary privileges are already gone. I'm not completely sure about this but I remember that when I tried to write this in Bash completely long time ago (using for setting up namespaces mounts and chroot were a problem.\nHow about using this one?\nbind mounts, sysfs, tmpfs and procfs should be\nI can confirm that these mounts are possible from using unprivileged lxc containers. But you cannot bind mount something from the host this way, because it needs to be done after . UPDATE: ok even that should be possible if the correct order is maintained: unshare -mount -chroot.\nOh, I should look at it! cc in case he's interested in this thread. I think that checks if the user is root -- that's why this doesn't work. This means that we need to call by ourselves... (I was going to hit \"Comment\" but you were faster ~_^) I expect that LXC containers do user maps such that you have UID 0 in new userns -- we, however, need to retain user uid.\nwhy do we have to retain user id?\nMultiple user apps use uid and username for their purposes -- we don't want to lie to them. I can't give a complete example (I remember that Steam breaks) but for example we have directories which apps can find based on uid.\nI have another suggestion: the Go programming language. Bear in mind that I'm generally not a super big fan of Go (in fact, while I use Go extensively at work, I generally use Haskell for my personal projects); however, I think that a higher level, simple (in terms of specification) language would be conducive to maintenance and further development. The binaries should be pretty small, and the closure should be pretty small, too. I might give that a go (no pun intended) and see what we think.\nSeveral possible issues: need native and then before any calls to pthreads (or you'll get or something close); I remember that Go has a runtime so there may be problems; need several syscalls which may not be readily available, namely , and others. In Ruby I import them from libc dynamically and redefine constants from C by hand, but doing this (especially redefining constants) is one of the reasons I want to move from Ruby in the first place. However these are only potential problems -- I don't know if they actually exist! I'm actually interested in how this turns out.\nYou cannot use clone() properly because of the language runtime. That's why docker uses a little C for that job.\nAh, you must be referring to this from : I'll need to give that a thorough reading before I understand why the runtime gets in the way (unless, perhaps, you have an explanation of why/how pthreads mucks things up).\nOh, I'm guessing that's probably stuff like this: Though, if there are other details, I'd love to hear them :smile:.\nIf you refer to my remark about fork and pthreads, it's actually 's limitation. You can look at how I workaround this in Ruby by calling imported instead of Ruby's builtin. You will know if you encounter it -- will just fail. I think the best way to find out is with an experiment. (notice that I don't know about Go runtime and haven't even used Go before, so, as I underline again, those might be non-issues)\nInteresting. I referred to the , but I don't see any mention of failure when used with pthreads. I don't doubt you; I'd just like to know how all this stuff works.\nNo problem even if these were doubts ~^. From man page:\nAh, dunno why I didn't try reading the man page -- thanks for pointing that out :wink:.\nAnybody done any more work on this? Also, this should probably be tagged with security, due to\na rewrite in a different language will not solve your grsecurity problems. I also do not see how the rewrite discussed here is related to security.\nAnything related to grsecurity is security-related. A rewrite into a compiled language means that a setuid wrapper can be created, which means I don't have to run shit as root.\nYou can drop your privileges via right after you enter the environment as -- it's less convenient but you get roughly what you want.", "positive_passages": [{"docid": "doc-en-nixpkgs-b629b84f97ed570db1fc8f4f71b13a49f6fea76f67e540277739afe81b965f52", "text": "passthru = passthru // { env = runCommand \"${name}-shell-env\" { shellHook = '' ${lib.optionalString (extraBindMounts != []) ''export CHROOTENV_EXTRA_BINDS=\"${lib.concatStringsSep \":\" extraBindMounts}:$CHROOTENV_EXTRA_BINDS\"''} exec ${chroot-user} ${init \"bash\"} \"$(pwd)\" exec ${chrootenv} ${init \"bash\"} \"$(pwd)\" ''; } '' echo >&2 \"\"", "commid": "nixpkgs_pr_31182"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-4282c34f0d9a0257061fb3ef2ce242e23b512dbf587d15b10181118645268527", "query": "consists mostly of syscalls (including ). There are even Ruby-specific workarounds. C/C++ would be a better language for the task. This should also reduce closure size and startup time of FHS-sandboxed apps (Ruby needs to load itself and its libraries from disk).\nCan't we just use to setup the chroot?\nI'm not sure if it's capable of doing all things that we need for this, but it should be worth checking. Can it run a container as a process (not as a systemd service), and can it be used not by a superuser?\nneeds root privileges. btw has C code to set them up, the rest is probably bash only?\nD: A pity. Well, let's continue with the old plan then. Unfortunately we can't do much more in Bash than we already do because we need to do mounts in the same process we set the namespaces, in children necessary privileges are already gone. I'm not completely sure about this but I remember that when I tried to write this in Bash completely long time ago (using for setting up namespaces mounts and chroot were a problem.\nHow about using this one?\nbind mounts, sysfs, tmpfs and procfs should be\nI can confirm that these mounts are possible from using unprivileged lxc containers. But you cannot bind mount something from the host this way, because it needs to be done after . UPDATE: ok even that should be possible if the correct order is maintained: unshare -mount -chroot.\nOh, I should look at it! cc in case he's interested in this thread. I think that checks if the user is root -- that's why this doesn't work. This means that we need to call by ourselves... (I was going to hit \"Comment\" but you were faster ~_^) I expect that LXC containers do user maps such that you have UID 0 in new userns -- we, however, need to retain user uid.\nwhy do we have to retain user id?\nMultiple user apps use uid and username for their purposes -- we don't want to lie to them. I can't give a complete example (I remember that Steam breaks) but for example we have directories which apps can find based on uid.\nI have another suggestion: the Go programming language. Bear in mind that I'm generally not a super big fan of Go (in fact, while I use Go extensively at work, I generally use Haskell for my personal projects); however, I think that a higher level, simple (in terms of specification) language would be conducive to maintenance and further development. The binaries should be pretty small, and the closure should be pretty small, too. I might give that a go (no pun intended) and see what we think.\nSeveral possible issues: need native and then before any calls to pthreads (or you'll get or something close); I remember that Go has a runtime so there may be problems; need several syscalls which may not be readily available, namely , and others. In Ruby I import them from libc dynamically and redefine constants from C by hand, but doing this (especially redefining constants) is one of the reasons I want to move from Ruby in the first place. However these are only potential problems -- I don't know if they actually exist! I'm actually interested in how this turns out.\nYou cannot use clone() properly because of the language runtime. That's why docker uses a little C for that job.\nAh, you must be referring to this from : I'll need to give that a thorough reading before I understand why the runtime gets in the way (unless, perhaps, you have an explanation of why/how pthreads mucks things up).\nOh, I'm guessing that's probably stuff like this: Though, if there are other details, I'd love to hear them :smile:.\nIf you refer to my remark about fork and pthreads, it's actually 's limitation. You can look at how I workaround this in Ruby by calling imported instead of Ruby's builtin. You will know if you encounter it -- will just fail. I think the best way to find out is with an experiment. (notice that I don't know about Go runtime and haven't even used Go before, so, as I underline again, those might be non-issues)\nInteresting. I referred to the , but I don't see any mention of failure when used with pthreads. I don't doubt you; I'd just like to know how all this stuff works.\nNo problem even if these were doubts ~^. From man page:\nAh, dunno why I didn't try reading the man page -- thanks for pointing that out :wink:.\nAnybody done any more work on this? Also, this should probably be tagged with security, due to\na rewrite in a different language will not solve your grsecurity problems. I also do not see how the rewrite discussed here is related to security.\nAnything related to grsecurity is security-related. A rewrite into a compiled language means that a setuid wrapper can be created, which means I don't have to run shit as root.\nYou can drop your privileges via right after you enter the environment as -- it's less convenient but you get roughly what you want.", "positive_passages": [{"docid": "doc-en-nixpkgs-7f71082ad4ecfeb4c7fa8036145151d3f5dd93bb50aef6f45d34397b0eb16b6b", "text": "mkdir -p $out/bin cat <$out/bin/${name} #! ${stdenv.shell} ${lib.optionalString (extraBindMounts != []) ''export CHROOTENV_EXTRA_BINDS=\"${lib.concatStringsSep \":\" extraBindMounts}:$CHROOTENV_EXTRA_BINDS\"''} exec ${chroot-user} ${init runScript} \"$(pwd)\" \"$@\" exec ${chrootenv} ${init runScript} \"$(pwd)\" \"$@\" EOF chmod +x $out/bin/${name} ${extraInstallCommands}", "commid": "nixpkgs_pr_31182"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-e8dc5dcb30f4262ed938efe3be477937624b78d25a3c08703824e75909560bc5", "query": "Steps to reproduce the behavior: build -L 'nixpkgs#curlie' diff --git a/go.mod b/go.mod index 660463a..5249458 100644 --- a/go.mod +++ b/go.mod @@ -2,7 +2,7 @@ module github.com/rs/curlie require ( golang.org/x/crypto v0.0.0-20180524125353-159ae71589f3 -\tgolang.org/x/sys v0.0.0-20191026070338-33540a1f6037 +\tgolang.org/x/sys v0.0.0-20211110154304-99a53858aa08 ) go 1.13 ", "commid": "nixpkgs_pr_193368"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-e8dc5dcb30f4262ed938efe3be477937624b78d25a3c08703824e75909560bc5", "query": "Steps to reproduce the behavior: build -L 'nixpkgs#curlie' vendorSha256 = \"sha256-tYZtnD7RUurhl8yccXlTIvOxybBJITM+it1ollYJ1OI=\"; patches = [ ./bump-golang-x-sys.patch ]; vendorSha256 = \"sha256-VsPdMUfS4UVem6uJgFISfFHQEKtIumDQktHQFPC1muc=\"; ldflags = [ \"-s\" \"-w\" \"-X main.version=${version}\" ];", "commid": "nixpkgs_pr_193368"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-a5ce8108a9eb1ec970f91d1d1f62cddb62e7667bf4cdcbffb714b5e64d68e5e6", "query": "In GNOME keyboard shortcut settings, the list of categories based on and on my own experience with GNOME on other distros should be: Launchers Navigation Screenshots Sound and Media System Typing Universal Access Windows However, only the following categories are available: Launchers Screenshots Sound and Media System Typing Universal Access So I'm missing Navigation and Windows. Install gnome package and use GNOME. Open keyboard settings (press Super, type \"keyboard\", choose Keyboard). See the list of categories on the left panel. System: (NixOS: , Ubuntu/Fedora: , ...)Nix version: (run )Nixpkgs version: (run )\nI am affected too. Moreover doesn't lock the screen.\nI got that, too. Seems like that might be .\nAnother possible source of not working (if you're using GDM):\nApparently the Control Center derivation only provides some keybindings: the others are part of other packages like GNOME Shell or GPaste. The Control Center loads the bindings , basically using to locate them. But even explicitly passing the path does not make the Windows section appear \u2013 though, strace confirms the file being read. Edit: Nevermind, it looks like the navigation and windows keybindings come from .\nHey, have you somehow managed to get it to work using ? (Not quite sure how to interpret your edit). I tried messing around with that but so far I\u2019ve only been able to break :\nTry . The error you are seeing is caused by missing GNOME shell SCHEMAS, which will most likely be in the current variable.\nIt looks like the error I was seeing was related to fish shell not having setup properly and was failing even if I didn\u2019t attempt to change anything. I switched to bash and that particular problem disappeared, however I am now getting a different error message: However, this schema seems to exist in mutter, so I sadly have no idea what is going on here:\nRight, for that you also need to add share/gsettings/mutter-3.28.0 or something like that.\nThanks a ton! I finally got it to work using that!\nI was able to get it to work using .\nThe mutter keybindings are not available in control center in NixOS when . Explicitly adding mutter to fixes it. Should mutter perhaps be to ?\nI think adding it to dependencies of g-c-c is more in line with Nix. We can do it after we merge 3.32.", "positive_passages": [{"docid": "doc-en-nixpkgs-291c53f5331b6f098de91aca1ec9a54c70402601a0e82f41996d0eba04adfbc5", "text": ", gtk3, glib, glib-networking, gsettings-desktop-schemas , gnome-desktop, gnome-settings-daemon, gnome-online-accounts , vino, gnome-bluetooth, tracker, adwaita-icon-theme , udisks2, gsound, libhandy, cups }: , udisks2, gsound, libhandy, cups, mutter }: stdenv.mkDerivation rec { pname = \"gnome-control-center\";", "commid": "nixpkgs_pr_59765"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-a5ce8108a9eb1ec970f91d1d1f62cddb62e7667bf4cdcbffb714b5e64d68e5e6", "query": "In GNOME keyboard shortcut settings, the list of categories based on and on my own experience with GNOME on other distros should be: Launchers Navigation Screenshots Sound and Media System Typing Universal Access Windows However, only the following categories are available: Launchers Screenshots Sound and Media System Typing Universal Access So I'm missing Navigation and Windows. Install gnome package and use GNOME. Open keyboard settings (press Super, type \"keyboard\", choose Keyboard). See the list of categories on the left panel. System: (NixOS: , Ubuntu/Fedora: , ...)Nix version: (run )Nixpkgs version: (run )\nI am affected too. Moreover doesn't lock the screen.\nI got that, too. Seems like that might be .\nAnother possible source of not working (if you're using GDM):\nApparently the Control Center derivation only provides some keybindings: the others are part of other packages like GNOME Shell or GPaste. The Control Center loads the bindings , basically using to locate them. But even explicitly passing the path does not make the Windows section appear \u2013 though, strace confirms the file being read. Edit: Nevermind, it looks like the navigation and windows keybindings come from .\nHey, have you somehow managed to get it to work using ? (Not quite sure how to interpret your edit). I tried messing around with that but so far I\u2019ve only been able to break :\nTry . The error you are seeing is caused by missing GNOME shell SCHEMAS, which will most likely be in the current variable.\nIt looks like the error I was seeing was related to fish shell not having setup properly and was failing even if I didn\u2019t attempt to change anything. I switched to bash and that particular problem disappeared, however I am now getting a different error message: However, this schema seems to exist in mutter, so I sadly have no idea what is going on here:\nRight, for that you also need to add share/gsettings/mutter-3.28.0 or something like that.\nThanks a ton! I finally got it to work using that!\nI was able to get it to work using .\nThe mutter keybindings are not available in control center in NixOS when . Explicitly adding mutter to fixes it. Should mutter perhaps be to ?\nI think adding it to dependencies of g-c-c is more in line with Nix. We can do it after we merge 3.32.", "positive_passages": [{"docid": "doc-en-nixpkgs-929e4137d0e0a11a5b562d3bfc08a6f30e4795606448b17d6953eeaec68c5e47", "text": "# Thumbnailers (for setting user profile pictures) --prefix XDG_DATA_DIRS : \"${gdk_pixbuf}/share\" --prefix XDG_DATA_DIRS : \"${librsvg}/share\" # WM keyboard shortcuts --prefix XDG_DATA_DIRS : \"${mutter}/share\" ) for i in $out/share/applications/*; do substituteInPlace $i --replace \"Exec=gnome-control-center\" \"Exec=$out/bin/gnome-control-center\"", "commid": "nixpkgs_pr_59765"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-5ea7c5b8568434184f062601f7488cba89992adc1c38d36d2ba96ecf108e03fe", "query": "On current , (4.2.4) group voice chat will be stuck on \"connecting\" forever, while private group voice works. This issue exists when connecting from different countries, using different account, with or without proxy, so it seems not really a \"connection issue\". a voice chat in a private group. it stuck on \"connecting\" phase forever. Successfully starts or joins a voice chat. chat and live stream are broken. (one to one) voice chat works without issues. 's version of telegram works. (Its font is broken though) Please run and paste the result.", "positive_passages": [{"docid": "doc-en-nixpkgs-feaec37059e51bc1c5cc96bbd0af333eb885092e48adfff6de4807a81cda0b86", "text": "{ lib, stdenv, fetchFromGitHub , pkg-config, cmake, ninja, yasm , libjpeg, openssl, libopus, ffmpeg, alsa-lib, libpulseaudio, protobuf , libjpeg, openssl_1_1, libopus, ffmpeg, alsa-lib, libpulseaudio, protobuf , openh264, usrsctp, libevent, libvpx , libX11, libXtst, libXcomposite, libXdamage, libXext, libXrender, libXrandr, libXi , glib, abseil-cpp, pcre, util-linuxMinimal, libselinux, libsepol, pipewire", "commid": "nixpkgs_pr_196249"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-5ea7c5b8568434184f062601f7488cba89992adc1c38d36d2ba96ecf108e03fe", "query": "On current , (4.2.4) group voice chat will be stuck on \"connecting\" forever, while private group voice works. This issue exists when connecting from different countries, using different account, with or without proxy, so it seems not really a \"connection issue\". a voice chat in a private group. it stuck on \"connecting\" phase forever. Successfully starts or joins a voice chat. chat and live stream are broken. (one to one) voice chat works without issues. 's version of telegram works. (Its font is broken though) Please run and paste the result.", "positive_passages": [{"docid": "doc-en-nixpkgs-347eef6d1701a0708be44cc0656af40d7fa0f1b925a194ef5c1e1d29a4391cd3", "text": "nativeBuildInputs = [ pkg-config cmake ninja yasm ]; buildInputs = [ libjpeg openssl libopus ffmpeg alsa-lib libpulseaudio protobuf libjpeg libopus ffmpeg alsa-lib libpulseaudio protobuf openh264 usrsctp libevent libvpx libX11 libXtst libXcomposite libXdamage libXext libXrender libXrandr libXi glib abseil-cpp pcre util-linuxMinimal libselinux libsepol pipewire", "commid": "nixpkgs_pr_196249"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-5ea7c5b8568434184f062601f7488cba89992adc1c38d36d2ba96ecf108e03fe", "query": "On current , (4.2.4) group voice chat will be stuck on \"connecting\" forever, while private group voice works. This issue exists when connecting from different countries, using different account, with or without proxy, so it seems not really a \"connection issue\". a voice chat in a private group. it stuck on \"connecting\" phase forever. Successfully starts or joins a voice chat. chat and live stream are broken. (one to one) voice chat works without issues. 's version of telegram works. (Its font is broken though) Please run and paste the result.", "positive_passages": [{"docid": "doc-en-nixpkgs-477b938e4972aff86c8f1f375b04cb3af4c86ada6a9a525f743368ded7992113", "text": "propagatedBuildInputs = [ # Required for linking downstream binaries. abseil-cpp openh264 usrsctp libevent libvpx abseil-cpp openh264 usrsctp libevent libvpx openssl_1_1 ]; meta = with lib; {", "commid": "nixpkgs_pr_196249"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-8982b9473e513a1ab33ffd8d8b8d6063a3da275a6b4c40468141ba3c2bd1603e", "query": "Try building\nJust ran into the same problem when updating my system flake. For bisecting purposes, nixpkgs was my previous (working) configuration. EDIT: bisection in progress, have to do some large builds now:\nExcerpt from : which seems to be the change that breaks , so we probably need to file an upstream issue.\nAs a workaround, something like this should work:\nNote that the downgrade would undo some security fixes; see PR ... which is also why we backported this problem to 22.05.\nI see...I'll wait to re-enable qtile then\nDepending on how much value you place on the failing test, something like this worked for me: Modifying the package in a general overlay triggered huge rebuilds for me, so I've just replaced it inside my derivation, which is what pulls in in my system configuration.\nHow would you modify the package with a general overlay? Something like this didn't work for me:\nThis global overlay works for me, without annoying rebuilds: Note, I'm using and this is imported in . I don't know if you can use it without modifications otherwise.\nI have a similar setup, I have (minus the let bindings I have in my config): So I don't see the difference between our configs...\nSomehow, the overlay proposed by worked. This reaches about the limits of my Nix knowledge, but maybe is required instead of simply ? Is the only difference I can notice.", "positive_passages": [{"docid": "doc-en-nixpkgs-bba2c96f94c68596d7d9e6f438a5c66b715e277ce81dbd0fff2dd6a8fe0bd25b", "text": "]; # test_peer_interface hits a timeout # test_tcp_connection_with_forwarding fails due to dbus # creating unix socket anyway on v1.14.4 checkPhase = '' dbus-run-session --config-file=${dbus.daemon}/share/dbus-1/session.conf ${python.interpreter} -m pytest -sv --cov=dbus_next -k \"not test_peer_interface\" -k \"not test_peer_interface and not test_tcp_connection_with_forwarding\" ''; meta = with lib; {", "commid": "nixpkgs_pr_197968"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-8795d6d32e58f9507757b4816eaf917f27f7e8966a10da5892f6750c108b6fac", "query": "When one installs mastodon via the following minimal config: Then there is no obvious way to run tootctl. or any other login user doesn't have the executable by default, nor can this be enabled in an obvious way. is not a login user, so can't (and shouldn't?) log in as and execute . Steps to reproduce the behavior: mastodon as per minimal config above ... nope. ... nope. ... nope. ... nope. Any of: a setting such that is installed for that user an explanation in the docs what to do as a login user (probably bad idea?) Workaround: CC\nI think upstream intends only to be run by the mastodon user. My way for doing that is just running and continuing in that shell. The reason why doesn't work is probably because sudo inherits PATH from the user you are coming from? I'm not sure I understand the concept of a login user enough. How would mastodon become a login user and why would that be a bad idea?\nIn the mastodon docs, it is described the following way: But is not possible, it gives the error They do recommend (which is what I meant by it shouldn't be a login user), but still they seem to do something different than nixos does. Maybe that's fine, and it would be helpful to document this somewhere, so people don't spend a long time trying to find it out.\nThis is default for almost all service users because they have no login shell. Use ` This is wrong. Sudo resets all path like variables like PATH and PYTHON PATH. Also inheriting needs to be turned on explicitly and PATH mist always ve inherited explicitly. Other services like nextcloud include a wrapper that sudos to the right user. This should be for mastodon, too.\nSounds like a good solution. Then we could make the command globally available.\nThat isn't? I would have expected that it is very similar to nextcloud-occ.\nNo currently it is only available to the mastodon user, so tootctl never gets called as the wrong user.\nThere is a hack in the nixos nextcloud-occ script that automatically sudoes if called by a different user. This could be adapted to tootctl I think.\nYes, this should be adapted. Changing the mastodon to a login user would not be the correct fix.", "positive_passages": [{"docid": "doc-en-nixpkgs-71b7d6cd08d10a2d2831bf843659617312d897231bc8ebb2c25043e2b32101a3", "text": " services.mastodon gained a tootctl wrapped named mastodon-tootctl similar to nextcloud-occ which can be executed from any user and switches to the configured mastodon user with sudo and sources the environment variables. A new virtualisation.rosetta module was added to allow running x86_64 binaries through", "commid": "nixpkgs_pr_203825"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-8795d6d32e58f9507757b4816eaf917f27f7e8966a10da5892f6750c108b6fac", "query": "When one installs mastodon via the following minimal config: Then there is no obvious way to run tootctl. or any other login user doesn't have the executable by default, nor can this be enabled in an obvious way. is not a login user, so can't (and shouldn't?) log in as and execute . Steps to reproduce the behavior: mastodon as per minimal config above ... nope. ... nope. ... nope. ... nope. Any of: a setting such that is installed for that user an explanation in the docs what to do as a login user (probably bad idea?) Workaround: CC\nI think upstream intends only to be run by the mastodon user. My way for doing that is just running and continuing in that shell. The reason why doesn't work is probably because sudo inherits PATH from the user you are coming from? I'm not sure I understand the concept of a login user enough. How would mastodon become a login user and why would that be a bad idea?\nIn the mastodon docs, it is described the following way: But is not possible, it gives the error They do recommend (which is what I meant by it shouldn't be a login user), but still they seem to do something different than nixos does. Maybe that's fine, and it would be helpful to document this somewhere, so people don't spend a long time trying to find it out.\nThis is default for almost all service users because they have no login shell. Use ` This is wrong. Sudo resets all path like variables like PATH and PYTHON PATH. Also inheriting needs to be turned on explicitly and PATH mist always ve inherited explicitly. Other services like nextcloud include a wrapper that sudos to the right user. This should be for mastodon, too.\nSounds like a good solution. Then we could make the command globally available.\nThat isn't? I would have expected that it is very similar to nextcloud-occ.\nNo currently it is only available to the mastodon user, so tootctl never gets called as the wrong user.\nThere is a hack in the nixos nextcloud-occ script that automatically sudoes if called by a different user. This could be adapted to tootctl I think.\nYes, this should be adapted. Changing the mastodon to a login user would not be the correct fix.", "positive_passages": [{"docid": "doc-en-nixpkgs-202edaecb341b68cfab4f7bc372287e6cc0d93299852f3a4cc1147aaed8c3e3b", "text": "- The module for the application firewall `opensnitch` got the ability to configure rules. Available as [services.opensnitch.rules](#opt-services.opensnitch.rules) - `services.mastodon` gained a tootctl wrapped named `mastodon-tootctl` similar to `nextcloud-occ` which can be executed from any user and switches to the configured mastodon user with sudo and sources the environment variables. - A new `virtualisation.rosetta` module was added to allow running `x86_64` binaries through [Rosetta](https://developer.apple.com/documentation/apple-silicon/about-the-rosetta-translation-environment) inside virtualised NixOS guests on Apple silicon. This feature works by default with the [UTM](https://docs.getutm.app/) virtualisation [package](https://search.nixos.org/packages?channel=unstable&show=utm&from=0&size=1&sort=relevance&type=packages&query=utm).", "commid": "nixpkgs_pr_203825"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-8795d6d32e58f9507757b4816eaf917f27f7e8966a10da5892f6750c108b6fac", "query": "When one installs mastodon via the following minimal config: Then there is no obvious way to run tootctl. or any other login user doesn't have the executable by default, nor can this be enabled in an obvious way. is not a login user, so can't (and shouldn't?) log in as and execute . Steps to reproduce the behavior: mastodon as per minimal config above ... nope. ... nope. ... nope. ... nope. Any of: a setting such that is installed for that user an explanation in the docs what to do as a login user (probably bad idea?) Workaround: CC\nI think upstream intends only to be run by the mastodon user. My way for doing that is just running and continuing in that shell. The reason why doesn't work is probably because sudo inherits PATH from the user you are coming from? I'm not sure I understand the concept of a login user enough. How would mastodon become a login user and why would that be a bad idea?\nIn the mastodon docs, it is described the following way: But is not possible, it gives the error They do recommend (which is what I meant by it shouldn't be a login user), but still they seem to do something different than nixos does. Maybe that's fine, and it would be helpful to document this somewhere, so people don't spend a long time trying to find it out.\nThis is default for almost all service users because they have no login shell. Use ` This is wrong. Sudo resets all path like variables like PATH and PYTHON PATH. Also inheriting needs to be turned on explicitly and PATH mist always ve inherited explicitly. Other services like nextcloud include a wrapper that sudos to the right user. This should be for mastodon, too.\nSounds like a good solution. Then we could make the command globally available.\nThat isn't? I would have expected that it is very similar to nextcloud-occ.\nNo currently it is only available to the mastodon user, so tootctl never gets called as the wrong user.\nThere is a hack in the nixos nextcloud-occ script that automatically sudoes if called by a different user. This could be adapted to tootctl I think.\nYes, this should be adapted. Changing the mastodon to a login user would not be the correct fix.", "positive_passages": [{"docid": "doc-en-nixpkgs-91a6be7a9024e1631aa5f00a55eeb41d2df36f0a2f3c6ebddef4157db9cb4792", "text": "] else [] ) env)))); mastodonEnv = pkgs.writeShellScriptBin \"mastodon-env\" '' mastodonTootctl = pkgs.writeShellScriptBin \"mastodon-tootctl\" '' #! ${pkgs.runtimeShell} set -a export RAILS_ROOT=\"${cfg.package}\" source \"${envFile}\" source /var/lib/mastodon/.secrets_env eval -- \"$@\" sudo=exec if [[ \"$USER\" != ${cfg.user} ]]; then sudo='exec /run/wrappers/bin/sudo -u ${cfg.user} --preserve-env' fi $sudo ${cfg.package}/bin/tootctl \"$@\" ''; in {", "commid": "nixpkgs_pr_203825"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-8795d6d32e58f9507757b4816eaf917f27f7e8966a10da5892f6750c108b6fac", "query": "When one installs mastodon via the following minimal config: Then there is no obvious way to run tootctl. or any other login user doesn't have the executable by default, nor can this be enabled in an obvious way. is not a login user, so can't (and shouldn't?) log in as and execute . Steps to reproduce the behavior: mastodon as per minimal config above ... nope. ... nope. ... nope. ... nope. Any of: a setting such that is installed for that user an explanation in the docs what to do as a login user (probably bad idea?) Workaround: CC\nI think upstream intends only to be run by the mastodon user. My way for doing that is just running and continuing in that shell. The reason why doesn't work is probably because sudo inherits PATH from the user you are coming from? I'm not sure I understand the concept of a login user enough. How would mastodon become a login user and why would that be a bad idea?\nIn the mastodon docs, it is described the following way: But is not possible, it gives the error They do recommend (which is what I meant by it shouldn't be a login user), but still they seem to do something different than nixos does. Maybe that's fine, and it would be helpful to document this somewhere, so people don't spend a long time trying to find it out.\nThis is default for almost all service users because they have no login shell. Use ` This is wrong. Sudo resets all path like variables like PATH and PYTHON PATH. Also inheriting needs to be turned on explicitly and PATH mist always ve inherited explicitly. Other services like nextcloud include a wrapper that sudos to the right user. This should be for mastodon, too.\nSounds like a good solution. Then we could make the command globally available.\nThat isn't? I would have expected that it is very similar to nextcloud-occ.\nNo currently it is only available to the mastodon user, so tootctl never gets called as the wrong user.\nThere is a hack in the nixos nextcloud-occ script that automatically sudoes if called by a different user. This could be adapted to tootctl I think.\nYes, this should be adapted. Changing the mastodon to a login user would not be the correct fix.", "positive_passages": [{"docid": "doc-en-nixpkgs-c3be1d0c0d333078a74b81f19a0c2269a510a84c70262a19c9e67dea7583922b", "text": "description = lib.mdDoc '' User under which mastodon runs. If it is set to \"mastodon\", that user will be created, otherwise it should be set to the name of a user created elsewhere. In both cases, `mastodon` and a package containing only the shell script `mastodon-env` will be added to the user's package set. To run a command from `mastodon` such as `tootctl` with the environment configured by this module use `mastodon-env`, as in: `mastodon-env tootctl accounts create newuser --email newuser@example.com` name of a user created elsewhere. In both cases, the `mastodon` package will be added to the user's package set and a tootctl wrapper to system packages that switches to the configured account and load the right environment. ''; type = lib.types.str; default = \"mastodon\";", "commid": "nixpkgs_pr_203825"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-8795d6d32e58f9507757b4816eaf917f27f7e8966a10da5892f6750c108b6fac", "query": "When one installs mastodon via the following minimal config: Then there is no obvious way to run tootctl. or any other login user doesn't have the executable by default, nor can this be enabled in an obvious way. is not a login user, so can't (and shouldn't?) log in as and execute . Steps to reproduce the behavior: mastodon as per minimal config above ... nope. ... nope. ... nope. ... nope. Any of: a setting such that is installed for that user an explanation in the docs what to do as a login user (probably bad idea?) Workaround: CC\nI think upstream intends only to be run by the mastodon user. My way for doing that is just running and continuing in that shell. The reason why doesn't work is probably because sudo inherits PATH from the user you are coming from? I'm not sure I understand the concept of a login user enough. How would mastodon become a login user and why would that be a bad idea?\nIn the mastodon docs, it is described the following way: But is not possible, it gives the error They do recommend (which is what I meant by it shouldn't be a login user), but still they seem to do something different than nixos does. Maybe that's fine, and it would be helpful to document this somewhere, so people don't spend a long time trying to find it out.\nThis is default for almost all service users because they have no login shell. Use ` This is wrong. Sudo resets all path like variables like PATH and PYTHON PATH. Also inheriting needs to be turned on explicitly and PATH mist always ve inherited explicitly. Other services like nextcloud include a wrapper that sudos to the right user. This should be for mastodon, too.\nSounds like a good solution. Then we could make the command globally available.\nThat isn't? I would have expected that it is very similar to nextcloud-occ.\nNo currently it is only available to the mastodon user, so tootctl never gets called as the wrong user.\nThere is a hack in the nixos nextcloud-occ script that automatically sudoes if called by a different user. This could be adapted to tootctl I think.\nYes, this should be adapted. Changing the mastodon to a login user would not be the correct fix.", "positive_passages": [{"docid": "doc-en-nixpkgs-c7cdddaa785c8f7eed3569a2beaa6854935d75374f7f03d89a0bbe0058b12c1d", "text": "} ]; environment.systemPackages = [ mastodonTootctl ]; systemd.services.mastodon-init-dirs = { script = '' umask 077", "commid": "nixpkgs_pr_203825"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-8795d6d32e58f9507757b4816eaf917f27f7e8966a10da5892f6750c108b6fac", "query": "When one installs mastodon via the following minimal config: Then there is no obvious way to run tootctl. or any other login user doesn't have the executable by default, nor can this be enabled in an obvious way. is not a login user, so can't (and shouldn't?) log in as and execute . Steps to reproduce the behavior: mastodon as per minimal config above ... nope. ... nope. ... nope. ... nope. Any of: a setting such that is installed for that user an explanation in the docs what to do as a login user (probably bad idea?) Workaround: CC\nI think upstream intends only to be run by the mastodon user. My way for doing that is just running and continuing in that shell. The reason why doesn't work is probably because sudo inherits PATH from the user you are coming from? I'm not sure I understand the concept of a login user enough. How would mastodon become a login user and why would that be a bad idea?\nIn the mastodon docs, it is described the following way: But is not possible, it gives the error They do recommend (which is what I meant by it shouldn't be a login user), but still they seem to do something different than nixos does. Maybe that's fine, and it would be helpful to document this somewhere, so people don't spend a long time trying to find it out.\nThis is default for almost all service users because they have no login shell. Use ` This is wrong. Sudo resets all path like variables like PATH and PYTHON PATH. Also inheriting needs to be turned on explicitly and PATH mist always ve inherited explicitly. Other services like nextcloud include a wrapper that sudos to the right user. This should be for mastodon, too.\nSounds like a good solution. Then we could make the command globally available.\nThat isn't? I would have expected that it is very similar to nextcloud-occ.\nNo currently it is only available to the mastodon user, so tootctl never gets called as the wrong user.\nThere is a hack in the nixos nextcloud-occ script that automatically sudoes if called by a different user. This could be adapted to tootctl I think.\nYes, this should be adapted. Changing the mastodon to a login user would not be the correct fix.", "positive_passages": [{"docid": "doc-en-nixpkgs-6c7ac9f7987825ee7126d48c6054ef5836679f4f4f11f8b29db5964ce7de9839", "text": "inherit (cfg) group; }; }) (lib.attrsets.setAttrByPath [ cfg.user \"packages\" ] [ cfg.package mastodonEnv pkgs.imagemagick ]) (lib.attrsets.setAttrByPath [ cfg.user \"packages\" ] [ cfg.package pkgs.imagemagick ]) ]; users.groups.${cfg.group}.members = lib.optional cfg.configureNginx config.services.nginx.user;", "commid": "nixpkgs_pr_203825"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-8795d6d32e58f9507757b4816eaf917f27f7e8966a10da5892f6750c108b6fac", "query": "When one installs mastodon via the following minimal config: Then there is no obvious way to run tootctl. or any other login user doesn't have the executable by default, nor can this be enabled in an obvious way. is not a login user, so can't (and shouldn't?) log in as and execute . Steps to reproduce the behavior: mastodon as per minimal config above ... nope. ... nope. ... nope. ... nope. Any of: a setting such that is installed for that user an explanation in the docs what to do as a login user (probably bad idea?) Workaround: CC\nI think upstream intends only to be run by the mastodon user. My way for doing that is just running and continuing in that shell. The reason why doesn't work is probably because sudo inherits PATH from the user you are coming from? I'm not sure I understand the concept of a login user enough. How would mastodon become a login user and why would that be a bad idea?\nIn the mastodon docs, it is described the following way: But is not possible, it gives the error They do recommend (which is what I meant by it shouldn't be a login user), but still they seem to do something different than nixos does. Maybe that's fine, and it would be helpful to document this somewhere, so people don't spend a long time trying to find it out.\nThis is default for almost all service users because they have no login shell. Use ` This is wrong. Sudo resets all path like variables like PATH and PYTHON PATH. Also inheriting needs to be turned on explicitly and PATH mist always ve inherited explicitly. Other services like nextcloud include a wrapper that sudos to the right user. This should be for mastodon, too.\nSounds like a good solution. Then we could make the command globally available.\nThat isn't? I would have expected that it is very similar to nextcloud-occ.\nNo currently it is only available to the mastodon user, so tootctl never gets called as the wrong user.\nThere is a hack in the nixos nextcloud-occ script that automatically sudoes if called by a different user. This could be adapted to tootctl I think.\nYes, this should be adapted. Changing the mastodon to a login user would not be the correct fix.", "positive_passages": [{"docid": "doc-en-nixpkgs-4e25689157a036219e6387c925413896a81fef18d59bb907db05c70d44427ecb", "text": "# Simple check tootctl commands # Check Mastodon version server.succeed(\"su - mastodon -s /bin/sh -c 'mastodon-env tootctl version' | grep '${pkgs.mastodon.version}'\") server.succeed(\"mastodon-tootctl version | grep '${pkgs.mastodon.version}'\") # Manage accounts server.succeed(\"su - mastodon -s /bin/sh -c 'mastodon-env tootctl email_domain_blocks add example.com'\") server.succeed(\"su - mastodon -s /bin/sh -c 'mastodon-env tootctl email_domain_blocks list' | grep 'example.com'\") server.fail(\"su - mastodon -s /bin/sh -c 'mastodon-env tootctl email_domain_blocks list' | grep 'mastodon.local'\") server.fail(\"su - mastodon -s /bin/sh -c 'mastodon-env tootctl accounts create alice --email=alice@example.com'\") server.succeed(\"su - mastodon -s /bin/sh -c 'mastodon-env tootctl email_domain_blocks remove example.com'\") server.succeed(\"su - mastodon -s /bin/sh -c 'mastodon-env tootctl accounts create bob --email=bob@example.com'\") server.succeed(\"su - mastodon -s /bin/sh -c 'mastodon-env tootctl accounts approve bob'\") server.succeed(\"su - mastodon -s /bin/sh -c 'mastodon-env tootctl accounts delete bob'\") server.succeed(\"mastodon-tootctl email_domain_blocks add example.com\") server.succeed(\"mastodon-tootctl email_domain_blocks list | grep example.com\") server.fail(\"mastodon-tootctl email_domain_blocks list | grep mastodon.local\") server.fail(\"mastodon-tootctl accounts create alice --email=alice@example.com\") server.succeed(\"mastodon-tootctl email_domain_blocks remove example.com\") server.succeed(\"mastodon-tootctl accounts create bob --email=bob@example.com\") server.succeed(\"mastodon-tootctl accounts approve bob\") server.succeed(\"mastodon-tootctl accounts delete bob\") # Manage IP access server.succeed(\"su - mastodon -s /bin/sh -c 'mastodon-env tootctl ip_blocks add 192.168.0.0/16 --severity=no_access'\") server.succeed(\"su - mastodon -s /bin/sh -c 'mastodon-env tootctl ip_blocks export' | grep '192.168.0.0/16'\") server.fail(\"su - mastodon -s /bin/sh -c 'mastodon-env tootctl ip_blocks export' | grep '172.16.0.0/16'\") server.succeed(\"mastodon-tootctl ip_blocks add 192.168.0.0/16 --severity=no_access\") server.succeed(\"mastodon-tootctl ip_blocks export | grep 192.168.0.0/16\") server.fail(\"mastodon-tootctl ip_blocks export | grep 172.16.0.0/16\") client.fail(\"curl --fail https://mastodon.local/about\") server.succeed(\"su - mastodon -s /bin/sh -c 'mastodon-env tootctl ip_blocks remove 192.168.0.0/16'\") server.succeed(\"mastodon-tootctl ip_blocks remove 192.168.0.0/16\") client.succeed(\"curl --fail https://mastodon.local/about\") server.shutdown()", "commid": "nixpkgs_pr_203825"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-9f348d988efbd12c01214e8e8eeab863226e4a490317b78b7bc54f8b4097c506", "query": "When exporting the graph, logseq throws a permission exception. Steps to reproduce the behavior: a new graph a few pages them public ()) the graph The graph should successfully export and opening it should show a read-only view of the graph. The logseq documentation itself is an example thereof. If applicable, add screenshots to help explain your problem. Bug was first reported in the original repo When running the AppImage with it's fine because it's extracted into , but when the app is in then it won't work because of the read-only status. I tested the flatpak version because I suspected the same problem would occur, but the directories are mounted read-write in a read-only volume. So, 2 options exist as I see it: fix it upstream, but I don't know Clojure nor Electron start the AppImage with instead of extracting it Please run and paste the result.", "positive_passages": [{"docid": "doc-en-nixpkgs-1a2b023be06625d4253997a8e2a1ab84ce6c3a6fefa2ed62c074c88de9387c94", "text": ", stdenv , fetchurl , appimageTools , appimage-run , makeWrapper , electron , git }:", "commid": "nixpkgs_pr_205057"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-9f348d988efbd12c01214e8e8eeab863226e4a490317b78b7bc54f8b4097c506", "query": "When exporting the graph, logseq throws a permission exception. Steps to reproduce the behavior: a new graph a few pages them public ()) the graph The graph should successfully export and opening it should show a read-only view of the graph. The logseq documentation itself is an example thereof. If applicable, add screenshots to help explain your problem. Bug was first reported in the original repo When running the AppImage with it's fine because it's extracted into , but when the app is in then it won't work because of the read-only status. I tested the flatpak version because I suspected the same problem would occur, but the directories are mounted read-write in a read-only volume. So, 2 options exist as I see it: fix it upstream, but I don't know Clojure nor Electron start the AppImage with instead of extracting it Please run and paste the result.", "positive_passages": [{"docid": "doc-en-nixpkgs-b3bb5bb65186454db30040bfa8009f8924c6a3842227452c884874d54c4a814c", "text": "installPhase = '' runHook preInstall mkdir -p $out/bin $out/share/${pname} $out/share/applications cp -a ${appimageContents}/{locales,resources} $out/share/${pname} mkdir -p $out/bin $out/share/${pname} $out/share/applications $out/share/${pname}/resources/app/icons cp -a ${appimageContents}/resources/app/icons/logseq.png $out/share/${pname}/resources/app/icons/logseq.png cp -a ${appimageContents}/Logseq.desktop $out/share/applications/${pname}.desktop # remove the `git` in `dugite` because we want the `git` in `nixpkgs` chmod +w -R $out/share/${pname}/resources/app/node_modules/dugite/git chmod +w $out/share/${pname}/resources/app/node_modules/dugite rm -rf $out/share/${pname}/resources/app/node_modules/dugite/git chmod -w $out/share/${pname}/resources/app/node_modules/dugite # set the env \"LOCAL_GIT_DIRECTORY\" for dugite so that we can use the git in nixpkgs makeWrapper ${appimage-run}/bin/appimage-run $out/bin/logseq --set \"LOCAL_GIT_DIRECTORY\" ${git} --add-flags ${src} # Make the desktop entry run the app using appimage-run substituteInPlace $out/share/applications/${pname}.desktop --replace Exec=Logseq Exec=${pname} --replace Exec=Logseq \"Exec=$out/bin/logseq\" --replace Icon=Logseq Icon=$out/share/${pname}/resources/app/icons/logseq.png runHook postInstall ''; postFixup = '' # set the env \"LOCAL_GIT_DIRECTORY\" for dugite so that we can use the git in nixpkgs makeWrapper ${electron}/bin/electron $out/bin/${pname} --set \"LOCAL_GIT_DIRECTORY\" ${git} --add-flags $out/share/${pname}/resources/app ''; passthru.updateScript = ./update.sh; meta = with lib; {", "commid": "nixpkgs_pr_205057"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-9f348d988efbd12c01214e8e8eeab863226e4a490317b78b7bc54f8b4097c506", "query": "When exporting the graph, logseq throws a permission exception. Steps to reproduce the behavior: a new graph a few pages them public ()) the graph The graph should successfully export and opening it should show a read-only view of the graph. The logseq documentation itself is an example thereof. If applicable, add screenshots to help explain your problem. Bug was first reported in the original repo When running the AppImage with it's fine because it's extracted into , but when the app is in then it won't work because of the read-only status. I tested the flatpak version because I suspected the same problem would occur, but the directories are mounted read-write in a read-only volume. So, 2 options exist as I see it: fix it upstream, but I don't know Clojure nor Electron start the AppImage with instead of extracting it Please run and paste the result.", "positive_passages": [{"docid": "doc-en-nixpkgs-2400b6b8391fa057bb39991dcedd78f956878c7d952661af4092e17d143f5569", "text": "lilo = callPackage ../tools/misc/lilo { }; logseq = callPackage ../applications/misc/logseq { electron = electron_20; }; logseq = callPackage ../applications/misc/logseq { }; natls = callPackage ../tools/misc/natls { };", "commid": "nixpkgs_pr_205057"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-6b27e99607c9b09248b1e172673e899c8a590a0c0624774177a302b77cb91910", "query": "On my M1 Mac, with homebrew-installed libvirt / qemu-system-aarch64, I'm able to run the VM defined in the config below without issue. However with libvirt / qemu installed via nix, I get: Some possibly related discussion . Looking at the , they're explicitly setting ; adding this seems to resolve the issue: I'm not sure whether disabling those failing tests is a reasonable thing to do. Steps to reproduce the behavior: to in A clear and concise description of what you expected to happen. Should run without , like it does with homebrew. Please run and paste the result.\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nFWIW, I also encountered this issue, and have to use the following workaround: And -ing the efi firmware & vars manually. Fixing this bug can lead to great user experience: virt-manager can work out of box.\nWhere did you get ?", "positive_passages": [{"docid": "doc-en-nixpkgs-e8f2849d9e60d47e6d20f3737b7cd8e45f21ae451b255a81a02f853eb419e6bc", "text": "# Darwin , gmp , libiconv , qemu , Carbon , AppKit", "commid": "nixpkgs_pr_200106"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-6b27e99607c9b09248b1e172673e899c8a590a0c0624774177a302b77cb91910", "query": "On my M1 Mac, with homebrew-installed libvirt / qemu-system-aarch64, I'm able to run the VM defined in the config below without issue. However with libvirt / qemu installed via nix, I get: Some possibly related discussion . Looking at the , they're explicitly setting ; adding this seems to resolve the issue: I'm not sure whether disabling those failing tests is a reasonable thing to do. Steps to reproduce the behavior: to in A clear and concise description of what you expected to happen. Should run without , like it does with homebrew. Please run and paste the result.\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nFWIW, I also encountered this issue, and have to use the following workaround: And -ing the efi firmware & vars manually. Fixing this bug can lead to great user experience: virt-manager can work out of box.\nWhere did you get ?", "positive_passages": [{"docid": "doc-en-nixpkgs-320cec219edd64ec2b6c7254bb1189369457feda05bfbe418244a8426a1ae409", "text": "'' + optionalString isDarwin '' sed -i '/qemucapabilitiestest/d' tests/meson.build sed -i '/vircryptotest/d' tests/meson.build sed -i '/domaincapstest/d' tests/meson.build sed -i '/qemufirmwaretest/d' tests/meson.build sed -i '/qemuvhostusertest/d' tests/meson.build '' + optionalString (isDarwin && isx86_64) '' sed -i '/qemucaps2xmltest/d' tests/meson.build sed -i '/qemuhotplugtest/d' tests/meson.build", "commid": "nixpkgs_pr_200106"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-6b27e99607c9b09248b1e172673e899c8a590a0c0624774177a302b77cb91910", "query": "On my M1 Mac, with homebrew-installed libvirt / qemu-system-aarch64, I'm able to run the VM defined in the config below without issue. However with libvirt / qemu installed via nix, I get: Some possibly related discussion . Looking at the , they're explicitly setting ; adding this seems to resolve the issue: I'm not sure whether disabling those failing tests is a reasonable thing to do. Steps to reproduce the behavior: to in A clear and concise description of what you expected to happen. Should run without , like it does with homebrew. Please run and paste the result.\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nFWIW, I also encountered this issue, and have to use the following workaround: And -ing the efi firmware & vars manually. Fixing this bug can lead to great user experience: virt-manager can work out of box.\nWhere did you get ?", "positive_passages": [{"docid": "doc-en-nixpkgs-85d214d016c26f3a2db8045b6996abadf2745b9bf82068859f70cdb57d4b4895", "text": "(cfg \"runstatedir\" \"/run\") (cfg \"init_script\" (if isDarwin then \"none\" else \"systemd\")) (cfg \"qemu_datadir\" (if isDarwin then \"${qemu}/share/qemu\" else \"\")) (feat \"apparmor\" isLinux) (feat \"attr\" isLinux)", "commid": "nixpkgs_pr_200106"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-482fd8673585fe7c98847de5ccf84a66b96737eaaa047ef4db0c5870bd3fde7c", "query": "To reproduce, here is an example: The related code is at Some nice to have: As suggested should be something that can be accessible by everything and we are likely going to put our \"\" there and next we are going to import in basically every file. Adding to in is probably not a good idea since this is a desktop shell package you will end up having this variable everywhere, I imagine a treewide will be likely needed.", "positive_passages": [{"docid": "doc-en-nixpkgs-c101c1da3d2151d80880b08170d7827fec81340e6f898a232aec2ddf257d6f5d", "text": "python3.pkgs.buildPythonApplication rec { pname = \"sticky\"; version = \"1.14\"; version = \"1.16\"; format = \"other\"; src = fetchFromGitHub { owner = \"linuxmint\"; repo = pname; rev = version; hash = \"sha256-7UZbCbzQ1ZrSzxTUdbA+wsH3p27qj/c/cM4GY/kzG6E=\"; hash = \"sha256-+opzjvSdGwwn1imNzSsfD9rfs4naSXzcMBJRPhKW2WM=\"; }; postPatch = ''", "commid": "nixpkgs_pr_236641"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-482fd8673585fe7c98847de5ccf84a66b96737eaaa047ef4db0c5870bd3fde7c", "query": "To reproduce, here is an example: The related code is at Some nice to have: As suggested should be something that can be accessible by everything and we are likely going to put our \"\" there and next we are going to import in basically every file. Adding to in is probably not a good idea since this is a desktop shell package you will end up having this variable everywhere, I imagine a treewide will be likely needed.", "positive_passages": [{"docid": "doc-en-nixpkgs-e8a77a057df39be5c42fee1df6206c18a898d8a237f911b4504ace27e061170f", "text": "stdenv.mkDerivation rec { pname = \"bulky\"; version = \"2.8\"; version = \"2.9\"; src = fetchFromGitHub { owner = \"linuxmint\"; repo = \"bulky\"; rev = version; hash = \"sha256-DZjX4xPyA30TTyOX+VyGSY/FWPX2316CYImDWRma9r0=\"; hash = \"sha256-eCu7AgL4bzstu8vsqBJImRZm1qMVnnycuOShY5fB+C4=\"; }; nativeBuildInputs = [", "commid": "nixpkgs_pr_236641"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-482fd8673585fe7c98847de5ccf84a66b96737eaaa047ef4db0c5870bd3fde7c", "query": "To reproduce, here is an example: The related code is at Some nice to have: As suggested should be something that can be accessible by everything and we are likely going to put our \"\" there and next we are going to import in basically every file. Adding to in is probably not a good idea since this is a desktop shell package you will end up having this variable everywhere, I imagine a treewide will be likely needed.", "positive_passages": [{"docid": "doc-en-nixpkgs-1c06b3e08f6d28bdbbfb0ef8bdfc8fa5e015fff77c5413c43058133fb8f3599f", "text": "-e s,/usr/share/locale,/run/current-system/sw/share/locale,g {} + sed \"s|/usr/share/sounds|/run/current-system/sw/share/sounds|g\" -i ./files/usr/share/cinnamon/cinnamon-settings/bin/SettingsWidgets.py sed \"s|'python3'|'${pythonEnv.interpreter}'|g\" -i ./files/usr/share/cinnamon/cinnamon-settings/bin/CinnamonGtkSettings.py sed \"s|/usr/bin/cinnamon-screensaver-command|/run/current-system/sw/bin/cinnamon-screensaver-command|g\" -i ./files/usr/share/cinnamon/applets/menu@cinnamon.org/applet.js -i ./files/usr/share/cinnamon/applets/user@cinnamon.org/applet.js sed \"s|\"/usr/lib\"|\"${cinnamon-control-center}/lib\"|g\" -i ./files/usr/share/cinnamon/cinnamon-settings/bin/capi.py sed 's|\"lspci\"|\"${pciutils}/bin/lspci\"|g' -i ./files/usr/share/cinnamon/cinnamon-settings/modules/cs_info.py # All optional and may introduce circular dependency. find ./files/usr/share/cinnamon/applets -type f -exec sed -i -e '/^#/!s,/usr/bin,/run/current-system/sw/bin,g' {} + sed \"s| cinnamon-session| ${cinnamon-session}/bin/cinnamon-session|g\" -i ./files/usr/bin/cinnamon-session-cinnamon -i ./files/usr/bin/cinnamon-session-cinnamon2d pushd ./files/usr/share/cinnamon/cinnamon-settings substituteInPlace ./bin/capi.py --replace '\"/usr/lib\"' '\"${cinnamon-control-center}/lib\"' substituteInPlace ./bin/CinnamonGtkSettings.py --replace \"'python3'\" \"'${pythonEnv.interpreter}'\" substituteInPlace ./bin/SettingsWidgets.py --replace \"/usr/share/sounds\" \"/run/current-system/sw/share/sounds\" substituteInPlace ./bin/Spices.py --replace \"msgfmt\" \"${gettext}/bin/msgfmt\" substituteInPlace ./modules/cs_info.py --replace \"lspci\" \"${pciutils}/bin/lspci\" popd sed \"s|msgfmt|${gettext}/bin/msgfmt|g\" -i ./files/usr/share/cinnamon/cinnamon-settings/bin/Spices.py sed \"s| cinnamon-session| ${cinnamon-session}/bin/cinnamon-session|g\" -i ./files/usr/bin/cinnamon-session-{cinnamon,cinnamon2d} patchShebangs src/data-to-c.pl '';", "commid": "nixpkgs_pr_236641"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-482fd8673585fe7c98847de5ccf84a66b96737eaaa047ef4db0c5870bd3fde7c", "query": "To reproduce, here is an example: The related code is at Some nice to have: As suggested should be something that can be accessible by everything and we are likely going to put our \"\" there and next we are going to import in basically every file. Adding to in is probably not a good idea since this is a desktop shell package you will end up having this variable everywhere, I imagine a treewide will be likely needed.", "positive_passages": [{"docid": "doc-en-nixpkgs-1d41f908dfa7f09248c674e9efbcf5ea519dd4c14ed6a58be3e65ff907c4b763", "text": "--prefix XDG_DATA_DIRS : \"${gnome.caribou}/share\" ) buildPythonPath \"$out ${python3.pkgs.xapp}\" # https://github.com/NixOS/nixpkgs/issues/200397 patchPythonScript $out/bin/cinnamon-spice-updater # https://github.com/NixOS/nixpkgs/issues/129946 buildPythonPath \"${python3.pkgs.xapp}\" patchPythonScript $out/share/cinnamon/cinnamon-desktop-editor/cinnamon-desktop-editor.py # Called as `pkexec cinnamon-settings-users.py`. wrapGApp $out/share/cinnamon/cinnamon-settings-users/cinnamon-settings-users.py ''; passthru = {", "commid": "nixpkgs_pr_236641"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-482fd8673585fe7c98847de5ccf84a66b96737eaaa047ef4db0c5870bd3fde7c", "query": "To reproduce, here is an example: The related code is at Some nice to have: As suggested should be something that can be accessible by everything and we are likely going to put our \"\" there and next we are going to import in basically every file. Adding to in is probably not a good idea since this is a desktop shell package you will end up having this variable everywhere, I imagine a treewide will be likely needed.", "positive_passages": [{"docid": "doc-en-nixpkgs-388ecf87677dc818e8294b7520af2d840d66a08483cf948929a24114becce382", "text": "stdenvNoCC.mkDerivation rec { pname = \"mint-cursor-themes\"; version = \"1.0.1\"; version = \"1.0.2\"; src = fetchFromGitHub { owner = \"linuxmint\"; repo = pname; # They don't really do tags, this is just a named commit. rev = \"e17f8a4620827235dabbe5221bd0ee8c44dad0d5\"; hash = \"sha256-yLUmIVh884uDVkNil7qxf6t/gykipzBvPgzwmY3zvQk=\"; rev = \"d2c1428b499a347c291dafb13c89699fdbdd4be7\"; hash = \"sha256-i2Wf+OKwal9G5hkcAdmGSgX6txu1AHajqqPJdhpJoA0=\"; }; installPhase = ''", "commid": "nixpkgs_pr_236641"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-482fd8673585fe7c98847de5ccf84a66b96737eaaa047ef4db0c5870bd3fde7c", "query": "To reproduce, here is an example: The related code is at Some nice to have: As suggested should be something that can be accessible by everything and we are likely going to put our \"\" there and next we are going to import in basically every file. Adding to in is probably not a good idea since this is a desktop shell package you will end up having this variable everywhere, I imagine a treewide will be likely needed.", "positive_passages": [{"docid": "doc-en-nixpkgs-3241a4bfad7ad127d4dc43b6aafc453805ee190665e6c57bea2048772e4d09c2", "text": "in stdenv.mkDerivation rec { pname = \"warpinator\"; version = \"1.6.2\"; version = \"1.6.3\"; src = fetchFromGitHub { owner = \"linuxmint\"; repo = pname; rev = version; hash = \"sha256-crGW1FBfTEiKqx981EzG414we4icyBv/keGtMlr8UFc=\"; hash = \"sha256-iCq2cwZgsq5/bJqjYuZ6dZLqz2nIpgHCrIQeMVxJNXY=\"; }; nativeBuildInputs = [", "commid": "nixpkgs_pr_236641"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-482fd8673585fe7c98847de5ccf84a66b96737eaaa047ef4db0c5870bd3fde7c", "query": "To reproduce, here is an example: The related code is at Some nice to have: As suggested should be something that can be accessible by everything and we are likely going to put our \"\" there and next we are going to import in basically every file. Adding to in is probably not a good idea since this is a desktop shell package you will end up having this variable everywhere, I imagine a treewide will be likely needed.", "positive_passages": [{"docid": "doc-en-nixpkgs-8d5204b21dd8be8ab1de0e4cfa1c614133514df2926a03dfa44e94aa719100fc", "text": "# Patch pastebin & inxi location sed \"s|/usr/bin/pastebin|$out/bin/pastebin|\" -i scripts/upload-system-info sed \"s|'inxi'|'${inxi}/bin/inxi'|\" -i scripts/upload-system-info # Patch gtk3 module target dir substituteInPlace libxapp/meson.build --replace \"gtk3_dep.get_pkgconfig_variable('libdir')\" \"'$out'\" ''; # Fix gtk3 module target dir. Proper upstream solution should be using define_variable. PKG_CONFIG_GTK__3_0_LIBDIR = \"${placeholder \"out\"}/lib\"; meta = with lib; { homepage = \"https://github.com/linuxmint/xapp\"; description = \"Cross-desktop libraries and common resources\";", "commid": "nixpkgs_pr_236641"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-e4f4300eb1bd80ecd21fc0af2430b5787ac57f6d458483f50be3764ab76afc1e", "query": "When running , I get Restarting the system did not help. Steps to reproduce the behavior: The program should launch without crashing. If applicable, add screenshots to help explain your problem.\nHello Thanks for reporting this issue, and sorry for breaking the nvtop package! I made a pull-request to fix nvtop: What do you think about this fix?\nThank you for your fast reaction ! The PR looks good to me. I hope it will get merged soon :)", "positive_passages": [{"docid": "doc-en-nixpkgs-87ee931300c63b18c830370db6127b3998611660197d62a787eeaf8e7a68f0fa", "text": ", cudatoolkit , libdrm , ncurses , nvtop , testers , udev , addOpenGLRunpath , amd ? true , nvidia ? true , udev }: let pname-suffix = if amd && nvidia then \"\" else if amd then \"-amd\" else \"-nvidia\"; nvidia-postFixup = \"addOpenGLRunpath $out/bin/nvtop\"; libPath = lib.makeLibraryPath [ libdrm ncurses ]; libPath = lib.makeLibraryPath [ libdrm ncurses udev ]; amd-postFixup = '' patchelf --set-interpreter \"$(cat $NIX_CC/nix-support/dynamic-linker)\" ", "commid": "nixpkgs_pr_201557"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-e4f4300eb1bd80ecd21fc0af2430b5787ac57f6d458483f50be3764ab76afc1e", "query": "When running , I get Restarting the system did not help. Steps to reproduce the behavior: The program should launch without crashing. If applicable, add screenshots to help explain your problem.\nHello Thanks for reporting this issue, and sorry for breaking the nvtop package! I made a pull-request to fix nvtop: What do you think about this fix?\nThank you for your fast reaction ! The PR looks good to me. I hope it will get merged soon :)", "positive_passages": [{"docid": "doc-en-nixpkgs-d5421938381ba0b0b9305b8db896ba642a070b21991b484e99a3af15bf18bce8", "text": "cmakeFlags = with lib; [ \"-DCMAKE_BUILD_TYPE=Release\" \"-DBUILD_TESTING=ON\" \"-DUSE_LIBUDEV_OVER_LIBSYSTEMD=ON\" ] ++ optional nvidia \"-DNVML_INCLUDE_DIRS=${cudatoolkit}/include\" ++ optional nvidia \"-DNVML_LIBRARIES=${cudatoolkit}/targets/x86_64-linux/lib/stubs/libnvidia-ml.so\" ++ optional (!amd) \"-DAMDGPU_SUPPORT=OFF\"", "commid": "nixpkgs_pr_201557"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-e4f4300eb1bd80ecd21fc0af2430b5787ac57f6d458483f50be3764ab76afc1e", "query": "When running , I get Restarting the system did not help. Steps to reproduce the behavior: The program should launch without crashing. If applicable, add screenshots to help explain your problem.\nHello Thanks for reporting this issue, and sorry for breaking the nvtop package! I made a pull-request to fix nvtop: What do you think about this fix?\nThank you for your fast reaction ! The PR looks good to me. I hope it will get merged soon :)", "positive_passages": [{"docid": "doc-en-nixpkgs-ca831abc85892154a0a48fec01296c5d446fab6566a91416732ba0d6c0147d63", "text": "doCheck = true; passthru = { tests.version = testers.testVersion { inherit version; package = nvtop; command = \"nvtop --version\"; }; }; meta = with lib; { description = \"A (h)top like task monitor for AMD, Intel and NVIDIA GPUs\"; longDescription = ''", "commid": "nixpkgs_pr_201557"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-712d5b7f44df19162afcd5dbafa46ae6859ef7eb00cd5ca5240b0b590a30a6d3", "query": "pam_p11 causes login segfault in NixOS 22.11. GDM and Gnome lock screen are also affected. Steps to reproduce the behavior: to log in on the console or run `: Bug was not present in 22.05.\nReverting does not help.\nFixed by: Can someone with commit access apply this patch?\nCan you open a pull request with that patch?\nI hope that NixOS can be unbureaucratic enough that PRs are not required for this kind of patch.\nIt's generally preferred to do basically everything through PRs, so some basic CI checks can run & maintainers can be pinged automatically. We can just self-merge though. I created containing your diff and adding a comment for explanation.\nThis seems to be whats causing my 22.11-beta19 install on an Alder Lake 12700H (no gpu) to not boot into GDM. This is a pretty heinous issue that should be tested for. The graphical installer doesn't install Vim, WPA_Supplicant or anything useful for figuring out what went wrong, despite having Vim and WPA Supplicant available on the installation media/calamares.\nWell I just did - you're welcome. That's what beta releases are for, aren't they?", "positive_passages": [{"docid": "doc-en-nixpkgs-55d7b12d98670131e9f68d81d731f387883ae1445596519a0ba61e7bf83b5a0d", "text": "enableParallelBuilding = true; passthru = { inherit openssl; }; meta = with lib; { description = \"Small layer on top of PKCS#11 API to make PKCS#11 implementations easier\"; homepage = \"https://github.com/OpenSC/libp11\";", "commid": "nixpkgs_pr_202345"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-712d5b7f44df19162afcd5dbafa46ae6859ef7eb00cd5ca5240b0b590a30a6d3", "query": "pam_p11 causes login segfault in NixOS 22.11. GDM and Gnome lock screen are also affected. Steps to reproduce the behavior: to log in on the console or run `: Bug was not present in 22.05.\nReverting does not help.\nFixed by: Can someone with commit access apply this patch?\nCan you open a pull request with that patch?\nI hope that NixOS can be unbureaucratic enough that PRs are not required for this kind of patch.\nIt's generally preferred to do basically everything through PRs, so some basic CI checks can run & maintainers can be pinged automatically. We can just self-merge though. I created containing your diff and adding a comment for explanation.\nThis seems to be whats causing my 22.11-beta19 install on an Alder Lake 12700H (no gpu) to not boot into GDM. This is a pretty heinous issue that should be tested for. The graphical installer doesn't install Vim, WPA_Supplicant or anything useful for figuring out what went wrong, despite having Vim and WPA Supplicant available on the installation media/calamares.\nWell I just did - you're welcome. That's what beta releases are for, aren't they?", "positive_passages": [{"docid": "doc-en-nixpkgs-e965c8dd5e491d45ba405e4bfa5418ca80ccbcd8cf65228064fa55319bb086c6", "text": " { lib, stdenv, fetchFromGitHub, autoreconfHook, pkg-config, openssl, libp11, pam, libintl }: { lib, stdenv, fetchFromGitHub, autoreconfHook, pkg-config, libp11, pam, libintl }: stdenv.mkDerivation rec { pname = \"pam_p11\";", "commid": "nixpkgs_pr_202345"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-712d5b7f44df19162afcd5dbafa46ae6859ef7eb00cd5ca5240b0b590a30a6d3", "query": "pam_p11 causes login segfault in NixOS 22.11. GDM and Gnome lock screen are also affected. Steps to reproduce the behavior: to log in on the console or run `: Bug was not present in 22.05.\nReverting does not help.\nFixed by: Can someone with commit access apply this patch?\nCan you open a pull request with that patch?\nI hope that NixOS can be unbureaucratic enough that PRs are not required for this kind of patch.\nIt's generally preferred to do basically everything through PRs, so some basic CI checks can run & maintainers can be pinged automatically. We can just self-merge though. I created containing your diff and adding a comment for explanation.\nThis seems to be whats causing my 22.11-beta19 install on an Alder Lake 12700H (no gpu) to not boot into GDM. This is a pretty heinous issue that should be tested for. The graphical installer doesn't install Vim, WPA_Supplicant or anything useful for figuring out what went wrong, despite having Vim and WPA Supplicant available on the installation media/calamares.\nWell I just did - you're welcome. That's what beta releases are for, aren't they?", "positive_passages": [{"docid": "doc-en-nixpkgs-8195dd2ea18797f4b356cf77783c757f3513ae8752ea6d1c25966dc7b1f18d24", "text": "}; nativeBuildInputs = [ autoreconfHook pkg-config ]; buildInputs = [ pam openssl libp11 ] buildInputs = [ pam libp11.passthru.openssl libp11 ] ++ lib.optionals stdenv.isDarwin [ libintl ]; meta = with lib; {", "commid": "nixpkgs_pr_202345"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-712d5b7f44df19162afcd5dbafa46ae6859ef7eb00cd5ca5240b0b590a30a6d3", "query": "pam_p11 causes login segfault in NixOS 22.11. GDM and Gnome lock screen are also affected. Steps to reproduce the behavior: to log in on the console or run `: Bug was not present in 22.05.\nReverting does not help.\nFixed by: Can someone with commit access apply this patch?\nCan you open a pull request with that patch?\nI hope that NixOS can be unbureaucratic enough that PRs are not required for this kind of patch.\nIt's generally preferred to do basically everything through PRs, so some basic CI checks can run & maintainers can be pinged automatically. We can just self-merge though. I created containing your diff and adding a comment for explanation.\nThis seems to be whats causing my 22.11-beta19 install on an Alder Lake 12700H (no gpu) to not boot into GDM. This is a pretty heinous issue that should be tested for. The graphical installer doesn't install Vim, WPA_Supplicant or anything useful for figuring out what went wrong, despite having Vim and WPA Supplicant available on the installation media/calamares.\nWell I just did - you're welcome. That's what beta releases are for, aren't they?", "positive_passages": [{"docid": "doc-en-nixpkgs-07b6601f0990b14cde516b215fd038f209d69da9b20dc3e8a973641f7e65b49b", "text": "++ lib.optionals stdenv.hostPlatform.isMusl [ argp-standalone ] ++ lib.optionals withJitterEntropy [ jitterentropy ] ++ lib.optionals withNistBeacon [ curl jansson libxml2 ] ++ lib.optionals withPkcs11 [ libp11 openssl ] ++ lib.optionals withPkcs11 [ libp11 libp11.passthru.openssl ] ++ lib.optionals withRtlsdr [ librtlsdr ]; enableParallelBuilding = true;", "commid": "nixpkgs_pr_202345"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-712d5b7f44df19162afcd5dbafa46ae6859ef7eb00cd5ca5240b0b590a30a6d3", "query": "pam_p11 causes login segfault in NixOS 22.11. GDM and Gnome lock screen are also affected. Steps to reproduce the behavior: to log in on the console or run `: Bug was not present in 22.05.\nReverting does not help.\nFixed by: Can someone with commit access apply this patch?\nCan you open a pull request with that patch?\nI hope that NixOS can be unbureaucratic enough that PRs are not required for this kind of patch.\nIt's generally preferred to do basically everything through PRs, so some basic CI checks can run & maintainers can be pinged automatically. We can just self-merge though. I created containing your diff and adding a comment for explanation.\nThis seems to be whats causing my 22.11-beta19 install on an Alder Lake 12700H (no gpu) to not boot into GDM. This is a pretty heinous issue that should be tested for. The graphical installer doesn't install Vim, WPA_Supplicant or anything useful for figuring out what went wrong, despite having Vim and WPA Supplicant available on the installation media/calamares.\nWell I just did - you're welcome. That's what beta releases are for, aren't they?", "positive_passages": [{"docid": "doc-en-nixpkgs-59e558b971086467fb829c1a6aa57d4c1021e24c169b33d898d2a3fbe6433b0f", "text": "libow = callPackage ../development/libraries/libow { }; libp11 = callPackage ../development/libraries/libp11 { }; libp11 = callPackage ../development/libraries/libp11 { openssl = openssl_1_1; }; libpam-wrapper = callPackage ../development/libraries/libpam-wrapper { };", "commid": "nixpkgs_pr_202345"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-712d5b7f44df19162afcd5dbafa46ae6859ef7eb00cd5ca5240b0b590a30a6d3", "query": "pam_p11 causes login segfault in NixOS 22.11. GDM and Gnome lock screen are also affected. Steps to reproduce the behavior: to log in on the console or run `: Bug was not present in 22.05.\nReverting does not help.\nFixed by: Can someone with commit access apply this patch?\nCan you open a pull request with that patch?\nI hope that NixOS can be unbureaucratic enough that PRs are not required for this kind of patch.\nIt's generally preferred to do basically everything through PRs, so some basic CI checks can run & maintainers can be pinged automatically. We can just self-merge though. I created containing your diff and adding a comment for explanation.\nThis seems to be whats causing my 22.11-beta19 install on an Alder Lake 12700H (no gpu) to not boot into GDM. This is a pretty heinous issue that should be tested for. The graphical installer doesn't install Vim, WPA_Supplicant or anything useful for figuring out what went wrong, despite having Vim and WPA Supplicant available on the installation media/calamares.\nWell I just did - you're welcome. That's what beta releases are for, aren't they?", "positive_passages": [{"docid": "doc-en-nixpkgs-45232bad8db7b765289f0b89ce34b1f629d06832b41db98a204c707638af8b0a", "text": "pam_mysql = callPackage ../os-specific/linux/pam_mysql { }; pam_p11 = callPackage ../os-specific/linux/pam_p11 { openssl = openssl_1_1; }; pam_p11 = callPackage ../os-specific/linux/pam_p11 { }; pam_pgsql = callPackage ../os-specific/linux/pam_pgsql { };", "commid": "nixpkgs_pr_202345"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-07a7f4dbe892227e938d560ea16281033c880bb2019ece41fff50de72a9b0d43", "query": "i3 has been updated to 4.13. I attempted to update our derivation but they switched to and I don't know how that works :) If somebody could update i3, I would really appreciate that. /cc maintainers\nFYI, for to work it is sufficient to add to the (see ).\nThanks :) I think with the main i3 the issue was that the needed to change and I did not know what to set them to.\nYes, and indeed the and are already included with the source distribution for , but I had to add the for .", "positive_passages": [{"docid": "doc-en-nixpkgs-1375b3b1567abcea900e99c94277a9adc397ba925411eb7556c984222f712a1e", "text": "{ fetchurl, stdenv, which, pkgconfig, makeWrapper, libxcb, xcbutilkeysyms , xcbutil, xcbutilwm, libstartup_notification, libX11, pcre, libev, yajl , xcb-util-cursor, coreutils, perl, pango, perlPackages, libxkbcommon , xcbutil, xcbutilwm, xcbutilxrm, libstartup_notification, libX11, pcre, libev , yajl, xcb-util-cursor, coreutils, perl, pango, perlPackages, libxkbcommon , xorgserver, xvfb_run, dmenu, i3status }: stdenv.mkDerivation rec { name = \"i3-${version}\"; version = \"4.12\"; version = \"4.13\"; src = fetchurl { url = \"http://i3wm.org/downloads/${name}.tar.bz2\"; sha256 = \"1d3q3lgpjbkmcwzjhp0dfr0jq847silcfg087slcnj95ikh1r7p1\"; sha256 = \"12ngz32swh9n85xy0cz1lq16aqi9ys5hq19v589q9a97wn1k3hcl\"; }; nativeBuildInputs = [ which pkgconfig makeWrapper ]; buildInputs = [ which pkgconfig makeWrapper libxcb xcbutilkeysyms xcbutil xcbutilwm libxkbcommon libxcb xcbutilkeysyms xcbutil xcbutilwm xcbutilxrm libxkbcommon libstartup_notification libX11 pcre libev yajl xcb-util-cursor perl pango perlPackages.AnyEventI3 perlPackages.X11XCB perlPackages.IPCRun perlPackages.ExtUtilsPkgConfig perlPackages.TestMore perlPackages.InlineC xorgserver xvfb_run ]; configureFlags = [ \"--disable-builddir\" ]; enableParallelBuilding = true; postPatch = '' patchShebangs . '';", "commid": "nixpkgs_pr_20300"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-07a7f4dbe892227e938d560ea16281033c880bb2019ece41fff50de72a9b0d43", "query": "i3 has been updated to 4.13. I attempted to update our derivation but they switched to and I don't know how that works :) If somebody could update i3, I would really appreciate that. /cc maintainers\nFYI, for to work it is sufficient to add to the (see ).\nThanks :) I think with the main i3 the issue was that the needed to change and I did not know what to set them to.\nYes, and indeed the and are already included with the source distribution for , but I had to add the for .", "positive_passages": [{"docid": "doc-en-nixpkgs-803043074c0ba4fb62a2701d2ae7e540b05139dc9a0d4f9edeb3dcb6d6cbe03b", "text": "! grep -q '^not ok' testcases/latest/complete-run.log ''; configurePhase = \"makeFlags=PREFIX=$out\"; postInstall = '' wrapProgram \"$out/bin/i3-save-tree\" --prefix PERL5LIB \":\" \"$PERL5LIB\" mkdir -p $out/man/man1 cp man/*.1 $out/man/man1 for program in $out/bin/i3-sensible-*; do sed -i 's/which/command -v/' $program done", "commid": "nixpkgs_pr_20300"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-07a7f4dbe892227e938d560ea16281033c880bb2019ece41fff50de72a9b0d43", "query": "i3 has been updated to 4.13. I attempted to update our derivation but they switched to and I don't know how that works :) If somebody could update i3, I would really appreciate that. /cc maintainers\nFYI, for to work it is sufficient to add to the (see ).\nThanks :) I think with the main i3 the issue was that the needed to change and I did not know what to set them to.\nYes, and indeed the and are already included with the source distribution for , but I had to add the for .", "positive_passages": [{"docid": "doc-en-nixpkgs-dcde43c908435c4dec4f9e49d2dd123e268bd762634310bf3c313300890aee3d", "text": "meta = with stdenv.lib; { description = \"A tiling window manager\"; homepage = \"http://i3wm.org\"; maintainers = with maintainers; [ garbas modulistic ]; maintainers = with maintainers; [ garbas modulistic fpletz ]; license = licenses.bsd3; platforms = platforms.all;", "commid": "nixpkgs_pr_20300"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-3635650f75ebdbc7ddef5bbe27b00a995720d03117310c288c5b3ee1cc5ef93a", "query": "The srb2 assets are outdated. Steps to reproduce the behaviour: the game or run the command while in game The that the assets are being downloaded from hasn't been updated since 2020\nI just noticed this pr, but it seems to have gone dead 3 months ago\nclosing as I'm making a new issue", "positive_passages": [{"docid": "doc-en-nixpkgs-ae32bef4a1567b486560cf8c879d52b8f4bdf207a358b9ca4c8de1fcd8291ae9", "text": " diff --git a/CMakeLists.txt b/CMakeLists.txt index 915912af5..f5c2cf9cc 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -91,11 +91,6 @@ if(\"${CMAKE_HOST_SYSTEM_NAME}\" STREQUAL Windows) endif() endif() else() -\tCPMAddPackage( -\t\tNAME Ccache.cmake -\t\tGITHUB_REPOSITORY TheLartians/Ccache.cmake -\t\tVERSION 1.2 -\t) endif() # Dependencies -- 2.40.1 ", "commid": "nixpkgs_pr_233085"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-3635650f75ebdbc7ddef5bbe27b00a995720d03117310c288c5b3ee1cc5ef93a", "query": "The srb2 assets are outdated. Steps to reproduce the behaviour: the game or run the command while in game The that the assets are being downloaded from hasn't been updated since 2020\nI just noticed this pr, but it seems to have gone dead 3 months ago\nclosing as I'm making a new issue", "positive_passages": [{"docid": "doc-en-nixpkgs-86a894e309b64ff3c9ac2890a509d1e74172e61dbbffb006d8b7bcb2da801486", "text": ", stdenv , fetchurl , fetchFromGitHub , substituteAll , cmake , curl , nasm", "commid": "nixpkgs_pr_233085"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-3635650f75ebdbc7ddef5bbe27b00a995720d03117310c288c5b3ee1cc5ef93a", "query": "The srb2 assets are outdated. Steps to reproduce the behaviour: the game or run the command while in game The that the assets are being downloaded from hasn't been updated since 2020\nI just noticed this pr, but it seems to have gone dead 3 months ago\nclosing as I'm making a new issue", "positive_passages": [{"docid": "doc-en-nixpkgs-e3dcb4c27744abc3417613662ae2b4dc790ad06b8118ffa4f913efb13900dd83", "text": ", SDL2 , SDL2_mixer , zlib , unzip , makeWrapper , makeDesktopItem , copyDesktopItems }: let assets_version = \"2.2.5\"; assets = fetchurl { url = \"https://github.com/mazmazz/SRB2/releases/download/SRB2_assets_220/srb2-${assets_version}-assets.7z\"; sha256 = \"1m9xf3vraq9nipsi09cyvvfa4i37gzfxg970rnqfswd86z9v6v00\"; }; assets_optional = fetchurl { url = \"https://github.com/mazmazz/SRB2/releases/download/SRB2_assets_220/srb2-${assets_version}-optional-assets.7z\"; sha256 = \"1j29jrd0r1k2bb11wyyl6yv9b90s2i6jhrslnh77qkrhrwnwcdz4\"; }; in stdenv.mkDerivation rec { stdenv.mkDerivation (finalAttrs: { pname = \"srb2\"; version = \"2.2.10\"; version = \"2.2.11\"; src = fetchFromGitHub { owner = \"STJr\"; repo = \"SRB2\"; rev = \"SRB2_release_${version}\"; sha256 = \"03388n094d2yr5si6ngnggbqhm8b2l0s0qvfnkz49li9bd6a81gg\"; rev = \"SRB2_release_${finalAttrs.version}\"; hash = \"sha256-tyiXivJWjNnL+4YynUV6k6iaMs8o9HkHrp+qFj2+qvQ=\"; }; nativeBuildInputs = [ cmake nasm p7zip makeWrapper copyDesktopItems ]; buildInputs = [", "commid": "nixpkgs_pr_233085"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-3635650f75ebdbc7ddef5bbe27b00a995720d03117310c288c5b3ee1cc5ef93a", "query": "The srb2 assets are outdated. Steps to reproduce the behaviour: the game or run the command while in game The that the assets are being downloaded from hasn't been updated since 2020\nI just noticed this pr, but it seems to have gone dead 3 months ago\nclosing as I'm making a new issue", "positive_passages": [{"docid": "doc-en-nixpkgs-bd63c5576bb77a055878dd77b921d73fa1210c30188c71367f41f767302cae73", "text": "zlib ]; assets = stdenv.mkDerivation { pname = \"srb2-data\"; version = finalAttrs.version; nativeBuildInputs = [ unzip ]; src = fetchurl { url = \"https://github.com/STJr/SRB2/releases/download/SRB2_release_${finalAttrs.version}/SRB2-v${lib.replaceStrings [\".\"] [\"\"] finalAttrs.version}-Full.zip\"; hash = \"sha256-KsJIkCczD/HyIwEy5dI3zsHbWFCMBaCoCHizfupFoWM=\"; }; sourceRoot = \".\"; installPhase = '' mkdir -p $out/share/srb2 cp -r *pk3 *dta *dat models/ $out/share/srb2/ ''; }; cmakeFlags = [ \"-DSRB2_ASSET_DIRECTORY=/build/source/assets\" \"-DSRB2_ASSET_DIRECTORY=${finalAttrs.assets}/share/srb2\" \"-DGME_INCLUDE_DIR=${game-music-emu}/include\" \"-DOPENMPT_INCLUDE_DIR=${libopenmpt.dev}/include\" \"-DSDL2_MIXER_INCLUDE_DIR=${lib.getDev SDL2_mixer}/include/SDL2\" \"-DSDL2_INCLUDE_DIR=${lib.getDev SDL2}/include/SDL2\" \"-DSDL2_INCLUDE_DIR=${lib.getDev SDL2.dev}/include/SDL2\" ]; patches = [ ./wadlocation.patch # Fix unknown command \"CPMAddPackage\" by not using Ccache.cmake ./cmake.patch ]; postPatch = '' substituteInPlace src/sdl/i_system.c --replace '@wadlocation@' $out ''; desktopItems = [ (makeDesktopItem rec { name = \"Sonic Robo Blast 2\"; exec = finalAttrs.pname; icon = finalAttrs.pname; comment = finalAttrs.meta.description; desktopName = name; genericName = name; categories = [ \"Game\" ]; }) ]; preConfigure = '' 7z x ${assets} -o\"/build/source/assets\" -aos 7z x ${assets_optional} -o\"/build/source/assets\" -aos ''; installPhase = '' mkdir -p $out/bin $out/share/applications $out/share/pixmaps $out/share/icons copyDesktopItems cp ../srb2.png $out/share/pixmaps/. cp ../srb2.png $out/share/icons/. postInstall = '' mkdir $out/bin mv $out/lsdlsrb2-${version} $out/bin/srb2 cp bin/lsdlsrb2 $out/bin/srb2 wrapProgram $out/bin/srb2 --set SRB2WADDIR \"${finalAttrs.assets}/share/srb2\" ''; meta = with lib; {", "commid": "nixpkgs_pr_233085"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-3635650f75ebdbc7ddef5bbe27b00a995720d03117310c288c5b3ee1cc5ef93a", "query": "The srb2 assets are outdated. Steps to reproduce the behaviour: the game or run the command while in game The that the assets are being downloaded from hasn't been updated since 2020\nI just noticed this pr, but it seems to have gone dead 3 months ago\nclosing as I'm making a new issue", "positive_passages": [{"docid": "doc-en-nixpkgs-3b5405d22f38928e9dff3c553d4437e6fc284e7b52d51c0fcea345ac07e593a0", "text": "homepage = \"https://www.srb2.org/\"; platforms = platforms.linux; license = licenses.gpl2Plus; maintainers = with maintainers; [ zeratax ]; maintainers = with maintainers; [ zeratax donovanglover ]; }; } }) ", "commid": "nixpkgs_pr_233085"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-3635650f75ebdbc7ddef5bbe27b00a995720d03117310c288c5b3ee1cc5ef93a", "query": "The srb2 assets are outdated. Steps to reproduce the behaviour: the game or run the command while in game The that the assets are being downloaded from hasn't been updated since 2020\nI just noticed this pr, but it seems to have gone dead 3 months ago\nclosing as I'm making a new issue", "positive_passages": [{"docid": "doc-en-nixpkgs-a8a55d37f43cde79ba1c6ea2b8a5e4bd697809f34f5c8fd0a2f46b50be03d404", "text": " diff --git a/src/sdl/i_system.c b/src/sdl/i_system.c index 10c0747bf..861f00728 100644 --- a/src/sdl/i_system.c +++ b/src/sdl/i_system.c @@ -145,13 +145,7 @@ int TimeFunction(int requested_frequency); // Locations for searching the srb2.pk3 #if defined (__unix__) || defined(__APPLE__) || defined (UNIXCOMMON) -#define DEFAULTWADLOCATION1 \"/usr/local/share/games/SRB2\" -#define DEFAULTWADLOCATION2 \"/usr/local/games/SRB2\" -#define DEFAULTWADLOCATION3 \"/usr/share/games/SRB2\" -#define DEFAULTWADLOCATION4 \"/usr/games/SRB2\" -#define DEFAULTSEARCHPATH1 \"/usr/local/games\" -#define DEFAULTSEARCHPATH2 \"/usr/games\" -#define DEFAULTSEARCHPATH3 \"/usr/local\" +#define DEFAULTWADLOCATION1 \"@wadlocation@\" #elif defined (_WIN32) #define DEFAULTWADLOCATION1 \"c:gamessrb2\" #define DEFAULTWADLOCATION2 \"gamessrb2\" @@ -2812,34 +2806,6 @@ static const char *locateWad(void) if (((envstr = I_GetEnv(\"SRB2WADDIR\")) != NULL) && isWadPathOk(envstr)) return envstr; -#ifndef NOCWD -\tI_OutputMsg(\",.\"); -\t// examine current dir -\tstrcpy(returnWadPath, \".\"); -\tif (isWadPathOk(returnWadPath)) -\t\treturn NULL; -#endif - - -#ifdef CMAKECONFIG -#ifndef NDEBUG -\tI_OutputMsg(\",\"CMAKE_ASSETS_DIR); -\tstrcpy(returnWadPath, CMAKE_ASSETS_DIR); -\tif (isWadPathOk(returnWadPath)) -\t{ -\t\treturn returnWadPath; -\t} -#endif -#endif - -#ifdef __APPLE__ -\tOSX_GetResourcesPath(returnWadPath); -\tI_OutputMsg(\",%s\", returnWadPath); -\tif (isWadPathOk(returnWadPath)) -\t{ -\t\treturn returnWadPath; -\t} -#endif // examine default dirs #ifdef DEFAULTWADLOCATION1 @@ -2884,16 +2850,7 @@ static const char *locateWad(void) if (isWadPathOk(returnWadPath)) return returnWadPath; #endif -#ifndef NOHOME -\t// find in $HOME -\tI_OutputMsg(\",HOME\"); -\tif ((envstr = I_GetEnv(\"HOME\")) != NULL) -\t{ -\t\tWadPath = searchWad(envstr); -\t\tif (WadPath) -\t\t\treturn WadPath; -\t} -#endif + #ifdef DEFAULTSEARCHPATH1 // find in /usr/local I_OutputMsg(\", in:\"DEFAULTSEARCHPATH1); ", "commid": "nixpkgs_pr_233085"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-8134cc91aa1b30e156be8000d7086d595d40d47edc73e2d6c49d1c33dc37622b", "query": "Specifically systems with AVX but without BMI2 Same as this debian bug: They solved it by pulling the latest stable 2.35 patches: ;a=history;f=sysdeps/x86_64;hb=refs/heads/release/2.35/master For NixOS, one workaround is to install a NixOS system to a usb drive with microcode updates enabled, and use that for the installation. This is because for this series of CPUs (Haswell, 3rd/4th gen) the BMI2 instructions are via a microcode update. Rebuilding the iso with this overlay also works, but this is a mass-rebuild: The diff is produced like this: Where corresponds to 2.35-220 and corresponds to 2.35-163 (our previous state).\nIt was attempted to update glibc to the latest stable patches in , but this led to some issues.\nA temporary fix without rebuilds would be via , I suppose. EDIT: or 22.05 release in the meantime, as I expect it shouldn't be affected and it's still supported for a few weeks. Real fix (taking more time, etc.): most likely update glibc to latest 2.35.x and somehow resolve the regression (and possibly others), and then backport to 22.11 as well.\nRedoing update as PR for now.\nThe glibc update is contained in and channels now.", "positive_passages": [{"docid": "doc-en-nixpkgs-1b7f94bcaf33a4efbb7094fcfaf661d23ed7c34c3a8b7c9ebd96c6519393f392", "text": " https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=2d7ed98add14f75041499ac189696c9bd3d757fe --- a/Makeconfig +++ b/Makeconfig @@ -43,6 +43,22 @@ else $(error objdir must be defined by the build-directory Makefile) endif +# Did we request 'make -s' run? \"yes\" or \"no\". +# Starting from make-4.4 MAKEFLAGS now contains long +# options like '--shuffle'. To detect presence of 's' +# we pick first word with short options. Long options +# are guaranteed to come after whitespace. We use '-' +# prefix to always have a word before long options +# even if no short options were passed. +# Typical MAKEFLAGS values to watch for: +# \"rs --shuffle=42\" (silent) +# \" --shuffle\" (not silent) +ifeq ($(findstring s, $(firstword -$(MAKEFLAGS))),) +silent-make := no +else +silent-make := yes +endif + # Root of the sysdeps tree. sysdep_dir := $(..)sysdeps export sysdep_dir := $(sysdep_dir) @@ -917,7 +933,7 @@ endif # umpteen zillion filenames along with it (we use `...' instead) # but we don't want this echoing done when the user has said # he doesn't want to see commands echoed by using -s. -ifneq\t\"$(findstring s,$(MAKEFLAGS))\" \"\"\t# if -s +ifeq ($(silent-make),yes)\t\t\t# if -s +cmdecho\t:= echo >/dev/null else\t\t\t\t\t\t# not -s +cmdecho\t:= echo --- a/Makerules +++ b/Makerules @@ -794,7 +794,7 @@ endif # Maximize efficiency by minimizing the number of rules. .SUFFIXES:\t# Clear the suffix list. We don't use suffix rules. # Don't define any builtin rules. -MAKEFLAGS := $(MAKEFLAGS)r +MAKEFLAGS := $(MAKEFLAGS) -r # Generic rule for making directories. %/: @@ -811,7 +811,7 @@ MAKEFLAGS := $(MAKEFLAGS)r .PRECIOUS: $(foreach l,$(libtypes),$(patsubst %,$(common-objpfx)$l,c)) # Use the verbose option of ar and tar when not running silently. -ifeq\t\"$(findstring s,$(MAKEFLAGS))\" \"\"\t# if not -s +ifeq ($(silent-make),no)\t\t\t# if not -s verbose := v else\t \t\t\t\t\t# -s verbose\t:= --- a/elf/rtld-Rules +++ b/elf/rtld-Rules @@ -52,7 +52,7 @@ $(objpfx)rtld-libc.a: $(foreach dir,$(rtld-subdirs), mv -f $@T $@ # Use the verbose option of ar and tar when not running silently. -ifeq\t\"$(findstring s,$(MAKEFLAGS))\" \"\"\t# if not -s +ifeq ($(silent-make),no)\t\t\t# if not -s verbose := v else\t\t\t\t\t\t# -s verbose\t:= ", "commid": "nixpkgs_pr_205133"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-8134cc91aa1b30e156be8000d7086d595d40d47edc73e2d6c49d1c33dc37622b", "query": "Specifically systems with AVX but without BMI2 Same as this debian bug: They solved it by pulling the latest stable 2.35 patches: ;a=history;f=sysdeps/x86_64;hb=refs/heads/release/2.35/master For NixOS, one workaround is to install a NixOS system to a usb drive with microcode updates enabled, and use that for the installation. This is because for this series of CPUs (Haswell, 3rd/4th gen) the BMI2 instructions are via a microcode update. Rebuilding the iso with this overlay also works, but this is a mass-rebuild: The diff is produced like this: Where corresponds to 2.35-220 and corresponds to 2.35-163 (our previous state).\nIt was attempted to update glibc to the latest stable patches in , but this led to some issues.\nA temporary fix without rebuilds would be via , I suppose. EDIT: or 22.05 release in the meantime, as I expect it shouldn't be affected and it's still supported for a few weeks. Real fix (taking more time, etc.): most likely update glibc to latest 2.35.x and somehow resolve the regression (and possibly others), and then backport to 22.11 as well.\nRedoing update as PR for now.\nThe glibc update is contained in and channels now.", "positive_passages": [{"docid": "doc-en-nixpkgs-29d95cd7c6bd5a91014e4809628bbc2cd07f575db470cc9c4fc74648b4be95e9", "text": "let version = \"2.35\"; patchSuffix = \"-163\"; patchSuffix = \"-224\"; sha256 = \"sha256-USNzL2tnzNMZMF79OZlx1YWSEivMKmUYob0lEN0M9S4=\"; in", "commid": "nixpkgs_pr_205133"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-8134cc91aa1b30e156be8000d7086d595d40d47edc73e2d6c49d1c33dc37622b", "query": "Specifically systems with AVX but without BMI2 Same as this debian bug: They solved it by pulling the latest stable 2.35 patches: ;a=history;f=sysdeps/x86_64;hb=refs/heads/release/2.35/master For NixOS, one workaround is to install a NixOS system to a usb drive with microcode updates enabled, and use that for the installation. This is because for this series of CPUs (Haswell, 3rd/4th gen) the BMI2 instructions are via a microcode update. Rebuilding the iso with this overlay also works, but this is a mass-rebuild: The diff is produced like this: Where corresponds to 2.35-220 and corresponds to 2.35-163 (our previous state).\nIt was attempted to update glibc to the latest stable patches in , but this led to some issues.\nA temporary fix without rebuilds would be via , I suppose. EDIT: or 22.05 release in the meantime, as I expect it shouldn't be affected and it's still supported for a few weeks. Real fix (taking more time, etc.): most likely update glibc to latest 2.35.x and somehow resolve the regression (and possibly others), and then backport to 22.11 as well.\nRedoing update as PR for now.\nThe glibc update is contained in and channels now.", "positive_passages": [{"docid": "doc-en-nixpkgs-edecb9ddb083570806f826931c0fbb687f66f9fc488e18c6ffe5c0b93db9b5a7", "text": "*/ ./2.35-master.patch.gz /* Can be removed after next snapshot update or release update. */ ./2.35-make-4.4.patch /* Revert this patch contained in the previous bundle. For now, until we know more. */ ./revert-mktime.patch /* Allow NixOS and Nix to handle the locale-archive. */ ./nix-locale-archive.patch", "commid": "nixpkgs_pr_205133"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-8134cc91aa1b30e156be8000d7086d595d40d47edc73e2d6c49d1c33dc37622b", "query": "Specifically systems with AVX but without BMI2 Same as this debian bug: They solved it by pulling the latest stable 2.35 patches: ;a=history;f=sysdeps/x86_64;hb=refs/heads/release/2.35/master For NixOS, one workaround is to install a NixOS system to a usb drive with microcode updates enabled, and use that for the installation. This is because for this series of CPUs (Haswell, 3rd/4th gen) the BMI2 instructions are via a microcode update. Rebuilding the iso with this overlay also works, but this is a mass-rebuild: The diff is produced like this: Where corresponds to 2.35-220 and corresponds to 2.35-163 (our previous state).\nIt was attempted to update glibc to the latest stable patches in , but this led to some issues.\nA temporary fix without rebuilds would be via , I suppose. EDIT: or 22.05 release in the meantime, as I expect it shouldn't be affected and it's still supported for a few weeks. Real fix (taking more time, etc.): most likely update glibc to latest 2.35.x and somehow resolve the regression (and possibly others), and then backport to 22.11 as well.\nRedoing update as PR for now.\nThe glibc update is contained in and channels now.", "positive_passages": [{"docid": "doc-en-nixpkgs-48976d797f2e01498f9715182578499fb4cb02c0cfbd47e0ca0cf11735a5af0f", "text": " commit f6d4c1ac648c4ff8baad94500df0bb13108a4f79 Author: Paul Eggert Date: Thu Sep 8 20:08:32 2022 -0500 REVERT: mktime: improve heuristic for ca-1986 Indiana DST This patch syncs mktime.c from Gnulib, fixing a problem reported by Mark Krenz , and it should fix BZ#29035 too. * time/mktime.c (__mktime_internal): Be more generous about accepting arguments with the wrong value of tm_isdst, by falling back to a one-hour DST difference if we find no nearby DST that is unusual. This fixes a problem where \"1986-04-28 00:00 EDT\" was rejected when TZ=\"America/Indianapolis\" because the nearest DST timestamp occurred in 1970, a temporal distance too great for the old heuristic. This also also narrows the search a bit, which is a minor performance win. (cherry picked from commit 83859e1115269cf56d21669361d4ddbe2687831c) diff --git b/time/mktime.c a/time/mktime.c index e9a6006710..494c89bf54 100644 --- b/time/mktime.c +++ a/time/mktime.c @@ -429,13 +429,8 @@ __mktime_internal (struct tm *tp, time with the right value, and use its UTC offset. Heuristic: probe the adjacent timestamps in both directions, -\t looking for the desired isdst. If none is found within a -\t reasonable duration bound, assume a one-hour DST difference. -\t This should work for all real time zone histories in the tz -\t database. */ - - /* +1 if we wanted standard time but got DST, -1 if the reverse. */ - int dst_difference = (isdst == 0) - (tm.tm_isdst == 0); +\t looking for the desired isdst. This should work for all real +\t time zone histories in the tz database. */ /* Distance between probes when looking for a DST boundary. In tzdata2003a, the shortest period of DST is 601200 seconds @@ -446,14 +441,12 @@ __mktime_internal (struct tm *tp, periods when probing. */ int stride = 601200; - /* In TZDB 2021e, the longest period of DST (or of non-DST), in -\t which the DST (or adjacent DST) difference is not one hour, -\t is 457243209 seconds: e.g., America/Cambridge_Bay with leap -\t seconds, starting 1965-10-31 00:00 in a switch from -\t double-daylight time (-05) to standard time (-07), and -\t continuing to 1980-04-27 02:00 in a switch from standard time -\t (-07) to daylight time (-06). */ - int duration_max = 457243209; + /* The longest period of DST in tzdata2003a is 536454000 seconds +\t (e.g., America/Jujuy starting 1946-10-01 01:00). The longest +\t period of non-DST is much longer, but it makes no real sense +\t to search for more than a year of non-DST, so use the DST +\t max. */ + int duration_max = 536454000; /* Search in both directions, so the maximum distance is half the duration; add the stride to avoid off-by-1 problems. */ @@ -490,11 +483,6 @@ __mktime_internal (struct tm *tp, } } - /* No unusual DST offset was found nearby. Assume one-hour DST. */ - t += 60 * 60 * dst_difference; - if (mktime_min <= t && t <= mktime_max && convert_time (convert, t, &tm)) -\tgoto offset_found; - __set_errno (EOVERFLOW); return -1; } ", "commid": "nixpkgs_pr_205133"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-3c59237d2f55e457fecdf94b553c79f1097e62ee8e9b175bf9080384bc19675c", "query": "Running Dwarf Fortress () on darwin-aarch64 opens a window that is completely white. It receives inputs and sound also plays, but nothing is displayed. This might be due to the package not having an app bundle as an output (e.g. 'Applications/Dwarf Fortress' next to bin) Steps to reproduce the behavior: dwarf-fortress on macOS Window opens with graphics displayed ! ", "commid": "nixpkgs_pr_305586"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-d4a8267c002d18325d5d43f72e6cb262827fbb528ab8ef6b99339b84315c39a2", "query": "Project description Interact privately with your documents using the power of GPT, 100% privately, no data leaks Metadata homepage source license: asl-2 platforms: all?\ni am really new to nix, and i made this by adding dependency until it worked.. but hopefully a good starting point now just need to do is, which will download the models and to run it.", "positive_passages": [{"docid": "doc-en-nixpkgs-7d05f1c213fa2095cddcbfaf9046e7bca28c8c9a413dcf6619d8b0b82312f6a9", "text": "./services/misc/polaris.nix ./services/misc/portunus.nix ./services/misc/preload.nix ./services/misc/private-gpt.nix ./services/misc/prowlarr.nix ./services/misc/pufferpanel.nix ./services/misc/pykms.nix", "commid": "nixpkgs_pr_305586"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-d4a8267c002d18325d5d43f72e6cb262827fbb528ab8ef6b99339b84315c39a2", "query": "Project description Interact privately with your documents using the power of GPT, 100% privately, no data leaks Metadata homepage source license: asl-2 platforms: all?\ni am really new to nix, and i made this by adding dependency until it worked.. but hopefully a good starting point now just need to do is, which will download the models and to run it.", "positive_passages": [{"docid": "doc-en-nixpkgs-7d8fa79a95412bdab6452429e230c24d9e249911705c752c2afa73bd14500e0b", "text": " { config , lib , pkgs , ... }: let inherit (lib) types; format = pkgs.formats.yaml { }; cfg = config.services.private-gpt; in { options = { services.private-gpt = { enable = lib.mkEnableOption \"private-gpt for local large language models\"; package = lib.mkPackageOption pkgs \"private-gpt\" { }; stateDir = lib.mkOption { type = types.path; default = \"/var/lib/private-gpt\"; description = \"State directory of private-gpt.\"; }; settings = lib.mkOption { type = format.type; default = { llm = { mode = \"ollama\"; tokenizer = \"\"; }; embedding = { mode = \"ollama\"; }; ollama = { llm_model = \"llama3\"; embedding_model = \"nomic-embed-text\"; api_base = \"http://localhost:11434\"; embedding_api_base = \"http://localhost:11434\"; keep_alive = \"5m\"; tfs_z = 1; top_k = 40; top_p = 0.9; repeat_last_n = 64; repeat_penalty = 1.2; request_timeout = 120; }; vectorstore = { database = \"qdrant\"; }; qdrant = { path = \"/var/lib/private-gpt/vectorstore/qdrant\"; }; data = { local_data_folder = \"/var/lib/private-gpt\"; }; openai = { }; azopenai = { }; }; description = '' settings-local.yaml for private-gpt ''; }; }; }; config = lib.mkIf cfg.enable { systemd.services.private-gpt = { description = \"Interact with your documents using the power of GPT, 100% privately, no data leaks\"; wantedBy = [ \"multi-user.target\" ]; after = [ \"network.target\" ]; preStart = let config = format.generate \"settings-local.yaml\" (cfg.settings // { server.env_name = \"local\"; }); in '' mkdir -p ${cfg.stateDir}/{settings,huggingface,matplotlib,tiktoken_cache} cp ${cfg.package.cl100k_base.tiktoken} ${cfg.stateDir}/tiktoken_cache/9b5ad71b2ce5302211f9c61530b329a4922fc6a4 cp ${pkgs.python3Packages.private-gpt}/${pkgs.python3.sitePackages}/private_gpt/settings.yaml ${cfg.stateDir}/settings/settings.yaml cp \"${config}\" \"${cfg.stateDir}/settings/settings-local.yaml\" chmod 600 \"${cfg.stateDir}/settings/settings-local.yaml\" ''; environment = { PGPT_PROFILES = \"local\"; PGPT_SETTINGS_FOLDER = \"${cfg.stateDir}/settings\"; HF_HOME = \"${cfg.stateDir}/huggingface\"; TRANSFORMERS_OFFLINE = \"1\"; HF_DATASETS_OFFLINE = \"1\"; MPLCONFIGDIR = \"${cfg.stateDir}/matplotlib\"; }; serviceConfig = { ExecStart = lib.getExe cfg.package; WorkingDirectory = cfg.stateDir; StateDirectory = \"private-gpt\"; RuntimeDirectory = \"private-gpt\"; RuntimeDirectoryMode = \"0755\"; PrivateTmp = true; DynamicUser = true; DevicePolicy = \"closed\"; LockPersonality = true; MemoryDenyWriteExecute = true; PrivateUsers = true; ProtectHome = true; ProtectHostname = true; ProtectKernelLogs = true; ProtectKernelModules = true; ProtectKernelTunables = true; ProtectControlGroups = true; ProcSubset = \"pid\"; RestrictNamespaces = true; RestrictRealtime = true; SystemCallArchitectures = \"native\"; UMask = \"0077\"; }; }; }; meta.maintainers = with lib.maintainers; [ drupol ]; } ", "commid": "nixpkgs_pr_305586"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-d4a8267c002d18325d5d43f72e6cb262827fbb528ab8ef6b99339b84315c39a2", "query": "Project description Interact privately with your documents using the power of GPT, 100% privately, no data leaks Metadata homepage source license: asl-2 platforms: all?\ni am really new to nix, and i made this by adding dependency until it worked.. but hopefully a good starting point now just need to do is, which will download the models and to run it.", "positive_passages": [{"docid": "doc-en-nixpkgs-95ccd7259b78348d8d99e861d2acce02c8c1564c5c4ef264afd32eb3ac9d5299", "text": "pretix = runTest ./web-apps/pretix.nix; printing-socket = handleTest ./printing.nix { socket = true; }; printing-service = handleTest ./printing.nix { socket = false; }; private-gpt = handleTest ./private-gpt.nix {}; privoxy = handleTest ./privoxy.nix {}; prometheus = handleTest ./prometheus.nix {}; prometheus-exporters = handleTest ./prometheus-exporters.nix {};", "commid": "nixpkgs_pr_305586"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-d4a8267c002d18325d5d43f72e6cb262827fbb528ab8ef6b99339b84315c39a2", "query": "Project description Interact privately with your documents using the power of GPT, 100% privately, no data leaks Metadata homepage source license: asl-2 platforms: all?\ni am really new to nix, and i made this by adding dependency until it worked.. but hopefully a good starting point now just need to do is, which will download the models and to run it.", "positive_passages": [{"docid": "doc-en-nixpkgs-13027b2a85a0f5ccde1e3a464901b19b1fbdafa68fc3bf9a0eecbd981cbee496", "text": " import ./make-test-python.nix ({ pkgs, lib, ... }: let mainPort = \"8001\"; in { name = \"private-gpt\"; meta = with lib.maintainers; { maintainers = [ drupol ]; }; nodes = { machine = { ... }: { services.private-gpt = { enable = true; }; }; }; testScript = '' machine.start() machine.wait_for_unit(\"private-gpt.service\") machine.wait_for_open_port(${mainPort}) machine.succeed(\"curl http://127.0.0.1:${mainPort}\") ''; }) ", "commid": "nixpkgs_pr_305586"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-d4a8267c002d18325d5d43f72e6cb262827fbb528ab8ef6b99339b84315c39a2", "query": "Project description Interact privately with your documents using the power of GPT, 100% privately, no data leaks Metadata homepage source license: asl-2 platforms: all?\ni am really new to nix, and i made this by adding dependency until it worked.. but hopefully a good starting point now just need to do is, which will download the models and to run it.", "positive_passages": [{"docid": "doc-en-nixpkgs-99649078954bdd7b3b1d13d0caf850e0112fdc0dbeed113d6d65f57f9593e879", "text": " { python3Packages , makeBinaryWrapper }: python3Packages.toPythonApplication (python3Packages.private-gpt.overrideAttrs (oldAttrs: { nativeBuildInputs = oldAttrs.nativeBuildInputs ++ [ makeBinaryWrapper ]; passthru.cl100k_base = { inherit (python3Packages.private-gpt.cl100k_base) tiktoken; }; postInstall = '' makeWrapper ${python3Packages.python.interpreter} $out/bin/private-gpt --prefix PYTHONPATH : \"$PYTHONPATH\" --add-flags \"-m private_gpt\" ''; })) ", "commid": "nixpkgs_pr_305586"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-d4a8267c002d18325d5d43f72e6cb262827fbb528ab8ef6b99339b84315c39a2", "query": "Project description Interact privately with your documents using the power of GPT, 100% privately, no data leaks Metadata homepage source license: asl-2 platforms: all?\ni am really new to nix, and i made this by adding dependency until it worked.. but hopefully a good starting point now just need to do is, which will download the models and to run it.", "positive_passages": [{"docid": "doc-en-nixpkgs-0ed08053a094b06fe928929207c6bab1aea654e93d60942546da25b159682133", "text": " { lib , buildPythonPackage , python , fetchFromGitHub , poetry-core , fastapi , injector , llama-index-core , llama-index-readers-file , huggingface-hub , python-multipart , pyyaml , transformers , uvicorn , watchdog , gradio , fetchurl , fetchpatch }: buildPythonPackage rec { pname = \"private-gpt\"; version = \"0.5.0\"; pyproject = true; src = fetchFromGitHub { owner = \"zylon-ai\"; repo = \"private-gpt\"; rev = \"v${version}\"; hash = \"sha256-bjydzJhOJjmbflcJbuMyNsmby7HtNPFW3MY2Tw12cHw=\"; }; patches = [ # Fix a vulnerability, to be removed in the next bump version # See https://github.com/zylon-ai/private-gpt/pull/1890 (fetchpatch { url = \"https://github.com/zylon-ai/private-gpt/commit/86368c61760c9cee5d977131d23ad2a3e063cbe9.patch\"; hash = \"sha256-4ysRUuNaHW4bmNzg4fn++89b430LP6AzYDoX2HplVH0=\"; }) ]; build-system = [ poetry-core ]; dependencies = [ fastapi injector llama-index-core llama-index-readers-file python-multipart pyyaml transformers uvicorn watchdog ] ++ lib.flatten (builtins.attrValues passthru.optional-dependencies); # This is needed for running the tests and the service in offline mode, # See related issue at https://github.com/zylon-ai/private-gpt/issues/1870 passthru.cl100k_base.tiktoken = fetchurl { url = \"https://openaipublic.blob.core.windows.net/encodings/cl100k_base.tiktoken\"; hash = \"sha256-Ijkht27pm96ZW3/3OFE+7xAPtR0YyTWXoRO8/+hlsqc=\"; }; passthru.optional-dependencies = with python.pkgs; { embeddings-huggingface = [ huggingface-hub llama-index-embeddings-huggingface ]; embeddings-ollama = [ llama-index-embeddings-ollama ]; embeddings-openai = [ llama-index-embeddings-openai ]; embeddings-sagemaker = [ boto3 ]; llms-ollama = [ llama-index-llms-ollama ]; llms-openai = [ llama-index-llms-openai ]; llms-openai-like = [ llama-index-llms-openai-like ]; llms-sagemaker = [ boto3 ]; ui = [ gradio ]; vector-stores-chroma = [ llama-index-vector-stores-chroma ]; vector-stores-postgres = [ llama-index-vector-stores-postgres ]; vector-stores-qdrant = [ llama-index-vector-stores-qdrant ]; }; postInstall = '' cp settings*.yaml $out/${python.sitePackages}/private_gpt/ ''; pythonImportsCheck = [ \"private_gpt\" ]; meta = { changelog = \"https://github.com/zylon-ai/private-gpt/blob/${src.rev}/CHANGELOG.md\"; description = \"Interact with your documents using the power of GPT, 100% privately, no data leaks\"; homepage = \"https://github.com/zylon-ai/private-gpt\"; license = lib.licenses.asl20; mainProgram = \"private-gpt\"; maintainers = with lib.maintainers; [ drupol ]; }; } ", "commid": "nixpkgs_pr_305586"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-d4a8267c002d18325d5d43f72e6cb262827fbb528ab8ef6b99339b84315c39a2", "query": "Project description Interact privately with your documents using the power of GPT, 100% privately, no data leaks Metadata homepage source license: asl-2 platforms: all?\ni am really new to nix, and i made this by adding dependency until it worked.. but hopefully a good starting point now just need to do is, which will download the models and to run it.", "positive_passages": [{"docid": "doc-en-nixpkgs-6e9af1384216845c0599f57821a04398e6cbfef7251974dc3effdb3ba5ccf84f", "text": "ppdeep = callPackage ../development/python-modules/ppdeep { }; private-gpt = callPackage ../development/python-modules/private-gpt { }; prodict = callPackage ../development/python-modules/prodict { }; prometheus-pandas = callPackage ../development/python-modules/prometheus-pandas { };", "commid": "nixpkgs_pr_305586"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-36c39d823929801232f4daa556f02765771b5c95ddb3f7b4c962c2977c75ccb9", "query": "A clear and concise description of what the bug is. You can browse files and it'll show them but playing a song (in my case an MP3 file) results in this error: On the next start, the song is greyed out. I've d it and it seems to try (and fail?) to load libavcodec. That might be why. is in spotify's library path but somehow it's not loading. Investigating now. ", "commid": "nixpkgs_pr_315205"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-b624e2e8c4cee3c185a7b6eafba4a27ad8422bef0d37215a6d958e57376a11e2", "query": "No crash n/a n/a Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nSame problem, same message, with the following system. WM: sway\nAttempted hacky workaround from This changes error to Progress?", "positive_passages": [{"docid": "doc-en-nixpkgs-af738fcda99fe473ab66e657466b8928ada3d4dc70aadf7f1e9f7969e690ffbb", "text": " diff --git a/profiler/build/unix/legacy.mk b/profiler/build/unix/legacy.mk index 24765f1a..8baffb68 100644 --- a/profiler/build/unix/legacy.mk +++ b/profiler/build/unix/legacy.mk @@ -16,7 +16,7 @@ else UNAME := $(shell uname -s) ifeq ($(UNAME),Darwin) SRC3 += ../../../nfd/nfd_cocoa.m -\t\tLIBS += -framework CoreFoundation -framework AppKit -framework UniformTypeIdentifiers +\t\tLIBS += -framework CoreFoundation -framework AppKit else ifdef TRACY_GTK_FILESELECTOR SRC += ../../../nfd/nfd_gtk.cpp ", "commid": "nixpkgs_pr_315205"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-b624e2e8c4cee3c185a7b6eafba4a27ad8422bef0d37215a6d958e57376a11e2", "query": "No crash n/a n/a Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nSame problem, same message, with the following system. WM: sway\nAttempted hacky workaround from This changes error to Progress?", "positive_passages": [{"docid": "doc-en-nixpkgs-a09cbc36261de8bd021d3892f0fd77bd3b0720f1b1bc75dbb263e43b0347c256", "text": " { lib , stdenv , fetchFromGitHub , capstone , darwin , dbus , freetype , glfw , hicolor-icon-theme , pkg-config , tbb , withWayland ? stdenv.isLinux , libxkbcommon , wayland }: stdenv.mkDerivation rec { pname = \"tracy\"; version = \"0.10\"; src = fetchFromGitHub { owner = \"wolfpld\"; repo = \"tracy\"; rev = \"v${version}\"; sha256 = \"sha256-DN1ExvQ5wcIUyhMAfiakFbZkDsx+5l8VMtYGvSdboPA=\"; }; patches = lib.optionals (stdenv.isDarwin && !(lib.versionAtLeast stdenv.hostPlatform.darwinMinVersion \"11\")) [ ./0001-remove-unifiedtypeidentifiers-framework ]; nativeBuildInputs = [ pkg-config ]; buildInputs = [ capstone freetype glfw ] ++ lib.optionals (stdenv.isLinux && withWayland) [ libxkbcommon wayland ] ++ lib.optionals stdenv.isLinux [ dbus hicolor-icon-theme tbb ] ++ lib.optionals stdenv.isDarwin [ darwin.apple_sdk.frameworks.AppKit darwin.apple_sdk.frameworks.Carbon ] ++ lib.optionals (stdenv.isDarwin && lib.versionAtLeast stdenv.hostPlatform.darwinMinVersion \"11\") [ darwin.apple_sdk.frameworks.UniformTypeIdentifiers ]; env.NIX_CFLAGS_COMPILE = toString ([ ] # Apple's compiler finds a format string security error on # ../../../server/TracyView.cpp:649:34, preventing building. ++ lib.optional stdenv.isDarwin \"-Wno-format-security\" ++ lib.optional stdenv.isLinux \"-ltbb\" ++ lib.optional stdenv.cc.isClang \"-faligned-allocation\" # workaround issue #19098 ++ lib.optional (stdenv.cc.isClang && stdenv.isDarwin) \"-fno-lto\"); buildPhase = '' runHook preBuild make -j $NIX_BUILD_CORES -C capture/build/unix release make -j $NIX_BUILD_CORES -C csvexport/build/unix release make -j $NIX_BUILD_CORES -C import-chrome/build/unix release make -j $NIX_BUILD_CORES -C library/unix release make -j $NIX_BUILD_CORES -C profiler/build/unix release ${lib.optionalString (stdenv.isLinux && !withWayland) \"LEGACY=1\"} make -j $NIX_BUILD_CORES -C update/build/unix release runHook postBuild ''; installPhase = '' runHook preInstall install -D -m 0755 capture/build/unix/capture-release $out/bin/capture install -D -m 0755 csvexport/build/unix/csvexport-release $out/bin/tracy-csvexport install -D -m 0755 import-chrome/build/unix/import-chrome-release $out/bin/import-chrome install -D -m 0755 library/unix/libtracy-release.so $out/lib/libtracy.so install -D -m 0755 profiler/build/unix/Tracy-release $out/bin/tracy install -D -m 0755 update/build/unix/update-release $out/bin/update mkdir -p $out/include/Tracy/client mkdir -p $out/include/Tracy/common mkdir -p $out/include/Tracy/tracy cp -p public/client/*.{h,hpp} $out/include/Tracy/client cp -p public/common/*.{h,hpp} $out/include/Tracy/common cp -p public/tracy/*.{h,hpp} $out/include/Tracy/tracy '' + lib.optionalString stdenv.isLinux '' substituteInPlace extra/desktop/tracy.desktop --replace Exec=/usr/bin/tracy Exec=tracy install -D -m 0644 extra/desktop/application-tracy.xml $out/share/mime/packages/application-tracy.xml install -D -m 0644 extra/desktop/tracy.desktop $out/share/applications/tracy.desktop install -D -m 0644 icon/application-tracy.svg $out/share/icons/hicolor/scalable/apps/application-tracy.svg install -D -m 0644 icon/icon.png $out/share/icons/hicolor/256x256/apps/tracy.png install -D -m 0644 icon/icon.svg $out/share/icons/hicolor/scalable/apps/tracy.svg '' + '' runHook postInstall ''; postFixup = lib.optionalString stdenv.isDarwin '' install_name_tool -change libcapstone.4.dylib ${capstone}/lib/libcapstone.4.dylib $out/bin/tracy ''; meta = with lib; { description = \"Real time, nanosecond resolution, remote telemetry frame profiler for games and other applications\"; homepage = \"https://github.com/wolfpld/tracy\"; platforms = platforms.linux ++ platforms.darwin; license = licenses.bsd3; mainProgram = \"tracy\"; maintainers = with maintainers; [ mpickering nagisa paveloom ]; }; } ", "commid": "nixpkgs_pr_315205"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-b624e2e8c4cee3c185a7b6eafba4a27ad8422bef0d37215a6d958e57376a11e2", "query": "No crash n/a n/a Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nSame problem, same message, with the following system. WM: sway\nAttempted hacky workaround from This changes error to Progress?", "positive_passages": [{"docid": "doc-en-nixpkgs-11548df87c90bc48543bfc6e8c7d9678b32c0ce28403891a303996f1ca2d6de2", "text": " diff --git a/profiler/build/unix/legacy.mk b/profiler/build/unix/legacy.mk index 24765f1a..8baffb68 100644 --- a/profiler/build/unix/legacy.mk +++ b/profiler/build/unix/legacy.mk @@ -16,7 +16,7 @@ else UNAME := $(shell uname -s) ifeq ($(UNAME),Darwin) SRC3 += ../../../nfd/nfd_cocoa.m -\t\tLIBS += -framework CoreFoundation -framework AppKit -framework UniformTypeIdentifiers +\t\tLIBS += -framework CoreFoundation -framework AppKit else ifdef TRACY_GTK_FILESELECTOR SRC += ../../../nfd/nfd_gtk.cpp ", "commid": "nixpkgs_pr_315205"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-b624e2e8c4cee3c185a7b6eafba4a27ad8422bef0d37215a6d958e57376a11e2", "query": "No crash n/a n/a Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nSame problem, same message, with the following system. WM: sway\nAttempted hacky workaround from This changes error to Progress?", "positive_passages": [{"docid": "doc-en-nixpkgs-6edb29d1f91a5b236f4128177bb8b1d9c9ee07c95958680adf9c28a4eda6c1fb", "text": " { lib , stdenv , fetchFromGitHub , capstone , darwin , dbus , freetype , glfw , hicolor-icon-theme , pkg-config , tbb }: stdenv.mkDerivation rec { pname = \"tracy\"; version = \"0.10\"; src = fetchFromGitHub { owner = \"wolfpld\"; repo = \"tracy\"; rev = \"v${version}\"; sha256 = \"sha256-DN1ExvQ5wcIUyhMAfiakFbZkDsx+5l8VMtYGvSdboPA=\"; }; patches = lib.optionals (stdenv.isDarwin && !(lib.versionAtLeast stdenv.hostPlatform.darwinMinVersion \"11\")) [ ./0001-remove-unifiedtypeidentifiers-framework ]; nativeBuildInputs = [ pkg-config ]; buildInputs = [ capstone freetype glfw ] ++ lib.optionals stdenv.isLinux [ dbus hicolor-icon-theme tbb ] ++ lib.optionals stdenv.isDarwin [ darwin.apple_sdk.frameworks.AppKit darwin.apple_sdk.frameworks.Carbon ] ++ lib.optionals (stdenv.isDarwin && lib.versionAtLeast stdenv.hostPlatform.darwinMinVersion \"11\") [ darwin.apple_sdk.frameworks.UniformTypeIdentifiers ]; env.NIX_CFLAGS_COMPILE = toString ([ ] # Apple's compiler finds a format string security error on # ../../../server/TracyView.cpp:649:34, preventing building. ++ lib.optional stdenv.isDarwin \"-Wno-format-security\" ++ lib.optional stdenv.isLinux \"-ltbb\" ++ lib.optional stdenv.cc.isClang \"-faligned-allocation\" # workaround issue #19098 ++ lib.optional (stdenv.cc.isClang && stdenv.isDarwin) \"-fno-lto\"); buildPhase = '' runHook preBuild make -j $NIX_BUILD_CORES -C capture/build/unix release make -j $NIX_BUILD_CORES -C csvexport/build/unix release make -j $NIX_BUILD_CORES -C import-chrome/build/unix release make -j $NIX_BUILD_CORES -C library/unix release make -j $NIX_BUILD_CORES -C profiler/build/unix release LEGACY=1 make -j $NIX_BUILD_CORES -C update/build/unix release runHook postBuild ''; installPhase = '' runHook preInstall install -D -m 0755 capture/build/unix/capture-release $out/bin/capture install -D -m 0755 csvexport/build/unix/csvexport-release $out/bin/tracy-csvexport install -D -m 0755 import-chrome/build/unix/import-chrome-release $out/bin/import-chrome install -D -m 0755 library/unix/libtracy-release.so $out/lib/libtracy.so install -D -m 0755 profiler/build/unix/Tracy-release $out/bin/tracy install -D -m 0755 update/build/unix/update-release $out/bin/update mkdir -p $out/include/Tracy/client mkdir -p $out/include/Tracy/common mkdir -p $out/include/Tracy/tracy cp -p public/client/*.{h,hpp} $out/include/Tracy/client cp -p public/common/*.{h,hpp} $out/include/Tracy/common cp -p public/tracy/*.{h,hpp} $out/include/Tracy/tracy '' + lib.optionalString stdenv.isLinux '' substituteInPlace extra/desktop/tracy.desktop --replace Exec=/usr/bin/tracy Exec=tracy install -D -m 0644 extra/desktop/application-tracy.xml $out/share/mime/packages/application-tracy.xml install -D -m 0644 extra/desktop/tracy.desktop $out/share/applications/tracy.desktop install -D -m 0644 icon/application-tracy.svg $out/share/icons/hicolor/scalable/apps/application-tracy.svg install -D -m 0644 icon/icon.png $out/share/icons/hicolor/256x256/apps/tracy.png install -D -m 0644 icon/icon.svg $out/share/icons/hicolor/scalable/apps/tracy.svg '' + '' runHook postInstall ''; postFixup = lib.optionalString stdenv.isDarwin '' install_name_tool -change libcapstone.4.dylib ${capstone}/lib/libcapstone.4.dylib $out/bin/tracy ''; meta = with lib; { description = \"Real time, nanosecond resolution, remote telemetry frame profiler for games and other applications\"; homepage = \"https://github.com/wolfpld/tracy\"; platforms = platforms.linux ++ platforms.darwin; license = licenses.bsd3; mainProgram = \"tracy\"; maintainers = with maintainers; [ mpickering nagisa paveloom ]; }; } ", "commid": "nixpkgs_pr_315205"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-b624e2e8c4cee3c185a7b6eafba4a27ad8422bef0d37215a6d958e57376a11e2", "query": "No crash n/a n/a Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nSame problem, same message, with the following system. WM: sway\nAttempted hacky workaround from This changes error to Progress?", "positive_passages": [{"docid": "doc-en-nixpkgs-49857cc2142dd0ca6a50b45c5d147c90bf312a3cd4f265917817064b93a8083c", "text": "tracker = callPackage ../development/libraries/tracker { }; tracy = callPackage ../development/tools/tracy { }; tracy-x11 = callPackage ../by-name/tr/tracy/package.nix { withWayland = false; }; trivy = callPackage ../tools/admin/trivy { };", "commid": "nixpkgs_pr_315205"}], "negative_passages": []} {"query_id": "q-en-nixpkgs-a0d77f17df829f9cd4ee8b6c20e8434aafec46bfc0d019efbf818fd0b8556a3e", "query": "A clear and concise description of what the bug is. In , XDGSESSIONTYPE is now set to wayland by default for Hyprland users. However, SDDM will crash when this env var is set. Steps to reproduce the behavior: SDDM with Set under . SDDM greet will never show, and the screen will be black. These two lines can be seen in journalctl, and they are not present for boots from older generations. SDDM does not crash.