jiebi/CodeConvo huggingface dataset:
Code change:
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.

Related discussion:
text: <del> let inherit (import <nixpkgs> { }) 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"; }; } </del>
Code change:
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.

Related discussion:
text: <del> let inherit (import <nixpkgs> { }) 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"; }; } </del>
Code change:
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.

Related discussion:
text: <ins> # 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 <nixpkgs> { }) 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 <nixpkgs> { }) 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). </ins>
Code change:
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.

Related discussion:
text: <del> <section xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xi="http://www.w3.org/2001/XInclude" xml:id="sec-pkgs-snapTools"> <title>pkgs.snapTools</title> <para> <varname>pkgs.snapTools</varname> is a set of functions for creating Snapcraft images. Snap and Snapcraft is not used to perform these operations. </para> <section xml:id="ssec-pkgs-snapTools-makeSnap-signature"> <title>The makeSnap Function</title> <para> <function>makeSnap</function> takes a single named argument, <parameter>meta</parameter>. This argument mirrors <link xlink:href="https://docs.snapcraft.io/snap-format">the upstream <filename>snap.yaml</filename> format</link> exactly. </para> <para> The <parameter>base</parameter> should not be specified, as <function>makeSnap</function> will force set it. </para> <para> Currently, <function>makeSnap</function> does not support creating GUI stubs. </para> </section> <section xml:id="ssec-pkgs-snapTools-build-a-snap-hello"> <title>Build a Hello World Snap</title> <example xml:id="ex-snapTools-buildSnap-hello"> <title>Making a Hello World Snap</title> <para> The following expression packages GNU Hello as a Snapcraft snap. </para> <programlisting><xi:include href="./snap/example-hello.nix" parse="text" /></programlisting> <para> <command>nix-build</command> this expression and install it with <command>snap install ./result --dangerous</command>. <command>hello</command> will now be the Snapcraft version of the package. </para> </example> </section> <section xml:id="ssec-pkgs-snapTools-build-a-snap-firefox"> <title>Build a Hello World Snap</title> <example xml:id="ex-snapTools-buildSnap-firefox"> <title>Making a Graphical Snap</title> <para> 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. </para> <programlisting><xi:include href="./snap/example-firefox.nix" parse="text" /></programlisting> <para> <command>nix-build</command> this expression and install it with <command>snap install ./result --dangerous</command>. <command>nix-example-firefox</command> will now be the Snapcraft version of the Firefox package. </para> <para> The specific meaning behind plugs can be looked up in the <link xlink:href="https://docs.snapcraft.io/supported-interfaces">Snapcraft interface documentation</link>. </para> </example> </section> </section> </del>
Code change:
Describe the bug Milkytracker is missing a menu entry to launch the application Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --

Related discussion:
text: # Somehow this does not get set automatically cmakeFlags = [ "-DSDL2MAIN_LIBRARY=${SDL2}/lib/libSDL2.so" ]; <ins> postInstall = '' install -Dm644 $src/resources/milkytracker.desktop $out/share/applications/milkytracker.desktop install -Dm644 $src/resources/pictures/carton.png $out/share/pixmaps/milkytracker.png install -Dm644 $src/resources/milkytracker.appdata $out/share/appdata/milkytracker.appdata.xml ''; </ins> meta = with stdenv.lib; { description = "Music tracker application, similar to Fasttracker II"; homepage = "http://milkytracker.org";
Code change:
We should replace the discontinued source with the more active fork . wrecker/stern hasn't received any commits since 2019. The maintainer of stern doesn't work at wercker anymore, and it seems no one else there is maintaining it (wercker/stern). The community has since moved to stern/stern with improvements to the original source. Project description Multi pod and container log tailing for Kubernetes Metadata homepage URL: source URL: license: Apache-2.0 platforms: unix

Related discussion:
text: <del> { stdenv, lib, buildPackages, buildGoPackage, fetchFromGitHub, installShellFiles }: </del> <ins> { stdenv, lib, buildPackages, buildGoModule, fetchFromGitHub, installShellFiles }: let isCrossBuild = stdenv.hostPlatform != stdenv.buildPlatform; </ins> <del> let isCrossBuild = stdenv.hostPlatform != stdenv.buildPlatform; in buildGoPackage rec { </del> <ins> in buildGoModule rec { </ins> pname = "stern"; <del> version = "1.11.0"; goPackagePath = "github.com/wercker/stern"; </del> <ins> version = "1.13.1"; </ins> src = fetchFromGitHub { <del> owner = "wercker"; </del> <ins> owner = "stern"; </ins> repo = "stern"; <del> rev = version; sha256 = "0xndlq0ks8flzx6rdd4lnkxpkbvdy9sj1jwys5yj7p989ls8by3n"; </del> <ins> rev = "v${version}"; sha256 = "0fj6a52wb0jv5bz2j2wq3ljnlxnsj9bg3kbzgkz0vh0b63zyn782"; </ins> }; <del> deleteVendor = true; goDeps = ./deps.nix; </del> <ins> vendorSha256 = "14nrdaaby74bjbk777hr82p0ybzk3spc59lbrjn9z0q3hc0p4vaf"; </ins> nativeBuildInputs = [ installShellFiles ]; <ins> buildFlagsArray = [ "-ldflags=-s -w -X github.com/stern/stern/cmd.version=${version}" ]; </ins> postInstall = <del> let stern = if isCrossBuild then buildPackages.stern else "$out"; in </del> <ins> let stern = if isCrossBuild then buildPackages.stern else "$out"; in </ins> '' for shell in bash zsh; do ${stern}/bin/stern --completion $shell > stern.$shell
Code change:
We should replace the discontinued source with the more active fork . wrecker/stern hasn't received any commits since 2019. The maintainer of stern doesn't work at wercker anymore, and it seems no one else there is maintaining it (wercker/stern). The community has since moved to stern/stern with improvements to the original source. Project description Multi pod and container log tailing for Kubernetes Metadata homepage URL: source URL: license: Apache-2.0 platforms: unix

Related discussion:
text: ''; meta = with lib; { <del> description      = "Multi pod and container log tailing for Kubernetes"; homepage         = "https://github.com/wercker/stern"; license          = licenses.asl20; maintainers      = with maintainers; [ mbode ]; platforms        = platforms.unix; </del> <ins> description = "Multi pod and container log tailing for Kubernetes"; homepage = "https://github.com/stern/stern"; license = licenses.asl20; maintainers = with maintainers; [ mbode preisschild ]; platforms = platforms.unix; </ins> }; }
Code change:
Describe the bug spacefm segfaults on start with the following output: invoke spacefm on the command line Expected behavior an up and running GUI program Screenshots see error message above Additional context I noticed that there is no It makes no difference whether spacefm is installed via nix-env or Notify maintainers Metadata** $ nix-shell -p nix-info --run "nix-info -m" system: host os: multi-user?: sandbox: version: channels(root): channels(oo): nixpkgs:
I bisected this crash down to Perhaps the package needs to be updated to support the newer version of gtk3?
Hi. I cannot reproduce the crash with (current master). How about you?
Yep, that same binary segfaults for me. I'm on
still crashing with the same error message. Then out of curiosity I ran . The backtrace of the main thread has: 0x0000000000000000 in ?? () 0x00007fa6931c3ceb in ghashtablelookup () from /nix/store/hnk0s558k2h4v8abjzagagflvw1l0cb2-glib-2.66.4/lib/libglib- 0x00007fa69375c50c in gdkx11windowlookupfordisplay () from /nix/store/8pidhwid3ww58wlq705irf48c01dr0hv-gtk+3-3.24.24/lib/libgdk-3.so.0 0x0000000000499915 in getdesktopindex (win=win at main-window.c:4179 0x000000000049bfd1 in fmmainwindowgetoncurrentdesktop () at main-window.c:4225 0x0000000000496343 in handleparsedcommandlineargs () at main.c:1143 0x0000000000421808 in main (argc=<optimized out, argv=<optimized out) at main.c:1526 and now I am wondering about as I am running Wayland and sway. I don't know if it's relevant though.
Does it help if you run spacefm with the environment variable set? BTW, I am using X11.
Seems this a known bug:
GDKBACKEND=wayland does not help. Found an even older bug report from 2015: Question: this is an upstream known bug. Should I close this issue? (I don't know what the protocol is in this case)
I am not sure. Maybe we can at least improve something here? Change the description to call out that this does not work with wayland for example? Patch it that it fails gracefully with an explanatory message when not run under X11? Then, it seems the project is also not really maintained anymore. Maybe it's time to let it go?
Another idea: a wayland display driver (is this the right wording?) should fall back to x11 support via xwayland if an application cannot run under wayland natively. SpaceFM is a x11 only application, could you try to use and see if it makes a difference?
it actually runs with GDK_BACKEND=x11! Thanks for the suggestion.
I have created a PR to make x11 the only backend that is used.

Related discussion:
text: sha256 = "089r6i40lxcwzp60553b18f130asspnzqldlpii53smz52kvpirx"; }; <del> patches = [ ./glibc-fix.patch ]; </del> <ins> patches = [ # fix compilation error due to missing include ./glibc-fix.patch # restrict GDK backends to only X11 ./x11-only.patch ]; </ins> configureFlags = [ "--with-bash-path=${pkgs.bash}/bin/bash"
Code change:
Describe the bug spacefm segfaults on start with the following output: invoke spacefm on the command line Expected behavior an up and running GUI program Screenshots see error message above Additional context I noticed that there is no It makes no difference whether spacefm is installed via nix-env or Notify maintainers Metadata** $ nix-shell -p nix-info --run "nix-info -m" system: host os: multi-user?: sandbox: version: channels(root): channels(oo): nixpkgs:
I bisected this crash down to Perhaps the package needs to be updated to support the newer version of gtk3?
Hi. I cannot reproduce the crash with (current master). How about you?
Yep, that same binary segfaults for me. I'm on
still crashing with the same error message. Then out of curiosity I ran . The backtrace of the main thread has: 0x0000000000000000 in ?? () 0x00007fa6931c3ceb in ghashtablelookup () from /nix/store/hnk0s558k2h4v8abjzagagflvw1l0cb2-glib-2.66.4/lib/libglib- 0x00007fa69375c50c in gdkx11windowlookupfordisplay () from /nix/store/8pidhwid3ww58wlq705irf48c01dr0hv-gtk+3-3.24.24/lib/libgdk-3.so.0 0x0000000000499915 in getdesktopindex (win=win at main-window.c:4179 0x000000000049bfd1 in fmmainwindowgetoncurrentdesktop () at main-window.c:4225 0x0000000000496343 in handleparsedcommandlineargs () at main.c:1143 0x0000000000421808 in main (argc=<optimized out, argv=<optimized out) at main.c:1526 and now I am wondering about as I am running Wayland and sway. I don't know if it's relevant though.
Does it help if you run spacefm with the environment variable set? BTW, I am using X11.
Seems this a known bug:
GDKBACKEND=wayland does not help. Found an even older bug report from 2015: Question: this is an upstream known bug. Should I close this issue? (I don't know what the protocol is in this case)
I am not sure. Maybe we can at least improve something here? Change the description to call out that this does not work with wayland for example? Patch it that it fails gracefully with an explanatory message when not run under X11? Then, it seems the project is also not really maintained anymore. Maybe it's time to let it go?
Another idea: a wayland display driver (is this the right wording?) should fall back to x11 support via xwayland if an application cannot run under wayland natively. SpaceFM is a x11 only application, could you try to use and see if it makes a difference?
it actually runs with GDK_BACKEND=x11! Thanks for the suggestion.
I have created a PR to make x11 the only backend that is used.

Related discussion:
text: <ins> --- a/src/main.c	2021-02-09 13:54:32.847364236 +0100 +++ b/src/main.c	2021-02-09 10:41:51.541203271 +0100 @@ -1350,6 +1351,7 @@ vfs_file_monitor_clean(); return 1; } +            gdk_set_allowed_backends("x11"); gtk_init (&argc, &argv); int ret = custom_dialog_init( argc, argv ); if ( ret != 0 ) </ins>
Code change:
Describe the bug There may be something flaky about the python3{789} build. It's been going on and off on hydra. I can't reliably reproduce the failures seen on hydra locally when building from the exact same commits that failed on hydra, but I have observed the same failure at least once on my machine. ! Expected behavior dask should build cleanly. Notify maintainers Metadata

Related discussion:
text: "test_count_nonzero_str" "rolling_methods"  # floating percision error ~0.1*10^8 small "num_workers_config" # flaky <ins> "test_2args_with_array[pandas1-darray1-ldexp]"  # flaky </ins> ]; meta = {
Code change:
Describe the bug Just lost on two different NixOS machine my Signal Desktop history because of this faulty update... I don't know, probably doesn't make sense for people to downgrade who are already upgraded but for others it dataloss To Reproduce Steps to reproduce the behavior: Signal Desktop Signal Desktop you to delete db, if you interact in a wrong way it will delete your data Notify maintainers ( and
Sorry to hear that. I recently lost my history too... It's really frustrating! Yeah, unfortunately I don't think there's anything we can do about it (as downstream package maintainers). AFAIK the source of the bug is still unknown, it doesn't seem to affect all users, and all releases have a limited lifetime ("expire" 90 days after the release, see my comment in ). Thanks for saying that! This really bothered me too... I just didn't say anything because I was too angry to keep it nice enough. (I raged a bit here but after I realized that one cannot even import old backups I had to take a break.)
I just got hit by a similar issue by moving from Archlinux (encrypted database) to NixOS (non encrypted database). After many things, the easiest fix to ensure proper functionalities IMHO is installing: This will disable tracker3 and prevent SQLite to be loaded in the process which will replace SQLCipher and cause the SQLite3 API to be the original one (i.e. non-encrypted) and cause many issues down the road I guess. That might not fix everything though :upsidedownface: Opened a PR:
FYI, in case anyone has feedback/suggestions: We might merge soon and it should cause another "Database startup error: Error: SQLITE_NOTADB: file is not a database" error (which is really unfortunate but not easily avoidable).
Heads-up: I've just merged to hopefully resolve this once and for all and the Python wrapper script should take care of the database re-encryption when launching Signal-Desktop as usual but the user experience isn't that great and you probably want to backup first in case the script fails unexpectedly.
Thank you, I just upgraded Signal on my computer and the re-encryption did work as intended

Related discussion:
text: # - https://github.com/NixOS/nixpkgs/issues/108772 # - https://github.com/NixOS/nixpkgs/pull/117555 print(machine.succeed("su - alice -c 'file ~/.config/Signal/sql/db.sqlite'")) <del> # TODO: The DB should be encrypted and the following should be machine.fail # instead of machine.succeed but the DB is currently unencrypted and we # want to notice if this isn't the case anymore as the transition to a # encrypted DB can cause data loss!: </del> machine.succeed( <del> "su - alice -c 'file ~/.config/Signal/sql/db.sqlite' | grep -i sqlite" </del> <ins> "su - alice -c 'file ~/.config/Signal/sql/db.sqlite' | grep 'db.sqlite: data'" ) machine.fail( "su - alice -c 'file ~/.config/Signal/sql/db.sqlite' | grep -e SQLite -e database" </ins> ) ''; })
Code change:
Describe the bug Just lost on two different NixOS machine my Signal Desktop history because of this faulty update... I don't know, probably doesn't make sense for people to downgrade who are already upgraded but for others it dataloss To Reproduce Steps to reproduce the behavior: Signal Desktop Signal Desktop you to delete db, if you interact in a wrong way it will delete your data Notify maintainers ( and
Sorry to hear that. I recently lost my history too... It's really frustrating! Yeah, unfortunately I don't think there's anything we can do about it (as downstream package maintainers). AFAIK the source of the bug is still unknown, it doesn't seem to affect all users, and all releases have a limited lifetime ("expire" 90 days after the release, see my comment in ). Thanks for saying that! This really bothered me too... I just didn't say anything because I was too angry to keep it nice enough. (I raged a bit here but after I realized that one cannot even import old backups I had to take a break.)
I just got hit by a similar issue by moving from Archlinux (encrypted database) to NixOS (non encrypted database). After many things, the easiest fix to ensure proper functionalities IMHO is installing: This will disable tracker3 and prevent SQLite to be loaded in the process which will replace SQLCipher and cause the SQLite3 API to be the original one (i.e. non-encrypted) and cause many issues down the road I guess. That might not fix everything though :upsidedownface: Opened a PR:
FYI, in case anyone has feedback/suggestions: We might merge soon and it should cause another "Database startup error: Error: SQLITE_NOTADB: file is not a database" error (which is really unfortunate but not easily avoidable).
Heads-up: I've just merged to hopefully resolve this once and for all and the Python wrapper script should take care of the database re-encryption when launching Signal-Desktop as usual but the user experience isn't that great and you probably want to backup first in case the script fails unexpectedly.
Thank you, I just upgraded Signal on my computer and the re-encryption did work as intended

Related discussion:
text: , hunspellDicts, spellcheckerLanguage ? null # E.g. "de_DE" # For a full list of available languages: # $ cat pkgs/development/libraries/hunspell/dictionaries.nix | grep "dictFileName =" | awk '{ print $3 }' <ins> , python3 , gnome , sqlcipher </ins> }: let