jiebi/CodeConvo huggingface dataset:
Change:
meta = with lib; { description = "An open source Spotify client running as a UNIX daemon"; homepage = "https://spotifyd.rs/"; <del> changelog = "https://github.com/Spotifyd/spotifyd/raw/v${version}/CHANGELOG.md"; </del> <ins> changelog = "https://github.com/Spotifyd/spotifyd/blob/${src.rev}/CHANGELOG.md"; </ins> license = licenses.gpl3Plus; maintainers = with maintainers; [ anderslundstedt Br1ght0ne marsam ]; platforms = platforms.unix;

Discussion:
Steps to reproduce the behavior: from Looks like a problem with building . May be related to . Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
url = "https://gitweb.gentoo.org/repo/gentoo.git/plain/media-gfx/iscan/files/iscan-3.61.0-imagemagick-7.patch?id=985c92af4730d864e86fa87746185b0246e9db93"; sha256 = "sha256-dfdVMp3ZfclYeRxYjMIvl+ZdlLn9S+IwQ+OmlHW8318="; }) <ins> (fetchpatch { url = "https://raw.githubusercontent.com/archlinux/svntogit-community/b3046e0e78b95440f135fcadb19a9eb531729a58/trunk/boost-1.74.patch"; sha256 = "sha256-W8R1l7ZPcsfiIy1QBJvh0M8du0w1cnTg3PyAz65v4rE="; }) </ins> ]; nativeBuildInputs = [

Discussion:
The change introduced in breaks building utsushi package (on my system) Steps to reproduce the behavior: Add package like this: Results in an error during the build: <details<summaryOutput of </summary</detailsWhen pinning the channel and installing the package to the previous revision the package doesn't break. Please let me know if you need any more input
Thanks for the report!
Thanks, the fix works! :raised_hands:
Change:
{ stdenv, fetchurl, meson, ninja, pkgconfig, gettext, gnome3, dbus <del> , glib, libgudev, udisks2, libgcrypt, libcap, polkit </del> <ins> , glib, libgudev, udisks2, libgcrypt, libcap, polkit, fetchpatch </ins> , libgphoto2, avahi, libarchive, fuse, libcdio , libxml2, libxslt, docbook_xsl, docbook_xml_dtd_42, samba, libmtp , gnomeSupport ? false, gnome, gcr, wrapGAppsHook

Discussion:
, (nixos-19.03) Scanned versions: nixos-19.03: . May contain false positives.
See also

, (nixos-19.03) (nixos-19.03) (nixos-19.03) Scanned versions: nixos-19.03: . May contain false positives.
Change:
{ stdenv, fetchurl, meson, ninja, pkgconfig, gettext, gnome3, dbus <del> , glib, libgudev, udisks2, libgcrypt, libcap, polkit </del> <ins> , glib, libgudev, udisks2, libgcrypt, libcap, polkit, fetchpatch </ins> , libgphoto2, avahi, libarchive, fuse, libcdio , libxml2, libxslt, docbook_xsl, docbook_xml_dtd_42, samba, libmtp , gnomeSupport ? false, gnome, gcr, wrapGAppsHook

Discussion:
, (nixos-19.03) Scanned versions: nixos-19.03: . May contain false positives.
See also
Change:
darwin.apple_sdk.frameworks.Foundation ]; <ins> preFixup = '' gappsWrapperArgs+=( --prefix PATH : "${lib.makeBinPath [ imagemagick ]}" ) ''; </ins> # Workaround for the gettext-sys issue # https://github.com/Koka/gettext-rs/issues/114 env.NIX_CFLAGS_COMPILE = lib.optionalString

Discussion:
Switcheroo fails with the error in the title. This does not happen in the Flatpak version (tested). (the formats might not matter, but I've specified them just in case) Steps to reproduce the behavior: a PNG file in Switcheroo to a JPEG file. the output filename. should happen. The image should convert without any errors. ! 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Oops, I had in my path when I originally packaged and tested this. I have it as a dependency in and tested it with this time. Thank you for trying the flatpak and reporting it here first instead of upstream :slightlysmilingface:
Change:
"bin/macdeployqt" ]; <ins> NIX_CFLAGS_COMPILE = lib.optional stdenv.isDarwin ''-DNIXPKGS_QMLIMPORTSCANNER="${qtdeclarative.dev}/bin/qmlimportscanner"''; </ins> setupHook = ../hooks/qttools-setup-hook.sh; }

Discussion:
We are currently stuck on qt 5.11 on darwin/macOS. To get things consistent, this should update to qt 5.12 (or even 5.13) soon. Please run and paste the results.
If qt512 builds on darwin we should change the default version:
is currently broken:
Fixed in

When running the provided by the package, it complains about not finding the tool, which is provided by . I have not found a suitable workaround, since it seems like the location of the scanner is hardcoded inside Invoke on a project using Qt. How to use this tool is explained here: Please run and paste the results. system: host os: multi-user?: sandbox: version: channels(raskolnikov): nixpkgs:
The error is as follows:
Hi I tried withyour latestchanges from . The fact that Qt 5.12 now works on Darwin again is great news! However, this issue seems to not be resolved. Now the does not bail out inmmediately as it did before. It does indeed do something for a while, but then later I get: Maybe there is some other part of the code where it is missing the path correction? Thanks a lot!
My bad, I was actually using the old one by mistake... I am getting new errors though: I will investigate...
I think I found the issue. The problem is this line: is returning , which is incorrect. I think lines 1258-1260 can be discarded altogether since without the tool is still correctly using , which is a better way of passing the import paths, since inside Nix we actually need multiple import paths anyways due to the modularized Qt installation. Would you be happy to extend the patch with such a modification?
Ok... I have further investigated and I was wrong... One must indeed pass to to really make it work. One can indeed pass multiple times, and probably we shall do it for every entry in . Probably this can be patched... but it seems like we are getting into non trivial patching territory...
Thanks Mathew for reopening the issue. I opened a corresponding issue on Qt:
I marked this as stale due to inactivity. &rarr;
Actually this still stands and it'd be nice to have it fixed some day. There are other issues that are blocking me on Mac these days though, like .
I marked this as stale due to inactivity. &rarr;
Change:
meta = { description = "Commodore 64, 128 and other emulators"; <del> homepage = "http://www.viceteam.org"; </del> <ins> homepage = "https://vice-emu.sourceforge.io/"; </ins> license = lib.licenses.gpl2Plus; maintainers = [ lib.maintainers.sander ]; platforms = lib.platforms.linux;

Discussion:
<!-- 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: vice <!-- The current version can be found easily with the same process than above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 3.1 desired version: 3.5 <!-- 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. Also, the homepage should be https://vice-, seems completely unrelated to the project.
I marked this as stale due to inactivity. &rarr;
Change:
--replace  "install_args <- c("CMD", "INSTALL", "--no-multiarch", "--with-keep.source", tarball)"  "install_args <- c("CMD", "INSTALL", "--no-multiarch", "--with-keep.source", "-l $out/library", tarball)" <ins> # Retry this test in next release. Something fails in the setup, so GTEST_FILTER is not enough rm tests/cpp_tests/test_arrow.cpp </ins> ''; cmakeFlags = lib.optionals doCheck [ "-DBUILD_CPP_TEST=ON" ]

Discussion:
Package name: lightgbm Latest released version: 4.3.0 <!-- Search your package here: --- Current version on the unstable channel: 4.1.0 Current version on the stable/release channel: 4.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! --- Version 4.1.0 gets broken by . Version 4.3.0 incorporates which builds tests with C++14. 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]:
Thanks. I'll have a look
Change:
buildPythonPackage rec { pname = "flet"; version = "0.18.0"; <del> format = "pyproject"; </del> <ins> pyproject = true; </ins> src = fetchPypi { inherit pname version;

Discussion:
Steps to reproduce the behavior: Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
snom = mk "applications/mod_snom" []; sonar = mk "applications/mod_sonar" []; soundtouch = mk "applications/mod_soundtouch" []; <del> spandsp = mk "applications/mod_spandsp" [ spandsp ]; </del> <ins> spandsp = mk "applications/mod_spandsp" [ spandsp3 ]; </ins> spy = mk "applications/mod_spy" []; stress = mk "applications/mod_stress" []; translate = mk "applications/mod_translate" [];

Discussion:
Describe the bug version 1.18.0 fails to build. To Reproduce Steps to reproduce the behavior: Expected behavior Build properly completes. Logs Full build log: Additional context This is blocking rebuilds. Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(anna): nixpkgs: Maintainer information:
I'm experiencing this as well.
might be due to spansp upgrade in
Change:
libcap libtiff libva libgphoto2 libxslt libtxc_dxtn libsndfile giflib zlib glib alsaLib zziplib bash dbus keyutils zip cabextract freetype unzip coreutils readline gcc SDL SDL2 curl graphite2 gtk2 gtk3 udev ncurses wayland libglvnd <del> vulkan-loader xdg_utils sqlite gnutls </del> <ins> vulkan-loader xdg_utils sqlite gnutls libbsd </ins> # PCSX2 // TODO: "libgobject-2.0.so.0: wrong ELF class: ELFCLASS64"

Discussion:
Describe the bug When I start a scummvm game installed via the integration, I get an error in the logs about To Reproduce Steps to reproduce the behavior: Blade Runner from using Lutris. Blade Runner. Expected behavior Game starts without any problems. Metadata
do you mind checking out and trying to run the game with those changes?
That works an absolute treat!
Change:
"tests/integrations/rq/" # broken since pytest 7.0.1; AssertionError: previous item was not torn down properly "tests/utils/test_contextvars.py" <ins> # broken since Flask and Werkzeug update to 2.1.0 (different error messages) "tests/integrations/flask/test_flask.py" "tests/integrations/bottle/test_bottle.py" "tests/integrations/django/test_basic.py" "tests/integrations/pyramid/test_pyramid.py" ] # test crashes on aarch64 ++ lib.optionals (stdenv.buildPlatform != "x86_64-linux") [ "tests/test_transport.py" "tests/integrations/threading/test_threading.py" </ins> ]; pythonImportsCheck = [

Discussion:
Build of failed on x86_64-linux as of . This is currently breaking maintainers cc: maintainers cc: Other cc: n/a nixpkgs at commit This issue was automatically generated by . that created this issue. Internal tag:
can confirm for and
I'm trying to bisect this atm, but it's a truly massive undertaking since there's hundreds of commits between current master and the last successful build... plus there's lots of other irrelevant failures :/
I was unable to find the exact commit that caused these failures, since it was interlaced a bunch of other commits that broke dependencies. Created upstream. We'll see what they say. We're not doing any patching of required dependency versions, so the test suite ought to be passing.
I also tried bisecting. Due to the massive rebuilds, I canceled after 8 hours and did a bisect with . The bad commit is from , which is a merge from staging with changes to python and others: <details</detailsLooking at the there is a requirement for werkzeug < 2.1.0. When applied, the test mostly pass. The only failing test is: There is also a requirement for pytest < 7. Since this packaged builds with the latest nixos/unstable, which includes pytest 7.0.1 I am now testing with that version.
The updates usually breaks the package. I guess from 1.5.7 to 1.5.8. Edit: Was part of
Further investigation: When I apply the following two changes: downgrade to downgrade to sentry-sdk builds without issues. How should we go about this? Just disabling the tests could lead to malfunction of the sentry-sdk package (because they did correctly detected a regression in the SDK). Downgrading both packages Adding an override in for those two packages could lead to potential breakages due to dual imports of two different or imports in packages, which import sentry-sdk and one of the two packages. Obviously it would be awesome if upstream update their end of the SDK of werkzeug. This could take some time and sentry-sdk is needed by other packages.
I notified the authors of the breaking commits and
Another breakage is pgadmin (tracked in )
Module can't have overrides. Thus, till the issues are fixed by upstream the failing tests should be disabled.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
<ins> diff --git a/configure.ac b/configure.ac index 3ad983d..ff8ff96 100644 --- a/configure.ac +++ b/configure.ac @@ -476,13 +476,7 @@ AS_IF([echo "$protobuf_LIBS" | grep -q -- -pthread], # Bash completion needs to ask where it goes if >= 2.0 is installed. AS_IF([test "$install_completion" != no], -  [PKG_CHECK_MODULES([BASH_COMPLETION], [bash-completion >= 2.0], -     [if test "$prefix" = "NONE"; then -        completions="`pkg-config --variable=completionsdir bash-completion`" -      else -        completions="`pkg-config --define-variable=prefix=$prefix --variable=completionsdir bash-completion`" -      fi], -     [completions="${sysconfdir}/bash_completion.d"]) +   [completions="`pkg-config --define-variable=datadir=$datadir --variable=completionsdir bash-completion`"] AC_SUBST([completions])]) AC_CONFIG_FILES([ </ins>

Discussion:
Describe the bug A clear and concise description of what the bug is. The package fails to build. It errors out during the installation of bash completions with "Permissions denied". To Reproduce Steps to reproduce the behavior: -build -A mosh Expected behavior Successful build Notify maintainers Metadata on Maintainer information:
The breaking commit is the bash-completion update from 2.9 to 2.10: . Any idea how to resolve this?
I think you meant to link . Seems to be a regression from incorrectly dropping by ( in ). The "wrong" prefix comes from . A possible alternative would be to drop the dependency on for (if there's a correct fallback - since we don't actually the prefix from anyway).
I think removing this patch was correct, as the functionality introduced in that patch was to 2.10, however a program needs to define instead of when reading variable, which may necessitate patches (which could be upstreamed). It's unfortunate that the upstream decided on different approach than what was done previously, but trying to preserve the old behaviour would cause more issues in long-term. Let's not overcomplicate things when some of upstream projects already have code that uses when using = 2.10. I imagine this is the line that needs changing:
sorry, my assumption about the patch was wrong then :o And thanks for the fix :) Edit: And I agree that we should follow upstream then.
Change:
xdg-desktop-portal-gtk = callPackage ../development/libraries/xdg-desktop-portal-gtk { }; <ins> xdg-desktop-portal-hyprland = callPackage ../applications/window-managers/hyprwm/xdg-desktop-portal-hyprland { }; </ins> xdg-desktop-portal-wlr = callPackage ../development/libraries/xdg-desktop-portal-wlr { }; xdg-user-dirs = callPackage ../tools/X11/xdg-user-dirs { };

Discussion:
Project description A wlroots-compatible Wayland color picker that does not suck. Metadata homepage URL: source URL: license: platforms: linux Just because you made available on NixOS, I wanted to point you on hyprpicker, too - if you're interested to have a look into this(?)
I'll take a look into packaging this.
Change:
let qt5Deps = pkgs: with pkgs.qt5; [ qtbase qtmultimedia ]; <del> gnome3Deps = pkgs: with pkgs.gnome3; [ zenity gtksourceview gnome-desktop libgnome-keyring webkitgtk ]; </del> <ins> gnome3Deps = pkgs: with pkgs; [ gnome3.zenity gtksourceview gnome3.gnome-desktop gnome3.libgnome-keyring webkitgtk ]; </ins> xorgDeps = pkgs: with pkgs.xorg; [ libX11 libXrender libXrandr libxcb libXmu libpthreadstubs libXext libXdmcp libXxf86vm libXinerama libSM libXv libXaw libXi libXcursor libXcomposite

Discussion:
Describe the bug Seems like some updates to pango broke a few packages Among the broken ones: ettercap (see ) pangox-compat (which anydesk needs) probably a few more To Reproduce Steps to reproduce the behavior: to build ettercap or anydesk from master will fail to build with some pango-related errors Expected behavior It should work Screenshots If applicable, add screenshots to help explain your problem. Additional context Add any other context about the problem here. Metadata system: host os: multi-user?: sandbox: version: channels(maciej): nixpkgs: Maintainer information:
Also remmina is broken But doesn't seem to depend on pango directly, so unsure which dependency actually is broken
Here's an issue for pangox-compat
Lutris is broken too - not an urgent requirement but just making you fine folks aware!
Not sure why Lutris is broken, but Lutris-unwrap is fine.
It's a failure in the dependency chain, in this case .
no longer depends on on its master branch: We should probably switch to that. should not be needed in according to the README in , I suspect it was only there because we did not propagate it until ebassi also suggests switching to HEAD and says we need not worry about ABI changes:
Not having pangox_compat fixed is definitively still an issue. Can this be re-opened?
After , the only program depending on this is anydesk and openmodelica which is broken.
So it breaks anydesk thus either we mark anydesk as broken or we fix that?
Anydesk shouldn't use this deprecated library. Yes, we can mark it as broken.
Change:
pcsxr = callPackage ../applications/emulators/pcsxr { }; <del> ppsspp-sdl = ppsspp.override { enableQt = false; enableVulkan = true; }; ppsspp-sdl-wayland = ppsspp.override { forceWayland = true; enableVulkan = false; # https://github.com/hrydgard/ppsspp/issues/13845 }; ppsspp-qt = ppsspp.override { enableQt = true; enableVulkan = false; # https://github.com/hrydgard/ppsspp/issues/11628 }; </del> <ins> ppsspp-sdl = let argset = { ffmpeg = ffmpeg_4; glew = glew.override { enableEGL = argset.forceWayland; }; enableQt = false; enableVulkan = true; forceWayland = false; }; in ppsspp.override argset; ppsspp-sdl-wayland = let argset = { ffmpeg = ffmpeg_4; glew = glew.override { enableEGL = argset.forceWayland; }; enableQt = false; enableVulkan = false; # https://github.com/hrydgard/ppsspp/issues/13845 forceWayland = true; }; in ppsspp.override argset; ppsspp-qt = let argset = { ffmpeg = ffmpeg_4; glew = glew.override { enableEGL = argset.forceWayland; }; enableQt = true; enableVulkan = false; # https://github.com/hrydgard/ppsspp/issues/11628 forceWayland = false; }; in ppsspp.override argset; </ins> proton-caller = callPackage ../applications/emulators/proton-caller { };

Discussion:
When adding the ppsspp package (or any of its derivates such as ppsspp-sdl-wayland) and running a game, I would get very severe graphical glitches during cutscene or video playback. After reaching out to the PPSSPP team, they mentioned that building with the USESYSTEMFFMPEG flag set to true can cause these issues and is not recommended. After locally building PPSSPP using the file from this repo modified to have USESYSTEMFFMPEG = false (and removing the ffmpeg4 build inputs), I can confirm that the games that I used to have graphical glitches on, now work perfectly. I can create a pull request for this but this is my first time working with packaging in nix and wanted to see if there was a specific reason why USESYSTEMFFMPEG is used (or if it's maybe against design principles of nix to use bundled ffmpeg libraries in apps) Steps to reproduce the behavior: package ppsspp as normal -you get behaviour similar to the before screenshot package ppsspp using modified that has USESYSTEMFFMPEG = false -you get behaviour similar to the after screenshot The after behaviour is expected. Before: <img width="567" alt="Screenshot 2024-04-16 " src=""<img width="563" alt="Screenshot 2024-04-16 " src=""After: ! Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
By default we prefer to use system libraries, in order to avoid duplication and increase "cache hits" from Hydra. Further, I particularly subscribe to some recommendations from Gentoo team: Nonetheless I will verify this issue tomorrow or asap
I agree with that statement to limit dependency bundling as much as possible, but happy to see what you get out of your testing :). I'm good for now since I build the package myself with my modified
Would be interesting to know why they bundle ffmpeg and what patches they use
Change:
rustPlatform.buildRustPackage rec { pname = "lightningcss"; <del> version = "1.26.0"; </del> <ins> version = "1.27.0"; </ins> src = fetchFromGitHub { owner = "parcel-bundler"; repo = "lightningcss"; rev = "refs/tags/v${version}"; <del> hash = "sha256-ZPqRxHbca8iflWwsDT2/sVbTstWnKVFcExcgrBXgzGc="; </del> <ins> hash = "sha256-YOTFyIDQIdqnrbXtnnY5U32rk9/fZ+1NcSb3slgkxZU="; </ins> }; <del> cargoHash = "sha256-QYrjDJJTJo4BDQOqY1pZn7ph+uuQvbsMbzaAUr4siaE="; </del> <ins> cargoHash = "sha256-nzRvsdW+PfcS1ocg49JtRQ9RmFJ3iz65plH1ToQXSGU="; </ins> patches = [ # Backport fix for build error for lightningcss-napi

Discussion:
Package name: lightningcss Latest released version: 1.27.0 <!-- Search your package here: --- Current version on the unstable channel: 1.26.0 Current version on the stable/release channel: <!-- 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 Note for maintainers: Please tag this issue in your PR. Bumping the hash to from tag, failed to get to the phase about vendored dependencies. I don’t really know Rust’s packaging system to understand what these errors mean. Log trying to build: Again, since the color mixing regression so I still can’t upgrade past 1.23.x personally so it is hard to be motivated to maintain versions I can’t use. you helped out with the previous patch, perhaps you have some insight? Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]: [^no-ms-gh] or offering a non-proprietary, non-US-corporate-controlled mirror for this free software project. I wish to delete this Microsoft account in the future, but I need more projects like this to support alternative methods to send patches & contribute.
I usually run update scripts for packages like these. did its job perfectly, even updated the .