jiebi/CodeConvo huggingface dataset:
Change:
<ins> { stdenv , lib , fetchFromGitHub , cpp-utilities , qtutilities , qttools , qtbase , cmake , perl }: let fork_awesome_release = fetchFromGitHub { owner = "ForkAwesome"; repo = "Fork-Awesome"; rev = "1.2.0"; sha256 = "sha256-zG6/0dWjU7/y/oDZuSEv+54Mchng64LVyV8bluskYzc="; }; in stdenv.mkDerivation rec { pname = "qtforkawesome"; version = "0.0.4"; src = fetchFromGitHub { owner = "Martchus"; repo = pname; rev = "v${version}"; sha256 = "sha256-J3F+ikz6gQqV+JsOX8EpMOWoTmI6UK5KndFALUo4oiU="; }; buildInputs = [ qtbase cpp-utilities qtutilities ]; nativeBuildInputs = [ cmake qttools perl perl.pkgs.YAML ]; cmakeFlags = [ "-DFORK_AWESOME_FONT_FILE=${fork_awesome_release}/fonts/forkawesome-webfont.woff2" "-DFORK_AWESOME_ICON_DEFINITIONS=${fork_awesome_release}/src/icons/icons.yml" ]; dontWrapQtApps = true; meta = with lib; { homepage = "https://github.com/Martchus/qtforkawesome"; description = "Library that bundles ForkAwesome for use within Qt applications"; license = licenses.gpl2Plus; maintainers = with maintainers; [ doronbehar ]; platforms   = platforms.linux; }; } </ins>

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 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: syncthingtray <!-- 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: 1.1.3 desired version: 1.1.20 <!-- 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.
There's a new dependency now needed for syncthingtray - but there's a problem in the logic upstream here: Here's my packaging attempt:
Change:
<ins> { lib, rustPlatform, fetchFromGitHub, installShellFiles }: rustPlatform.buildRustPackage rec { pname = "ab-av1"; version = "0.7.14"; src = fetchFromGitHub { owner = "alexheretic"; repo = "ab-av1"; rev = "v${version}"; hash = "sha256-cDabGXNzusVnp4exINqUitEL1HnzSgpcRtYXU5pSRhY="; }; cargoHash = "sha256-sW/673orvK+mIUqTijpNh4YGd9ZrgSveGT6F1O5OYfI="; nativeBuildInputs = [ installShellFiles ]; postInstall = '' installShellCompletion --cmd ab-av1  --bash <($out/bin/ab-av1 print-completions bash)  --fish <($out/bin/ab-av1 print-completions fish)  --zsh <($out/bin/ab-av1 print-completions zsh) ''; meta = with lib; { description = "AV1 re-encoding using ffmpeg, svt-av1 & vmaf"; homepage = "https://github.com/alexheretic/ab-av1"; changelog = "https://github.com/alexheretic/ab-av1/blob/${src.rev}/CHANGELOG.md"; license = licenses.mit; maintainers = [ maintainers.marsam ]; mainProgram = "ab-av1"; }; } </ins>

Discussion:
Project description ab-av1 is a VMAF-based reencoding frontend for ffmpeg, primarily for av1 but works well with x265 and other encoders. It is a rust project and requires ffmpeg newer than git-2022-02-24 with libsvtav1, libvmaf, libopus enabled. Metadata homepage URL: source URL: license: MIT platforms: unix, linux, darwin, windows Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
<ins> { lib, buildPythonPackage, fetchPypi, isPy27 , attrs , functools32 , importlib-metadata , mock , nose , pyperf , pyrsistent , setuptools-scm , twisted , vcversioner }: buildPythonPackage rec { pname = "jsonschema"; version = "3.2.0"; src = fetchPypi { inherit pname version; sha256 = "c8a85b28d377cc7737e46e2d9f2b4f44ee3c0e1deac6bf46ddefc7187d30797a"; }; nativeBuildInputs = [ setuptools-scm ]; propagatedBuildInputs = [ attrs importlib-metadata functools32 pyrsistent ]; checkInputs = [ nose mock pyperf twisted vcversioner ]; # zope namespace collides on py27 doCheck = !isPy27; checkPhase = '' nosetests ''; meta = with lib; { homepage = "https://github.com/Julian/jsonschema"; description = "An implementation of JSON Schema validation for Python"; license = licenses.mit; maintainers = with maintainers; [ domenkozar ]; }; } </ins>

Discussion:
Steps to reproduce the behavior: (as of ) <details<summaryBuild Log</summary<preerror: builder for '/nix/store/8r1frbwzxwncagff57r7zz86zl2nsxbm-python3.10-jsonschema-' failed with exit code 1; last 10 log lines: For full logs, run 'nix log /nix/store/8r1frbwzxwncagff57r7zz86zl2nsxbm-python3.10-jsonschema-'. error: 1 dependencies of derivation '/nix/store/2413pkb4n4z1bj0rywpcfbi8s1yisvkg-python3.10-bravado-core-' failed to build error: 1 dependencies of derivation '/nix/store/x9h491ipp10gpp771jzfr3qyn3y6pbf9-powerdns-admin-' failed to build </pre</detailsLooks like json schema got updated to 4.13 which requires adding a patch. When , we're not patching (please excuse the pun), so it tries to apply to new patch against 3.2.0 which, of course, fails. Seems like we probably just need to override the to remove the offending patch? <!-- 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.
, and are also broken in similar fashion.
I'll take a look later today.
I opened .
Change:
zlib ]; <ins> buildFeatures = lib.optionals withClipboard [ "clipboard" ]; </ins> RUSTONIG_SYSTEM_LIBONIG = true; postPatch = ''

Discussion:
When running with a shortcut, broot shows the errror message . Can you please enable it or make it optional? add to your broot config (HJSON format). this on a file within broot. <!-- 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.
Could you please look into this (i just saw, that you did the recent updates for broot)?
Thank you!
Change:
<ins> { cacert , cmake , fetchFromGitHub , git , lib , lld , ninja , nix-update-script , perl , python3 , stdenv }: let version = "0.15.5"; src = fetchFromGitHub { owner = "exaloop"; repo = "codon"; rev = "v${version}"; sha256 = "sha256-/IUGX5iSRvZzwyRdkGe0IVHp44D+GXZtbkdtswekwSU="; }; depsDir = "deps"; codon-llvm = stdenv.mkDerivation { pname = "codon-llvm"; version = "unstable-2022-09-23"; src = fetchFromGitHub { owner = "exaloop"; repo = "llvm-project"; rev = "55b0b8fa1c9f9082b535628fc9fa6313280c0b9a"; sha256 = "sha256-03SPQgNdrpR6/JZ5aR/ntoh/FnZvCjT/6bTAcZaFafw="; }; nativeBuildInputs = [ cmake git lld ninja python3 ]; cmakeFlags = [ "-DCMAKE_CXX_COMPILER=clang++" "-DCMAKE_C_COMPILER=clang" "-DLLVM_ENABLE_RTTI=ON" "-DLLVM_ENABLE_TERMINFO=OFF" "-DLLVM_ENABLE_ZLIB=OFF" "-DLLVM_INCLUDE_TESTS=OFF" "-DLLVM_TARGETS_TO_BUILD=all" "-DLLVM_USE_LINKER=lld" "-S ../llvm" ]; }; codon-deps = stdenv.mkDerivation { name = "codon-deps-${version}.tar.gz"; inherit src; nativeBuildInputs = [ cacert cmake git perl python3 ]; dontBuild = true; cmakeFlags = [ "-DCPM_DOWNLOAD_ALL=ON" "-DCPM_SOURCE_CACHE=${depsDir}" "-DLLVM_DIR=${codon-llvm}/lib/cmake/llvm" ]; installPhase = '' # Prune the `.git` directories find ${depsDir} -name .git -type d -prune -exec rm -rf {} ;; # Build a reproducible tar, per instructions at https://reproducible-builds.org/docs/archives/ tar --owner=0 --group=0 --numeric-owner --format=gnu  --sort=name --mtime="@$SOURCE_DATE_EPOCH"  -czf $out  ${depsDir}  cmake  _deps/googletest-subbuild/googletest-populate-prefix/src/*.zip ''; outputHash = "sha256-a1zGSpbMjfQBrcgW/aiIdKX8+uI3p/S9pgZjHe2HtWs="; outputHashAlgo = "sha256"; }; in stdenv.mkDerivation { pname = "codon"; inherit src version; patches = [ # Without the hash, CMake will try to replace the `.zip` file ./Add-a-hash-to-the-googletest-binary.patch ]; nativeBuildInputs = [ cmake git lld ninja perl python3 ]; postUnpack = '' mkdir -p $sourceRoot/build tar -xf ${codon-deps} -C $sourceRoot/build ''; cmakeFlags = [ "-DCMAKE_BUILD_TYPE=Release" "-DCMAKE_CXX_COMPILER=clang++" "-DCMAKE_C_COMPILER=clang" "-DCPM_SOURCE_CACHE=${depsDir}" "-DLLVM_DIR=${codon-llvm}/lib/cmake/llvm" "-DLLVM_USE_LINKER=lld" ]; passthru.updateScript = nix-update-script { }; meta = { description = "A high-performance, zero-overhead, extensible Python compiler using LLVM"; homepage = "https://docs.exaloop.io/codon"; maintainers = [ lib.maintainers.paveloom ]; license = lib.licenses.bsl11; platforms = lib.platforms.all; }; } </ins>

Discussion:
Project description Codon is a high-performance Python compiler that compiles Python code to native machine code without any runtime overhead. Typical speedups over Python are on the order of 10-100x or more, on a single thread. Codon's performance is typically on par with (and sometimes better than) that of C/C++. Unlike Python, Codon supports native multithreading, which can lead to speedups many times higher still. Codon grew out of the . Metadata homepage URL: source URL: license: Business Source License 1.1 platforms: unix, linux, darwin
I didn't compile it properly, but if you want to run the official binaries on NixOS, this does the job:
Change:
hash = "sha256-QdhJp7oUqOY8Z36haIrHgP4hVGaFXlOxNVg1ams7uhg="; }; <ins> postInstall = '' # Helper files are not handled by setup.py mkdir -p $out/${python3.sitePackages}/src/txt install -vD src/txt/* $out/${python3.sitePackages}/src/txt/ ''; </ins> # Project has no tests doCheck = false; meta = with lib; { description = "Automated Command Injection Exploitation Tool"; homepage = "https://github.com/commixproject/commix"; <ins> changelog = "https://github.com/commixproject/commix/releases/tag/v${version}"; </ins> license = with licenses; [ gpl3Plus ]; maintainers = with maintainers; [ fab ]; };

Discussion:
package provides txt files for some reason in it's folder. When running commix, these files are missing and cause critical error. Steps to reproduce the behaviour: package commix on some target it's a valid target, it's should pass "Testing the connection" but it would immediately fail after that stating that txt files are not found. To be able to run properly. !
should include those missing files.
Great, thank you for fixing this quickly.
Change:
<del> { stdenv, fetchurl, utillinux, libcap }: </del> <ins> { stdenv, fetchurl, fetchpatch, getopt, libcap }: </ins> stdenv.mkDerivation rec { version = "1.20.2";

Discussion:
does not appear to be supported on ; this is possible via , and works with no issue, so it does not appear to be a technical limitation. I am not familiar enough with Nix to port over the homebrew packaging, but was planning on taking a stab if this issue does not get traction. or and System: Nix version: Nixpkgs version:
Change:
meta = with lib; { description = "Realtek rtl88x2bu driver"; homepage = "https://github.com/cilynx/rtl88x2bu"; <del> license = licenses.gpl2; </del> <ins> license = licenses.gpl2Only; </ins> platforms = platforms.linux; maintainers = [ maintainers.ralith ]; };

Discussion:
With this in : I get compilation errors similar to I was able to get things compiling (and WiFi working) by bumping the version and applying
Change:
<del> {stdenv, fetchurl, which}: </del> <ins> {stdenv, fetchurl, fetchpatch, which}: </ins> let s = # Generated upstream information rec {

Discussion:
, CVSSv3=9.8 (nixos-20.03) CVSSv3=7.8 (nixos-20.03) Scanned versions: nixos-20.03: . Cc
Resolved via .
Change:
<del> { stdenv, fetchurl, lib, makeWrapper, gvfs, atomEnv}: </del> <ins> { stdenv, pkgs, fetchurl, lib, makeWrapper, gvfs, atomEnv}: </ins> stdenv.mkDerivation rec { name = "atom-${version}";

Discussion:
Atom editor ships with Git and GitHub integration bundled since version 1.18.0 (). On NixOS it does not work. The errors in the developer's console: Seems like GitHub integration package is shipped with it's own binary and indeed trying to execute it from a shell results in error: I suppose the binary needs to be patched with and I would love to contribute a PR, but frankly I'm a JavaScript monkey and can't figure out where to start, so I'll do the next best thing and file an issue. Install atom editor: Initialize a Git repository: Make some changes and start Atom editor If it's not already opened, open Git panel with Note that tree view shows changes correctly (green file), but the Git panel is empty Open Dev Tools and see red error messages. System: 17.09pre113107. (Hummingbird) Nix version: nix-env (Nix) 1.11.13 Nixpkgs version: 17.09pre113107. Sandboxing enabled: build-use-sandbox = false
Above pull request resolves the issue. I'm not the best at using atom, but I saw a green line next to my changes made, and no errors output to stdout when I opened the git panel.
Maybe replace the binary with a symbolic link to our own git?
How can I test it locally? I suppose I need to clone this report, checkout your PR and use somehow, but how do I point it to use the expression from the PR? I'm a total noob and a monkey when it comes to Nix and NixOS
I ran it using
That works as well and is a cleaner way to handle it in my opinion. I opened a new PR because my last PR I forgot to branch before pushing and it was PR'd to my master branch.
Hi again and thanks for all the help! I'm a little bit embarrassed to ask, but after two days of trying I still can't figure how to install this patched version of Atom using . I have a clone of at . Current contains the patch. If I start as explained by it works - I have an editor with working Git integration: but if I try to install it in my standard env it apparently installs the un-patched version: I have also tried variant with .

Then it compiles and installs version 1.18 (I don't understand where is it coming from). How can I install the version from my cloned repository and - perhaps more importantly - troubleshoot this kind of issues? Is there a way to print a path to expression used by ? Or the expression itself?
With you can use the option to point to a Nix expression, in this case your Nixpkgs repository. The option is not used by because does not use . Instead, it checks by default . It is confusing...
It worked! Thank you For the record and a benefit of posterity, this is the whole command that installs a package from local clone:
Change:
let cfg = config.services.minio; <ins> legacyCredentials = cfg: pkgs.writeText "minio-legacy-credentials" '' MINIO_ROOT_USER=${cfg.accessKey} MINIO_ROOT_PASSWORD=${cfg.secretKey} ''; </ins> in { meta.maintainers = [ maintainers.bachp ];

Discussion:
Describe the bug The minio service set environment variables - which are . This is the release currently used hence the breakage. Tested on To Reproduce Expected behavior It should be possible to login with the provided key.
thanks for the report! In future please tag maintainers so they actually see the issue, no one watches all nixpkgs issues :sweat_smile:
While the variables are deprecated, they are by minio. So I'm not sure this is really the cause of the breakage. However I will update the module to make use of the new variables and maybe even rename (or alias) the current options to make it consistent.
Yeah minio (on unstable) seems to be working just fine for me, but updating the variables seems to be the proper thing to do.
I implemented a the change in
Change:
<del> { lib, stdenv, fetchFromGitHub, cmake, pkg-config, qttools, wrapQtAppsHook , alsa-lib, dssi, fluidsynth, ladspaH, lash, libinstpatch, libjack2, liblo , libsamplerate, libsndfile, lilv, lrdf, lv2, qtsvg, rtaudio, rubberband, sord, serd </del> <ins> { lib , stdenv , fetchFromGitHub , cmake , pkg-config , qttools , wrapQtAppsHook , alsa-lib , dssi , fluidsynth , ladspaH , lash , libinstpatch , libjack2 , liblo , libsamplerate , libsndfile , lilv , lrdf , lv2 , qtsvg , rtaudio , rubberband , sord , serd </ins> }: <del> stdenv.mkDerivation rec { </del> <ins> stdenv.mkDerivation (finalAttrs: { </ins> pname = "muse-sequencer"; <del> version = "3.1.1"; </del> <ins> version = "4.1.0"; </ins> src = fetchFromGitHub { owner = "muse-sequencer"; repo = "muse"; <del> rev = "muse_${builtins.replaceStrings ["."] ["_"] version}"; sha256 = "1rasp2v1ds2aw296lbf27rzw0l9fjl0cvbvw85d5ycvh6wkm301p"; </del> <ins> rev = finalAttrs.version; hash = "sha256-JPvoximDL4oKO8reXW7alMegwUyUTSAcdq3ueXeUMMY="; </ins> }; <del> sourceRoot = "${src.name}/muse3"; patches = [ ./fix-parallel-building.patch ]; </del> <ins> sourceRoot = "${finalAttrs.src.name}/src"; </ins> nativeBuildInputs = [ cmake pkg-config qttools wrapQtAppsHook ]; buildInputs = [ <del> alsa-lib dssi fluidsynth ladspaH lash libinstpatch libjack2 liblo libsamplerate libsndfile lilv lrdf lv2 qtsvg rtaudio rubberband sord </del> <ins> alsa-lib dssi fluidsynth ladspaH lash libinstpatch libjack2 liblo libsamplerate libsndfile lilv lrdf lv2 qtsvg rtaudio rubberband sord </ins> ]; env.NIX_CFLAGS_COMPILE = toString [ "-I${lib.getDev serd}/include/serd-0" ]; <del> meta = with lib; { </del> <ins> meta = { </ins> homepage = "https://muse-sequencer.github.io/"; description = "MIDI/Audio sequencer with recording and editing capabilities"; longDescription = ''

Discussion:
Package name: muse-sequencer Latest released version: 4.1.0 Current version on the unstable channel: 3.1.1 Current version on the stable/release channel: 3.1.1 Notify maintainers No idea who the maintainer is:
Change:
<ins> { stdenv , fetchFromGitHub , cmake , lib }: stdenv.mkDerivation (finalAttrs: { pname = "louvain-community"; version = "unstable-2021-03-18"; src = fetchFromGitHub { owner = "meelgroup"; repo = "louvain-community"; rev = "8cc5382d4844af127b1c1257373740d7e6b76f1e"; hash = "sha256-0i3wrDdOyleOPv5iVO1YzPfTPnIdljLabCvl3SYEQOs="; }; nativeBuildInputs = [ cmake ]; meta = with lib; { description = "Louvain Community Detection Library"; homepage = "https://github.com/meelgroup/louvain-community"; license = licenses.lgpl3Only; maintainers = with maintainers; [ t4ccer ]; platforms = platforms.unix; }; }) </ins>

Discussion:
Project description is an approximate model counter for CNF formulas. Metadata homepage URL: source URL: license: mit platforms: linux Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
, vulkan-loader , libappindicator , libnotify <ins> , miniupnpc </ins> , config , cudaSupport ? config.cudaSupport <del> , cudaPackages ? {} </del> <ins> , cudaPackages ? { } </ins> }: <del> stdenv.mkDerivation rec { </del> <ins> let stdenv' = if cudaSupport then cudaPackages.backendStdenv else stdenv; in stdenv'.mkDerivation rec { </ins> pname = "sunshine"; <del> version = "0.21.0"; </del> <ins> version = "0.22.0"; </ins> src = fetchFromGitHub { owner = "LizardByte"; repo = "Sunshine"; rev = "v${version}"; <del> sha256 = "sha256-uvQAJkoKazFLz5iTpYSAGYJQZ2EprQ+p9+tryqorFHM="; </del> <ins> sha256 = "sha256-O9U4zP1o6yWtzk+2DW7ueimvsTuajLY8IETlvCT4jTE="; </ins> fetchSubmodules = true; }; <del> # fetch node_modules needed for webui </del> <ins> patches = [ # remove npm install as it needs internet access -- handled separately below ./dont-build-webui.patch # revert https://github.com/LizardByte/Sunshine/pull/2046 - let cmake install handle udev and systemd files (fetchpatch { url = "https://github.com/LizardByte/Sunshine/commit/0d4dfcd708c0027b7d8827a03163858800fa79fa.patch"; hash = "sha256-77NtfX0zB7ty92AyFOz9wJoa1jHshlNbPQ7NOpqUuYo="; revert = true; }) ]; # build webui </ins> ui = buildNpmPackage { inherit src version; pname = "sunshine-ui"; <del> npmDepsHash = "sha256-+T1XAf4SThoJLOFpnVxDa2qiKFLIKQPGewjA83GQovM="; dontNpmBuild = true; </del> <ins> npmDepsHash = "sha256-jAZUu2CfcqhC2xMiZYpY7KPCRVFQgT/kgUvSI+5Cpkc="; </ins> # use generated package-lock.json as upstream does not provide one postPatch = ''

Discussion:
Package name: sunshine Latest released version: 0.22.0 <!-- Search your package here: --- Current version on the unstable channel: 0.21.0 Current version on the stable/release channel: 0.21.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:
{ config, pkgs, lib, ... }: with lib; let cfg = config.services.undervolt; <del> in { </del> <ins> cliArgs = lib.cli.toGNUCommandLineShell {} { inherit (cfg) verbose temp ; # `core` and `cache` are both intentionally set to `cfg.coreOffset` as according to the undervolt docs: # #     Core or Cache offsets have no effect. It is not possible to set different offsets for #     CPU Core and Cache. The CPU will take the smaller of the two offsets, and apply that to #     both CPU and Cache. A warning message will be displayed if you attempt to set different offsets. core = cfg.coreOffset; cache = cfg.coreOffset; gpu = cfg.gpuOffset; uncore = cfg.uncoreOffset; analogio = cfg.analogioOffset; temp-bat = cfg.tempBat; temp-ac = cfg.tempAc; }; in { </ins> options.services.undervolt = { <del> enable = mkOption { type = types.bool; default = false; description = '' Whether to undervolt intel cpus. ''; }; </del> <ins> enable = mkEnableOption "Intel CPU undervolting service (WARNING: may permanently damage your hardware!)"; </ins> verbose = mkOption { type = types.bool;

Discussion:
Describe the bug The undervolt module is potentially damaging to hardware when misconfigured. The module description needs an appropriate warning informing users that they are taking a risk when enabling it (even though I think it's fairly obvious that's the case). Maintainer information: cc
It would also be nice if the options' description specified what units are expected for the "amount of voltage". And I don't know how feasible it is but if the options accept a floating point number as per their documenation they should perhaps be of a numeric type as well.
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 .
Still relevant.
Change:
Each attribute in this set specifies an option in the <literal>[Timer]</literal> section of the unit.  See <citerefentry><refentrytitle>systemd.timer</refentrytitle> <del> <manvolnum>7</manvolnum></citerefentry> and </del> <ins> <manvolnum>5</manvolnum></citerefentry> and </ins> <citerefentry><refentrytitle>systemd.time</refentrytitle> <manvolnum>7</manvolnum></citerefentry> for details. '';

Discussion:
Should be man volume 5 for and 7 for None
is the file if you're keen on doing a PR.
Change:
antlr4_12.runtime.cpp python3 mysql <del> libxml2 </del> <ins> (libxml2.override { enableHttp = true; }) </ins> libmysqlconnectorcpp vsqlite gdal

Discussion:
Steps to reproduce the behavior: mysql-workbench-8.0.38 Might be related to or Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]: