jiebi/CodeConvo huggingface dataset:
Code change:
The reason why I didn't open a PR, is described in . I'm aware of four platforms for Qt's themes right now: Using GTK themes through + ; Using GNOME themes through + ; Using Qt themes, with the non-KDE solution , which uses ; Using Plasma-targeted Qt themes, with as , as done natively in a plasma session, using the theme's colorscheme. Steps to reproduce the behavior:  and it does not provide ; equivalent to  providing ; , then add some Pasma-target themes like , then adjust envvars , set the theme in or with , you'll get the right theme with the proper color scheme. should provide (or ) as an option, it should add only the required packages to the system, and set the proper envvars. (or maybe rename it, since qt6 also uses the same variables and envvars) qbittorrent + breeze + + dark: ! qbittorrent + breeze + + dark: ! qbittorrent + (ignored my theme): ! qbittorrent + (also ignored my theme): ! I tried to discover what package that is being when evaluating provides this platform-theme, but I failed miserably. stated as maintainers of plasma-integration: stated as maintainer of qt5ct: qt5 module contributors: cc Please run and paste the result.
Not exactly your bug, but we should remove and integrate it with configs instead.
is another QT platform theme that can be integrated into config.

Related discussion:
text: isQtStyle = cfg.platformTheme == "gtk2" && !(builtins.elem cfg.style ["adwaita" "adwaita-dark"]); isQt5ct = cfg.platformTheme == "qt5ct"; isLxqt = cfg.platformTheme == "lxqt"; <ins> isKde = cfg.platformTheme == "kde"; </ins> packages = if isQGnome then [ pkgs.qgnomeplatform pkgs.adwaita-qt ] else if isQtStyle then [ pkgs.libsForQt5.qtstyleplugins ] else if isQt5ct then [ pkgs.libsForQt5.qt5ct ] else if isLxqt then [ pkgs.lxqt.lxqt-qtplugin pkgs.lxqt.lxqt-config ] <ins> else if isKde then [ pkgs.libsForQt5.plasma-integration pkgs.libsForQt5.systemsettings ] </ins> else throw "`qt5.platformTheme` ${cfg.platformTheme} and `qt5.style` ${cfg.style} are not compatible."; in
Code change:
The reason why I didn't open a PR, is described in . I'm aware of four platforms for Qt's themes right now: Using GTK themes through + ; Using GNOME themes through + ; Using Qt themes, with the non-KDE solution , which uses ; Using Plasma-targeted Qt themes, with as , as done natively in a plasma session, using the theme's colorscheme. Steps to reproduce the behavior:  and it does not provide ; equivalent to  providing ; , then add some Pasma-target themes like , then adjust envvars , set the theme in or with , you'll get the right theme with the proper color scheme. should provide (or ) as an option, it should add only the required packages to the system, and set the proper envvars. (or maybe rename it, since qt6 also uses the same variables and envvars) qbittorrent + breeze + + dark: ! qbittorrent + breeze + + dark: ! qbittorrent + (ignored my theme): ! qbittorrent + (also ignored my theme): ! I tried to discover what package that is being when evaluating provides this platform-theme, but I failed miserably. stated as maintainers of plasma-integration: stated as maintainer of qt5ct: qt5 module contributors: cc Please run and paste the result.
Not exactly your bug, but we should remove and integrate it with configs instead.
is another QT platform theme that can be integrated into config.

Related discussion:
text: "gnome" "lxqt" "qt5ct" <ins> "kde" </ins> ]; example = "gnome"; relatedPackages = [
Code change:
The reason why I didn't open a PR, is described in . I'm aware of four platforms for Qt's themes right now: Using GTK themes through + ; Using GNOME themes through + ; Using Qt themes, with the non-KDE solution , which uses ; Using Plasma-targeted Qt themes, with as , as done natively in a plasma session, using the theme's colorscheme. Steps to reproduce the behavior:  and it does not provide ; equivalent to  providing ; , then add some Pasma-target themes like , then adjust envvars , set the theme in or with , you'll get the right theme with the proper color scheme. should provide (or ) as an option, it should add only the required packages to the system, and set the proper envvars. (or maybe rename it, since qt6 also uses the same variables and envvars) qbittorrent + breeze + + dark: ! qbittorrent + breeze + + dark: ! qbittorrent + (ignored my theme): ! qbittorrent + (also ignored my theme): ! I tried to discover what package that is being when evaluating provides this platform-theme, but I failed miserably. stated as maintainers of plasma-integration: stated as maintainer of qt5ct: qt5 module contributors: cc Please run and paste the result.
Not exactly your bug, but we should remove and integrate it with configs instead.
is another QT platform theme that can be integrated into config.

Related discussion:
text: ["libsForQt5" "qtstyleplugins"] ["libsForQt5" "qt5ct"] ["lxqt" "lxqt-qtplugin"] <ins> ["libsForQt5" "plasma-integration"] </ins> ]; description = '' Selects the platform theme to use for Qt5 applications.</para>
Code change:
The reason why I didn't open a PR, is described in . I'm aware of four platforms for Qt's themes right now: Using GTK themes through + ; Using GNOME themes through + ; Using Qt themes, with the non-KDE solution , which uses ; Using Plasma-targeted Qt themes, with as , as done natively in a plasma session, using the theme's colorscheme. Steps to reproduce the behavior:  and it does not provide ; equivalent to  providing ; , then add some Pasma-target themes like , then adjust envvars , set the theme in or with , you'll get the right theme with the proper color scheme. should provide (or ) as an option, it should add only the required packages to the system, and set the proper envvars. (or maybe rename it, since qt6 also uses the same variables and envvars) qbittorrent + breeze + + dark: ! qbittorrent + breeze + + dark: ! qbittorrent + (ignored my theme): ! qbittorrent + (also ignored my theme): ! I tried to discover what package that is being when evaluating provides this platform-theme, but I failed miserably. stated as maintainers of plasma-integration: stated as maintainer of qt5ct: qt5 module contributors: cc Please run and paste the result.
Not exactly your bug, but we should remove and integrate it with configs instead.
is another QT platform theme that can be integrated into config.

Related discussion:
text: application. </para></listitem> </varlistentry> <ins> <varlistentry> <term><literal>kde</literal></term> <listitem><para>Use Qt settings from Plasma.</para></listitem> </varlistentry> </ins> </variablelist> ''; };
Code change:
The reason why I didn't open a PR, is described in . I'm aware of four platforms for Qt's themes right now: Using GTK themes through + ; Using GNOME themes through + ; Using Qt themes, with the non-KDE solution , which uses ; Using Plasma-targeted Qt themes, with as , as done natively in a plasma session, using the theme's colorscheme. Steps to reproduce the behavior:  and it does not provide ; equivalent to  providing ; , then add some Pasma-target themes like , then adjust envvars , set the theme in or with , you'll get the right theme with the proper color scheme. should provide (or ) as an option, it should add only the required packages to the system, and set the proper envvars. (or maybe rename it, since qt6 also uses the same variables and envvars) qbittorrent + breeze + + dark: ! qbittorrent + breeze + + dark: ! qbittorrent + (ignored my theme): ! qbittorrent + (also ignored my theme): ! I tried to discover what package that is being when evaluating provides this platform-theme, but I failed miserably. stated as maintainers of plasma-integration: stated as maintainer of qt5ct: qt5 module contributors: cc Please run and paste the result.
Not exactly your bug, but we should remove and integrate it with configs instead.
is another QT platform theme that can be integrated into config.

Related discussion:
text: environment.variables.QT_QPA_PLATFORMTHEME = cfg.platformTheme; <del> environment.variables.QT_STYLE_OVERRIDE = mkIf (! (isQt5ct || isLxqt)) cfg.style; </del> <ins> environment.variables.QT_STYLE_OVERRIDE = mkIf (! (isQt5ct || isLxqt || isKde)) cfg.style; </ins> environment.systemPackages = packages;
Code change:
Latest version uses Electron 18 instead of 16, which fixes issues with Wayland + Nvidia graphics. <!-- 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 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: mullvad-vpn <!-- The current version can be found easily with the same process as 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: 2022.1 desired version: 2022.2 <!-- 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.

Related discussion:
text: stdenv.mkDerivation rec { pname = "mullvad-vpn"; <del> version = "2022.1"; </del> <ins> version = "2022.2"; </ins> src = fetchurl { url = "https://github.com/mullvad/mullvadvpn-app/releases/download/${version}/MullvadVPN-${version}_amd64.deb"; <del> sha256 = "0s12y9j75k59kqkcvfflb1v5p3ny7xgc1m5bd635lvql1bv46c3i"; </del> <ins> sha256 = "sha256-h/c4aPH6E2TzbXGROpLJgF9uHYcjvKiW5upIobpJM9o="; </ins> }; nativeBuildInputs = [
Code change:
Latest version uses Electron 18 instead of 16, which fixes issues with Wayland + Nvidia graphics. <!-- 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 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: mullvad-vpn <!-- The current version can be found easily with the same process as 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: 2022.1 desired version: 2022.2 <!-- 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.

Related discussion:
text: , openvpn-mullvad , shadowsocks-rust }: <del> let # result of running address_cache as of 02 Mar 2022 bootstrap-address-cache = writeText "api-ip-address.txt" '' 193.138.218.78:443 193.138.218.71:444 185.65.134.66:444 185.65.135.117:444 217.138.254.130:444 91.90.44.10:444 ''; in </del> rustPlatform.buildRustPackage rec { pname = "mullvad"; <del> version = "2022.1"; </del> <ins> version = "2022.2"; </ins> src = fetchFromGitHub { owner = "mullvad"; repo = "mullvadvpn-app"; rev = version; <del> hash = "sha256-bLwuM3Qy2iStbXIvDEWp31vuiihSQThOej297XKo5Xc="; </del> <ins> hash = "sha256-ZtQKzbFrkacrfPIkMz/UOfIwQBXQUoVVlFla//jmMwY="; </ins> }; <del> cargoHash = "sha256-CBbm8cJHTjyvvzCFQfKmsE5d9N7azEm8nI6KeWLVaa8="; </del> <ins> cargoHash = "sha256-J6h3KY1RDCnAc/tQHNGEyOlVQoQNhRqjWbmimPitydQ="; </ins> nativeBuildInputs = [ pkg-config
Code change:
Latest version uses Electron 18 instead of 16, which fixes issues with Wayland + Nvidia graphics. <!-- 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 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: mullvad-vpn <!-- The current version can be found easily with the same process as 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: 2022.1 desired version: 2022.2 <!-- 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.

Related discussion:
text: postFixup = # Place all binaries in the 'mullvad-' namespace, even though these # specific binaries aren't used in the lifetime of the program. <del> # `address_cache` is used to generate the `api-ip-address.txt` file, which # contains list of Mullvad API servers -- though we provide a "backup" of # the output of this command, it could change at any time, so we want # users to be able to regenerate the list at any time. (The daemon will # refuse to start without this file.) </del> '' <del> for bin in address_cache relay_list translations-converter; do </del> <ins> for bin in relay_list translations-converter; do </ins> mv "$out/bin/$bin" "$out/bin/mullvad-$bin" done '' + <del> # Put distributed assets in-place -- specifically, the # bootstrap-address-cache is necessary; otherwise, the user will have to run # the `address_cache` binary and move the contents into place at # `/var/cache/mullvad-vpn/api-ip-address.txt` manually. '' mkdir -p $out/share/mullvad ln -s ${bootstrap-address-cache} $out/share/mullvad/api-ip-address.txt '' + </del> # Files necessary for OpenVPN tunnels to work. '' <ins> mkdir -p $out/share/mullvad </ins> cp dist-assets/ca.crt $out/share/mullvad ln -s ${openvpn-mullvad}/bin/openvpn $out/share/mullvad ln -s ${shadowsocks-rust}/bin/sslocal $out/share/mullvad
Code change:
Steps to reproduce the behavior:
I don't have an M1 to test
Oh, it suffices to use . I'll open a pull request.

Related discussion:
text: <del> { lib, stdenv, fetchurl, cctools, fixDarwinDylibNames }: </del> <ins> { lib , stdenv , fetchurl , cctools , fixDarwinDylibNames , autoSignDarwinBinariesHook }: </ins> stdenv.mkDerivation rec { pname = "lp_solve"; version = "5.5.2.11";
Code change:
Steps to reproduce the behavior:
I don't have an M1 to test
Oh, it suffices to use . I'll open a pull request.

Related discussion:
text: nativeBuildInputs = lib.optionals stdenv.isDarwin [ cctools fixDarwinDylibNames <ins> ] ++ lib.optionals (stdenv.isDarwin && stdenv.isAarch64) [ autoSignDarwinBinariesHook </ins> ]; dontConfigure = true; <del> buildPhase = let ccc = if stdenv.isDarwin then "ccc.osx" else "ccc"; in '' runHook preBuild </del> <ins> buildPhase = let ccc = if stdenv.isDarwin then "ccc.osx" else "ccc"; in '' runHook preBuild </ins> <del> (cd lpsolve55 && bash -x -e ${ccc}) (cd lp_solve  && bash -x -e ${ccc}) </del> <ins> (cd lpsolve55 && bash -x -e ${ccc}) (cd lp_solve  && bash -x -e ${ccc}) </ins> <del> runHook postBuild ''; </del> <ins> runHook postBuild ''; </ins> installPhase = '' runHook preInstall
Code change:
Steps to reproduce the behavior:
I don't have an M1 to test
Oh, it suffices to use . I'll open a pull request.

Related discussion:
text: meta = with lib; { description = "A Mixed Integer Linear Programming (MILP) solver"; <del> homepage    = "http://lpsolve.sourceforge.net"; license     = licenses.gpl2Plus; </del> <ins> homepage = "http://lpsolve.sourceforge.net"; license = licenses.gpl2Plus; </ins> maintainers = with maintainers; [ smironov ]; <del> platforms   = platforms.unix; </del> <ins> platforms = platforms.unix; </ins> }; }
Code change:
Steps to reproduce the behavior:
I don't have an M1 to test
Oh, it suffices to use . I'll open a pull request.

Related discussion:
text: }; lp_solve = callPackage ../applications/science/math/lp_solve { <del> inherit (darwin) cctools; </del> <ins> inherit (darwin) cctools autoSignDarwinBinariesHook; </ins> }; fabric-installer = callPackage ../tools/games/minecraft/fabric-installer { };
Code change:
<!-- 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 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: winePackages.{unstable,staging} <!-- The current version can be found easily with the same process as 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: 7.10 desired version: 7.12 <!-- 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.
cc
PR at , needs to be tested still. My last attempts at updating have been held back by the fact that there are so many variants that building everything is prohibitively time consuming on my machine, and PRs that were ready have been lingering so long that I've had to update them with one or two even newer wine versions before they were merged, so I was not particularly motivated.

Related discussion:
text: unstable = fetchurl rec { # NOTE: Don't forget to change the SHA256 for staging as well. <del> version = "7.10"; </del> <ins> version = "7.12"; </ins> url = "https://dl.winehq.org/wine/source/7.x/wine-${version}.tar.xz"; <del> sha256 = "sha256-P+skzYWYwQ9q9xHnSsK10kQrtNO4wHj506JTroc2SA0="; </del> <ins> sha256 = "sha256-gJzsE3FmNubq/Uw9pzEkVqhE0xYCClV4YRvNuiEGnGg="; </ins> inherit (stable) gecko32 gecko64 patches; mono = fetchurl rec {
Code change:
<!-- 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 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: winePackages.{unstable,staging} <!-- The current version can be found easily with the same process as 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: 7.10 desired version: 7.12 <!-- 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.
cc
PR at , needs to be tested still. My last attempts at updating have been held back by the fact that there are so many variants that building everything is prohibitively time consuming on my machine, and PRs that were ready have been lingering so long that I've had to update them with one or two even newer wine versions before they were merged, so I was not particularly motivated.

Related discussion:
text: staging = fetchFromGitHub rec { # https://github.com/wine-staging/wine-staging/releases inherit (unstable) version; <del> sha256 = "sha256-5Pt98pla6t+B3FjB80hOWJUO64jY1EmOPQ0hEkFBWxY="; </del> <ins> sha256 = "sha256-A7IcBm3LzXzFu/NT+kbf2InTTuBzyQju/uMxSnIfsls="; </ins> owner = "wine-staging"; repo = "wine-staging"; rev = "v${version}";
Code change:
<!-- 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 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: winePackages.{unstable,staging} <!-- The current version can be found easily with the same process as 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: 7.10 desired version: 7.12 <!-- 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.
cc
PR at , needs to be tested still. My last attempts at updating have been held back by the fact that there are so many variants that building everything is prohibitively time consuming on my machine, and PRs that were ready have been lingering so long that I've had to update them with one or two even newer wine versions before they were merged, so I was not particularly motivated.

Related discussion:
text: stdenv.mkDerivation rec { pname = "vkd3d"; <del> version = "1.3"; </del> <ins> version = "1.4"; </ins> src = fetchurl { url = "https://dl.winehq.org/vkd3d/source/vkd3d-${version}.tar.xz"; <del> sha256 = "134b347806d34a4d2b39ea29ff1c2b38443793803a3adc50800855bb929fb8b2"; </del> <ins> sha256 = "sha256-yLqF9gSCyHPAVs9tuw6veRvIq30W1ipH83uYQbapCr0="; </ins> }; nativeBuildInputs = [ flex bison ];
Code change:
The onlykey package crashes when a file dialog should open ("Save as" / "Choose file") Steps to reproduce the behavior: onlykey to the Firmware / Backup Tab "Choose file" or "Save as" A select file window should open, not crash. ! ! I have nautilus and LF installed, which is successfully used by other programs (firefox etc). Already tried installing gsettings-desktop-schemas and setting XDGDATADIRS as described . I use dwm and no Gnome and no Gnome Packages except nautilus. I would guess it needs to use wrapGAppsHook as nativeBuildInputs but I have no idea how/where to add that. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- [username nix-shell -p nix-info --run "nix-info -m" system: host os: multi-user?: sandbox: version: channels(root): channels(username): nixpkgs:
Have you cloned nixpkgs? Did you find the nix file where the package recipe is defined?
Yes, the uses node2nix which I do not really understand. It doesn't look like other .nix files. According to this , wrapGAppsHook can be like in . But I can't find , the hook or even just the part where it is supposed to be .
the important parts of are and runCommand so you could replace the call with the usual

Related discussion:
text: { lib , node_webkit , pkgs <del> , runCommand </del> <ins> , copyDesktopItems , makeDesktopItem </ins> , stdenv , writeShellScript <ins> , wrapGAppsHook </ins> }: let