jiebi/CodeConvo huggingface dataset:
Code change:
sha256 = "05s9dclmk7x5d7wnnj4qr6r6c827m72a44gizcv09lxr28pr9inz"; fetchSubmodules = true; }; <del> # we need the packed archive </del> <ins> # The CMake external projects expect the packed archives </ins> rxcpp = fetchurl { url = "https://github.com/Reactive-Extensions/RxCpp/archive/v${rxcppVersion}.tar.gz"; sha256 = "0y2isr8dy2n1yjr9c5570kpc9lvdlch6jv0jvw000amwn5d3krsh";

Related discussion:
text: I don't really use Eigen but the patch makes sense. So, I can send a PR to keep this package on the repo for another cycle at least. I mean, I already did all of the work and it builds. Other distros end up removing it because nobody cares to maintain it.
Nice! Thanks for looking into it. Like you said, if you've already done the work to get it working I don't see why not. If it's too much work to keep it working in the future we can always revisit this and drop it.
Code change:
cudatoolkit ]; <ins> patches = [ # global context library is separated from libethash ./add-global-context.patch ]; </ins> preConfigure = '' sed -i 's/_lib_static//' libpoolprotocols/CMakeLists.txt '';

Related discussion:
text: On the master branch ethminer fails to compile with messages about missing getglobalepochcontext from ethash namespace. Attempt to build ethminer on master branch. Successful compilation. Root of the failure is in changes done to the structure of the dependency chfast/ethash; specifically, 0.6.0 -0.7.0. Patching the libethcore/EthashAux.h file in the ethminer repo, by adding to the headers, and the file by changing the line to does the job.
Code change:
libs=( symbols templates footprints packages3d ) get_rev() { <del> git ls-remote --tags "$@" </del> <ins> if [[ ${version} == "master" ]]; then git ls-remote --heads "$@" else git ls-remote --tags "$@" fi </ins> } gitlab="https://gitlab.com/kicad"

Related discussion:
text: Steps to reproduce the behavior: kicad (tested on ) The relevant part of the build log is: Complete build log is here: Setting the flag in the cmake build flags, solves the issue. Please run and paste the result.
thanks for filing an issue i'm not sure what changed to cause this issue, or why that change didn't notify me of the breakage... i'll try to get your fix or something similar in a PR today
Code change:
<del> { lib, stdenv, callPackage, fetchurl, nixosTests }: </del> <ins> { lib, stdenv, callPackage, fetchurl, nixosTests, commandLineArgs ? "" }: </ins> let inherit (stdenv.hostPlatform) system;

Related discussion:
text: For Chromium, there's a convenient way to define custom flags through . However, there doesn't seem to be a similar option for . I tried setting to "--touch-events", but touchscreen scrolling is not enabled when starting VSCode from desktop launcher, while running in console works as expected. Steps to reproduce the behavior: to "--touch-events" VSCode from desktop launcher on the editor area through touchscreen The editor should scroll as I drag. system: host os: multi-user?: sandbox: version: channels(yes): channels(root): nixpkgs:
Code change:
''; buildInputs = [ <del> dconf gtk3 gobject-introspection ibus (python3.withPackages (pypkgs: with pypkgs; [ pygobject3 ])) </del> <ins> dconf gtk3 gobject-introspection ibus (python3.withPackages (pypkgs: with pypkgs; [ pygobject3 (toPythonModule ibus) ])) </ins> ]; <del> nativeBuildInputs = [ autoreconfHook docbook2x pkgconfig python3.pkgs.wrapPython ]; </del> <ins> nativeBuildInputs = [ autoreconfHook docbook2x pkgconfig python3.pkgs.wrapPython wrapGAppsHook ]; </ins> postUnpack = '' substituteInPlace $sourceRoot/engine/Makefile.am  --replace "docbook2man" "docbook2man --sgml" ''; <del> postFixup = "wrapPythonPrograms"; </del> meta = with stdenv.lib; { isIbusEngine = true; description  = "An IBus framework for table-based input methods";

Related discussion:
text: Input methods based on do not work as of , at least on my machine as it is now. Upstream, I think the change comes from , which made start using . Other IBus input methods still work (mozc, hangul, Anthy). It feels as if this should have an easy solution amounting to “do what worked for other packages using ”, but I can't work out what it is that they do that makes them work. It's also believable that from is not being run. 1) 2) Switch to an -base input method (example: from ). Then, the input method is not changed, and the rest of the output is: Alternatively: 1) 2) Try to open the preferences for an -based input method. No preferences are shown. The following error message is printed. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
So, adding to stops the error message, but preference dialogs still do not show and all of the problems with actually using remain.
How did you install and activate the input method? i18n.inputMethod.enabled = "ibus"; = with ; [ table ]; does not seem to be enough.
Change to (ibus-table acts like a framework within a framework, and provides some actual input methods using it). Then, use -Input Method -Add -More... -Others -IPA-X-SAMPA (and maybe another to see the switching behaviour). Then, switch using the key combination from the preferences (I forget what the default is; maybe Ctrl-space). Expected behaviour from IPA-X-SAMPA includes ↦ and ↦ .
Have you managed to reproduce this problem?
I can confirm your observations in Maybe this could be the culprit:
I've found what appears to be a solution, but it's in some sense weird. Looking at other input methods, they seem to use rather than . Replacing the latter with the former on seems to fix the issue. I have no idea, though, why isn't broken on other platforms. is the new package description.
Code change:
meta = { homepage = "https://github.com/vcrhonek/hwdata"; description = "Hardware Database, including Monitors, pci.ids, usb.ids, and video cards"; <del> license = lib.licenses.gpl2; platforms = lib.platforms.linux; </del> <ins> license = lib.licenses.gpl2Plus; platforms = lib.platforms.all; </ins> }; }

Related discussion:
text: Describe the bug pciutils is using a really old file which doesn't include any definitions for AMD Radeon 6800 XT cards. When running you get the following output If you get a newer version of the file from https://pci- which update-pciids script in package normally updates (but is disabled in nix package). You get the following: Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(wil): nixpkgs: Maintainer information:
Should also mention when running strace on lspci it reads the file from /nix/store/464020m9r6mhsivgp9v1bhkyzz5pa0gq-pciutils- and not from hwdata like I originally thought.
Would it make sense to make lspci depend on hwdata and then use from hwdata? cc'ing (who is listed as shadow maintainer of pciutils)
Hmm, makes sense. Except that seems to be in significantly more closures than , so depending on the extra 6+ MB of other data seems significant. Perhaps make put it into a separate output? Or could just copy it as a quick work-around (that's free for people with )
Oh, we can't "just" make multi-output, as it's a fixed-output derivation, but we could fake it through multiple derivations. Maybe just the work-around for simplicity then?
I think the work-around is actually pretty sensible. I'll prepare a pull request :-) Update: Did so, . Once both and are merged, our issue should be resolved.
Thanks for fixing that :). I tried your two updates on my machine and it appears to be resolved. Closing the issue out. Now we just wait for this to get into unstable :).
Code change:
va_end (ap); return res; <ins> diff --git a/src/builder-source-bzr.c b/src/builder-source-bzr.c index ceeec94a..8abe6f53 100644 </ins> --- a/src/builder-source-bzr.c +++ b/src/builder-source-bzr.c @@ -124,7 +124,7 @@ bzr (GFile   *dir, <ins> gboolean res; </ins> va_list ap; <del> va_start (ap, error); -  res = flatpak_spawn (dir, output, 0, error, "bzr", ap); +  res = flatpak_spawn (dir, output, 0, error, "@bzr@", ap); va_end (ap); </del> <ins> -  brz = g_find_program_in_path ("brz"); +  brz = g_find_program_in_path ("@brz@"); </ins> <del> return res; </del> <ins> va_start (ap, error); res = flatpak_spawn (dir, output, 0, error, brz ? brz : "bzr", ap); diff --git a/src/builder-source-patch.c b/src/builder-source-patch.c index 8721e1e4..d7f4d840 100644 </ins> --- a/src/builder-source-patch.c +++ b/src/builder-source-patch.c @@ -247,15 +247,15 @@ patch (GFile      *dir,

Related discussion:
text: Describe the bug flatpak-builder for some reasons can't use rofiles-fuse To Reproduce Steps to reproduce the behavior: build any app using flatpak-builder Expected behavior flatpak-builder should use rofiles-fuse. Screenshots Additional context Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(piotrek): nixpkgs: Maintainer information:
installing solve this problem so maybe should be ?
We patch the paths to the executables to be hardcoded, so the program doesn't have to rely on something like ostree being installed. I believe one path isn't hardcoded with the current patch That looks it up in PATH, probably why it was working once you installed it.
cc
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . 3. Ask on the on .
should fix that issue.
Code change:
sha256 = "1fa7cmwrzn6kx87kms8i98p9azdlwyh2gnif29l340syl9hkr5qy"; }; <del> configFile = optionalString (conf != null) (builtins.toFile "nnn.h" conf); preBuild = optionalString (conf != null) "cp ${configFile} src/nnn.h"; </del> <ins> configFile = lib.optionalString (conf != null) (builtins.toFile "nnn.h" conf); preBuild = lib.optionalString (conf != null) "cp ${configFile} src/nnn.h"; </ins> nativeBuildInputs = [ pkg-config ]; buildInputs = [ readline ncurses ]; <del> makeFlags = [ "DESTDIR=${placeholder "out"}" "PREFIX=" ]; </del> <ins> makeFlags = [ "DESTDIR=${placeholder "out"}" "PREFIX=" ] ++ lib.optional withIcons [ "O_ICONS=1" ] ++ lib.optional withNerdIcons [ "O_NERD=1" ]; </ins> # shell completions postInstall = ''

Related discussion:
text: It would be great to have option to fetch nnn plugins with nxpkgs or with additional package instead of manually fetching it like developer advise. And second is it possible to implement some option to include icons support from nerdfont to nnn binary file instead of recompiling it? Thanks.
I think this issue was closed preemptively by the line in the PR, there doesn't seem to be any way to include plugins as of now
nnn seems to expect plugins in . This might work better as a home-manager module, maybe with the plugins themselves as an output of nixpkgs. I might take a look at this next week.
I marked this as stale due to inactivity. &rarr;
I've recompiled nnn with icons, by using unstable branch and overriding nnn-package:
I marked this as stale due to inactivity. &rarr;
Code change:
rustPlatform.buildRustPackage.override { stdenv = clangStdenv; } rec { pname = "neovide"; <del> version = "0.12.2"; </del> <ins> version = "0.13.0"; </ins> src = fetchFromGitHub { owner = "neovide"; repo = "neovide"; rev = version; <del> sha256 = "sha256-M19LKNjUmC0WkVGm4t7vjxgMMe0FdMTmB1mLcG33OUg="; </del> <ins> sha256 = "sha256-lYahMSaagT6DloFMXT2lLPM1xX/9IEGNIPvbo1MQgSw="; </ins> }; <del> cargoHash = "sha256-2fPprZVT7V+Ot8aCpWj6WTdyFylmzlujFdTJCrtE0rk="; </del> <ins> cargoHash = "sha256-g/Ezyz2gC1YaPMdIy/WdoOvezJUH3aB2FA87viahRzc="; </ins> SKIA_SOURCE_DIR = let

Related discussion:
text: Package name: neovide Latest released version: 0.13.0 <!-- Search your package here: --- Current version on the unstable channel: 0.12.2 Current version on the stable/release channel: 0.11.2 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --- Note for maintainers: Please tag this issue in your PR. As an additional note, I am currently working on updating Neovide myself. Part of my plans this summer are to begin giving at least two contributions to Nix/NixOS/Nixpkgs each week. I intend to begin maintaining Neovide as part of this goal. Gotta figure out how to A.) apply as a maintainer and B.) figure out if I'm even eligible. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
For future issues/prs/etc. where should I add an additional summary/context if I have any? I've sandwiched it between the Note for maintainers... and Add a reaction... sections in this issue.
Code change:
You cannot configure both an Intel iGPU and an AMD APU. Pick the one corresponding to your processor. ''; } { assertion = primeEnabled -> pCfg.nvidiaBusId != "" && (pCfg.intelBusId != "" || pCfg.amdgpuBusId != ""); message = '' When NVIDIA PRIME is enabled, the GPU bus IDs must configured. ''; } { assertion = offloadCfg.enable -> versionAtLeast nvidia_x11.version "435.21"; message = "NVIDIA PRIME render offload is currently only supported on versions >= 435.21."; } { assertion = !(syncCfg.enable && offloadCfg.enable); message = "Only one NVIDIA PRIME solution may be used at a time."; } { assertion = !(syncCfg.enable && cfg.powerManagement.finegrained); message = "Sync precludes powering down the NVIDIA GPU."; } { assertion = cfg.powerManagement.enable -> offloadCfg.enable; message = "Fine-grained power management requires offload to be enabled."; } <ins> { assertion = cfg.powerManagement.enable -> ( builtins.pathExists (cfg.package.out + "/bin/nvidia-sleep.sh") && builtins.pathExists (cfg.package.out + "/lib/systemd/system-sleep/nvidia") ); message = "Required files for driver based power management don't exist."; } </ins> ]; # If Optimus/PRIME is enabled, we:

Related discussion:
text: In is installed if it exists, and the install siliently continues if it doesn't exist. In the service the script is executed unconditionally, even if the script doesn't exist. That breaks suspend with the 465 beta driver, because there the script does not exist. I think we should [ ] fail loudly if it doesn't exist (so that if you close the laptop and put it in a bag, it doesn't catch fire) [ ] figure out where the script went / what the replacement is. CC
I will look into this in an hour or two, have a thing to do soon.
Code change:
strings.  The latter is concatenated, interspersed with colon characters. ''; <del> type = with types; attrsOf (oneOf [ str path (listOf str) ]); </del> <ins> type = with types; attrsOf (oneOf [ (listOf str) str path ]); </ins> apply = mapAttrs (n: v: if isList v then concatStringsSep ":" v else "${v}"); };

Related discussion:
text: Steps to reproduce the behavior: -rebuild of NixOS with GNOME Known workaround: reverting ( ) Please run and paste the result.
Opened an issue but unsure about what is going on / how to fix other than reverting that commit. I don't know that much nix :C
does fix the issue for you?
It does, thanks for the fix. :3
Code change:
<del> { lib, stdenv, fetchFromGitHub, fetchpatch, pkg-config, fuse, adb }: </del> <ins> { lib , stdenv , fetchFromGitHub , pkg-config , fuse , android-tools }: </ins> stdenv.mkDerivation rec { pname = "adbfs-rootless"; <del> version = "2016-10-02"; </del> <ins> version = "unstable-2023-03-21"; </ins> src = fetchFromGitHub { owner = "spion"; <del> repo = "adbfs-rootless"; rev = "b58963430e40c9246710a16cec58e7ffc88baa48"; sha256 = "1kjibl86k6pf7vciwaaxwv5m4q28zdpd2g7yhp71av32jq6j3wm8"; </del> <ins> repo = pname; rev = "fd56381af4dc9ae2f09b904c295686871a46ed0f"; sha256 = "atiVjRfqvhTlm8Q+3iTNNPQiNkLIaHDLg5HZDJvpl2Q="; </ins> }; <del> patches = [ (fetchpatch { # https://github.com/spion/adbfs-rootless/issues/14 url = "https://github.com/kronenpj/adbfs-rootless/commit/35f87ce0a7aeddaaad118daed3022e01453b838d.patch"; sha256 = "1iigla74n3hphnyx9ffli9wqk7v71ylvsxama868czlg7851jqj9"; }) ]; </del> nativeBuildInputs = [ pkg-config ]; buildInputs = [ fuse ]; postPatch = '' # very ugly way of replacing the adb calls <del> sed -e 's|"adb |"${adb}/bin/adb |g'  -i adbfs.cpp </del> <ins> substituteInPlace adbfs.cpp  --replace '"adb ' '"${android-tools}/bin/adb ' </ins> ''; installPhase = '' <ins> runHook preInstall </ins> install -D adbfs $out/bin/adbfs <ins> runHook postInstall </ins> ''; meta = with lib; { description = "Mount Android phones on Linux with adb, no root required"; inherit (src.meta) homepage; license = licenses.bsd3; <del> maintainers = with maintainers; [ Profpatsch ]; platforms = platforms.linux; </del> <ins> maintainers = with maintainers; [ Profpatsch aleksana ]; platforms = platforms.unix; </ins> }; }

Related discussion:
text: Package name: adbfs-rootless Latest released version: 2023-03-21 <!-- Search your package here: --- Current version on the unstable channel: 2016-10-02 Current version on the stable/release channel: 2016-10-02 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR.
Code change:
}; <del> dvisvgm = stdenv.mkDerivation { </del> <ins> dvisvgm = stdenv.mkDerivation rec { </ins> pname = "texlive-dvisvgm.bin"; <del> inherit version; inherit (common) src; </del> <ins> version = "2.11"; # TODO: dvisvgm was switched to build from upstream sources # to address https://github.com/NixOS/nixpkgs/issues/104847 # We might want to consider reverting that change in the future. src = fetchurl { url = "https://github.com/mgieseki/dvisvgm/releases/download/${version}/dvisvgm-${version}.tar.gz"; sha256 = "12b6h0h8rc487yjh3sq9zsdabm9cs2vqcrb0znnfi8277f87zf3j"; }; </ins> nativeBuildInputs = [ pkgconfig ]; <del> # TODO: dvisvgm still uses vendored dependencies buildInputs = [ core/*kpathsea*/ ghostscript zlib freetype /*potrace xxHash*/ ]; preConfigure = "cd texk/dvisvgm"; configureFlags = common.configureFlags ++ [ "--with-system-kpathsea" ]; </del> <ins> buildInputs = [ core/*kpathsea*/ brotli ghostscript zlib freetype woff2 potrace xxHash ]; </ins> enableParallelBuilding = true; };

Related discussion:
text: <!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on github to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the the current version of the package --- <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- name: texlive- current version: 2.9.1 desired version: 2.10.1 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Please tag this issue in your PR.
Can you tell a bit about your use case?
I knew I forgot something! :smile: I'm using emacs + org-mode, and am using the =unicode-math= package with =stix2-otf= along with lualatex. In order to preview equations, the pipeline goes /However/, =dvisvgm= 2.9.1 doesn't understand the extended font data that lualatex emits (see the comments in ), and so produces corrupt output images. This was fixed in 2.10.1, which was recently released and pushed to CTAN.
Code change:
<del> Updating the QEMU patches ========================= When updating to the latest American Fuzzy Lop, make sure to check for any new patches to qemu for binary fuzzing support: https://github.com/google/AFL/tree/master/qemu_mode Be sure to check the build script and make sure it's also using the right QEMU version and options in `qemu.nix`: https://github.com/google/AFL/blob/master/qemu_mode/build_qemu_support.sh `afl-config.h`, `afl-types.h`, and `afl-qemu-cpu-inl.h` are part of the afl source code, and copied from `config.h`, `types.h` and `afl-qemu-cpu-inl.h` appropriately. These files and the QEMU patches need to be slightly adjusted to fix their `#include`s (the patches try to otherwise include files like `../../config.h` which causes the build to fail). </del>

Related discussion:
text: Steps to reproduce the behavior: afl <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
If you are planing to open a PR, you don't need to create an issue first.
I wasn't sure, thanks for clarification
Code change:
preFixup = '' gappsWrapperArgs+=( <del> --prefix "PATH" : "${gvfs}/bin" </del> <ins> # needed for gio executable to be able to delete files --prefix "PATH" : "${glib.bin}/bin" </ins> ) '';

Related discussion:
text: Describe the bug It is not possible to delete files in atom. To Reproduce Steps to reproduce the behavior: to delete a file Expected behavior This action should not result in an error. Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
gvfs-trash has been removed for a few years () after several years of deprecation period. For the atom issue, this is likely a duplicate of
Ah thank you for this, I will update the title and description accordingly
You can try installing globally. That contains command, which is ’s successor and most programs support it. Not sure about Atom though.