{"query_id": "q-en-nixpkgs-5c6c65eca04b10446947d8085f6fac9674a23872d4042d5bae7e40b2107ba2a7", "query": "Describe the bug On NixOS 20.09 and unstable, is not in the search path, even though it is installed with the php package. To Reproduce Steps to reproduce the behavior: [example from 20.09 system] Expected behavior [example from 20.03 system] Additional context Debugging with reveals that on 20.09, php is searching in , then , which fails. On 20.03, it searches in , then , which succeeds. On 20.09 and unstable, php74 and php73 both fail. On 20.03, php73 (the default) works, but php74 fails, but I believe it fails for a different reason. This line is new since release-20.03. At first glance, it seems as though is resolving to null here, but I'm not sure what to replace it with: Notify maintainers Metadata Maintainer information:\nThanks for reporting this issue! Your guess was right on spot and it was a really simple fix it seems :slightlysmilingface: As you may have seen: Right after 20.03 branched off we started a big refactoring of the PHP ecosystem. So bugs and issues was to be expected :slightlysmilingface:", "positive_passages": [{"docid": "doc-en-nixpkgs-fba1ec65e889673097e30113e6a52b7cb705a95fad6406cbd939fef826b69357", "text": "++ lib.optional (!cgiSupport) \"--disable-cgi\" ++ lib.optional (!cliSupport) \"--disable-cli\" ++ lib.optional fpmSupport \"--enable-fpm\" ++ lib.optional pearSupport [ \"--with-pear=$(out)/lib/php/pear\" \"--enable-xml\" \"--with-libxml\" ] ++ lib.optional pearSupport [ \"--with-pear\" \"--enable-xml\" \"--with-libxml\" ] ++ lib.optionals (pearSupport && (lib.versionOlder version \"7.4\")) [ \"--enable-libxml\" \"--with-libxml-dir=${libxml2.dev}\"", "commid": "nixpkgs_pr_100473"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-381d4f3bd022fc45e1f3a963a51ff21141f861531b553dcd5cae11bfb14dd7a9", "query": "I'm using the example of which renders correctly in firefox (the text in that section matches the image), but not in chromium (I see some placeholder boxes) my font configuration is exactly that given in I'm running nixos-unstable. I don't have flash enabled, or any other modifications to the default chromium package. From a bit of research, I've found that it might be the case that chromium restricts access to system fonts in some way, as a privacy aid - possibly that is to blame. Note: this occurs without any addons (running chromium as )", "positive_passages": [{"docid": "doc-en-nixpkgs-993ee1b8954095e9ed121217222877a81bd233b1c2cd3c2266c6d854ac73670a", "text": "{stdenv, fetchurl}: stdenv.mkDerivation rec { name = \"ncompress-4.2.4.3\"; name = \"ncompress-4.2.4.4\"; builder = ./builder.sh;", "commid": "nixpkgs_pr_22"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-381d4f3bd022fc45e1f3a963a51ff21141f861531b553dcd5cae11bfb14dd7a9", "query": "I'm using the example of which renders correctly in firefox (the text in that section matches the image), but not in chromium (I see some placeholder boxes) my font configuration is exactly that given in I'm running nixos-unstable. I don't have flash enabled, or any other modifications to the default chromium package. From a bit of research, I've found that it might be the case that chromium restricts access to system fonts in some way, as a privacy aid - possibly that is to blame. Note: this occurs without any addons (running chromium as )", "positive_passages": [{"docid": "doc-en-nixpkgs-a1c30d85cc5a9652a65ff7701252e9d3222fed9969214ff476ff2e9c54894afc", "text": "src = fetchurl { url = \"mirror://sourceforge/project/ncompress/${name}.tar.gz\"; sha256 = \"1y44ixc1w2vfvj1lm4dkcljlwv882ynrvm5i6l0lg1gf883j246l\"; sha256 = \"0yjiwv1hwb253x3m6r1dq2k7m5c9nz0ib2j7fnm3hark7y6s42xh\"; }; meta = {", "commid": "nixpkgs_pr_22"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-4a6f04bb476939757eab596e4c318e0af047adf3e8544928d4ad651325023c32", "query": "Describe the bug When cinnamon is started either via gdm or in a . Sometimes the desktop icons do load Always a window spawns telling me that I'm in fallback mode no taskbar, no window decorations (hence I think no compositor & window manager) To Reproduce Here I'm kind of unsure: I deleted all nemo and cinnamon folder in $HOME, .config and .local/share. Still this occurs on all of my machines. IIRC this first happen when accidentally starting a \"virtual keyboard\" app cinnamon \"Virtual keyboard\" cinnamon components crash instantly, the and the behavior is reproducible on further attempts of starting cinnamon Expected behavior Cinnamon starts and is usable Additional context Booting into an old generation did not fix this, however, I'm quite unsure what could be the cause of it. This is some log which I could create by running cinnamon from a . I'm not sure whether this is related to the issue or not. relevant : Output captured (the log is over 2000 lines long, this is from the very end and might be the issue): Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(wucke13): nixpkgs: Maintainer information:\nI will say that it does start in lightdm. IIRC upstream uses slick greeter and lightdm, so maybe it's just broken for that dm.\nit is broken when started on as well, and it used to work in gdm just a day a go as well. Thinking more of the problem, what else can break the startup of cinnamon if all of these are empty/removed: + + + ? There must be something in my $HOME which alters the startup procedure of cinnamon to break (otherwise it wouldn't work for you?!) but what can it be? Edit: I now gathered a more meaningful error: Edit 2: Found the remaining part thing: dconf. After renaming , cinnamon starts just fine. Holy moly. Running \"Virtual keyboard\" from the cinnamon menu breaks it immediately, though.\nWhich package provides gio for ? We'd need to add that to buildInputs then the error should be fixed\nThat is . Be sure to on the source code to always run a to see what namespaces are imported. From there you track where those typelibs come from to determine the dependencies that belong in\nAny updates on this?\nIt would need to be tested if the issue still persists.\nThe bug is still persistent. system: host os: multi-user?: sandbox: version: channels(root): channels(wucke13): nixpkgs:\nThe bug is still present in 21.05: system: host os: multi-user?: sandbox: version: channels(root): channels(wucke13): nixpkgs:\nThe main problem I have is that I have no idea where to even start debugging the segfault, as it seems to be part of native code\nAny chances upstream has some idea? Not sure how to get in touch with them without making it seem like \"We have a problem and you shall fix it\".\nI ran and I found that it is missing , just install it and the bug will disappear. I think this package is a must or we have a security-issue here\nI can confirm installing caribou fixes the issue. I haven't really looked into it yet, the related line is likely at And I managed to SIGSEGV gjs-console (cjs-console) in a shell with: I search for the output , and found this So I do and the SIGSEGV is gone. So I guess caribou is needed for this case.", "positive_passages": [{"docid": "doc-en-nixpkgs-f8ca1b68dde7f45bc1b408242c5e8525e2bbe204858f3887bd413ccaecc6cf25", "text": "intltool gtk-doc perl python3.pkgs.wrapPython ]; # use locales from cinnamon-translations (not using --localedir because datadir is used)", "commid": "nixpkgs_pr_187434"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-4a6f04bb476939757eab596e4c318e0af047adf3e8544928d4ad651325023c32", "query": "Describe the bug When cinnamon is started either via gdm or in a . Sometimes the desktop icons do load Always a window spawns telling me that I'm in fallback mode no taskbar, no window decorations (hence I think no compositor & window manager) To Reproduce Here I'm kind of unsure: I deleted all nemo and cinnamon folder in $HOME, .config and .local/share. Still this occurs on all of my machines. IIRC this first happen when accidentally starting a \"virtual keyboard\" app cinnamon \"Virtual keyboard\" cinnamon components crash instantly, the and the behavior is reproducible on further attempts of starting cinnamon Expected behavior Cinnamon starts and is usable Additional context Booting into an old generation did not fix this, however, I'm quite unsure what could be the cause of it. This is some log which I could create by running cinnamon from a . I'm not sure whether this is related to the issue or not. relevant : Output captured (the log is over 2000 lines long, this is from the very end and might be the issue): Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(wucke13): nixpkgs: Maintainer information:\nI will say that it does start in lightdm. IIRC upstream uses slick greeter and lightdm, so maybe it's just broken for that dm.\nit is broken when started on as well, and it used to work in gdm just a day a go as well. Thinking more of the problem, what else can break the startup of cinnamon if all of these are empty/removed: + + + ? There must be something in my $HOME which alters the startup procedure of cinnamon to break (otherwise it wouldn't work for you?!) but what can it be? Edit: I now gathered a more meaningful error: Edit 2: Found the remaining part thing: dconf. After renaming , cinnamon starts just fine. Holy moly. Running \"Virtual keyboard\" from the cinnamon menu breaks it immediately, though.\nWhich package provides gio for ? We'd need to add that to buildInputs then the error should be fixed\nThat is . Be sure to on the source code to always run a to see what namespaces are imported. From there you track where those typelibs come from to determine the dependencies that belong in\nAny updates on this?\nIt would need to be tested if the issue still persists.\nThe bug is still persistent. system: host os: multi-user?: sandbox: version: channels(root): channels(wucke13): nixpkgs:\nThe bug is still present in 21.05: system: host os: multi-user?: sandbox: version: channels(root): channels(wucke13): nixpkgs:\nThe main problem I have is that I have no idea where to even start debugging the segfault, as it seems to be part of native code\nAny chances upstream has some idea? Not sure how to get in touch with them without making it seem like \"We have a problem and you shall fix it\".\nI ran and I found that it is missing , just install it and the bug will disappear. I think this package is a must or we have a security-issue here\nI can confirm installing caribou fixes the issue. I haven't really looked into it yet, the related line is likely at And I managed to SIGSEGV gjs-console (cjs-console) in a shell with: I search for the output , and found this So I do and the SIGSEGV is gone. So I guess caribou is needed for this case.", "positive_passages": [{"docid": "doc-en-nixpkgs-3977dbd4aca2257100fdb2c36079c59aa267c86407dd91997cc01494080581f2", "text": "patchShebangs src/data-to-c.pl ''; preFixup = '' # https://github.com/NixOS/nixpkgs/issues/101881 gappsWrapperArgs+=( --prefix XDG_DATA_DIRS : \"${gnome.caribou}/share\" ) # https://github.com/NixOS/nixpkgs/issues/129946 buildPythonPath \"${python3.pkgs.xapp}\" patchPythonScript $out/share/cinnamon/cinnamon-desktop-editor/cinnamon-desktop-editor.py ''; passthru = { providedSessions = [ \"cinnamon\" \"cinnamon2d\" ]; };", "commid": "nixpkgs_pr_187434"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-749c78a9d855c6c677e5baf80960970da2301fce8486aa55b91ac39497ecefd2", "query": ", CVSSv3=8.8 (nixos-20.03, nixos-20.09, nixos-unstable) Scanned versions: nixos-20.03: ; nixos-20.09: ; nixos-unstable: . Cc", "positive_passages": [{"docid": "doc-en-nixpkgs-ce914f0ea1d95c5626e7cdb0096a256a07b7111cbe1614d790b594cdcfb5ddff", "text": "{ stdenv, fetchurl, pkgconfig, yasm , freetype, fribidi , freetype, fribidi, harfbuzz , encaSupport ? true, enca ? null # enca support , fontconfigSupport ? true, fontconfig ? null # fontconfig support , harfbuzzSupport ? true, harfbuzz ? null # harfbuzz support , rasterizerSupport ? false # Internal rasterizer , largeTilesSupport ? false # Use larger tiles in the rasterizer , libiconv", "commid": "nixpkgs_pr_105597"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-749c78a9d855c6c677e5baf80960970da2301fce8486aa55b91ac39497ecefd2", "query": ", CVSSv3=8.8 (nixos-20.03, nixos-20.09, nixos-unstable) Scanned versions: nixos-20.03: ; nixos-20.09: ; nixos-unstable: . Cc", "positive_passages": [{"docid": "doc-en-nixpkgs-e6107949890a3a0f55251dbf05fff3e276594312a78e342ca8d788e501334931", "text": "assert encaSupport -> enca != null; assert fontconfigSupport -> fontconfig != null; assert harfbuzzSupport -> harfbuzz != null; let mkFlag = optSet: flag: if optSet then \"--enable-${flag}\" else \"--disable-${flag}\";", "commid": "nixpkgs_pr_105597"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-749c78a9d855c6c677e5baf80960970da2301fce8486aa55b91ac39497ecefd2", "query": ", CVSSv3=8.8 (nixos-20.03, nixos-20.09, nixos-unstable) Scanned versions: nixos-20.03: ; nixos-20.09: ; nixos-unstable: . Cc", "positive_passages": [{"docid": "doc-en-nixpkgs-6af4c4707316a0aad069619adc8f985fbbc4ebae93192b2edc7605f81a5dad27", "text": "with stdenv.lib; stdenv.mkDerivation rec { pname = \"libass\"; version = \"0.14.0\"; version = \"0.15.0\"; src = fetchurl { url = \"https://github.com/libass/libass/releases/download/${version}/${pname}-${version}.tar.xz\"; sha256 = \"18iqznl4mabhj9ywfsz4kwvbsplcv1jjxq50nxssvbj8my1267w8\"; sha256 = \"0cz8v6kh3f2j5rdjrra2z0h715fa16vjm7kambvqx9hak86262cz\"; }; configureFlags = [ (mkFlag encaSupport \"enca\") (mkFlag fontconfigSupport \"fontconfig\") (mkFlag harfbuzzSupport \"harfbuzz\") (mkFlag rasterizerSupport \"rasterizer\") (mkFlag largeTilesSupport \"large-tiles\") ]; nativeBuildInputs = [ pkgconfig yasm ]; buildInputs = [ freetype fribidi ] buildInputs = [ freetype fribidi harfbuzz ] ++ optional encaSupport enca ++ optional fontconfigSupport fontconfig ++ optional harfbuzzSupport harfbuzz ++ optional stdenv.isDarwin libiconv; meta = {", "commid": "nixpkgs_pr_105597"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-dfe78460f143649386dc0f21faa0d370d531760a0fd0c262501f001c65398e2f", "query": "With NixOS 15.09 I get this error running LilyPond: I can work around this (clumsily) by using an old version of in LilyPond's . This differs by not including . This seems to be related to Changing apparently can break some users of as well as those of .\ncc\nHmm, perhaps we should add or some similar option to handle these cases easily?\nIt's better to set in most cases, which I just did in and .", "positive_passages": [{"docid": "doc-en-nixpkgs-993ee1b8954095e9ed121217222877a81bd233b1c2cd3c2266c6d854ac73670a", "text": "{stdenv, fetchurl}: stdenv.mkDerivation rec { name = \"ncompress-4.2.4.3\"; name = \"ncompress-4.2.4.4\"; builder = ./builder.sh;", "commid": "nixpkgs_pr_22"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-dfe78460f143649386dc0f21faa0d370d531760a0fd0c262501f001c65398e2f", "query": "With NixOS 15.09 I get this error running LilyPond: I can work around this (clumsily) by using an old version of in LilyPond's . This differs by not including . This seems to be related to Changing apparently can break some users of as well as those of .\ncc\nHmm, perhaps we should add or some similar option to handle these cases easily?\nIt's better to set in most cases, which I just did in and .", "positive_passages": [{"docid": "doc-en-nixpkgs-a1c30d85cc5a9652a65ff7701252e9d3222fed9969214ff476ff2e9c54894afc", "text": "src = fetchurl { url = \"mirror://sourceforge/project/ncompress/${name}.tar.gz\"; sha256 = \"1y44ixc1w2vfvj1lm4dkcljlwv882ynrvm5i6l0lg1gf883j246l\"; sha256 = \"0yjiwv1hwb253x3m6r1dq2k7m5c9nz0ib2j7fnm3hark7y6s42xh\"; }; meta = {", "commid": "nixpkgs_pr_22"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-171246af152b99fef20bf6d1eb66375d9cbbce0c3d165d607e1e49a6712dc218", "query": "Describe the bug defines the CMake path. The environment variable is included in this, and addons like SDL2mixer append themselves to this path. However, that same file also defines an target, which does not include in its include directories. See for an example of an issue caused by this. To Reproduce Steps to reproduce the behavior: to build an application relying on SDL2::SDL2 adding SDL2mixer to the include path, such as Expected behavior 's should include the environment variable, just like . Screenshots N/A Additional context N/A Notify maintainers (SDL2), (SDL2mixer) Metadata Maintainer information:", "positive_passages": [{"docid": "doc-en-nixpkgs-1116232fbb5c1d36717158abe329318d561a5e556da97a9f8ce7e3f6a0aa5365", "text": " diff -ru3 SDL2-2.0.4/sdl2-config.cmake.in SDL2-2.0.4-new/sdl2-config.cmake.in --- SDL2-2.0.4/sdl2-config.cmake.in\t2016-01-02 22:56:31.000000000 +0300 +++ SDL2-2.0.4-new/sdl2-config.cmake.in\t2016-08-22 05:26:42.420397323 +0300 @@ -6,5 +6,6 @@ diff -ru3 SDL2-2.0.12/sdl2-config.cmake.in SDL2-2.0.12-new/sdl2-config.cmake.in --- SDL2-2.0.12/sdl2-config.cmake.in\t2020-03-11 02:36:18.000000000 +0100 +++ SDL2-2.0.12-new/sdl2-config.cmake.in\t2020-11-11 11:59:05.178703826 +0100 @@ -6,7 +6,8 @@ set(SDL2_PREFIX \"@prefix@\") set(SDL2_EXEC_PREFIX \"@prefix@\") set(SDL2_LIBDIR \"@libdir@\")", "commid": "nixpkgs_pr_103438"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-171246af152b99fef20bf6d1eb66375d9cbbce0c3d165d607e1e49a6712dc218", "query": "Describe the bug defines the CMake path. The environment variable is included in this, and addons like SDL2mixer append themselves to this path. However, that same file also defines an target, which does not include in its include directories. See for an example of an issue caused by this. To Reproduce Steps to reproduce the behavior: to build an application relying on SDL2::SDL2 adding SDL2mixer to the include path, such as Expected behavior 's should include the environment variable, just like . Screenshots N/A Additional context N/A Notify maintainers (SDL2), (SDL2mixer) Metadata Maintainer information:", "positive_passages": [{"docid": "doc-en-nixpkgs-14de40185027d0b5d9206b732743dd6efac833304b844e5253293d38ba9e0427", "text": "+set(SDL2_INCLUDE_DIRS \"@includedir@/SDL2\" $ENV{SDL2_PATH}) +separate_arguments(SDL2_INCLUDE_DIRS) set(SDL2_LIBRARIES \"-L${SDL2_LIBDIR} @SDL_RLD_FLAGS@ @SDL_LIBS@\") diff -ru3 SDL2-2.0.4/sdl2-config.in SDL2-2.0.4-new/sdl2-config.in --- SDL2-2.0.4/sdl2-config.in\t2016-01-02 22:56:31.000000000 +0300 +++ SDL2-2.0.4-new/sdl2-config.in\t2016-08-22 05:32:02.256397839 +0300 string(STRIP \"${SDL2_LIBRARIES}\" SDL2_LIBRARIES) @@ -20,14 +21,14 @@ add_library(SDL2::SDL2 SHARED IMPORTED) set_target_properties(SDL2::SDL2 PROPERTIES - INTERFACE_INCLUDE_DIRECTORIES \"@includedir@/SDL2\" + INTERFACE_INCLUDE_DIRECTORIES \"${SDL2_INCLUDE_DIRS}\" IMPORTED_LINK_INTERFACE_LANGUAGES \"C\" IMPORTED_LOCATION \"@libdir@/libSDL2.so\" INTERFACE_LINK_LIBRARIES \"${SDL2_EXTRA_LINK_FLAGS}\") add_library(SDL2::SDL2-static STATIC IMPORTED) set_target_properties(SDL2::SDL2-static PROPERTIES - INTERFACE_INCLUDE_DIRECTORIES \"@includedir@/SDL2\" + INTERFACE_INCLUDE_DIRECTORIES \"${SDL2_INCLUDE_DIRS}\" IMPORTED_LINK_INTERFACE_LANGUAGES \"C\" IMPORTED_LOCATION \"@libdir@/libSDL2.a\" INTERFACE_LINK_LIBRARIES \"${SDL2_EXTRA_LINK_FLAGS_STATIC}\") Nom\u00e9s a SDL2-2.0.12-new/: sdl2-config.cmake.in.orig diff -ru3 SDL2-2.0.12/sdl2-config.in SDL2-2.0.12-new/sdl2-config.in --- SDL2-2.0.12/sdl2-config.in\t2020-03-11 02:36:18.000000000 +0100 +++ SDL2-2.0.12-new/sdl2-config.in\t2020-11-11 11:56:26.432955479 +0100 @@ -42,7 +42,11 @@ echo @SDL_VERSION@ ;;", "commid": "nixpkgs_pr_103438"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-f7843ba261ada76f891f97521061321d01474bb552975cca6be10311f1bda28e", "query": "Experienced on gnome3.38 which is currently on master. alacritty 0.5.0 isn't functional at all. 0.6.0rc-1 is. Should we update in order to make our packages set functional? Or should we wait for a real, no rc release upstream?\nyou should update yourself in the maintainers list - I had to go to to see who is .\nIs this a wayland issue on gnome?\nYes.\nSound fine to me.\nThanks for pointing this out. As much as I want to see my first username long gone, the change was not worth it :)", "positive_passages": [{"docid": "doc-en-nixpkgs-d77f6fcc0d88631600ec7ec251d138295ef1ec1839da7acbb5b39275d847f6a5", "text": "in rustPlatform.buildRustPackage rec { pname = \"alacritty\"; version = \"0.5.0\"; # 0.5.0 is not compatible with gnome 3.38 version = \"0.6.0-rc1\"; src = fetchFromGitHub { owner = \"alacritty\"; repo = pname; rev = \"v${version}\"; sha256 = \"1948j57xhqvc5y876s929x9rhd6j0xnw5c91g1zqw2rfncn602g2\"; sha256 = \"RuIJvB0J/BQFqemOkEUiqS1uz0gMS49Dd8UQt0nbrQ0=\"; }; cargoSha256 = \"17lyzcj07f0vyki3091vgjd0w8ki11sw5m8gb3bxdph1dl04rria\"; cargoSha256 = \"+3iZywLvy+8C7j6g9bqij2DSLjBoE2u1GXgfV04cWRY=\"; nativeBuildInputs = [ cmake", "commid": "nixpkgs_pr_103817"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-7f9d7f5b6e9df6d755b618a2472254c1b3c6ebe8c3dc80511b27795ca067ca8c", "query": "Updated using I though most of the packages have moved on to openblas, what is pulling in this package? How would I find out?\nA few packages still reference it. should show what derivations use it directly, from those you have instantiated.", "positive_passages": [{"docid": "doc-en-nixpkgs-993ee1b8954095e9ed121217222877a81bd233b1c2cd3c2266c6d854ac73670a", "text": "{stdenv, fetchurl}: stdenv.mkDerivation rec { name = \"ncompress-4.2.4.3\"; name = \"ncompress-4.2.4.4\"; builder = ./builder.sh;", "commid": "nixpkgs_pr_22"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-7f9d7f5b6e9df6d755b618a2472254c1b3c6ebe8c3dc80511b27795ca067ca8c", "query": "Updated using I though most of the packages have moved on to openblas, what is pulling in this package? How would I find out?\nA few packages still reference it. should show what derivations use it directly, from those you have instantiated.", "positive_passages": [{"docid": "doc-en-nixpkgs-a1c30d85cc5a9652a65ff7701252e9d3222fed9969214ff476ff2e9c54894afc", "text": "src = fetchurl { url = \"mirror://sourceforge/project/ncompress/${name}.tar.gz\"; sha256 = \"1y44ixc1w2vfvj1lm4dkcljlwv882ynrvm5i6l0lg1gf883j246l\"; sha256 = \"0yjiwv1hwb253x3m6r1dq2k7m5c9nz0ib2j7fnm3hark7y6s42xh\"; }; meta = {", "commid": "nixpkgs_pr_22"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-78bfcf7d442e0fe3591828407bf6d4792aebae2aab1291d74526be84b96c68d5", "query": "Describe the bug option is not working To Reproduce Steps to reproduce the behavior: service and its option in . Add as well for testing. In my case I used something similar to the password read bit is set, for the test generation: (eventually) inspect logs with in a separate terminal a mail The command might return And you might find an error similar to this in your logs Tested on 19.09 and 20.09, on different machines with three different SMTP hosts, various passwords, with and without special characters. As explicitly warn in the doc Path to a file that contains the password used for SMTP auth. The file should not contain a trailing newline, if the password does not contain one. This file should be readable by the users that need to execute ssmtp. I ensured that the password do not contains a leading space or carriage return. Expected behavior should work just as well as its former obsolete attribute. Additional context eventually check again my password in the store: which is yet followed by the character . It's obviously a control character and I cannot find a definition of its meaning. The very same command (original pass file) won't return the . following configuration works, with of course the exact same password as provided in the password file. Which is obviously not the expected setup. Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:\nMake sure that it doesn't have a trailing either. Editors like vim tend to insert one by default.\nI can confirm.\nIs this still a problem?\nI haven't been able to validate the response using or alternative editors.\nUse to avoid the trailing newline. To check whether there's one, use ; with this command, newlines are displayed as .", "positive_passages": [{"docid": "doc-en-nixpkgs-9d4b7dccd79b82a98dfe0488e6bf8566db29335d436b99618c259e322b2947e7", "text": "example = \"/run/keys/ssmtp-authpass\"; description = '' Path to a file that contains the password used for SMTP auth. The file should not contain a trailing newline, if the password does not contain one. should not contain a trailing newline, if the password does not contain one (e.g. use echo -n \"password\" > file). This file should be readable by the users that need to execute ssmtp. ''; };", "commid": "nixpkgs_pr_128855"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-7e2dd9d1869c0b37e1a421e9345bc8dc92126b6e9ff1900ea93c779135deb20c", "query": "Seems like nmap changed the licence with the 7.90 release from GPL-2 to NPSL (Nmap public source licence). NPSL is \"based\" on GPL but adds some nasty things such as: Which conflicts with the freedom 0: Discussions about this: Debian: Gentoo: Upstream: The actual license file: They also seem to bundle a GPL library, and their license doesn't seem to be GPL compatible. So we should probably add this new license at least. NPSL looks non-free to me. Non-free is a good default until FSF or anyone has looked at it. We can always follow suit with what Debian does as well.\nAnother option would be to revert to 7.80 for now. The new license seems to be a legal minefield even if you're ok with closed source.\nYeah while looking at the issue in the train I thought of the same as well, will do that now.\nI just read the release annoncement for 7.90: Just to see if the license change was mentioned there. Which it is: Do I read this right they weren't really GPLv2 to begin with and just clarified that? That's like a major thing...\nFirst of all I just realized that I merged the original PR, so I really have to apologize for missing that license thing back then! cc in case you currently have time and energy for that, would you mind taking a look at the issue? I'm pretty sure that you have way more knowledge and insights about that kind of licensing issue than we have :). Is there any kind of statement from OSI or FSF yet? Also, I'm wondering if other distros that are even more focused on free software than we are (such as Guix) have e.g. started a new fork that we may want to use as well.\nMore details from the changelog: I must say that I'm not sure if it's worth to roll the package back since it actually haven't seemed to change really. It just was weird to begin with and just now got a name on the weirdness.\nIt's not just a new name, apparently they also new requirements in 7.90:\nI don't think we should revert it either. Add the new license and mark it unfree until this is clarified.\nOof.... that's actually another reason for reverting.\nI'm in favor of marking as nonfree until the FSF or some other authoritative organisation decides otherwise.\nEither revert, or mark as non-free. Or, revert and add the new, non-free, version next to it.\nThe nmap update has already been reverted. Let's wait what upstream and the legal teams of debian/fedora say. See also the upstream issue\nFedora's stance\nThat's the old license (until version 7.80). This issue is about the new license (in version 7.90).\nFedora the new licence to the bad list and marked it as \"not acceptable for use in Fedora\" due to being incompatible to the open source definition\nSo, now there's an update here that we may want to act on: To quote the post: This means that 7.91 is now available under the same license as 7.80 is. The license that 7.80 uses is still a \"bad license\" because it's still a custom license. But it's a license that we and other distributions have considered good because it was assumed to be GPLv2. So I'm thinking that we could upgrade to 7.91 by now, because it's still not good, but it's not worse than before except we are aware of it now. Then we just hope that they do some good re-licensing in a future release.\nMerged which removed nmap-unfree. This issue is done for now. Thanks everyone.", "positive_passages": [{"docid": "doc-en-nixpkgs-e81b1ca57b06ba40e6a6c584918acde5d9b2a9802b45cb1627b7f817bd469c57", "text": "stdenv.mkDerivation rec { name = \"nmap${optionalString graphicalSupport \"-graphical\"}-${version}\"; version = \"7.90\"; version = \"7.80\"; src = fetchurl { url = \"https://nmap.org/dist/nmap-${version}.tar.bz2\"; sha256 = \"1s20i84m9bci70lrl0p2j7h3kpbi9snmvyhc3lzc9s3mh92w6msm\"; sha256 = \"1aizfys6l9f9grm82bk878w56mg0zpkfns3spzj157h98875mypw\"; }; patches = [ ./zenmap.patch ]", "commid": "nixpkgs_pr_105129"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-48d6df343288765639073b6c2560bcab44bba033afd46fe03f5e7adeb01b63b3", "query": "This issue tracks the conversion of from Docbook to CommonMark per . If you intend to work on this conversion, please comment below! here that you intend to work on it. (Please also post if you stop working on it.) a new branch of nixpkgs master. : change to . to . the contents from Docbook to . Follow . Use existing sections for inspiration. from the folder to build the manual. the manual on your computer at after running from folder: it looks good, submit a PR and reference this issue.\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nI opened a PR here: Thanks in advance for reviewing :-)", "positive_passages": [{"docid": "doc-en-nixpkgs-23a168ecfbeff01eac8221ccf399e80bd003ee6a0607529d7a491b539693467e", "text": " This chapter describes tools for creating various types of images. ", "commid": "nixpkgs_pr_120231"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-48d6df343288765639073b6c2560bcab44bba033afd46fe03f5e7adeb01b63b3", "query": "This issue tracks the conversion of from Docbook to CommonMark per . If you intend to work on this conversion, please comment below! here that you intend to work on it. (Please also post if you stop working on it.) a new branch of nixpkgs master. : change to . to . the contents from Docbook to . Follow . Use existing sections for inspiration. from the folder to build the manual. the manual on your computer at after running from folder: it looks good, submit a PR and reference this issue.\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nI opened a PR here: Thanks in advance for reviewing :-)", "positive_passages": [{"docid": "doc-en-nixpkgs-bf40d342ce14c74b3e657088fd855850cfa041ec62e99025ce402942c12ae4fd", "text": " # pkgs.appimageTools {#sec-pkgs-appimageTools} `pkgs.appimageTools` is a set of functions for extracting and wrapping [AppImage](https://appimage.org/) files. They are meant to be used if traditional packaging from source is infeasible, or it would take too long. To quickly run an AppImage file, `pkgs.appimage-run` can be used as well. ::: warning The `appimageTools` API is unstable and may be subject to backwards-incompatible changes in the future. ::: ## AppImage formats {#ssec-pkgs-appimageTools-formats} There are different formats for AppImages, see [the specification](https://github.com/AppImage/AppImageSpec/blob/74ad9ca2f94bf864a4a0dac1f369dd4f00bd1c28/draft.md#image-format) for details. - Type 1 images are ISO 9660 files that are also ELF executables. - Type 2 images are ELF executables with an appended filesystem. They can be told apart with `file -k`: ```ShellSession $ file -k type1.AppImage type1.AppImage: ELF 64-bit LSB executable, x86-64, version 1 (SYSV) ISO 9660 CD-ROM filesystem data 'AppImage' (Lepton 3.x), scale 0-0, spot sensor temperature 0.000000, unit celsius, color scheme 0, calibration: offset 0.000000, slope 0.000000, dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.18, BuildID[sha1]=d629f6099d2344ad82818172add1d38c5e11bc6d, stripped012- data $ file -k type2.AppImage type2.AppImage: ELF 64-bit LSB executable, x86-64, version 1 (SYSV) (Lepton 3.x), scale 232-60668, spot sensor temperature -4.187500, color scheme 15, show scale bar, calibration: offset -0.000000, slope 0.000000 (Lepton 2.x), scale 4111-45000, spot sensor temperature 412442.250000, color scheme 3, minimum point enabled, calibration: offset -75402534979642766821519867692934234112.000000, slope 5815371847733706829839455140374904832.000000, dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.18, BuildID[sha1]=79dcc4e55a61c293c5e19edbd8d65b202842579f, stripped012- data ``` Note how the type 1 AppImage is described as an `ISO 9660 CD-ROM filesystem`, and the type 2 AppImage is not. ## Wrapping {#ssec-pkgs-appimageTools-wrapping} Depending on the type of AppImage you're wrapping, you'll have to use `wrapType1` or `wrapType2`. ```nix appimageTools.wrapType2 { # or wrapType1 name = \"patchwork\"; src = fetchurl { url = \"https://github.com/ssbc/patchwork/releases/download/v3.11.4/Patchwork-3.11.4-linux-x86_64.AppImage\"; sha256 = \"1blsprpkvm0ws9b96gb36f0rbf8f5jgmw4x6dsb1kswr4ysf591s\"; }; extraPkgs = pkgs: with pkgs; [ ]; } ``` - `name` specifies the name of the resulting image. - `src` specifies the AppImage file to extract. - `extraPkgs` allows you to pass a function to include additional packages inside the FHS environment your AppImage is going to run in. There are a few ways to learn which dependencies an application needs: - Looking through the extracted AppImage files, reading its scripts and running `patchelf` and `ldd` on its executables. This can also be done in `appimage-run`, by setting `APPIMAGE_DEBUG_EXEC=bash`. - Running `strace -vfefile` on the wrapped executable, looking for libraries that can't be found. ", "commid": "nixpkgs_pr_120231"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-48d6df343288765639073b6c2560bcab44bba033afd46fe03f5e7adeb01b63b3", "query": "This issue tracks the conversion of from Docbook to CommonMark per . If you intend to work on this conversion, please comment below! here that you intend to work on it. (Please also post if you stop working on it.) a new branch of nixpkgs master. : change to . to . the contents from Docbook to . Follow . Use existing sections for inspiration. from the folder to build the manual. the manual on your computer at after running from folder: it looks good, submit a PR and reference this issue.\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nI opened a PR here: Thanks in advance for reviewing :-)", "positive_passages": [{"docid": "doc-en-nixpkgs-f9f9614029f676b6b1cb9b1df94bb189abaf2976455b18fed4a353c190ad872b", "text": "pkgs.appimageToolspkgs.appimageTools is a set of functions for extracting and wrapping AppImage files. They are meant to be used if traditional packaging from source is infeasible, or it would take too long. To quickly run an AppImage file, pkgs.appimage-run can be used as well. The appimageTools API is unstable and may be subject to backwards-incompatible changes in the future. AppImage formats There are different formats for AppImages, see the specification for details. Type 1 images are ISO 9660 files that are also ELF executables. Type 2 images are ELF executables with an appended filesystem. They can be told apart with file -k: $ file -k type1.AppImage type1.AppImage: ELF 64-bit LSB executable, x86-64, version 1 (SYSV) ISO 9660 CD-ROM filesystem data 'AppImage' (Lepton 3.x), scale 0-0, spot sensor temperature 0.000000, unit celsius, color scheme 0, calibration: offset 0.000000, slope 0.000000, dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.18, BuildID[sha1]=d629f6099d2344ad82818172add1d38c5e11bc6d, stripped012- data $ file -k type2.AppImage type2.AppImage: ELF 64-bit LSB executable, x86-64, version 1 (SYSV) (Lepton 3.x), scale 232-60668, spot sensor temperature -4.187500, color scheme 15, show scale bar, calibration: offset -0.000000, slope 0.000000 (Lepton 2.x), scale 4111-45000, spot sensor temperature 412442.250000, color scheme 3, minimum point enabled, calibration: offset -75402534979642766821519867692934234112.000000, slope 5815371847733706829839455140374904832.000000, dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.18, BuildID[sha1]=79dcc4e55a61c293c5e19edbd8d65b202842579f, stripped012- data Note how the type 1 AppImage is described as an ISO 9660 CD-ROM filesystem, and the type 2 AppImage is not. Wrapping Depending on the type of AppImage you're wrapping, you'll have to use wrapType1 or wrapType2. appimageTools.wrapType2 { # or wrapType1 name = \"patchwork\"; src = fetchurl { url = \"https://github.com/ssbc/patchwork/releases/download/v3.11.4/Patchwork-3.11.4-linux-x86_64.AppImage\"; sha256 = \"1blsprpkvm0ws9b96gb36f0rbf8f5jgmw4x6dsb1kswr4ysf591s\"; }; extraPkgs = pkgs: with pkgs; [ ]; }name specifies the name of the resulting image. src specifies the AppImage file to extract. extraPkgs allows you to pass a function to include additional packages inside the FHS environment your AppImage is going to run in. There are a few ways to learn which dependencies an application needs: Looking through the extracted AppImage files, reading its scripts and running patchelf and ldd on its executables. This can also be done in appimage-run, by setting APPIMAGE_DEBUG_EXEC=bash. Running strace -vfefile on the wrapped executable, looking for libraries that can't be found. ", "commid": "nixpkgs_pr_120231"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-48d6df343288765639073b6c2560bcab44bba033afd46fe03f5e7adeb01b63b3", "query": "This issue tracks the conversion of from Docbook to CommonMark per . If you intend to work on this conversion, please comment below! here that you intend to work on it. (Please also post if you stop working on it.) a new branch of nixpkgs master. : change to . to . the contents from Docbook to . Follow . Use existing sections for inspiration. from the folder to build the manual. the manual on your computer at after running from folder: it looks good, submit a PR and reference this issue.\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nI opened a PR here: Thanks in advance for reviewing :-)", "positive_passages": [{"docid": "doc-en-nixpkgs-90390b12151f21bf713576de7d2ecba8692ba1db5ea33bffad6499a03dc2f6dd", "text": " let inherit (import { }) snapTools firefox; in snapTools.makeSnap { meta = { name = \"nix-example-firefox\"; summary = firefox.meta.description; architectures = [ \"amd64\" ]; apps.nix-example-firefox = { command = \"${firefox}/bin/firefox\"; plugs = [ \"pulseaudio\" \"camera\" \"browser-support\" \"avahi-observe\" \"cups-control\" \"desktop\" \"desktop-legacy\" \"gsettings\" \"home\" \"network\" \"mount-observe\" \"removable-media\" \"x11\" ]; }; confinement = \"strict\"; }; } ", "commid": "nixpkgs_pr_120231"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-48d6df343288765639073b6c2560bcab44bba033afd46fe03f5e7adeb01b63b3", "query": "This issue tracks the conversion of from Docbook to CommonMark per . If you intend to work on this conversion, please comment below! here that you intend to work on it. (Please also post if you stop working on it.) a new branch of nixpkgs master. : change to . to . the contents from Docbook to . Follow . Use existing sections for inspiration. from the folder to build the manual. the manual on your computer at after running from folder: it looks good, submit a PR and reference this issue.\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nI opened a PR here: Thanks in advance for reviewing :-)", "positive_passages": [{"docid": "doc-en-nixpkgs-9eed34667f52211a153b408433863df64b8ac60c15605fef226877479c9233b0", "text": " let inherit (import { }) snapTools hello; in snapTools.makeSnap { meta = { name = \"hello\"; summary = hello.meta.description; description = hello.meta.longDescription; architectures = [ \"amd64\" ]; confinement = \"strict\"; apps.hello.command = \"${hello}/bin/hello\"; }; } ", "commid": "nixpkgs_pr_120231"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-48d6df343288765639073b6c2560bcab44bba033afd46fe03f5e7adeb01b63b3", "query": "This issue tracks the conversion of from Docbook to CommonMark per . If you intend to work on this conversion, please comment below! here that you intend to work on it. (Please also post if you stop working on it.) a new branch of nixpkgs master. : change to . to . the contents from Docbook to . Follow . Use existing sections for inspiration. from the folder to build the manual. the manual on your computer at after running from folder: it looks good, submit a PR and reference this issue.\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nI opened a PR here: Thanks in advance for reviewing :-)", "positive_passages": [{"docid": "doc-en-nixpkgs-25f86e73862959de732ce2bf249e716ab86264fcbdba63dc3532538d0880b424", "text": " # pkgs.snapTools {#sec-pkgs-snapTools} `pkgs.snapTools` is a set of functions for creating Snapcraft images. Snap and Snapcraft is not used to perform these operations. ## The makeSnap Function {#ssec-pkgs-snapTools-makeSnap-signature} `makeSnap` takes a single named argument, `meta`. This argument mirrors [the upstream `snap.yaml` format](https://docs.snapcraft.io/snap-format) exactly. The `base` should not be specified, as `makeSnap` will force set it. Currently, `makeSnap` does not support creating GUI stubs. ## Build a Hello World Snap {#ssec-pkgs-snapTools-build-a-snap-hello} The following expression packages GNU Hello as a Snapcraft snap. ```{#ex-snapTools-buildSnap-hello .nix} let inherit (import { }) snapTools hello; in snapTools.makeSnap { meta = { name = \"hello\"; summary = hello.meta.description; description = hello.meta.longDescription; architectures = [ \"amd64\" ]; confinement = \"strict\"; apps.hello.command = \"${hello}/bin/hello\"; }; } ``` `nix-build` this expression and install it with `snap install ./result --dangerous`. `hello` will now be the Snapcraft version of the package. ## Build a Graphical Snap {#ssec-pkgs-snapTools-build-a-snap-firefox} Graphical programs require many more integrations with the host. This example uses Firefox as an example, because it is one of the most complicated programs we could package. ```{#ex-snapTools-buildSnap-firefox .nix} let inherit (import { }) snapTools firefox; in snapTools.makeSnap { meta = { name = \"nix-example-firefox\"; summary = firefox.meta.description; architectures = [ \"amd64\" ]; apps.nix-example-firefox = { command = \"${firefox}/bin/firefox\"; plugs = [ \"pulseaudio\" \"camera\" \"browser-support\" \"avahi-observe\" \"cups-control\" \"desktop\" \"desktop-legacy\" \"gsettings\" \"home\" \"network\" \"mount-observe\" \"removable-media\" \"x11\" ]; }; confinement = \"strict\"; }; } ``` `nix-build` this expression and install it with `snap install ./result --dangerous`. `nix-example-firefox` will now be the Snapcraft version of the Firefox package. The specific meaning behind plugs can be looked up in the [Snapcraft interface documentation](https://docs.snapcraft.io/supported-interfaces). ", "commid": "nixpkgs_pr_120231"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-48d6df343288765639073b6c2560bcab44bba033afd46fe03f5e7adeb01b63b3", "query": "This issue tracks the conversion of from Docbook to CommonMark per . If you intend to work on this conversion, please comment below! here that you intend to work on it. (Please also post if you stop working on it.) a new branch of nixpkgs master. : change to . to . the contents from Docbook to . Follow . Use existing sections for inspiration. from the folder to build the manual. the manual on your computer at after running from folder: it looks good, submit a PR and reference this issue.\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nI opened a PR here: Thanks in advance for reviewing :-)", "positive_passages": [{"docid": "doc-en-nixpkgs-23a23b6ac822c2b2d70d60da368d86fe7563ba53110c294ef30dd3f14ed872a9", "text": "pkgs.snapToolspkgs.snapTools is a set of functions for creating Snapcraft images. Snap and Snapcraft is not used to perform these operations. The makeSnap FunctionmakeSnap takes a single named argument, meta. This argument mirrors the upstream snap.yaml format exactly. The base should not be specified, as makeSnap will force set it. Currently, makeSnap does not support creating GUI stubs. Build a Hello World SnapMaking a Hello World Snap The following expression packages GNU Hello as a Snapcraft snap. nix-build this expression and install it with snap install ./result --dangerous. hello will now be the Snapcraft version of the package. Build a Hello World SnapMaking a Graphical Snap Graphical programs require many more integrations with the host. This example uses Firefox as an example, because it is one of the most complicated programs we could package. nix-build this expression and install it with snap install ./result --dangerous. nix-example-firefox will now be the Snapcraft version of the Firefox package. The specific meaning behind plugs can be looked up in the Snapcraft interface documentation. ", "commid": "nixpkgs_pr_120231"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-fc7af294ae92797743c832a4bd070673650fa5e986c6f83d3c9ed4e24f01707e", "query": "This issue tracks the conversion of from Docbook to CommonMark per . If you intend to work on this conversion, please comment below! here that you intend to work on it. (Please also post if you stop working on it.) a new branch of nixpkgs master. : change to . to . the contents from Docbook to . Follow . Use existing sections for inspiration. from the folder to build the manual. the manual on your computer at after running from folder: it looks good, submit a PR and reference this issue.", "positive_passages": [{"docid": "doc-en-nixpkgs-23a168ecfbeff01eac8221ccf399e80bd003ee6a0607529d7a491b539693467e", "text": " This chapter describes tools for creating various types of images. ", "commid": "nixpkgs_pr_120231"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-fc7af294ae92797743c832a4bd070673650fa5e986c6f83d3c9ed4e24f01707e", "query": "This issue tracks the conversion of from Docbook to CommonMark per . If you intend to work on this conversion, please comment below! here that you intend to work on it. (Please also post if you stop working on it.) a new branch of nixpkgs master. : change to . to . the contents from Docbook to . Follow . Use existing sections for inspiration. from the folder to build the manual. the manual on your computer at after running from folder: it looks good, submit a PR and reference this issue.", "positive_passages": [{"docid": "doc-en-nixpkgs-bf40d342ce14c74b3e657088fd855850cfa041ec62e99025ce402942c12ae4fd", "text": " # pkgs.appimageTools {#sec-pkgs-appimageTools} `pkgs.appimageTools` is a set of functions for extracting and wrapping [AppImage](https://appimage.org/) files. They are meant to be used if traditional packaging from source is infeasible, or it would take too long. To quickly run an AppImage file, `pkgs.appimage-run` can be used as well. ::: warning The `appimageTools` API is unstable and may be subject to backwards-incompatible changes in the future. ::: ## AppImage formats {#ssec-pkgs-appimageTools-formats} There are different formats for AppImages, see [the specification](https://github.com/AppImage/AppImageSpec/blob/74ad9ca2f94bf864a4a0dac1f369dd4f00bd1c28/draft.md#image-format) for details. - Type 1 images are ISO 9660 files that are also ELF executables. - Type 2 images are ELF executables with an appended filesystem. They can be told apart with `file -k`: ```ShellSession $ file -k type1.AppImage type1.AppImage: ELF 64-bit LSB executable, x86-64, version 1 (SYSV) ISO 9660 CD-ROM filesystem data 'AppImage' (Lepton 3.x), scale 0-0, spot sensor temperature 0.000000, unit celsius, color scheme 0, calibration: offset 0.000000, slope 0.000000, dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.18, BuildID[sha1]=d629f6099d2344ad82818172add1d38c5e11bc6d, stripped012- data $ file -k type2.AppImage type2.AppImage: ELF 64-bit LSB executable, x86-64, version 1 (SYSV) (Lepton 3.x), scale 232-60668, spot sensor temperature -4.187500, color scheme 15, show scale bar, calibration: offset -0.000000, slope 0.000000 (Lepton 2.x), scale 4111-45000, spot sensor temperature 412442.250000, color scheme 3, minimum point enabled, calibration: offset -75402534979642766821519867692934234112.000000, slope 5815371847733706829839455140374904832.000000, dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.18, BuildID[sha1]=79dcc4e55a61c293c5e19edbd8d65b202842579f, stripped012- data ``` Note how the type 1 AppImage is described as an `ISO 9660 CD-ROM filesystem`, and the type 2 AppImage is not. ## Wrapping {#ssec-pkgs-appimageTools-wrapping} Depending on the type of AppImage you're wrapping, you'll have to use `wrapType1` or `wrapType2`. ```nix appimageTools.wrapType2 { # or wrapType1 name = \"patchwork\"; src = fetchurl { url = \"https://github.com/ssbc/patchwork/releases/download/v3.11.4/Patchwork-3.11.4-linux-x86_64.AppImage\"; sha256 = \"1blsprpkvm0ws9b96gb36f0rbf8f5jgmw4x6dsb1kswr4ysf591s\"; }; extraPkgs = pkgs: with pkgs; [ ]; } ``` - `name` specifies the name of the resulting image. - `src` specifies the AppImage file to extract. - `extraPkgs` allows you to pass a function to include additional packages inside the FHS environment your AppImage is going to run in. There are a few ways to learn which dependencies an application needs: - Looking through the extracted AppImage files, reading its scripts and running `patchelf` and `ldd` on its executables. This can also be done in `appimage-run`, by setting `APPIMAGE_DEBUG_EXEC=bash`. - Running `strace -vfefile` on the wrapped executable, looking for libraries that can't be found. ", "commid": "nixpkgs_pr_120231"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-fc7af294ae92797743c832a4bd070673650fa5e986c6f83d3c9ed4e24f01707e", "query": "This issue tracks the conversion of from Docbook to CommonMark per . If you intend to work on this conversion, please comment below! here that you intend to work on it. (Please also post if you stop working on it.) a new branch of nixpkgs master. : change to . to . the contents from Docbook to . Follow . Use existing sections for inspiration. from the folder to build the manual. the manual on your computer at after running from folder: it looks good, submit a PR and reference this issue.", "positive_passages": [{"docid": "doc-en-nixpkgs-f9f9614029f676b6b1cb9b1df94bb189abaf2976455b18fed4a353c190ad872b", "text": "pkgs.appimageToolspkgs.appimageTools is a set of functions for extracting and wrapping AppImage files. They are meant to be used if traditional packaging from source is infeasible, or it would take too long. To quickly run an AppImage file, pkgs.appimage-run can be used as well. The appimageTools API is unstable and may be subject to backwards-incompatible changes in the future. AppImage formats There are different formats for AppImages, see the specification for details. Type 1 images are ISO 9660 files that are also ELF executables. Type 2 images are ELF executables with an appended filesystem. They can be told apart with file -k: $ file -k type1.AppImage type1.AppImage: ELF 64-bit LSB executable, x86-64, version 1 (SYSV) ISO 9660 CD-ROM filesystem data 'AppImage' (Lepton 3.x), scale 0-0, spot sensor temperature 0.000000, unit celsius, color scheme 0, calibration: offset 0.000000, slope 0.000000, dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.18, BuildID[sha1]=d629f6099d2344ad82818172add1d38c5e11bc6d, stripped012- data $ file -k type2.AppImage type2.AppImage: ELF 64-bit LSB executable, x86-64, version 1 (SYSV) (Lepton 3.x), scale 232-60668, spot sensor temperature -4.187500, color scheme 15, show scale bar, calibration: offset -0.000000, slope 0.000000 (Lepton 2.x), scale 4111-45000, spot sensor temperature 412442.250000, color scheme 3, minimum point enabled, calibration: offset -75402534979642766821519867692934234112.000000, slope 5815371847733706829839455140374904832.000000, dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.18, BuildID[sha1]=79dcc4e55a61c293c5e19edbd8d65b202842579f, stripped012- data Note how the type 1 AppImage is described as an ISO 9660 CD-ROM filesystem, and the type 2 AppImage is not. Wrapping Depending on the type of AppImage you're wrapping, you'll have to use wrapType1 or wrapType2. appimageTools.wrapType2 { # or wrapType1 name = \"patchwork\"; src = fetchurl { url = \"https://github.com/ssbc/patchwork/releases/download/v3.11.4/Patchwork-3.11.4-linux-x86_64.AppImage\"; sha256 = \"1blsprpkvm0ws9b96gb36f0rbf8f5jgmw4x6dsb1kswr4ysf591s\"; }; extraPkgs = pkgs: with pkgs; [ ]; }name specifies the name of the resulting image. src specifies the AppImage file to extract. extraPkgs allows you to pass a function to include additional packages inside the FHS environment your AppImage is going to run in. There are a few ways to learn which dependencies an application needs: Looking through the extracted AppImage files, reading its scripts and running patchelf and ldd on its executables. This can also be done in appimage-run, by setting APPIMAGE_DEBUG_EXEC=bash. Running strace -vfefile on the wrapped executable, looking for libraries that can't be found. ", "commid": "nixpkgs_pr_120231"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-fc7af294ae92797743c832a4bd070673650fa5e986c6f83d3c9ed4e24f01707e", "query": "This issue tracks the conversion of from Docbook to CommonMark per . If you intend to work on this conversion, please comment below! here that you intend to work on it. (Please also post if you stop working on it.) a new branch of nixpkgs master. : change to . to . the contents from Docbook to . Follow . Use existing sections for inspiration. from the folder to build the manual. the manual on your computer at after running from folder: it looks good, submit a PR and reference this issue.", "positive_passages": [{"docid": "doc-en-nixpkgs-90390b12151f21bf713576de7d2ecba8692ba1db5ea33bffad6499a03dc2f6dd", "text": " let inherit (import { }) snapTools firefox; in snapTools.makeSnap { meta = { name = \"nix-example-firefox\"; summary = firefox.meta.description; architectures = [ \"amd64\" ]; apps.nix-example-firefox = { command = \"${firefox}/bin/firefox\"; plugs = [ \"pulseaudio\" \"camera\" \"browser-support\" \"avahi-observe\" \"cups-control\" \"desktop\" \"desktop-legacy\" \"gsettings\" \"home\" \"network\" \"mount-observe\" \"removable-media\" \"x11\" ]; }; confinement = \"strict\"; }; } ", "commid": "nixpkgs_pr_120231"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-fc7af294ae92797743c832a4bd070673650fa5e986c6f83d3c9ed4e24f01707e", "query": "This issue tracks the conversion of from Docbook to CommonMark per . If you intend to work on this conversion, please comment below! here that you intend to work on it. (Please also post if you stop working on it.) a new branch of nixpkgs master. : change to . to . the contents from Docbook to . Follow . Use existing sections for inspiration. from the folder to build the manual. the manual on your computer at after running from folder: it looks good, submit a PR and reference this issue.", "positive_passages": [{"docid": "doc-en-nixpkgs-9eed34667f52211a153b408433863df64b8ac60c15605fef226877479c9233b0", "text": " let inherit (import { }) snapTools hello; in snapTools.makeSnap { meta = { name = \"hello\"; summary = hello.meta.description; description = hello.meta.longDescription; architectures = [ \"amd64\" ]; confinement = \"strict\"; apps.hello.command = \"${hello}/bin/hello\"; }; } ", "commid": "nixpkgs_pr_120231"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-fc7af294ae92797743c832a4bd070673650fa5e986c6f83d3c9ed4e24f01707e", "query": "This issue tracks the conversion of from Docbook to CommonMark per . If you intend to work on this conversion, please comment below! here that you intend to work on it. (Please also post if you stop working on it.) a new branch of nixpkgs master. : change to . to . the contents from Docbook to . Follow . Use existing sections for inspiration. from the folder to build the manual. the manual on your computer at after running from folder: it looks good, submit a PR and reference this issue.", "positive_passages": [{"docid": "doc-en-nixpkgs-25f86e73862959de732ce2bf249e716ab86264fcbdba63dc3532538d0880b424", "text": " # pkgs.snapTools {#sec-pkgs-snapTools} `pkgs.snapTools` is a set of functions for creating Snapcraft images. Snap and Snapcraft is not used to perform these operations. ## The makeSnap Function {#ssec-pkgs-snapTools-makeSnap-signature} `makeSnap` takes a single named argument, `meta`. This argument mirrors [the upstream `snap.yaml` format](https://docs.snapcraft.io/snap-format) exactly. The `base` should not be specified, as `makeSnap` will force set it. Currently, `makeSnap` does not support creating GUI stubs. ## Build a Hello World Snap {#ssec-pkgs-snapTools-build-a-snap-hello} The following expression packages GNU Hello as a Snapcraft snap. ```{#ex-snapTools-buildSnap-hello .nix} let inherit (import { }) snapTools hello; in snapTools.makeSnap { meta = { name = \"hello\"; summary = hello.meta.description; description = hello.meta.longDescription; architectures = [ \"amd64\" ]; confinement = \"strict\"; apps.hello.command = \"${hello}/bin/hello\"; }; } ``` `nix-build` this expression and install it with `snap install ./result --dangerous`. `hello` will now be the Snapcraft version of the package. ## Build a Graphical Snap {#ssec-pkgs-snapTools-build-a-snap-firefox} Graphical programs require many more integrations with the host. This example uses Firefox as an example, because it is one of the most complicated programs we could package. ```{#ex-snapTools-buildSnap-firefox .nix} let inherit (import { }) snapTools firefox; in snapTools.makeSnap { meta = { name = \"nix-example-firefox\"; summary = firefox.meta.description; architectures = [ \"amd64\" ]; apps.nix-example-firefox = { command = \"${firefox}/bin/firefox\"; plugs = [ \"pulseaudio\" \"camera\" \"browser-support\" \"avahi-observe\" \"cups-control\" \"desktop\" \"desktop-legacy\" \"gsettings\" \"home\" \"network\" \"mount-observe\" \"removable-media\" \"x11\" ]; }; confinement = \"strict\"; }; } ``` `nix-build` this expression and install it with `snap install ./result --dangerous`. `nix-example-firefox` will now be the Snapcraft version of the Firefox package. The specific meaning behind plugs can be looked up in the [Snapcraft interface documentation](https://docs.snapcraft.io/supported-interfaces). ", "commid": "nixpkgs_pr_120231"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-fc7af294ae92797743c832a4bd070673650fa5e986c6f83d3c9ed4e24f01707e", "query": "This issue tracks the conversion of from Docbook to CommonMark per . If you intend to work on this conversion, please comment below! here that you intend to work on it. (Please also post if you stop working on it.) a new branch of nixpkgs master. : change to . to . the contents from Docbook to . Follow . Use existing sections for inspiration. from the folder to build the manual. the manual on your computer at after running from folder: it looks good, submit a PR and reference this issue.", "positive_passages": [{"docid": "doc-en-nixpkgs-23a23b6ac822c2b2d70d60da368d86fe7563ba53110c294ef30dd3f14ed872a9", "text": "pkgs.snapToolspkgs.snapTools is a set of functions for creating Snapcraft images. Snap and Snapcraft is not used to perform these operations. The makeSnap FunctionmakeSnap takes a single named argument, meta. This argument mirrors the upstream snap.yaml format exactly. The base should not be specified, as makeSnap will force set it. Currently, makeSnap does not support creating GUI stubs. Build a Hello World SnapMaking a Hello World Snap The following expression packages GNU Hello as a Snapcraft snap. nix-build this expression and install it with snap install ./result --dangerous. hello will now be the Snapcraft version of the package. Build a Hello World SnapMaking a Graphical Snap Graphical programs require many more integrations with the host. This example uses Firefox as an example, because it is one of the most complicated programs we could package. nix-build this expression and install it with snap install ./result --dangerous. nix-example-firefox will now be the Snapcraft version of the Firefox package. The specific meaning behind plugs can be looked up in the Snapcraft interface documentation. ", "commid": "nixpkgs_pr_120231"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-662032e7f643781cf5072e7cf48420cfdf46bb2a962ca391b10765c3ca7c5fe0", "query": "Describe the bug Milkytracker is missing a menu entry to launch the application Notify maintainers ", "commid": "nixpkgs_pr_212133"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-a7079e198aca988098951b4fa76cc9c83dc618ebe0d3503c23f6bfa32d8f7208", "query": "Since May 10, .NET 5.0 is EOL (End Of Life), and should not be used. Should it be marked as EOF similar to dotnet 2.2 and 3.0? See All packages using dotnet 5.0 should be updated to use a newer, supported version. These packages still need updating: [x] - [x] - [x] - [x] pkgs/development/tools/build- - [x] -\nThere is at least one package, which currently uses dotnet 5 sdk - . So we will need to update it beforehand. Btw, I'm not sure if we have any policy regarding packages removal, for nixpkgs in general or specifically for it's dotnet part. , what do you think?\nThe package is also using .NET 5: . But this is because I made the PR upstream updating it from .NET 4 to 5. I suspect that the transition to 6 will be similarly easy.\nI think we should just mark it as depricated, as many projects do still use it upstream. Dotnet version 3 is also still commonly used, so I dont expect it would be realistic to remove version 5 any time soon. also uses dotnet 5 by default, I'll go ahead and switch that over now. See . That doesnt mark dotnet 5 as deprecated or change anything from a SDK perspective, just some preperation work.\nSee as well, it adds a warning whenever dotnet version 5 is used. Not using a throw for now since a few packages depend on it and I dont have the time to clean that all up at the moment.\nCan you provide a list of packages that need updating?\nBased on a quick grep: pkgs/development/tools/build-\nI believe that after all the above PRs are merged, we should be able to safely remove .NET 5 from nixpkgs :)", "positive_passages": [{"docid": "doc-en-nixpkgs-3103f22975b87705799c76e83ebc9165b4e0be6b5f4bcf778f0a60f7760b645e", "text": "## Files in versions/ are generated automatically by update.sh ## dotnet_3_1 = import ./versions/3.1.nix (buildAttrs // { icu = icu70; }); dotnet_5_0 = import ./versions/5.0.nix (buildAttrs // { inherit icu; }); dotnet_6_0 = import ./versions/6.0.nix (buildAttrs // { inherit icu; }); dotnet_7_0 = import ./versions/7.0.nix (buildAttrs // { inherit icu; }); in", "commid": "nixpkgs_pr_212133"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-a7079e198aca988098951b4fa76cc9c83dc618ebe0d3503c23f6bfa32d8f7208", "query": "Since May 10, .NET 5.0 is EOL (End Of Life), and should not be used. Should it be marked as EOF similar to dotnet 2.2 and 3.0? See All packages using dotnet 5.0 should be updated to use a newer, supported version. These packages still need updating: [x] - [x] - [x] - [x] pkgs/development/tools/build- - [x] -\nThere is at least one package, which currently uses dotnet 5 sdk - . So we will need to update it beforehand. Btw, I'm not sure if we have any policy regarding packages removal, for nixpkgs in general or specifically for it's dotnet part. , what do you think?\nThe package is also using .NET 5: . But this is because I made the PR upstream updating it from .NET 4 to 5. I suspect that the transition to 6 will be similarly easy.\nI think we should just mark it as depricated, as many projects do still use it upstream. Dotnet version 3 is also still commonly used, so I dont expect it would be realistic to remove version 5 any time soon. also uses dotnet 5 by default, I'll go ahead and switch that over now. See . That doesnt mark dotnet 5 as deprecated or change anything from a SDK perspective, just some preperation work.\nSee as well, it adds a warning whenever dotnet version 5 is used. Not using a throw for now since a few packages depend on it and I dont have the time to clean that all up at the moment.\nCan you provide a list of packages that need updating?\nBased on a quick grep: pkgs/development/tools/build-\nI believe that after all the above PRs are merged, we should be able to safely remove .NET 5 from nixpkgs :)", "positive_passages": [{"docid": "doc-en-nixpkgs-1ebae56799282ad51c12b3086598db637ec6fdc2d8f1f8332f8af91349d216ee", "text": "combinePackages = attrs: callPackage (import ./combine-packages.nix attrs) {}; # EOL sdk_2_1 = throw \"Dotnet SDK 2.1 is EOL, please use 3.1 (LTS), 5.0 (Current) or 6.0 (LTS)\"; sdk_2_2 = throw \"Dotnet SDK 2.2 is EOL, please use 3.1 (LTS), 5.0 (Current) or 6.0 (LTS)\"; sdk_3_0 = throw \"Dotnet SDK 3.0 is EOL, please use 3.1 (LTS), 5.0 (Current) or 6.0 (LTS)\"; } // dotnet_3_1 // dotnet_5_0 // dotnet_6_0 // dotnet_7_0 sdk_2_1 = throw \"Dotnet SDK 2.1 is EOL, please use 6.0 (LTS) or 7.0 (Current)\"; sdk_2_2 = throw \"Dotnet SDK 2.2 is EOL, please use 6.0 (LTS) or 7.0 (Current)\"; sdk_3_0 = throw \"Dotnet SDK 3.0 is EOL, please use 6.0 (LTS) or 7.0 (Current)\"; sdk_5_0 = throw \"Dotnet SDK 5.0 is EOL, please use 6.0 (LTS) or 7.0 (Current)\"; } // dotnet_3_1 // dotnet_6_0 // dotnet_7_0 ", "commid": "nixpkgs_pr_212133"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-a7079e198aca988098951b4fa76cc9c83dc618ebe0d3503c23f6bfa32d8f7208", "query": "Since May 10, .NET 5.0 is EOL (End Of Life), and should not be used. Should it be marked as EOF similar to dotnet 2.2 and 3.0? See All packages using dotnet 5.0 should be updated to use a newer, supported version. These packages still need updating: [x] - [x] - [x] - [x] pkgs/development/tools/build- - [x] -\nThere is at least one package, which currently uses dotnet 5 sdk - . So we will need to update it beforehand. Btw, I'm not sure if we have any policy regarding packages removal, for nixpkgs in general or specifically for it's dotnet part. , what do you think?\nThe package is also using .NET 5: . But this is because I made the PR upstream updating it from .NET 4 to 5. I suspect that the transition to 6 will be similarly easy.\nI think we should just mark it as depricated, as many projects do still use it upstream. Dotnet version 3 is also still commonly used, so I dont expect it would be realistic to remove version 5 any time soon. also uses dotnet 5 by default, I'll go ahead and switch that over now. See . That doesnt mark dotnet 5 as deprecated or change anything from a SDK perspective, just some preperation work.\nSee as well, it adds a warning whenever dotnet version 5 is used. Not using a throw for now since a few packages depend on it and I dont have the time to clean that all up at the moment.\nCan you provide a list of packages that need updating?\nBased on a quick grep: pkgs/development/tools/build-\nI believe that after all the above PRs are merged, we should be able to safely remove .NET 5 from nixpkgs :)", "positive_passages": [{"docid": "doc-en-nixpkgs-abc5ca1dd4e930febbba19fb31962de8331f7f7c754704942baad46fd1abd5e3", "text": " { buildAspNetCore, buildNetRuntime, buildNetSdk, icu }: # v5.0 (eol) { aspnetcore_5_0 = buildAspNetCore { inherit icu; version = \"5.0.17\"; srcs = { x86_64-linux = { url = \"https://download.visualstudio.microsoft.com/download/pr/a2b96f83-e22a-4fa6-a10e-709b3effac9a/0d6ade6c0ceebc8ef7dbf2b1a6d86f17/aspnetcore-runtime-5.0.17-linux-x64.tar.gz\"; sha512 = \"d8e87804e9e86273c6512785bd5a6f0e834ff3f4bbebc11c4fcdf16ab4fdfabd0d981a756955267c1aa9bbeec596de3728ce9b2e6415d2d80daef0d999a5df6d\"; }; aarch64-linux = { url = \"https://download.visualstudio.microsoft.com/download/pr/6eb8aee2-cbea-4c4f-9bb9-ea6229ec229b/d6c438e5071c359ad995134f0a33e731/aspnetcore-runtime-5.0.17-linux-arm64.tar.gz\"; sha512 = \"ac1a9d89f1b730dfdca9c2e48373ef21f8f9316014eefbe6b11516f8195d3b3efc4e482883774b74ea2ff1cb77174a2cb471bd1157ab5b7d71621e3026c38e9b\"; }; x86_64-darwin = { url = \"https://download.visualstudio.microsoft.com/download/pr/25e4817f-6fd0-46dc-be0d-d819445bac5c/a8fa228c872df683741c8a79745f8fb3/aspnetcore-runtime-5.0.17-osx-x64.tar.gz\"; sha512 = \"bb0c43c723090fa2d8a0255e6fc8c004ebe7baf2d5d56e22ad2e6336a67fe415333d451e459c8857c0ccb5819d998232c9617bf45f222559d4b8891b0af41f20\"; }; }; }; runtime_5_0 = buildNetRuntime { inherit icu; version = \"5.0.17\"; srcs = { x86_64-linux = { url = \"https://download.visualstudio.microsoft.com/download/pr/e77438f6-865f-45e0-9a52-3e4b04aa609f/024a880ed4bfbfd3b9f222fec0b6aaff/dotnet-runtime-5.0.17-linux-x64.tar.gz\"; sha512 = \"a9c4784930a977abbc42aff1337dda06ec588c1ec4769a59f9fcab4d5df4fc9efe65f8e61e5433db078f67a94ea2dfe870c32c482a50d4c16283ffacacff4261\"; }; aarch64-linux = { url = \"https://download.visualstudio.microsoft.com/download/pr/6690730f-cf10-40f1-9d4d-4c0d002f22d0/e117133858f190c169873200b8d7b9d7/dotnet-runtime-5.0.17-linux-arm64.tar.gz\"; sha512 = \"99cb11871924d3abedcc9c8079c54bc0c550203c7cbe4e349ed70d4355f40e4620b68d90b797e6461d898c06bed6953580e2cd4ad01483e5de107ca5a3409610\"; }; x86_64-darwin = { url = \"https://download.visualstudio.microsoft.com/download/pr/39326cf0-dc7f-42a3-9f7a-fe30c75c7a7f/33cbce552148e13d47120fe4502f5b5e/dotnet-runtime-5.0.17-osx-x64.tar.gz\"; sha512 = \"31add512418640f98bc9511509db2049a2674c7725169d26be89218a02ac7972e03e5d6be5a3d45a0dfa764e6eade503a8f4957b7b198ec6ad412e423d95f1b9\"; }; }; }; sdk_5_0 = buildNetSdk { inherit icu; version = \"5.0.408\"; srcs = { x86_64-linux = { url = \"https://download.visualstudio.microsoft.com/download/pr/904da7d0-ff02-49db-bd6b-5ea615cbdfc5/966690e36643662dcc65e3ca2423041e/dotnet-sdk-5.0.408-linux-x64.tar.gz\"; sha512 = \"abbf22c420df2d8398d1616efa3d31e1b8f96130697746c45ad68668676d12e65ec3b4dd75f28a5dc7607da58b6e369693c0e658def15ce2431303c28e99db55\"; }; aarch64-linux = { url = \"https://download.visualstudio.microsoft.com/download/pr/d4b71fac-a2fd-4516-ac58-100fb09d796a/e79d6c2a8040b59bf49c0d167ae70a7b/dotnet-sdk-5.0.408-linux-arm64.tar.gz\"; sha512 = \"50f23d7aca91051d8b7c37f1a76b1eb51e6fe73e017d98558d757a6b9699e4237d401ce81515c1601b8c21eb62fee4e0b4f0bbed8967eefa3ceba75fc242f01b\"; }; x86_64-darwin = { url = \"https://download.visualstudio.microsoft.com/download/pr/4aeecc7c-7ffa-418f-9362-cf5eb3ed0396/055d5e6064a9fdecd7d906f5f262373d/dotnet-sdk-5.0.408-osx-x64.tar.gz\"; sha512 = \"3fdd4deac2809b00c0f669d5488000ac1b9a47dee6ab7b31167d7cec4759a10ee347fd4f52090a40684e5ecc1e1f57eb99c558e561edfd1436a2f77fc1c1a0b2\"; }; }; packages = { fetchNuGet }: [ (fetchNuGet { pname = \"Microsoft.AspNetCore.App.Runtime.linux-arm\"; version = \"5.0.17\"; sha256 = \"0mfawgcc23r44a1r7ynafxwga6jzn0f0z5ys03qssrvlcdsb376x\"; }) (fetchNuGet { pname = \"Microsoft.AspNetCore.App.Runtime.linux-arm64\"; version = \"5.0.17\"; sha256 = \"183xgqzlwd5lhacxdwcjl8vcq7r7xypv0hddps9k32mmmwf83d8h\"; }) (fetchNuGet { pname = \"Microsoft.AspNetCore.App.Runtime.linux-musl-arm64\"; version = \"5.0.17\"; sha256 = \"0i5pp1smjkyhiyhcbkyc3cxz0sx9204bfml8wsdy7bxznbh2gkmw\"; }) (fetchNuGet { pname = \"Microsoft.AspNetCore.App.Runtime.linux-musl-x64\"; version = \"5.0.17\"; sha256 = \"1fmd9jq2nzy63hjh4sa6zl636wpgwr3r8ahzln5w14m9k87lfdbk\"; }) (fetchNuGet { pname = \"Microsoft.AspNetCore.App.Runtime.linux-x64\"; version = \"5.0.17\"; sha256 = \"066fwdlssbv556zd9w1x87x1j8j4kafj9rxyy0692bssdb4gcyc8\"; }) (fetchNuGet { pname = \"Microsoft.AspNetCore.App.Runtime.osx-x64\"; version = \"5.0.17\"; sha256 = \"1qvvqf8mmzzc7a7fhx324dprnbxhknr3qxspb2xhsn3yyg44xn2d\"; }) (fetchNuGet { pname = \"Microsoft.AspNetCore.App.Runtime.win-arm\"; version = \"5.0.17\"; sha256 = \"1gzf2gv4z9bn1cr1kpqpf1jf7m0p0wd1pxq5ndylq6bw353yglk1\"; }) (fetchNuGet { pname = \"Microsoft.AspNetCore.App.Runtime.win-arm64\"; version = \"5.0.17\"; sha256 = \"1lml70ln9bfjrfjf3jbxfzd5kgd4cp4h7v052md5ja364g7lalsy\"; }) (fetchNuGet { pname = \"Microsoft.AspNetCore.App.Runtime.win-x64\"; version = \"5.0.17\"; sha256 = \"0j90fri15c05lw96xybgvqkysfm7g8grhkrg25g75vhi6ni2ricj\"; }) (fetchNuGet { pname = \"Microsoft.AspNetCore.App.Runtime.win-x86\"; version = \"5.0.17\"; sha256 = \"1bdb887xvgxsmphys83zp9skn848p1r8viclc8p29w1rby4wi19i\"; }) (fetchNuGet { pname = \"Microsoft.NETCore.App.Host.linux-arm\"; version = \"5.0.17\"; sha256 = \"0y90p765sj54clf2bwrka99w73g8b9550b4qvyilqggzydl1c1hk\"; }) (fetchNuGet { pname = \"Microsoft.NETCore.App.Host.linux-arm64\"; version = \"5.0.17\"; sha256 = \"07v7vyqm556xr1ypkazfp6gh6drgf20zkwbhkpja8bwdcr6lphbb\"; }) (fetchNuGet { pname = \"Microsoft.NETCore.App.Host.linux-musl-arm64\"; version = \"5.0.17\"; sha256 = \"0sbzlzhazh31s63hw9553hk9j56fxssncmfgidiyh0dg73aacrsp\"; }) (fetchNuGet { pname = \"Microsoft.NETCore.App.Host.linux-musl-x64\"; version = \"5.0.17\"; sha256 = \"1qxphvlr882rvmj71y2imnf6r3hh4ln2n138qjyv1z129dp2g4y1\"; }) (fetchNuGet { pname = \"Microsoft.NETCore.App.Host.linux-x64\"; version = \"5.0.17\"; sha256 = \"1lc2jhr4ikffi5ylyf8f6ya6k0hdj0wp1l0017grrwd4m5ajj4vv\"; }) (fetchNuGet { pname = \"Microsoft.NETCore.App.Host.osx-x64\"; version = \"5.0.17\"; sha256 = \"02g5w41ivrw3n6cy3l3ixhcl8bw1fsv4bzs2m34k9h5fqmliaf3c\"; }) (fetchNuGet { pname = \"Microsoft.NETCore.App.Host.win-arm\"; version = \"5.0.17\"; sha256 = \"07rfkxpf6rp8x0lybl8hx40mk09w5gjrr9djkjcp8lvjgzidnxq9\"; }) (fetchNuGet { pname = \"Microsoft.NETCore.App.Host.win-arm64\"; version = \"5.0.17\"; sha256 = \"1i7wka56n3akr96jrkj37jx98bwxfzhpx5705930v50izligd08x\"; }) (fetchNuGet { pname = \"Microsoft.NETCore.App.Host.win-x64\"; version = \"5.0.17\"; sha256 = \"15f1kqlpp1d05dhg3dfya32vvzbpj6c7gxds947f10jb0hqlnhdj\"; }) (fetchNuGet { pname = \"Microsoft.NETCore.App.Host.win-x86\"; version = \"5.0.17\"; sha256 = \"1j1334zxv815ksdnllnbwwsbwnimjlpknjmqy1riy2zpswxlfkz6\"; }) (fetchNuGet { pname = \"Microsoft.NETCore.App.Runtime.linux-arm\"; version = \"5.0.17\"; sha256 = \"0mmgd6nacx4fzf0w02ch0qxa43vrv6wfspykxsy2bkpvrnvr8xr9\"; }) (fetchNuGet { pname = \"Microsoft.NETCore.App.Runtime.linux-arm64\"; version = \"5.0.17\"; sha256 = \"16whaq82pj6fqa0vam3a0va9ly843aa1z12hza040vn6252kk9fq\"; }) (fetchNuGet { pname = \"Microsoft.NETCore.App.Runtime.linux-musl-arm64\"; version = \"5.0.17\"; sha256 = \"1zavnwqvn2f7lhb880wgv02anrvqsh6l34w72knwd31irggph08l\"; }) (fetchNuGet { pname = \"Microsoft.NETCore.App.Runtime.linux-musl-x64\"; version = \"5.0.17\"; sha256 = \"173r2srcbad2prrw3l914scmdks3mghxgszvlwypdjnv0f2szgvv\"; }) (fetchNuGet { pname = \"Microsoft.NETCore.App.Runtime.linux-x64\"; version = \"5.0.17\"; sha256 = \"0jgcfs3jc98jfyaaamssznckbpnaygplk8pjsp6dswpansz5bnnq\"; }) (fetchNuGet { pname = \"Microsoft.NETCore.App.Runtime.osx-x64\"; version = \"5.0.17\"; sha256 = \"1ph5kx18syinp8bpzw80bgq3njl65gwzws727xcmxnysgm7snmjp\"; }) (fetchNuGet { pname = \"Microsoft.NETCore.App.Runtime.win-arm\"; version = \"5.0.17\"; sha256 = \"0m4jhn70parwnl18fql0sk9sf14y8cf08xw6x2cm5bfhnc9jvjny\"; }) (fetchNuGet { pname = \"Microsoft.NETCore.App.Runtime.win-arm64\"; version = \"5.0.17\"; sha256 = \"1af20jkv73767b4fy18s2dvjncaca1ny0csyr7wbhvqfs59y3n1x\"; }) (fetchNuGet { pname = \"Microsoft.NETCore.App.Runtime.win-x64\"; version = \"5.0.17\"; sha256 = \"0llhsi03wyp2yjqy0snywqgwjgam91i4nsf5lc9kaxkk5h6vj1a0\"; }) (fetchNuGet { pname = \"Microsoft.NETCore.App.Runtime.win-x86\"; version = \"5.0.17\"; sha256 = \"0xvprbjwd3fymddvavsy7wk5q2hp45hdi10qz4rdbmns23vqkzmf\"; }) (fetchNuGet { pname = \"Microsoft.NETCore.DotNetAppHost\"; version = \"5.0.17\"; sha256 = \"0vhvxpba3i9ffp4gp56l3rnlhq9yg07n3dv5qi89zb90vgyqjh1p\"; }) (fetchNuGet { pname = \"Microsoft.NETCore.DotNetHost\"; version = \"5.0.17\"; sha256 = \"074c9byxwmndfdavxn103220f5gklaaxc9wj7zpb5v3yr3ads30f\"; }) (fetchNuGet { pname = \"Microsoft.NETCore.DotNetHostPolicy\"; version = \"5.0.17\"; sha256 = \"03jkkpsy2zjfp722fa2fcnpk2g6jzy0bn9vip5c39k78y5pz29x6\"; }) (fetchNuGet { pname = \"Microsoft.NETCore.DotNetHostResolver\"; version = \"5.0.17\"; sha256 = \"1ih6c104skp9q17i2dnsma45l6nv5c62vv2i1988dcjw2v0sl98m\"; }) (fetchNuGet { pname = \"runtime.linux-arm64.Microsoft.NETCore.DotNetAppHost\"; version = \"5.0.17\"; sha256 = \"0gwsxd1l0n32xnw0lyjixj2634iyygdb8pd7chydsr3qk8njxnpk\"; }) (fetchNuGet { pname = \"runtime.linux-arm64.Microsoft.NETCore.DotNetHost\"; version = \"5.0.17\"; sha256 = \"0x5dhn1jkwqnd0cki1vi97rhyfac6w79hvh9dxvnkn2k04sbps8q\"; }) (fetchNuGet { pname = \"runtime.linux-arm64.Microsoft.NETCore.DotNetHostPolicy\"; version = \"5.0.17\"; sha256 = \"1ipx3qn78z6gi415c4fa9wgy8k75aifbml6ys1c9ghl6yxbv0fd0\"; }) (fetchNuGet { pname = \"runtime.linux-arm64.Microsoft.NETCore.DotNetHostResolver\"; version = \"5.0.17\"; sha256 = \"1wgbx648yndl0hh8vx6sflfwjyr5pfhi7vj7v19l6vxnrr1096w7\"; }) (fetchNuGet { pname = \"runtime.linux-arm.Microsoft.NETCore.DotNetAppHost\"; version = \"5.0.17\"; sha256 = \"17jc8jc2dk1g8996jpq3k0g6c5inijivxkbz0grxrgr5jbyiv19y\"; }) (fetchNuGet { pname = \"runtime.linux-arm.Microsoft.NETCore.DotNetHost\"; version = \"5.0.17\"; sha256 = \"0ydn40qn6cs6f20byvmc9j008s6csxjbh6jh5w4q995vipcmcpcj\"; }) (fetchNuGet { pname = \"runtime.linux-arm.Microsoft.NETCore.DotNetHostPolicy\"; version = \"5.0.17\"; sha256 = \"0bw08wlf96vcyix850y8jips1glrz2cbj647af4d7gggw8p3wwzw\"; }) (fetchNuGet { pname = \"runtime.linux-arm.Microsoft.NETCore.DotNetHostResolver\"; version = \"5.0.17\"; sha256 = \"0xsqyw848scwcz09pgc719776q712xabx4xv47srzij34p2pq7np\"; }) (fetchNuGet { pname = \"runtime.linux-musl-arm64.Microsoft.NETCore.DotNetAppHost\"; version = \"5.0.17\"; sha256 = \"00b0vipypjai4l8icr74kjhglxx2xlc3nw3vyiwisg52l9zyby66\"; }) (fetchNuGet { pname = \"runtime.linux-musl-arm64.Microsoft.NETCore.DotNetHost\"; version = \"5.0.17\"; sha256 = \"1cdgd4p5zr1mzz9hlb5mj946zfa1vn9wya5y2bhqn9y4ak831wzp\"; }) (fetchNuGet { pname = \"runtime.linux-musl-arm64.Microsoft.NETCore.DotNetHostPolicy\"; version = \"5.0.17\"; sha256 = \"17v8m4fxm4q40z49a2h4lw9dawg6pwfv4s2dskzc23ggcjgr6dp1\"; }) (fetchNuGet { pname = \"runtime.linux-musl-arm64.Microsoft.NETCore.DotNetHostResolver\"; version = \"5.0.17\"; sha256 = \"1fbqi92prqmvxx0rx7vhl10l665jmmhb2ng5jndimggydb0ckpqh\"; }) (fetchNuGet { pname = \"runtime.linux-musl-x64.Microsoft.NETCore.DotNetAppHost\"; version = \"5.0.17\"; sha256 = \"1rijxkzzk65xs9z2ygs13h0rhw1cli5vwshmvs1gfnwhhn8ic0gx\"; }) (fetchNuGet { pname = \"runtime.linux-musl-x64.Microsoft.NETCore.DotNetHost\"; version = \"5.0.17\"; sha256 = \"02mxvpm2zs5jvawigvxlnrw6si4zwj6qlcas99m9xdmm8yqq22cm\"; }) (fetchNuGet { pname = \"runtime.linux-musl-x64.Microsoft.NETCore.DotNetHostPolicy\"; version = \"5.0.17\"; sha256 = \"0c1lcl3yy88vdfw12c7h0ww596qfjd5f8l2mn7mlqs6i3f864bkg\"; }) (fetchNuGet { pname = \"runtime.linux-musl-x64.Microsoft.NETCore.DotNetHostResolver\"; version = \"5.0.17\"; sha256 = \"0w0wg9ah7vngvpyds67l6qhizpkdf2r6m6cqyyvv3s5dw5l8rxin\"; }) (fetchNuGet { pname = \"runtime.linux-x64.Microsoft.NETCore.DotNetAppHost\"; version = \"5.0.17\"; sha256 = \"17yy7605vkfz0f4h58005gdfg6fnjxlcnq0vg0hrxsgbdqmd7p1i\"; }) (fetchNuGet { pname = \"runtime.linux-x64.Microsoft.NETCore.DotNetHost\"; version = \"5.0.17\"; sha256 = \"0av25fgkdl7zvn44wp8gqx2xl2mdlv1f9cgxzp7xk5yq8f7ynxpq\"; }) (fetchNuGet { pname = \"runtime.linux-x64.Microsoft.NETCore.DotNetHostPolicy\"; version = \"5.0.17\"; sha256 = \"1smhmdfq0jlv1gq18hdaj0y9yzkvqzmki19c0b3j5b76yxxxpbwz\"; }) (fetchNuGet { pname = \"runtime.linux-x64.Microsoft.NETCore.DotNetHostResolver\"; version = \"5.0.17\"; sha256 = \"0n0cdb9zpdb4h4v6r265pqmqg8c94ydywvna6jp1c6qhqlr0qk39\"; }) (fetchNuGet { pname = \"runtime.osx-x64.Microsoft.NETCore.DotNetAppHost\"; version = \"5.0.17\"; sha256 = \"1s2n2sx29c8rx549zizj8yrddjl98a7vwvxw56y0jvvbwphr9gz4\"; }) (fetchNuGet { pname = \"runtime.osx-x64.Microsoft.NETCore.DotNetHost\"; version = \"5.0.17\"; sha256 = \"19m66yvv0hnmyrmx2l4drbls0fcib75fxq2csdx6p8gd54bnrsh3\"; }) (fetchNuGet { pname = \"runtime.osx-x64.Microsoft.NETCore.DotNetHostPolicy\"; version = \"5.0.17\"; sha256 = \"0bcnlsxcrvhybcjbb9879njx0c4z76y7djx4643g1rpjnkcrj9ww\"; }) (fetchNuGet { pname = \"runtime.osx-x64.Microsoft.NETCore.DotNetHostResolver\"; version = \"5.0.17\"; sha256 = \"1bf95h2f0dmpmv7z7961zia5vaqvmjq3wkf6iil9jxv4z674624w\"; }) (fetchNuGet { pname = \"runtime.win-arm64.Microsoft.NETCore.DotNetAppHost\"; version = \"5.0.17\"; sha256 = \"02q593q09mwwh23m86048vc7b7an7pqch5nd86d4hxzkamnpnpsa\"; }) (fetchNuGet { pname = \"runtime.win-arm64.Microsoft.NETCore.DotNetHost\"; version = \"5.0.17\"; sha256 = \"16vzxywfj88gjcwfnmcb6b50ld8dp46i4pqiwwcy7yz15xgdhbm2\"; }) (fetchNuGet { pname = \"runtime.win-arm64.Microsoft.NETCore.DotNetHostPolicy\"; version = \"5.0.17\"; sha256 = \"1ix5lg2j5ihdfp9j3jdxc042g4syjzc4bafid465j52h6znsm6wm\"; }) (fetchNuGet { pname = \"runtime.win-arm64.Microsoft.NETCore.DotNetHostResolver\"; version = \"5.0.17\"; sha256 = \"0w30v8r26cg427n5glm9nz6r10baalkqq5icqqxkq71hmh8fsjqb\"; }) (fetchNuGet { pname = \"runtime.win-arm.Microsoft.NETCore.DotNetAppHost\"; version = \"5.0.17\"; sha256 = \"168iq4hdp6bhdpgqa1mir1bygmh2ggwkys1r82d6kpl2lzbxjy28\"; }) (fetchNuGet { pname = \"runtime.win-arm.Microsoft.NETCore.DotNetHost\"; version = \"5.0.17\"; sha256 = \"18jpw2wbrb1b941729lb7hiq4yfq2z53pcxwz4mpgawnr58y0562\"; }) (fetchNuGet { pname = \"runtime.win-arm.Microsoft.NETCore.DotNetHostPolicy\"; version = \"5.0.17\"; sha256 = \"0ig464fcsj2jr0p02f6slifwf1m0408g95npm0vccf5ww1nbgkpi\"; }) (fetchNuGet { pname = \"runtime.win-arm.Microsoft.NETCore.DotNetHostResolver\"; version = \"5.0.17\"; sha256 = \"0qj5avmjrvabxzimprg4m54k3p6zkwrhbpv0byc8c9gbi47s323j\"; }) (fetchNuGet { pname = \"runtime.win-x64.Microsoft.NETCore.DotNetAppHost\"; version = \"5.0.17\"; sha256 = \"05ghz164lpff7n8mrxs7jm2h8n3clsg4w953zrag3k5ry9j36m9c\"; }) (fetchNuGet { pname = \"runtime.win-x64.Microsoft.NETCore.DotNetHost\"; version = \"5.0.17\"; sha256 = \"0azgs542mbg69jlc81529i2z5m728w8sc2i9m5dx15hvxqqqcjiz\"; }) (fetchNuGet { pname = \"runtime.win-x64.Microsoft.NETCore.DotNetHostPolicy\"; version = \"5.0.17\"; sha256 = \"12n1kcgcv5z8hkvjqfk0n705kcipbai4sgcwiimi52xpaf34xw8m\"; }) (fetchNuGet { pname = \"runtime.win-x64.Microsoft.NETCore.DotNetHostResolver\"; version = \"5.0.17\"; sha256 = \"0b1s2m0a7xcdzfz22x6k7v5hkca90azdjk6pw7wwdnvszwq26nxp\"; }) (fetchNuGet { pname = \"runtime.win-x86.Microsoft.NETCore.DotNetAppHost\"; version = \"5.0.17\"; sha256 = \"1sjpq07swgj0isdgyh6p2yb254qb9781lv44xfhj6nz7mx2yhdh1\"; }) (fetchNuGet { pname = \"runtime.win-x86.Microsoft.NETCore.DotNetHost\"; version = \"5.0.17\"; sha256 = \"1gnzrqdp26d7pwwz29gm4qb09n2zsb767qkhbwkifcsyxlwi6m0f\"; }) (fetchNuGet { pname = \"runtime.win-x86.Microsoft.NETCore.DotNetHostPolicy\"; version = \"5.0.17\"; sha256 = \"089jww13gaf7x7yd9d3qkyx9iq8abcp3r147hd9nblh561c9bzbg\"; }) (fetchNuGet { pname = \"runtime.win-x86.Microsoft.NETCore.DotNetHostResolver\"; version = \"5.0.17\"; sha256 = \"1nycl1rayk0fhaakpj6q9rfp2lv3dpl7pziavmd9kcfryz952ff5\"; }) ]; }; } ", "commid": "nixpkgs_pr_212133"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-a7079e198aca988098951b4fa76cc9c83dc618ebe0d3503c23f6bfa32d8f7208", "query": "Since May 10, .NET 5.0 is EOL (End Of Life), and should not be used. Should it be marked as EOF similar to dotnet 2.2 and 3.0? See All packages using dotnet 5.0 should be updated to use a newer, supported version. These packages still need updating: [x] - [x] - [x] - [x] pkgs/development/tools/build- - [x] -\nThere is at least one package, which currently uses dotnet 5 sdk - . So we will need to update it beforehand. Btw, I'm not sure if we have any policy regarding packages removal, for nixpkgs in general or specifically for it's dotnet part. , what do you think?\nThe package is also using .NET 5: . But this is because I made the PR upstream updating it from .NET 4 to 5. I suspect that the transition to 6 will be similarly easy.\nI think we should just mark it as depricated, as many projects do still use it upstream. Dotnet version 3 is also still commonly used, so I dont expect it would be realistic to remove version 5 any time soon. also uses dotnet 5 by default, I'll go ahead and switch that over now. See . That doesnt mark dotnet 5 as deprecated or change anything from a SDK perspective, just some preperation work.\nSee as well, it adds a warning whenever dotnet version 5 is used. Not using a throw for now since a few packages depend on it and I dont have the time to clean that all up at the moment.\nCan you provide a list of packages that need updating?\nBased on a quick grep: pkgs/development/tools/build-\nI believe that after all the above PRs are merged, we should be able to safely remove .NET 5 from nixpkgs :)", "positive_passages": [{"docid": "doc-en-nixpkgs-97bb0aefb24e176a33db8eb775d71e32958c60c895f7cfc54bdeb5048cc72299", "text": "dotnet-sdk_7 = dotnetCorePackages.sdk_7_0; dotnet-runtime_3 = dotnetCorePackages.runtime_3_1; dotnet-runtime_5 = dotnetCorePackages.runtime_5_0; dotnet-runtime_6 = dotnetCorePackages.runtime_6_0; dotnet-runtime_7 = dotnetCorePackages.runtime_7_0; dotnet-aspnetcore_3 = dotnetCorePackages.aspnetcore_3_1; dotnet-aspnetcore_5 = dotnetCorePackages.aspnetcore_5_0; dotnet-aspnetcore_6 = dotnetCorePackages.aspnetcore_6_0; dotnet-aspnetcore_7 = dotnetCorePackages.aspnetcore_7_0;", "commid": "nixpkgs_pr_212133"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-d54db5eab51dbf1c00801656215374098c238bfa9f0592c848836aed5763c9c2", "query": "Shotwell can't build thumbnails for video files. package has an additional executable , which is broken. When run manually, it fails with this message:", "positive_passages": [{"docid": "doc-en-nixpkgs-869094c2153b67c9c5ab2eb98e5b2cfce06405ef6ea48301b655e07eed6fbe3c", "text": "sqlite webkitgtk gst_all_1.gstreamer gst_all_1.gst-libav gst_all_1.gst-plugins-base gst_all_1.gst-plugins-good libgee libgudev gexiv2", "commid": "nixpkgs_pr_173616"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-15bc34de874989a461287283e008176cdc40a4547f6dec970d768d05e947bf1a", "query": "Project description Selectdefaultapplication is a very simple GUI application that lets you define default applications on Linux in a sane way. Basically it just loads all installed applications by reading their .desktop files, reads the MimeType fields to see what it supports, and updates with what the user wants. Not all desktop environments provide such a tool, prompting for an agnostic tool. Metadata homepage URL: source URL: license: gpl2 platforms: linux Additional info: AUR package:\nYou can try using this in an overlay, use .\nSeems to work!", "positive_passages": [{"docid": "doc-en-nixpkgs-493fb536479457900d674b57b4e3b5d88aa7b9bfbefa4c64585982eee0dd7281", "text": "githubId = 20391; name = \"Nahum Shalman\"; }; nsnelson = { email = \"noah.snelson@protonmail.com\"; github = \"peeley\"; githubId = 30942198; name = \"Noah Snelson\"; }; nthorne = { email = \"notrupertthorne@gmail.com\"; github = \"nthorne\";", "commid": "nixpkgs_pr_174354"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-15bc34de874989a461287283e008176cdc40a4547f6dec970d768d05e947bf1a", "query": "Project description Selectdefaultapplication is a very simple GUI application that lets you define default applications on Linux in a sane way. Basically it just loads all installed applications by reading their .desktop files, reads the MimeType fields to see what it supports, and updates with what the user wants. Not all desktop environments provide such a tool, prompting for an agnostic tool. Metadata homepage URL: source URL: license: gpl2 platforms: linux Additional info: AUR package:\nYou can try using this in an overlay, use .\nSeems to work!", "positive_passages": [{"docid": "doc-en-nixpkgs-c4ba8659f6b8816257d41901d25768c6f465e1c0e1119b31044e41fab360247e", "text": " { stdenv, lib, fetchFromGitHub, qmake, qtbase, wrapQtAppsHook }: stdenv.mkDerivation { pname = \"selectdefaultapplication\"; version = \"unstable-2021-08-12\"; src = fetchFromGitHub { owner = \"sandsmark\"; repo = \"selectdefaultapplication\"; rev = \"c752df6ba8caceeef54bcf6527f1bccc2ca8202a\"; sha256 = \"C/70xpt6RoQNIlAjSJhOCyheolK4Xp6RiSZmeqMP4fw=\"; }; nativeBuildInputs = [ qmake wrapQtAppsHook ]; buildInputs = [ qtbase ]; installPhase = '' runHook preInstall mkdir -p $out/bin cp selectdefaultapplication $out/bin install -Dm644 -t \"$out/share/applications\" selectdefaultapplication.desktop install -Dm644 -t \"$out/share/icons/hicolor/48x48/apps\" selectdefaultapplication.png runHook postInstall ''; meta = with lib; { description = \"A very simple application that lets you define default applications on Linux in a sane way\"; homepage = \"https://github.com/sandsmark/selectdefaultapplication\"; maintainers = with maintainers; [ nsnelson ]; license = licenses.gpl2; platforms = platforms.linux; }; } ", "commid": "nixpkgs_pr_174354"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-15bc34de874989a461287283e008176cdc40a4547f6dec970d768d05e947bf1a", "query": "Project description Selectdefaultapplication is a very simple GUI application that lets you define default applications on Linux in a sane way. Basically it just loads all installed applications by reading their .desktop files, reads the MimeType fields to see what it supports, and updates with what the user wants. Not all desktop environments provide such a tool, prompting for an agnostic tool. Metadata homepage URL: source URL: license: gpl2 platforms: linux Additional info: AUR package:\nYou can try using this in an overlay, use .\nSeems to work!", "positive_passages": [{"docid": "doc-en-nixpkgs-40b50bc7e4e2395c8cefc93b6602c4c6dcab5ff1a0884dd7d273890cd60c2ec2", "text": "seexpr = callPackage ../development/compilers/seexpr { }; selectdefaultapplication = libsForQt5.callPackage ../applications/misc/selectdefaultapplication { }; semgrep = python3.pkgs.callPackage ../tools/security/semgrep { }; semgrep-core = callPackage ../tools/security/semgrep/semgrep-core.nix { };", "commid": "nixpkgs_pr_174354"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-54c03bcf57ccdd85a2e9b5e1558e217789ba2b9db1c52fc4b96d2a1a4b02829f", "query": "I'm bringing up new RPis and their clocks are often wrong. Even though upstream systemd has given exceptions to be able to skip dnssec check for ntp sync, it doesn't... appear to be working. If I set the date manually, often by time I check timesyncd will have already taken care of kicking in and it reports that it's synced. Steps to reproduce the behavior: the clock badly. . and see if your DNS works\nIf I read it right, only works for systemd-resolved. One general workaround is to use hard-coded IP addresses for NTP (our routers actually do that IIRC).\nThat commit seems to indicate that it should bypass DNSSEC for timesyncd. This would get my clock back in sync, thus resolving DNSSEC errors for the rest of the system. But timesyncd isn't doing its job. I assume that's because: date wrong -dnssec failure. But maybe also fails if the clock is just too askew? I'll try to look more later, maybe I have to opt-in large corrections? Seems a bit weird to me. Or do we maybe use timesyncd in a non-standard way?\nI ran into this on a Raspberry Pi 3B. I'm using systemd-networkd including systemd-resolved. At some point DNS started failing, and I noticed the system clock was out of sync by about 4 hours and not synchronizing anymore. The log of systemd-resolved was full of DNSSEC s: I'm not sure what changed, because I was able to install NixOS just fine. It also was offline before for some time without this problem happening (as far as I noticed at least), and it started happening after it was online for some time without break. Also, the systemd-native workaround should be working on NixOS as well, I can't find anything that indicates a non-standard setup that might overwrite tha workaround. Checking is the standard original systemd unit file that includes the relevant line and as far as I can see it isn't overridden. I also checked and it includes . For now, I worked around the issue by specifying my NTP servers by IP (I used the ones by the ).\nClosing as this should be fixed by Please reopen if this is still an issue.", "positive_passages": [{"docid": "doc-en-nixpkgs-93a243a5f670249b7324f0a7fa75881b05ec152edfdc2e1d8caf905cf06a6443", "text": "wantedBy = [ \"sysinit.target\" ]; aliases = [ \"dbus-org.freedesktop.timesync1.service\" ]; restartTriggers = [ config.environment.etc.\"systemd/timesyncd.conf\".source ]; # systemd-timesyncd disables DNSSEC validation in the nss-resolve module by setting SYSTEMD_NSS_RESOLVE_VALIDATE to 0 in the unit file. # This is required in order to solve the chicken-and-egg problem when DNSSEC validation needs the correct time to work, but to set the # correct time, we need to connect to an NTP server, which usually requires resolving its hostname. # In order for nss-resolve to be able to read this environment variable we patch systemd-timesyncd to disable NSCD and use NSS modules directly. # This means that systemd-timesyncd needs to have NSS modules path in LD_LIBRARY_PATH. When systemd-resolved is disabled we still need to set # NSS module path so that systemd-timesyncd keeps using other NSS modules that are configured in the system. environment.LD_LIBRARY_PATH = config.system.nssModules.path; preStart = ( # Ensure that we have some stored time to prevent", "commid": "nixpkgs_pr_239201"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-54c03bcf57ccdd85a2e9b5e1558e217789ba2b9db1c52fc4b96d2a1a4b02829f", "query": "I'm bringing up new RPis and their clocks are often wrong. Even though upstream systemd has given exceptions to be able to skip dnssec check for ntp sync, it doesn't... appear to be working. If I set the date manually, often by time I check timesyncd will have already taken care of kicking in and it reports that it's synced. Steps to reproduce the behavior: the clock badly. . and see if your DNS works\nIf I read it right, only works for systemd-resolved. One general workaround is to use hard-coded IP addresses for NTP (our routers actually do that IIRC).\nThat commit seems to indicate that it should bypass DNSSEC for timesyncd. This would get my clock back in sync, thus resolving DNSSEC errors for the rest of the system. But timesyncd isn't doing its job. I assume that's because: date wrong -dnssec failure. But maybe also fails if the clock is just too askew? I'll try to look more later, maybe I have to opt-in large corrections? Seems a bit weird to me. Or do we maybe use timesyncd in a non-standard way?\nI ran into this on a Raspberry Pi 3B. I'm using systemd-networkd including systemd-resolved. At some point DNS started failing, and I noticed the system clock was out of sync by about 4 hours and not synchronizing anymore. The log of systemd-resolved was full of DNSSEC s: I'm not sure what changed, because I was able to install NixOS just fine. It also was offline before for some time without this problem happening (as far as I noticed at least), and it started happening after it was online for some time without break. Also, the systemd-native workaround should be working on NixOS as well, I can't find anything that indicates a non-standard setup that might overwrite tha workaround. Checking is the standard original systemd unit file that includes the relevant line and as far as I can see it isn't overridden. I also checked and it includes . For now, I worked around the issue by specifying my NTP servers by IP (I used the ones by the ).\nClosing as this should be fixed by Please reopen if this is still an issue.", "positive_passages": [{"docid": "doc-en-nixpkgs-4c7a41b67e4ee4d7047ace7888b1b78d04b22af81bca515d7b7069a5db93c2e6", "text": "systemd-shutdown = handleTest ./systemd-shutdown.nix {}; systemd-sysupdate = runTest ./systemd-sysupdate.nix; systemd-timesyncd = handleTest ./systemd-timesyncd.nix {}; systemd-timesyncd-nscd-dnssec = handleTest ./systemd-timesyncd-nscd-dnssec.nix {}; systemd-user-tmpfiles-rules = handleTest ./systemd-user-tmpfiles-rules.nix {}; systemd-misc = handleTest ./systemd-misc.nix {}; systemd-userdbd = handleTest ./systemd-userdbd.nix {};", "commid": "nixpkgs_pr_239201"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-54c03bcf57ccdd85a2e9b5e1558e217789ba2b9db1c52fc4b96d2a1a4b02829f", "query": "I'm bringing up new RPis and their clocks are often wrong. Even though upstream systemd has given exceptions to be able to skip dnssec check for ntp sync, it doesn't... appear to be working. If I set the date manually, often by time I check timesyncd will have already taken care of kicking in and it reports that it's synced. Steps to reproduce the behavior: the clock badly. . and see if your DNS works\nIf I read it right, only works for systemd-resolved. One general workaround is to use hard-coded IP addresses for NTP (our routers actually do that IIRC).\nThat commit seems to indicate that it should bypass DNSSEC for timesyncd. This would get my clock back in sync, thus resolving DNSSEC errors for the rest of the system. But timesyncd isn't doing its job. I assume that's because: date wrong -dnssec failure. But maybe also fails if the clock is just too askew? I'll try to look more later, maybe I have to opt-in large corrections? Seems a bit weird to me. Or do we maybe use timesyncd in a non-standard way?\nI ran into this on a Raspberry Pi 3B. I'm using systemd-networkd including systemd-resolved. At some point DNS started failing, and I noticed the system clock was out of sync by about 4 hours and not synchronizing anymore. The log of systemd-resolved was full of DNSSEC s: I'm not sure what changed, because I was able to install NixOS just fine. It also was offline before for some time without this problem happening (as far as I noticed at least), and it started happening after it was online for some time without break. Also, the systemd-native workaround should be working on NixOS as well, I can't find anything that indicates a non-standard setup that might overwrite tha workaround. Checking is the standard original systemd unit file that includes the relevant line and as far as I can see it isn't overridden. I also checked and it includes . For now, I worked around the issue by specifying my NTP servers by IP (I used the ones by the ).\nClosing as this should be fixed by Please reopen if this is still an issue.", "positive_passages": [{"docid": "doc-en-nixpkgs-33fc00db0bd6686e4d961aea1463a4041a1a82908fe603f2c57506483dd7f417", "text": " # This test verifies that systemd-timesyncd can resolve the NTP server hostname when DNSSEC validation # fails even though it is enforced in the systemd-resolved settings. It is required in order to solve # the chicken-and-egg problem when DNSSEC validation needs the correct time to work, but to set the # correct time, we need to connect to an NTP server, which usually requires resolving its hostname. # # This test does the following: # - Sets up a DNS server (tinydns) listening on the eth1 ip addess, serving .ntp and fake.ntp records. # - Configures that DNS server as a resolver and enables DNSSEC in systemd-resolved settings. # - Configures systemd-timesyncd to use fake.ntp hostname as an NTP server. # - Performs a regular DNS lookup, to ensure it fails due to broken DNSSEC. # - Waits until systemd-timesyncd resolves fake.ntp by checking its debug output. # Here, we don't expect systemd-timesyncd to connect and synchronize time because there is no NTP # server running. For this test to succeed, we only need to ensure that systemd-timesyncd # resolves the IP address of the fake.ntp host. import ./make-test-python.nix ({ pkgs, ... }: let ntpHostname = \"fake.ntp\"; ntpIP = \"192.0.2.1\"; in { name = \"systemd-timesyncd\"; nodes.machine = { pkgs, lib, config, ... }: let eth1IP = (lib.head config.networking.interfaces.eth1.ipv4.addresses).address; in { # Setup a local DNS server for the NTP domain on the eth1 IP address services.tinydns = { enable = true; ip = eth1IP; data = '' .ntp:${eth1IP} +.${ntpHostname}:${ntpIP} ''; }; # Enable systemd-resolved with DNSSEC and use the local DNS as a name server services.resolved.enable = true; services.resolved.dnssec = \"true\"; networking.nameservers = [ eth1IP ]; # Configure systemd-timesyncd to use our NTP hostname services.timesyncd.enable = lib.mkForce true; services.timesyncd.servers = [ ntpHostname ]; services.timesyncd.extraConfig = '' FallbackNTP=${ntpHostname} ''; # The debug output is necessary to determine whether systemd-timesyncd successfully resolves our NTP hostname or not systemd.services.systemd-timesyncd.environment.SYSTEMD_LOG_LEVEL = \"debug\"; }; testScript = '' machine.wait_for_unit(\"tinydns.service\") machine.wait_for_unit(\"systemd-timesyncd.service\") machine.fail(\"resolvectl query ${ntpHostname}\") machine.wait_until_succeeds(\"journalctl -u systemd-timesyncd.service --grep='Resolved address ${ntpIP}:123 for ${ntpHostname}'\") ''; }) ", "commid": "nixpkgs_pr_239201"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-54c03bcf57ccdd85a2e9b5e1558e217789ba2b9db1c52fc4b96d2a1a4b02829f", "query": "I'm bringing up new RPis and their clocks are often wrong. Even though upstream systemd has given exceptions to be able to skip dnssec check for ntp sync, it doesn't... appear to be working. If I set the date manually, often by time I check timesyncd will have already taken care of kicking in and it reports that it's synced. Steps to reproduce the behavior: the clock badly. . and see if your DNS works\nIf I read it right, only works for systemd-resolved. One general workaround is to use hard-coded IP addresses for NTP (our routers actually do that IIRC).\nThat commit seems to indicate that it should bypass DNSSEC for timesyncd. This would get my clock back in sync, thus resolving DNSSEC errors for the rest of the system. But timesyncd isn't doing its job. I assume that's because: date wrong -dnssec failure. But maybe also fails if the clock is just too askew? I'll try to look more later, maybe I have to opt-in large corrections? Seems a bit weird to me. Or do we maybe use timesyncd in a non-standard way?\nI ran into this on a Raspberry Pi 3B. I'm using systemd-networkd including systemd-resolved. At some point DNS started failing, and I noticed the system clock was out of sync by about 4 hours and not synchronizing anymore. The log of systemd-resolved was full of DNSSEC s: I'm not sure what changed, because I was able to install NixOS just fine. It also was offline before for some time without this problem happening (as far as I noticed at least), and it started happening after it was online for some time without break. Also, the systemd-native workaround should be working on NixOS as well, I can't find anything that indicates a non-standard setup that might overwrite tha workaround. Checking is the standard original systemd unit file that includes the relevant line and as far as I can see it isn't overridden. I also checked and it includes . For now, I worked around the issue by specifying my NTP servers by IP (I used the ones by the ).\nClosing as this should be fixed by Please reopen if this is still an issue.", "positive_passages": [{"docid": "doc-en-nixpkgs-9bdb68c4177f8f9373c137536ad5fdb66a9488c039dae565016ace61ed5eaaa0", "text": " From 7a27556920fe1feefd17096841c8f3ca1294a1b3 Mon Sep 17 00:00:00 2001 From: Yuri Nesterov Date: Wed, 21 Jun 2023 17:17:38 +0300 Subject: [PATCH] timesyncd: disable NSCD when DNSSEC validation is disabled Systemd-timesyncd sets SYSTEMD_NSS_RESOLVE_VALIDATE=0 in the unit file to disable DNSSEC validation but it doesn't work when NSCD is used in the system. This patch disabes NSCD in systemd-timesyncd when SYSTEMD_NSS_RESOLVE_VALIDATE is set to 0 so that it uses NSS libraries directly. --- src/timesync/timesyncd.c | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/src/timesync/timesyncd.c b/src/timesync/timesyncd.c index 1d8ebecc91..2b0ae361ff 100644 --- a/src/timesync/timesyncd.c +++ b/src/timesync/timesyncd.c @@ -21,6 +21,11 @@ #include \"timesyncd-conf.h\" #include \"timesyncd-manager.h\" #include \"user-util.h\" +#include \"env-util.h\" + +struct traced_file; +extern void __nss_disable_nscd(void (*)(size_t, struct traced_file *)); +static void register_traced_file(size_t dbidx, struct traced_file *finfo) {} static int advance_tstamp(int fd, const struct stat *st) { assert_se(fd >= 0); @@ -198,6 +203,12 @@ static int run(int argc, char *argv[]) { if (r < 0) return log_error_errno(r, \"Failed to parse fallback server strings: %m\"); + r = getenv_bool_secure(\"SYSTEMD_NSS_RESOLVE_VALIDATE\"); + if (r == 0) { + log_info(\"Disabling NSCD because DNSSEC validation is turned off\"); + __nss_disable_nscd(register_traced_file); + } + log_debug(\"systemd-timesyncd running as pid \" PID_FMT, getpid_cached()); notify_message = notify_start(\"READY=1n\" -- 2.34.1 ", "commid": "nixpkgs_pr_239201"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-54c03bcf57ccdd85a2e9b5e1558e217789ba2b9db1c52fc4b96d2a1a4b02829f", "query": "I'm bringing up new RPis and their clocks are often wrong. Even though upstream systemd has given exceptions to be able to skip dnssec check for ntp sync, it doesn't... appear to be working. If I set the date manually, often by time I check timesyncd will have already taken care of kicking in and it reports that it's synced. Steps to reproduce the behavior: the clock badly. . and see if your DNS works\nIf I read it right, only works for systemd-resolved. One general workaround is to use hard-coded IP addresses for NTP (our routers actually do that IIRC).\nThat commit seems to indicate that it should bypass DNSSEC for timesyncd. This would get my clock back in sync, thus resolving DNSSEC errors for the rest of the system. But timesyncd isn't doing its job. I assume that's because: date wrong -dnssec failure. But maybe also fails if the clock is just too askew? I'll try to look more later, maybe I have to opt-in large corrections? Seems a bit weird to me. Or do we maybe use timesyncd in a non-standard way?\nI ran into this on a Raspberry Pi 3B. I'm using systemd-networkd including systemd-resolved. At some point DNS started failing, and I noticed the system clock was out of sync by about 4 hours and not synchronizing anymore. The log of systemd-resolved was full of DNSSEC s: I'm not sure what changed, because I was able to install NixOS just fine. It also was offline before for some time without this problem happening (as far as I noticed at least), and it started happening after it was online for some time without break. Also, the systemd-native workaround should be working on NixOS as well, I can't find anything that indicates a non-standard setup that might overwrite tha workaround. Checking is the standard original systemd unit file that includes the relevant line and as far as I can see it isn't overridden. I also checked and it includes . For now, I worked around the issue by specifying my NTP servers by IP (I used the ones by the ).\nClosing as this should be fixed by Please reopen if this is still an issue.", "positive_passages": [{"docid": "doc-en-nixpkgs-f3f11755724b8b9209035e624ed3fbf2d5a3523c3522b4ad0643bdeff6e12f31", "text": "./0017-core-don-t-taint-on-unmerged-usr.patch ./0018-tpm2_context_init-fix-driver-name-checking.patch ./0019-systemctl-edit-suggest-systemdctl-edit-runtime-on-sy.patch ./0020-timesyncd-disable-NSCD-when-DNSSEC-validation-is-dis.patch ] ++ lib.optional stdenv.hostPlatform.isMusl ( let oe-core = fetchzip {", "commid": "nixpkgs_pr_239201"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-49083fac66991291239ddadc3c6dd4dcacc8378c187fffb755d73abbcfbf44ee", "query": " ``` The comments will not be rendered in the rendered HTML. #### Link reference definitions Links can reference a label, for example, to make the link target reusable: ```markdown ::: {.note} Reference links can also be used to [shorten URLs][url-id] and keep the markdown readable. ::: [url-id]: https://github.com/NixOS/nixpkgs/blob/19d4f7dc485f74109bd66ef74231285ff797a823/doc/README.md ``` This syntax is taken from [CommonMark](https://spec.commonmark.org/0.30/#link-reference-definitions). #### Typographic replacements Typographic replacements are enabled. Check the [list of possible replacement patterns check](https://github.com/executablebooks/markdown-it-py/blob/3613e8016ecafe21709471ee0032a90a4157c2d1/markdown_it/rules_core/replacements.py#L1-L15). ## Getting help If you need documentation-specific help or reviews, ping [@NixOS/documentation-reviewers](https://github.com/orgs/nixos/teams/documentation-reviewers) on your pull request.", "commid": "nixpkgs_pr_264450"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-b82978e60eecc691ae933eecb8185668502db649d652503be51f9fc63919a6c2", "query": "Contributors working on improving the nixpkgs manual would be redirected to the . This section is not up-to-date with all the syntax features supported by , forcing contributors to look for use examples over the whole manual. The same markdown syntax is used to write and generate the NixOS manual. However, this manual does not make any mention of the supported syntax. This makes it hard to contribute to the NixOS manual with relative isolation from the nixpkgs manual. Update in Nixpkgs manual to include reference material and examples on all the syntax features supported by . Link in Nixos manual for completion. [x] remove references to in the . : [x] remove references to in the . [x] add a redirecting to the syntax section in . [x] add reference to lack of support for [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support () () )", "positive_passages": [{"docid": "doc-en-nixpkgs-66f8344405e73522747078de4a774fac6982ba0f94e7245d5d9cdecd0abc95c0", "text": "# Contributing to this manual {#chap-contributing} The [DocBook] and CommonMark sources of the NixOS manual are in the [nixos/doc/manual](https://github.com/NixOS/nixpkgs/tree/master/nixos/doc/manual) subdirectory of the [Nixpkgs](https://github.com/NixOS/nixpkgs) repository. The sources of the NixOS manual are in the [nixos/doc/manual](https://github.com/NixOS/nixpkgs/tree/master/nixos/doc/manual) subdirectory of the [Nixpkgs](https://github.com/NixOS/nixpkgs) repository. This manual uses the [Nixpkgs manual syntax](https://nixos.org/manual/nixpkgs/unstable/#sec-contributing-markup). You can quickly check your edits with the following:", "commid": "nixpkgs_pr_264450"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-b82978e60eecc691ae933eecb8185668502db649d652503be51f9fc63919a6c2", "query": "Contributors working on improving the nixpkgs manual would be redirected to the . This section is not up-to-date with all the syntax features supported by , forcing contributors to look for use examples over the whole manual. The same markdown syntax is used to write and generate the NixOS manual. However, this manual does not make any mention of the supported syntax. This makes it hard to contribute to the NixOS manual with relative isolation from the nixpkgs manual. Update in Nixpkgs manual to include reference material and examples on all the syntax features supported by . Link in Nixos manual for completion. [x] remove references to in the . : [x] remove references to in the . [x] add a redirecting to the syntax section in . [x] add reference to lack of support for [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support () () )", "positive_passages": [{"docid": "doc-en-nixpkgs-b024c21cfd19bb403235efa10acfa3990a1de40c48ef4b82dd31d15d7929ab63", "text": "## Building the Manual {#sec-writing-docs-building-the-manual} The DocBook sources of the [](#book-nixos-manual) are in the The sources of the [](#book-nixos-manual) are in the [`nixos/doc/manual`](https://github.com/NixOS/nixpkgs/tree/master/nixos/doc/manual) subdirectory of the Nixpkgs repository.", "commid": "nixpkgs_pr_264450"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-b82978e60eecc691ae933eecb8185668502db649d652503be51f9fc63919a6c2", "query": "Contributors working on improving the nixpkgs manual would be redirected to the . This section is not up-to-date with all the syntax features supported by , forcing contributors to look for use examples over the whole manual. The same markdown syntax is used to write and generate the NixOS manual. However, this manual does not make any mention of the supported syntax. This makes it hard to contribute to the NixOS manual with relative isolation from the nixpkgs manual. Update in Nixpkgs manual to include reference material and examples on all the syntax features supported by . Link in Nixos manual for completion. [x] remove references to in the . : [x] remove references to in the . [x] add a redirecting to the syntax section in . [x] add reference to lack of support for [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support () () )", "positive_passages": [{"docid": "doc-en-nixpkgs-a1a51fb834b7c88d0e5b5ceb0474898a397b6c4d1880647e49b37627f80c5402", "text": "When this command successfully finishes, it will tell you where the manual got generated. The HTML will be accessible through the `result` symlink at `./result/share/doc/nixos/index.html`. ## Editing DocBook XML {#sec-writing-docs-editing-docbook-xml} For general information on how to write in DocBook, see [DocBook 5: The Definitive Guide](https://tdg.docbook.org/tdg/5.1/). Emacs nXML Mode is very helpful for editing DocBook XML because it validates the document as you write, and precisely locates errors. To use it, see [](#sec-emacs-docbook-xml). [Pandoc](https://pandoc.org/) can generate DocBook XML from a multitude of formats, which makes a good starting point. Here is an example of Pandoc invocation to convert GitHub-Flavoured MarkDown to DocBook 5 XML: ```ShellSession pandoc -f markdown_github -t docbook5 docs.md -o my-section.md ``` Pandoc can also quickly convert a single `section.xml` to HTML, which is helpful when drafting. Sometimes writing valid DocBook is too difficult. In this case, submit your documentation updates in a [GitHub Issue](https://github.com/NixOS/nixpkgs/issues/new) and someone will handle the conversion to XML for you. ## Creating a Topic {#sec-writing-docs-creating-a-topic} You can use an existing topic as a basis for the new topic or create a topic from scratch. Keep the following guidelines in mind when you create and add a topic: - The NixOS [`book`](https://tdg.docbook.org/tdg/5.0/book.html) element is in `nixos/doc/manual/manual.xml`. It includes several [`parts`](https://tdg.docbook.org/tdg/5.0/book.html) which are in subdirectories. - Store the topic file in the same directory as the `part` to which it belongs. If your topic is about configuring a NixOS module, then the XML file can be stored alongside the module definition `nix` file. - If you include multiple words in the file name, separate the words with a dash. For example: `ipv6-config.xml`. - Make sure that the `xml:id` value is unique. You can use abbreviations if the ID is too long. For example: `nixos-config`. - Determine whether your topic is a chapter or a section. If you are unsure, open an existing topic file and check whether the main element is chapter or section. ## Adding a Topic to the Book {#sec-writing-docs-adding-a-topic} Open the parent CommonMark file and add a line to the list of chapters with the file name of the topic that you created. If you created a `section`, you add the file to the `chapter` file. If you created a `chapter`, you add the file to the `part` file. If the topic is about configuring a NixOS module, it can be automatically included in the manual by using the `meta.doc` attribute. See [](#sec-meta-attributes) for an explanation. ", "commid": "nixpkgs_pr_264450"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-7e64332a5555de292062af9d2d908e1ce83095b4ba252849399ebb85205c9659", "query": "The wrapper only has , so the corresponding where would check for manpages is absent. don't have regular vim installed install something like 09pre104936.\nYou can find a fix in /", "positive_passages": [{"docid": "doc-en-nixpkgs-82539826ce3cf7bc1acd56675f3e1a0c66ca0b766a41d724450d34cf47bdc63d", "text": "inherit vimrcFile; # shell script with custom name passing [-u vimrc] [-U gvimrc] to vim vimWithRC = {vimExecutable, name ? null, vimrcFile ? null, gvimrcFile ? null}: let rcOption = o: file: stdenv.lib.optionalString (file != null) \"-${o} ${file}\"; in writeScriptBin (if name == null then \"vim\" else name) '' #!${stdenv.shell} exec ${vimExecutable} ${rcOption \"u\" vimrcFile} ${rcOption \"U\" gvimrcFile} \"$@\" vimWithRC = { vimExecutable, gvimExecutable, vimManPages, wrapManual, wrapGui, name ? \"vim\", vimrcFile ? null, gvimrcFile ? null, vimExecutableName, gvimExecutableName, }: let rcOption = o: file: stdenv.lib.optionalString (file != null) \"-${o} ${file}\"; vimWrapperScript = writeScriptBin vimExecutableName '' #!${stdenv.shell} exec ${vimExecutable} ${rcOption \"u\" vimrcFile} ${rcOption \"U\" gvimrcFile} \"$@\" ''; gvimWrapperScript = writeScriptBin gvimExecutableName '' #!${stdenv.shell} exec ${gvimExecutable} ${rcOption \"u\" vimrcFile} ${rcOption \"U\" gvimrcFile} \"$@\" ''; in buildEnv { inherit name; paths = [ vimWrapperScript ] ++ lib.optional wrapGui gvimWrapperScript ++ lib.optional wrapManual vimManPages ; }; # add a customize option to a vim derivation makeCustomizable = vim: vim // { customize = { name, vimrcConfig }: vimWithRC { customize = { name, vimrcConfig, wrapManual ? true, wrapGui ? false, vimExecutableName ? name, gvimExecutableName ? (lib.concatStrings [ \"g\" name ]), }: vimWithRC { vimExecutable = \"${vim}/bin/vim\"; inherit name; gvimExecutable = \"${vim}/bin/gvim\"; inherit name wrapManual wrapGui vimExecutableName gvimExecutableName; vimrcFile = vimrcFile vimrcConfig; vimManPages = buildEnv { name = \"vim-doc\"; paths = [ vim ]; pathsToLink = [ \"/share/man\" ]; }; }; override = f: makeCustomizable (vim.override f);", "commid": "nixpkgs_pr_56277"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-41436d08a5b44b3f5a9a956aadcf42b7ce39e17ebe176460441378f23dec6f2e", "query": "Hi TLP shows the following in output: Anything to do with it? Thanks. System: (NixOS: , Ubuntu/Fedora: , ...) Nix version: (run ) Nixpkgs version: (run )\nI believe the tlp module could be made to set for those systemd units\nFixed, thanks for your report!", "positive_passages": [{"docid": "doc-en-nixpkgs-fae726c04490d4e3d72d303d7d5de3df2d9d91a1417943764b6b9851f350b188", "text": " {stdenv, fetchurl, yacc, flex, pkgconfig, glib, xz}: stdenv.mkDerivation rec { version = \"0.15.2\"; name = \"vala-${version}\"; src = fetchurl { url = \"mirror://gnome/sources/vala/0.15/${name}.tar.xz\"; sha256 = \"0g71zq6dpqrw2f40wfzdf18fdw41ymr17laqniy2kr622hkxdi8w\"; }; buildNativeInputs = [ yacc flex pkgconfig xz ]; buildInputs = [ glib ]; meta = { description = \"Compiler for the GObject type system\"; homepage = \"http://live.gnome.org/Vala\"; license = \"free-copyleft\"; platforms = stdenv.lib.platforms.all; maintainers = [ stdenv.lib.maintainers.antono ]; }; } ", "commid": "nixpkgs_pr_25"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-41436d08a5b44b3f5a9a956aadcf42b7ce39e17ebe176460441378f23dec6f2e", "query": "Hi TLP shows the following in output: Anything to do with it? Thanks. System: (NixOS: , Ubuntu/Fedora: , ...) Nix version: (run ) Nixpkgs version: (run )\nI believe the tlp module could be made to set for those systemd units\nFixed, thanks for your report!", "positive_passages": [{"docid": "doc-en-nixpkgs-0eac5c7d63d59f38c6b13294bc30be296d9da2656e7d6b090a3cbcb26c357bd0", "text": " {stdenv, fetchurl, yacc, flex, pkgconfig, glib, xz}: stdenv.mkDerivation rec { version = \"0.16.1\"; name = \"vala-${version}\"; src = fetchurl { url = \"mirror://gnome/sources/vala/0.16/${name}.tar.xz\"; sha256 = \"1n708n9ixyy9qrzyv1wf4ybvcclx43ib9ki028wwpvkz6kv8zqlb\"; }; buildNativeInputs = [ yacc flex pkgconfig xz ]; buildInputs = [ glib ]; meta = { description = \"Compiler for the GObject type system\"; homepage = \"http://live.gnome.org/Vala\"; license = \"free-copyleft\"; platforms = stdenv.lib.platforms.all; maintainers = [ stdenv.lib.maintainers.antono ]; }; } ", "commid": "nixpkgs_pr_25"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-41436d08a5b44b3f5a9a956aadcf42b7ce39e17ebe176460441378f23dec6f2e", "query": "Hi TLP shows the following in output: Anything to do with it? Thanks. System: (NixOS: , Ubuntu/Fedora: , ...) Nix version: (run ) Nixpkgs version: (run )\nI believe the tlp module could be made to set for those systemd units\nFixed, thanks for your report!", "positive_passages": [{"docid": "doc-en-nixpkgs-1198a66ecb5ab956f0f8a0c88503173ee650f3c555df2a957ecbb31d1a38567f", "text": "{stdenv, fetchurl, yacc, flex, pkgconfig, glib, xz}: stdenv.mkDerivation rec { name = \"vala-0.14.2\"; version = \"0.17.2\"; name = \"vala-${version}\"; src = fetchurl { url = mirror://gnome/sources/vala/0.14/vala-0.14.2.tar.xz; sha256 = \"1l5kllw9vpwv24lzv9fp64l3sad46wpxgvsgryrwlrjg91w6jzl0\"; url = \"mirror://gnome/sources/vala/0.17/${name}.tar.xz\"; sha256 = \"09i2s0dwmrk147ind2dx7nq845g12fp6fsjqrphhrr0dbi0zzgh3\"; }; buildNativeInputs = [ yacc flex pkgconfig xz ];", "commid": "nixpkgs_pr_25"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-41436d08a5b44b3f5a9a956aadcf42b7ce39e17ebe176460441378f23dec6f2e", "query": "Hi TLP shows the following in output: Anything to do with it? Thanks. System: (NixOS: , Ubuntu/Fedora: , ...) Nix version: (run ) Nixpkgs version: (run )\nI believe the tlp module could be made to set for those systemd units\nFixed, thanks for your report!", "positive_passages": [{"docid": "doc-en-nixpkgs-cbe15c4f8327a866fa5d9e15616393c2f57facea6a6d8d73acd2634c59899100", "text": "meta = { description = \"Compiler for the GObject type system\"; homepage = \"http://live.gnome.org/Vala\"; license = \"free-copyleft\"; platforms = stdenv.lib.platforms.all; maintainers = [ stdenv.lib.maintainers.antono ]; }; }", "commid": "nixpkgs_pr_25"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-41436d08a5b44b3f5a9a956aadcf42b7ce39e17ebe176460441378f23dec6f2e", "query": "Hi TLP shows the following in output: Anything to do with it? Thanks. System: (NixOS: , Ubuntu/Fedora: , ...) Nix version: (run ) Nixpkgs version: (run )\nI believe the tlp module could be made to set for those systemd units\nFixed, thanks for your report!", "positive_passages": [{"docid": "doc-en-nixpkgs-48fa821f6f8341d4db76758057205edcbe7ff0bbf9be39a5d113923a5379e30a", "text": "urweb = callPackage ../development/compilers/urweb { }; vala = callPackage ../development/compilers/vala { }; vala = vala17; vala15 = callPackage ../development/compilers/vala/15.2.nix { }; vala16 = callPackage ../development/compilers/vala/16.1.nix { }; vala17 = callPackage ../development/compilers/vala/default.nix { }; visualcpp = callPackage ../development/compilers/visual-c++ { };", "commid": "nixpkgs_pr_25"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-f0089ad87b65aa7abe9d6886bb90316c566760867dcd9458411531e510274572", "query": "NixOS specialisations are supposed to have their own entries in the Grub menu for previous generations according to the . However in practice that is not the case. The older generations do not hold any boot entry for the specialisations, but only the default entry. nixpkgs: I am not sure, whether to update the wiki to correctly mention current behavior, or whether to fix the grub module to generate entries for specialisations for older generations. ---", "commid": "nixpkgs_pr_298333"}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-88f0d692a4604bfd114490f5e55f9090347811d322e053954752d9e88b251caf", "query": "Project description