jiebi/CodeConvo huggingface dataset:
Change:
inherit (darwin) cctools developer_cmds; inherit (darwin.apple_sdk.frameworks) CoreServices; boost = boost173; # Configure checks for specific version. <del> protobuf = protobuf3_7; </del> <ins> protobuf = protobuf3_11; </ins> icu =  icu67; };

Discussion:
<!-- Note that these are hard requirements --- name: mysql80 current version: 8.0.22 desired version: 8.0.25 maintainers: Orivej Desh < tag this issue in your PR.
I have started to work on this but the derivation build fails. My commit is here: Any ideas?
See for possible resolution.
Hello thank you for your response. I forgot to mention I already tried to set the C++ standards to no avail. Specifically, I tried to set and . Is there anything else I can try? EDIT: the linked Gentoo issue refers to GCC 11 while the GCC version I used is 10.3. EDIT 2: Tried also with GCC 11.1, same results.
Turned out to be : Since they upgraded to . I also built with but i'm not sure if that is an actual hard requirement or not. You should probably verify. Thanks for tackling this! Much appreciated :heart:
Great! Thanks! Shall I open a PR or you do it?
Please go ahead. Thank you!
Change:
perlPackages.buildPerlPackage rec { pname = "gscan2pdf"; <del> version = "2.13.2"; </del> <ins> version = "2.13.3"; </ins> src = fetchurl { url = "mirror://sourceforge/gscan2pdf/gscan2pdf-${version}.tar.xz"; <del> hash = "sha256-NGz6DUa7TdChpgwmD9pcGdvYr3R+Ft3jPPSJpybCW4Q="; </del> <ins> hash = "sha256-QAs6fsQDe9+nKM/OAVZUHB034K72jHsKoA2LY2JQa8Y="; </ins> }; patches = [ <del> # fixes warnings during tests. See https://sourceforge.net/p/gscan2pdf/bugs/421 (fetchpatch { name = "0001-Remove-given-and-when-keywords-and-operator.patch"; url = "https://sourceforge.net/p/gscan2pdf/bugs/_discuss/thread/602a7cedfd/1ea4/attachment/0001-Remove-given-and-when-keywords-and-operator.patch"; hash = "sha256-JtrHUkfEKnDhWfEVdIdYVlr5b/xChTzsrrPmruLaJ5M="; }) </del> # fixes an error with utf8 file names. See https://sourceforge.net/p/gscan2pdf/bugs/400 ./image-utf8-fix.patch ];

Discussion:
: can not open Edit-Preferences : can not open Edit-Preferences A dialogue should happen This is the debug log: Add any other context about the problem here. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Hi! I'm afraid I could not reproduce the issue; the Preferences dialogue shows up fine for me. I tried with on NixOS 23.11 with Sway.
Thank you for your fast reply. Does the dialogue connect to some service that must be running?
Quoting Jens Getreu (2024-03-03 14:46:03) The whole app might be trying to connect to SANE when it starts, but I don't think anything is needed for that particular dialogue.
works fine. All other dialogues open correctly. When I try to open Preferences the second time, a tiny little empty window opens. On the console the above error is dumped.
I am running the i3 window manager. Gnome has a settings deamon. I tried: with but it did not help. I still get and no Edit-Preferences dialogue appears.
I'm having the same issue - gscan2pdf v2.13.2, GNOME 45.3, kernel 6.6.16-1-lts
Same for me on KDE on current master with v2.13.2: EDIT: Upstream seems to be ware of the issue:
This should be fixed with Please test and review.
Change:
( cd unpacked/tensorflow* # Adjust dependency requirements: <del> # - Relax flatbuffers, gast and tensorflow-estimator version requirements that don't match what we have packaged </del> <ins> # - Relax flatbuffers, gast, protobuf, tensorboard, and tensorflow-estimator version requirements that don't match what we have packaged </ins> # - The purpose of python3Packages.libclang is not clear at the moment and we don't have it packaged yet # - keras and tensorlow-io-gcs-filesystem will be considered as optional for now. sed -i *.dist-info/METADATA  -e "/Requires-Dist: flatbuffers/d"  -e "/Requires-Dist: gast/d"  <del> -e "/Requires-Dist: libclang/d"  </del> -e "/Requires-Dist: keras/d"  <ins> -e "/Requires-Dist: libclang/d"  -e "/Requires-Dist: protobuf/d"  -e "/Requires-Dist: tensorboard/d"  </ins> -e "/Requires-Dist: tensorflow-estimator/d"  -e "/Requires-Dist: tensorflow-io-gcs-filesystem/d" )

Discussion:
Build of failed on x86_64-linux as of . This is currently breaking . python39Packages.tensorflow-bin maintainers cc: python39Packages.tensorflow maintainers cc: Other cc: n/a nixpkgs at commit This issue was automatically generated by . that created this issue. Internal tags: -
Change:
inherit hash; }; <ins> # Magma doesn't have anything which could be run under doCheck, but it does build test suite executables. # These are moved to $test/bin/ and $test/lib/ in postInstall. outputs = ["out" "test"]; # Fixup for the python test runners postPatch = '' patchShebangs ./testing/run_{tests,summarize}.py substituteInPlace ./testing/run_tests.py  --replace-fail  "print >>sys.stderr, cmdp, "doesn't exist (original name: " + cmd + ", precision: " + precision + ")""  "print(f"{cmdp} doesn't exist (original name: {cmd}, precision: {precision})", file=sys.stderr)" ''; </ins> nativeBuildInputs = [ <ins> autoPatchelfHook </ins> cmake ninja gfortran

Discussion:
Build of failed on x86_64-linux as of . This is currently breaking . python3Packages.torchvision maintainers cc: magma maintainers cc: Other cc: n/a nixpkgs at commit Contents of : This issue was automatically generated by . that created this issue. Internal tags:
This is also breaking atm
This shows that fortran name mangling is using the underscore ``. (See ) Magma should have the flag "-DADD" set during compilation to fix this
And, in fact, clmagma already sets :
Both of the following overlays fixed the problem: Specify the fortran name mangling convention To explain this, in , we see that if USEFORTRAN=off then the FORTRANCONVENTIONS flag is set and also copied to CFLAGS and CXXFLAGS. FORTRANCONVENTIONS is copied outside of this block into the NVCCFLAGS, and DEVCCFLAGS (which can't otherwise be set), so all three flags are necessary if we use the default of USE_FORTRAN=on. Disable fortran in magma
Nice! Would you be interested in turning that into a PR? It'd be great to fix on master!
Change:
<del> { lib , stdenv , fetchFromGitHub , rustPlatform , darwin </del> <ins> { lib, stdenv, fetchFromGitHub, rustPlatform, darwin, cmake, pkg-config, zstd, </ins> }: rustPlatform.buildRustPackage rec { pname = "wasm-pack"; <del> version = "0.12.1"; </del> <ins> version = "0.13.0"; </ins> src = fetchFromGitHub { owner = "rustwasm"; repo = "wasm-pack"; rev = "refs/tags/v${version}"; <del> hash = "sha256-L4mCgUPG4cgTUpCoaIUOTONBOggXn5vMyPKj48B3MMk="; </del> <ins> hash = "sha256-NEujk4ZPQ2xHWBCVjBCD7H6f58P4KrwCNoDHKa0d5JE="; </ins> }; <del> cargoHash = "sha256-mqQRQXaUW6mreE7UUEA0zhhaaGGKLRUngH9QLxcaIdY="; </del> <ins> cargoHash = "sha256-pFKGQcWW1/GaIIWMyWBzts4w1hMu27hTG/uUMjkfDMo="; </ins> <del> buildInputs = lib.optional stdenv.isDarwin darwin.apple_sdk.frameworks.Security; </del> <ins> nativeBuildInputs = [ cmake pkg-config ]; buildInputs = lib.optional stdenv.isDarwin darwin.apple_sdk.frameworks.Security ++ [ zstd ]; </ins> # Most tests rely on external resources and build artifacts. # Disabling check here to work with build sandboxing.

Discussion:
Package name: wasm-pack Latest released version: 0.13.0 <!-- Search your package here: --- Current version on the unstable channel: 0.12.1 Current version on the stable/release channel: 0.12.1 <!-- 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. I just tried to make a PR with the change, but I got when I tried to build (while compiling ), and used all of my RAM while running (it did not finish). I'm using a x86-64 machine with Debian.
I encountered that error too. After reading I tried this: That resulted in a new error log. I don't know what to do but I thought I'll leave it here in the case that I could be useful to someone else
Change:
postPatch = '' substituteInPlace session/eventlog/{app_event.go,login_event.go}  <del> --replace "/bin/bash" "${runtimeShell}" </del> <ins> --replace-fail "/bin/bash" "${runtimeShell}" </ins> substituteInPlace inputdevices/layout_list.go  <del> --replace "/usr/share/X11/xkb" "${xkeyboard_config}/share/X11/xkb" </del> <ins> --replace-fail "/usr/share/X11/xkb" "${xkeyboard_config}/share/X11/xkb" </ins> <del> substituteInPlace bin/dde-system-daemon/wallpaper.go accounts1/user.go  --replace "/usr/share/wallpapers" "/run/current-system/sw/share/wallpapers" </del> <ins> substituteInPlace accounts1/user.go  --replace-fail "/usr/share/wallpapers" "/run/current-system/sw/share/wallpapers" </ins> substituteInPlace timedate1/zoneinfo/zone.go  <del> --replace "/usr/share/dde" "$out/share/dde"  --replace "/usr/share/zoneinfo" "${tzdata}/share/zoneinfo" </del> <ins> --replace-fail "/usr/share/dde" "$out/share/dde"  --replace-fail "/usr/share/zoneinfo" "${tzdata}/share/zoneinfo" </ins> substituteInPlace accounts1/image_blur.go grub2/modify_manger.go  <del> --replace "/usr/lib/deepin-api" "/run/current-system/sw/lib/deepin-api" </del> <ins> --replace-fail "/usr/lib/deepin-api" "/run/current-system/sw/lib/deepin-api" </ins> substituteInPlace accounts1/user_chpwd_union_id.go  <del> --replace "/usr/lib/dde-control-center" "/run/current-system/sw/lib/dde-control-center" </del> <ins> --replace-fail "/usr/lib/dde-control-center" "/run/current-system/sw/lib/dde-control-center" substituteInPlace system/uadp1/crypto.go  --replace-fail "/usr/share/uadp" "/var/lib/dde-daemon/uadp" </ins> for file in $(grep "/usr/lib/deepin-daemon" * -nR |awk -F: '{print $1}') do

Discussion:
Podman exits with an error on unstable. <!-- 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]:
Hmm. I can't seem to reproduce this (also on 24.05..). How is your podman installed?
Just for reference mine is: virtualisation = { podman = { enable = true; dockerCompat = true; }; }; The only thing I can think of is to try removing the line to see if that is what is causing the issue?
Found the culprit. I recently tried Deepin which uses dde-daemon. dde-daemon creates . Removing altogether makes podman work again. A fix was introduced in but got reverted in for some reason. ?
Sorry, this is a mistake. I lost a patch when upgrading dde-daemon, should fix in
Change:
{ lib , stdenv <del> , fetchzip </del> <ins> , fetchFromGitLab </ins> , cmake , extra-cmake-modules , qttools

Discussion:
Package name:crow-translate Latest released version:3.0.0 <!-- Search your package here: --- Current version on the unstable channel:2.11.1 Current version on the stable/release channel:2.11.1 <!-- 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
mkdir -p $out/share/icons ln -s ${sparrow-icons}/hicolor $out/share/icons <del> mkdir -p $out/etc/udev ln -s ${udev-rules}/etc/udev/rules.d $out/etc/udev/rules.d </del> <ins> mkdir -p $out/etc/udev/rules.d cp ${hwi}/lib/python*/site-packages/hwilib/udev/*.rules $out/etc/udev/rules.d </ins> runHook postInstall '';

Discussion:
Steps to reproduce the behavior: sparrow Add any other context about the problem here. <!-- 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.
TLDR; This was caused by and is fixed in Upstream bundles a JDK/JRE with sparrow. Our sparrow package does not use the bundled JDK and instead replaces it with a JDK from Nixpkgs. Since the sparrow bundle contains the JDK and the sparrow code in a single JIMAGE, the sparrow package compares the files in the JIMAGE with the files provided by the JDK in Nixpkgs in order to determine which files in the JIMAGE are part of the JDK. Those files are then excluded from the sparrow derivation. When disabled JavaFX by default it changed the output of the aforementioned comparison, leaving behind some files which belong to the JDK as part of the sparrow derivation; The files which are part of JavaFX. This in turn causes the patchelf procedure to fail because the sparrow package is only expected to patch sparrow-specific dependencies, not the JDK.
Change:
<del> { lib, fetchFromGitHub, rustPlatform, alsa-lib, atk, cairo, dbus, gdk-pixbuf, glib, gtk3, pango, pkg-config }: </del> <ins> { lib, fetchFromGitHub, rustPlatform, alsa-lib, atk, cairo, dbus, gdk-pixbuf, glib, gtk3, pango, pkg-config, makeDesktopItem }: let desktopItem = makeDesktopItem { name = "Psst"; exec = "psst-gui"; comment = "Fast and multi-platform Spotify client with native GUI"; desktopName = "Psst"; type = "Application"; categories = [ "Audio" "AudioVideo" ]; icon = "psst"; terminal = false; }; in </ins> rustPlatform.buildRustPackage rec { pname = "psst"; version = "unstable-2022-05-19";

Discussion:
I'm unable to launch from my application launcher due to it missing the  entry & Please run and paste the result.
Change:
wrapQtApp "$out/bin/veusz" ''; <del> # Since sip 6 (we use sip 4 here, but pyqt5 is built with sip 6), sip files are # placed in a different directory layout and --sip-dir won't work anymore. # --sip-dir expects a directory with a PyQt5 subdirectory (where sip files are located), # but the new directory layout places sip files in a subdirectory named 'bindings'. # To workaround this, we patch the full path into pyqtdistutils.py. </del> <ins> # pyqt_setuptools.py uses the platlib path from sysconfig, but NixOS doesn't # really have a corresponding path, so patching the location of PyQt5 inplace </ins> postPatch = '' <del> substituteInPlace pyqtdistutils.py  --replace "'-I', pyqt5_include_dir," "'-I', '${python3Packages.pyqt5}/${python3Packages.python.sitePackages}/PyQt5/bindings'," </del> <ins> substituteInPlace pyqt_setuptools.py  --replace "get_path('platlib')" "'${python3Packages.pyqt5}/${python3Packages.python.sitePackages}'" </ins> patchShebangs tests/runselftest.py ''; # you can find these options at # https://github.com/veusz/veusz/blob/53b99dffa999f2bc41fdc5335d7797ae857c761f/pyqtdistutils.py#L71 <del> # --sip-dir cannot be used here for the reasons explained above </del> setupPyBuildFlags = [ <del> "--qt-include-dir=${qtbase.dev}/include" </del> # veusz tries to find a libinfix and fails without one # but we simply don't need a libinfix, so set it to empty here "--qt-libinfix="

Discussion:
Steps to reproduce the behavior: Add any other context about the problem here. system: host os: multi-user?: sandbox: version: channels(hervyqa): channels(root): nixpkgs:
issue still exits in unstable channel
Change:
"msg")) ''; <del> passthru.updateScript = unstableGitUpdater { }; </del> <ins> passthru.updateScript = writeScript "update.sh" '' #!/usr/bin/env nix-shell #!nix-shell -i bash -p common-updater-scripts coreutils git gnused set -eu -o pipefail tmpdir="$(mktemp -d)" git clone --depth=1 https://github.com/misohena/el-easydraw.git "$tmpdir" pushd "$tmpdir" commit=$(git show -s --pretty='format:%H') # Based on: https://github.com/melpa/melpa/blob/2d8716906a0c9e18d6c979d8450bf1d15dd785eb/package-build/package-build.el#L523-L533 version=$(TZ=UTC git show -s --pretty='format:%cd' --date='format-local:%Y%m%d.%H%M' | sed 's|.0*|.|') popd update-source-version emacsPackages.el-easydraw $version --rev="$commit" ''; </ins> meta = { homepage = "https://github.com/misohena/el-easydraw";

Discussion:
Package name: Latest released version: <!-- Search your package here: --- Current version on the unstable channel: 1.1.0 Current version on the stable/release channel: 1.1.0 <!-- 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
<ins> From 09efbe8090f501c60975d5467fb587ed633d6a01 Mon Sep 17 00:00:00 2001 From: Florian Klink <flokli@flokli.de> Date: Wed, 24 Jan 2024 14:29:28 +0200 Subject: [PATCH] substitute udevadm --- src/umockdev-record.vala     | 2 +- tests/test-umockdev-run.vala | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/src/umockdev-record.vala b/src/umockdev-record.vala index 2d49bc8..272f25e 100644 --- a/src/umockdev-record.vala +++ b/src/umockdev-record.vala @@ -223,7 +223,7 @@ record_device(string dev) int exitcode; try { Process.spawn_sync(null, -                           {"udevadm", "info", "--query=all", "--path", dev}, +                           {"@udevadm@", "info", "--query=all", "--path", dev}, null, SpawnFlags.SEARCH_PATH, null, diff --git a/tests/test-umockdev-run.vala b/tests/test-umockdev-run.vala index cd00a08..94616cb 100644 --- a/tests/test-umockdev-run.vala +++ b/tests/test-umockdev-run.vala @@ -199,8 +199,8 @@ A: size=1048576n // unfortunately the udevadm output between distros is not entirely constant assert (get_program_out ( -            "udevadm", -            umockdev_run_command + "-d " + umockdev_file + " -- udevadm info --query=all --name=/dev/loop23", +            "@udevadm@", +            umockdev_run_command + "-d " + umockdev_file + " -- @udevadm@ info --query=all --name=/dev/loop23", out sout, out serr, out exit)); assert_cmpstr (serr, CompareOperator.EQ, ""); -- 2.43.0 </ins>

Discussion:
Steps to reproduce the behavior: with enabled <!-- 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]:
This is not really a bug or a build failure, more of a feature request. The expression in nixpkgs doesn't set , as the build with it being set would fail. Someone needs to sit down and figure out why. I propose starting with the code of the two failed tests, seeing if something is missing from nativeCheckInputs. Happy to review a PR, but I don't have the bandwidth to drive this.
It's an indication that the packaging is incorrect. Incorrect packaging sounds like a packaging bug to me. See for the main tracking issue. If it's better categorised as a "bug" than a "build failure", then so be it, but it's absolutely not a "feature request." If you don't have time, that's a totally different topic, that could be just stated as is without the rest of it.
and the test for both use to get information about devices, which is not currently provided by any input. Adding (which provides ) to the check inputs makes this build without errors, even with . Since (a binary output) needs , should probably also be in the regular build inputs. (just stumbled across this randomly and thought I'd try to find out what's up)
Oh, very nice! Wondering how is currently sneaking in then :-) In any case, I'll try to add this to a PR and see how it goes!
I opened that does this, thanks!
The PR has been merged, this can be closed.
Change:
boot.initrd.availableKernelModules = lib.mkIf (initrdFileSystems != { }) [ "overlay" ]; <del> assertions = lib.concatLists (lib.mapAttrsToList (_name: fs: [ { assertion = (fs.overlay.upperdir == null) == (fs.overlay.workdir == null); message = "You cannot define a `lowerdir` without a `workdir` and vice versa for mount point: ${fs.mountPoint}"; } { assertion = (fs.overlay.lowerdir != null && fs.overlay.upperdir == null) -> (lib.length fs.overlay.lowerdir) >= 2; message = "A read-only overlay (without an `upperdir`) requires at least 2 `lowerdir`s: ${fs.mountPoint}"; } ]) config.fileSystems); </del> <ins> assertions = lib.concatLists ( lib.mapAttrsToList (_name: fs: [ { assertion = (fs.overlay.upperdir == null) == (fs.overlay.workdir == null); message = "You cannot define a `lowerdir` without a `workdir` and vice versa for mount point: ${fs.mountPoint}"; } { assertion = (fs.overlay.lowerdir != null && fs.overlay.upperdir == null) -> (lib.length fs.overlay.lowerdir) >= 2; message = "A read-only overlay (without an `upperdir`) requires at least 2 `lowerdir`s: ${fs.mountPoint}"; } ]) overlayFileSystems ) ++ lib.mapAttrsToList (_: fs: { assertion = fs.overlay.upperdir == null -> config.boot.initrd.systemd.enable; message = '' Stage 1 overlay file system ${fs.mountPoint} has no upperdir, which is not supported with scripted initrd. Please enable 'boot.initrd.systemd.enable'. ''; }) initrdFileSystems; </ins> boot.initrd.systemd.services = lib.mkMerge (lib.mapAttrsToList preMountService initrdFileSystems); systemd.services = lib.mkMerge (lib.mapAttrsToList preMountService userspaceFileSystems);

Discussion:
systemd doesn't respect the option for file systems. Usually this is ok because systemd will mount file systems in the correct topological ordering. The option is useful because it allows you to express dependencies on e.g. the file systems that an FS's lower/upper/work directories exist on. This test should hang forever. Instead, it exits cleanly. The service never exits, so is never mounted, and therefore should never be mounted. So the test should hang. This is also a problem for systemd stage 1, but it's worse because we also have to account for the prefix. We can fix this by adding options for every dependency, and prefixing for the systemd stage 1 file systems.
Do we even need the option? I don't think it's particularly useful. The overlay also shouldn't be a concern since anymore.
Well, currently literally only does anything in scripted stage 1. In stage 2 and in systemd stage 1, you have to use , which is what the stuff does. That's fine, but it's an incompatibility between scripted and systemd stage 1. So we need to either deprecate it or implement it, and it's really easy to implement (I just need to fixup ). It's a handy convenience for people I guess, though far from a necessary one.
Change:
''; }; <del> priority = mkOption { </del> <ins> priority = lib.mkOption { </ins> default = 5; <del> type = types.int; </del> <ins> type = lib.types.int; </ins> description = lib.mdDoc '' Priority of the zram swap devices. It should be a number higher than the priority of your disk-based swap devices (so that the system will

Discussion:
Project description In the author says, In 2020 the zram-generator doesn't seem to have had any releases. In the meantime, it's gone from initial release version 0.2.0 up to the somewhat-mature version 1.1.2. It's probably a good time to port this to zram-generator. Metadata homepage URL: source URL: license: mit platforms: linux