jiebi/CodeConvo huggingface dataset:
Change:
{ lib, buildPythonPackage, <del> fetchFromGitHub, </del> <ins> fetchPypi, </ins> dash, setuptools, pythonOlder,

Discussion:
Importing as recommended in the docs should work. The circular import was notificed by the expression author: ,L32 Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
owner = "roddhjav"; repo = "pass-audit"; rev = "v${version}"; <del> sha256 = "sha256-xigP8LxRXITLF3X21zhWx6ooFNSTKGv46yFSt1dd4vs="; </del> <ins> hash = "sha256-xigP8LxRXITLF3X21zhWx6ooFNSTKGv46yFSt1dd4vs="; </ins> }; patches = [

Discussion:
Steps to reproduce the behavior: X <!-- 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]:
Change:
ffmpeg gdk-pixbuf glib <del> gobject-introspection </del> gtk3 librsvg libvpx

Discussion:
Any (client-side) command results in an error (failing to use via ). , these are likely related: They seem to all have been fallout from this PR: Please run and paste the result.
As a workaround, doing this in seems to work: Trying this specifically was inspired by: I am very likely to forget about this btw (just wanted to get this working somehow so I can GC the old generation), so feel free to open a PR if you run into this (should just require adding to 's ).
Change:
substituteInPlace setup.py  --replace "pathlib==1.0.1" "pathlib>=1.0.0,<2.0.0"  --replace "plac>=0.9.6,<1.0.0" "plac>=0.9.6"  <del> --replace "msgpack-numpy<0.4.4" "msgpack-numpy" </del> <ins> --replace "msgpack-numpy<0.4.4" "msgpack-numpy"  --replace "wheel>=0.32.0,<0.33.0" "wheel"  --replace "wrapt>=1.10.0,<1.11.0" "wrapt"  --replace "msgpack>=0.5.6,<0.6.0" "msgpack" </ins> ''; # Cannot find cython modules.

Discussion:
The packages fails to build on a recent with the following error: - system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
Change:
"-Dresolvconf=${openresolv}/bin/resolvconf" # DHCP clients <del> "-Ddhclient=${dhcp}/bin/dhclient" # Upstream prefers dhclient, so don't add dhcpcd to the closure "-Ddhcpcd=no" </del> <ins> # ISC DHCP client has reached it's end of life, so stop using it "-Ddhclient=no" "-Ddhcpcd=${dhcpcd}/bin/dhcpcd" </ins> "-Ddhcpcanon=no" # Miscellaneous

Discussion:
Was announced multiple times, now it is EOL with release 4.2.3 We should remove it before branching 22.05.
Change:
<del> { lib, stdenv, fetchFromGitHub, curl, openssl, zlib }: </del> <ins> { lib, stdenv, fetchFromGitHub, pkg-config, curl, openssl, zlib }: </ins> stdenv.mkDerivation rec { pname = "hcxtools"; <del> version = "6.0.3"; </del> <ins> version = "6.1.5"; </ins> src = fetchFromGitHub { owner = "ZerBea"; repo = pname; rev = version; <del> sha256 = "0s9l5mvzcv6hnj7h28piabnm66b09hk2l57vb85ny35w99hzpkc0"; </del> <ins> sha256 = "1xvr89r6287788bx5qbw9sr8jvmajps0rpc7fvh9bfzb6zw2rq6w"; </ins> }; <ins> nativeBuildInputs = [ pkg-config ]; </ins> buildInputs = [ curl openssl zlib ]; makeFlags = [

Discussion:
Result of run on x8664-linux <details<summary2 packages built:</summary<ul<lihcxtools</li<liwifite2</li</ul</detailsOriginally posted by in
make error (latest source release) hcxpcapngtool.c:(.text+0x82ae): undefined reference to `PKCS5PBKDF2HMAC_SHA1' collect2: error: ld returned 1 exit status make: * No rule to make target 'hcxpcapngtool', needed by 'build'. Stop.
Can not build hcxtools all required packages installed libpcap-dev libcurl4-openssl-dev libssl-dev Kali 5.9
Reopen (closed by mistake)
Change:
{ lib , stdenv <del> , fetchurl </del> <ins> , fetchFromGitLab </ins> , makeWrapper , pkg-config , nasm , makeDesktopItem <ins> , copyDesktopItems </ins> , alsa-lib , flac , gtk2 , libvorbis , libvpx <del> , libGLU </del> , libGL , SDL2 , SDL2_mixer

Discussion:
Package name: Latest released version: <!-- Search your package here: --- Current version on the unstable channel: 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 <!-- 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 realized through the , which refers to the source code of the following repo: "See for more details.", that eduke32 seems to support Shadow Warrior, which the confirms with: "Shadow Warrior (Note: Supported by VoidSW ONLY, not EDuke32 itself!)". Furthermore it seems that this "EDuke32's VoidSW launcher" (to run Shadow Warrior) could be build with a eduke32 build flag, as Gentoo did it, for example: -flag name="voidsw" Enable support for Shadow Warrior (Classic) through VoidSW In addition to the apparently uninteresting project: , this could be another option to start Shadow Warrior emulated under NixOS, or is there anything against it? What do you think?
Updated in to version
Change:
<ins> /* # Updating To update the list of packages from nongnu devel (ELPA), 1. Run `./update-nongnu-devel`. 2. Check for evaluation errors: # "../../../../../" points to the default.nix from root of Nixpkgs tree env NIXPKGS_ALLOW_BROKEN=1 nix-instantiate ../../../../../ -A emacs.pkgs.nongnuDevelPackages 3. Run `git commit -m "nongnu-devel-packages $(date -Idate)" -- nongnu-devel-generated.nix` */ { lib, buildPackages }: self: let generateNongnu = lib.makeOverridable ( { generated ? ./nongnu-devel-generated.nix, }: let imported = import generated { callPackage = pkgs: args: self.callPackage pkgs ( args // { # Use custom elpa url fetcher with fallback/uncompress fetchurl = buildPackages.callPackage ./fetchelpa.nix { }; } ); }; super = imported; overrides = { }; in super // overrides ); in generateNongnu { } </ins>

Discussion:
Project description NonGNU-devel ELPA Packages; i.e., development versions of the already packaged Metadata homepage URL: source URL: license: probably (guessed by looking at ) platforms: probably all (guessed by looking at ) Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
This feels like something that should only live in the emacs-overlay, not in Nixpkgs.
Consider that the other two supported ELPAs have both their stable/unstable versions supported in nixpkgs: elpa/elpaDevel; melpaStable/melpa (see to quickly fact-check). What's the reason for this feeling; why should nongnu be an exception?
I think the same about the others.
Change:
# included after the ifdef... patches = lib.optional (lib.versionOlder php.version "7.4") [ (pkgs.writeText "zend_file_cache_config.patch" '' <del> --- a/zend_file_cache.c +++ b/zend_file_cache.c </del> <ins> --- a/ext/opcache/zend_file_cache.c +++ b/ext/opcache/zend_file_cache.c </ins> @@ -27,9 +27,9 @@ #include "ext/standard/md5.h" #endif

Discussion:
After PR phpExtensions.mysqlnd not supported compression. Checked with
cc
Not supported gzip compression and OpenSSL signatures on phar package before update
Change:
stanchion = throw "Stanchion was part of riak-cs which is not maintained anymore"; # added 2020-10-14 steam-run-native = steam-run; # added 2022-02-21 stumpwm-git = throw "stumpwm-git has been broken for a long time and lispPackages.stumpwm follows Quicklisp that is close to git version"; # Added 2021-05-09 <ins> subversion_1_10 = throw "subversion_1_10 has been removed as it has reached its end of life"; # Added 2022-04-26 </ins> subversion19 = throw "subversion19 has been removed as it has reached its end of life"; # Added 2021-03-31 sudolikeaboss = throw "sudolikeaboss is no longer maintained by upstream"; # Added 2022-04-16 sundials_3 = throw "sundials_3 was removed in 2020-02. outdated and no longer needed";

Discussion:
While checking why we have two subversion releases I noticed that both releases are LTS versions. They receive 4 years of support and 1.10 was first released on 2018-04-13, so it's probably wise to remove it before the 22.05 release. Originally posted by in
I don't see anything that depends on in nixpkgs (anymore), so IMO we can just remove it now, instead of waiting for some kind of EOL announcement.
Change:
"--enable-bittorrent" "--enable-nntp" "--enable-256-colors" <ins> "--enable-true-color" "--with-lzma" </ins> "--with-libev" <ins> "--with-terminfo" </ins> ] ++ stdenv.lib.optional enableGuile        "--with-guile" ++ stdenv.lib.optional enablePython       "--with-python" ++ stdenv.lib.optional enablePerl         "--with-perl" <del> ++ stdenv.lib.optional enableSpidermonkey "--with-spidermonkey=${spidermonkey_38}" </del> ; <del> preConfigure = '' patchShebangs ./autogen.sh ./autogen.sh ''; </del> meta = with stdenv.lib; { description = "Full-featured text-mode web browser (package based on the fork felinks)"; homepage = "https://github.com/rkd77/felinks"; license = licenses.gpl2; platforms = with platforms; linux ++ darwin; <del> maintainers = with maintainers; [ iblech ]; </del> <ins> maintainers = with maintainers; [ iblech gebner ]; </ins> }; }

Discussion:
Describe the bug elinks, although built with spidermonkey / JavaScript support enabled, fails to detect spidermonkey during its configure phase. This is not fatal to the configure phase, so the build continues without issue, resulting in elinks without javascript support To Reproduce Steps to reproduce the behavior: This shows during build that Spidermonkey is enable via : But later ... shows no JavaScript support; same from within elinks Expected behavior elinks should have JavaScript support enabled Metadata Output of (please note that nixpkgs below is not relevant; 19.09 release used): system: host os: multi-user?: sandbox: version: channels(musteresel): channels(root): nixpkgs: Maintainer information:
is not the cause of this; building with nixpkgs set to the parent commit yields the same result. This seems to be broken since a long time ...
of that elinks version searches for libraries , or . The libraries of spidermonkey are named , or for later versions (38, 52, 60 are on my system). Patching to use the correct lib and using Spidermonkey 1.8.5 again ... ... fails then during built; with errors like ... ... and lots of warnings. Other Spidermonkey versions (38, 52, 60) seem to have a different API; there the configure checks fail to compile their test programs.
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 .
Change:
, # Shell code executed after the VM has finished. postVM ? "" <ins> , # Guest memory size memSize ? 1024 </ins> , name ? "nixos-disk-image" , # Disk image format, one of qcow2, qcow2-compressed, vdi, vpc, raw.

Discussion:
Building an Amazon AMI with zfs root fails with inside the vm getting an error trying to allocate memory partway through building the new store. It isn’t surprising that a zfs-using system needs more memory when doing intensive filesystem writes. Unfortunately I don't know how to adjust the config (other than globally in a nixpkgs fork) for how much memory to give the vm. $ nix-build -A amazonImageZfs.x8664-linux … error: reading directory '/nix/store/4l99mg8j2c3bqjlc10ncdfcq5vaazxb9-nixos-22.11pre130979.gfedcba/nixos/pkgs/tools/misc/tagref': Cannot allocate memory (the specific package or failure point varies a little on each run based on random timings and resource usage) system: host os: multi-user?: sandbox: version: channels(root): channels(dan): nixpkgs:
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
{ stdenv , buildPythonPackage <del> , fetchPypi </del> <ins> , fetchFromGitHub </ins> , isPy27 <del> , pytest </del> , pytestrunner , pytestCheckHook , numpy , pillow }: <del> buildPythonPackage rec { version = "2.1.1"; </del> <ins> let </ins> pname = "pydicom"; <del> disabled = isPy27; </del> <ins> version = "2.1.2"; src = fetchFromGitHub { owner = "${pname}"; repo = "${pname}"; rev = "v${version}"; sha256 = "sha256-iExy+mUs1uqs/u9N6btlqyP6/TvoPVsuOuzs56zZAS8="; }; </ins> <del> src = fetchPypi { inherit pname version; sha256 = "72a11086f6a277c1529a552583fde73e03256a912173f15e9bc256e5b28f28f1"; </del> <ins> # Pydicom needs pydicom-data to run some tests. If these files are downloaded # before the package creation, it'll try to download during the checkPhase. test_data = fetchFromGitHub { owner = "${pname}"; repo = "${pname}-data"; rev = "bbb723879690bb77e077a6d57657930998e92bd5"; sha256 = "sha256-dCI1temvpNWiWJYVfQZKy/YJ4ad5B0e9hEKHJnEeqzk="; </ins> }; <ins> in buildPythonPackage { inherit pname version src; disabled = isPy27; </ins> propagatedBuildInputs = [ numpy pillow ]; <del> checkInputs = [ pytest pytestrunner pytestCheckHook ]; disabledTests = [ "test_invalid_bit_depth_raises" ]; # harmless failure; see https://github.com/pydicom/pydicom/issues/1119 </del> <ins> checkInputs = [ pytestrunner pytestCheckHook ]; # Setting $HOME to prevent pytest to try to create a folder inside # /homeless-shelter which is read-only. # Linking pydicom-data dicom files to $HOME/.pydicom/data preCheck = '' export HOME=$TMP/test-home mkdir -p $HOME/.pydicom/ ln -s ${test_data}/data_store/data $HOME/.pydicom/data ''; # This test try to remove a dicom inside $HOME/.pydicom/data/ and download it again. disabledTests = [ "test_fetch_data_files" ]; </ins> meta = with stdenv.lib; { homepage = "https://pydicom.github.io";

Discussion:
Pydicom is failing to build because of a fail in test. The error: Add pydicom in your system packages. Please run and paste the result.
Change:
scModels = [ pkgs.mpfr.dev ]; multibridge = [ pkgs.mpfr.dev ]; RcppCWB = with pkgs; [ pcre.dev glib.dev ]; <ins> redux = [ pkgs.hiredis ]; </ins> RmecabKo = [ pkgs.mecab ]; PoissonBinomial = [ pkgs.fftw.dev ]; rrd = [ pkgs.rrdtool ];

Discussion:
Steps to reproduce the behavior: 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. system: host os: multi-user?: sandbox: version: channels(hervyqa): channels(root): nixpkgs:
Change:
;; esac <del> # Create backing directories for unionfs-fuse. if [ "$fsType" = unionfs-fuse ]; then for i in $(IFS=:; echo ${options##*,dirs=}); do mkdir -m 0700 -p /mnt-root"${i%=*}" </del> <ins> # Create backing directories for overlayfs if [ "$fsType" = overlay ]; then for i in upper work; do dir="$( echo "$optionsPrefixed" | grep -o "${i}dir=[^,]*" )" mkdir -m 0700 -p "${dir##*=}" </ins> done fi

Discussion:
got it working with this for the AArch64 community box: Presumably the hackiness could be lowered by doing a thing like we already do for unionfs-fuse:
Change:
]; } else <del> swiftLlvmPackages.clang; </del> <ins> clangNoMarch; </ins> # Overrides that create a useful environment for swift packages, allowing # packaging with `swiftPackages.callPackage`. These are similar to

Discussion:
Since was merged into the master, swift cannot be built on aarch64. Steps to reproduce the behavior: reported in I'm not familiar with swift or clang, but I'm using the following overlay as a workaround until it's fixed. <!-- 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]:
states that this only fixed the swift build but all downstream packages are still broken. re-opening.
Actually, it seems only dark-mode-notify is broken, others seem fine. Probably because it uses Cocoa or disables sandbox. I don't know for sure.
I noticed that my personal package does not build either. Maybe it's because of swift itself or swiftpm?
The above open PR seems to run into the same issue…
Change:
<ins> { stdenv, buildPythonPackage, fetchFromGitHub , enum-compat , xorgserver, pytest, i3, python }: buildPythonPackage rec { pname = "i3ipc"; version = "1.4.0"; src = fetchFromGitHub { owner  = "acrisci"; repo   = "i3ipc-python"; rev    = "v${version}"; sha256 = "15drq16ncmjrgsri6gjzp0qm8abycm92nicm78q3k7vy7rqpvfnh"; }; propagatedBuildInputs = [ enum-compat ]; checkInputs = [ xorgserver pytest i3 ]; checkPhase = ''${python.interpreter} run-tests.py''; meta = with stdenv.lib; { description = "An improved Python library to control i3wm"; homepage    = https://github.com/acrisci/i3ipc-python; license     = licenses.bsd3; maintainers = with maintainers; [ vanzef ]; }; } </ins>

Discussion:
i3ipc python package exists in pypy but not in nixpackages. It would be great if we could use it. Link for reference: Thanks. I'm probably up for writing the nix package definition if someone can point me in the right direction,
for future reference, what mistakes did I make? It's my first week of nix (and I'm loving it).
Python packages are part of the attribute of the interpreter, so is the reference to the package. While it is now possible to use the supported solution is The other one typically works, but not always because is not always propagated and thus unavailable. Also, guarantees that you will have the Python that is "connected" to the package, and not accidentally the one that was in your . Good to hear!
Thanks! Interesting to see the differences.
Just wanted to let you know that I finally got my i3 setup working near perfectly on nixos! Loving it (Thank you all)
Change:
sed '/^void doit(void)/,/^{/ s/{/{ exit(77);/' -i tests/{trust-store,psk-file}.c sed 's:/usr/lib64/pkcs11/ /usr/lib/pkcs11/ /usr/lib/x86_64-linux-gnu/pkcs11/:`pkg-config --variable=p11_module_path p11-kit-1`:' -i tests/p11-kit-trust.sh '' + lib.optionalString stdenv.hostPlatform.isMusl '' # See https://gitlab.com/gnutls/gnutls/-/issues/945 <del> sed '2iecho "certtool tests skipped in musl build"nexit 0' -i tests/cert-tests/certtool </del> <ins> sed '2iecho "certtool tests skipped in musl build"nexit 0' -i tests/cert-tests/certtool.sh </ins> ''; preConfigure = "patchShebangs .";

Discussion:
Describe the bug does not build because of: To Reproduce Steps to reproduce the behavior: Expected behavior The library is built Screenshots If applicable, add screenshots to help explain your problem. Additional context Add any other context about the problem here. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Metadata system: host os: multi-user?: sandbox: version: channels(kpg): channels(root): nixpkgs: Maintainer information:
Change:
}; }; <ins> GooCanvas2CairoTypes = buildPerlPackage rec { pname = "GooCanvas2-CairoTypes"; version = "0.001"; src = fetchurl { url = "mirror://cpan/authors/id/A/AS/ASOKOLOV/GooCanvas2-CairoTypes-${version}.tar.gz"; sha256 = "sha256-uoBnNuvMnePYFBp2Omgr3quxy4cCveKZrf1XSs6HUFI="; }; propagatedBuildInputs = [ pkgs.goocanvas2 Gtk3 ]; meta = { description = "Bridge between GooCanvas2 and Cairo types"; license = with lib.licenses; [ artistic1 gpl1Plus ]; }; }; </ins> GoogleProtocolBuffers = buildPerlPackage { pname = "Google-ProtocolBuffers"; version = "0.12";

Discussion:
Shutter fails to build, looks like an issue with Imagemagick. Steps to reproduce the behavior: Expect that it should build, it was working on my last generation. If applicable, add screenshots to help explain your problem. Add any other context about the problem here. Maintainer information: Probably related to
'shutter' is outdated in nixpkgs, perhaps we should start with a package update.
That would be nice but I think the problem is due to changes in perl packages
i tested and fixes this
I'll update shutter but will make the pr after the above pr has been merged
Change:
preConfigure = '' # use empty inc file instead of a from linux kernel generated one touch lib/lirc/input_map.inc <ins> export PKGCONFIG="$PKG_CONFIG" </ins> ''; strictDeps = true;

Discussion:
Steps to reproduce the behavior: pkgsCross.aarch64- Cross-compiling as a dependency of Kodi. Possibly related to ~Please run and paste the result.~ Nixpkgs revision: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
<ins> { buildGoModule , fetchFromGitHub , go-rice , lib }: buildGoModule rec { pname = "linx-server"; version = "unstable-2021-12-24"; src = fetchFromGitHub { owner = "zizzydizzymc"; repo = pname; rev = "3f503442f10fca68a3212975b23cf74d92c9988c"; hash = "sha256-tTHw/rIb2Gs5i5vZKsSgbUePIY7Np6HofBXu4TTjKbw="; }; # upstream tests are broken, see zizzydizzymc/linx-server#34 patches = [ ./test.patch ]; vendorHash = "sha256-/N3AXrPyENp3li4X86LNXsfBYbjJulk+0EAyogPNIpc="; nativeBuildInputs = [ go-rice ]; preBuild = "rice embed-go"; meta = with lib; { description = "Self-hosted file/code/media sharing website."; homepage = "https://put.icu"; license = licenses.gpl3Only; maintainers = with maintainers; [ urandom ]; }; } </ins>

Discussion:
Project description Self-hosted file/code/media sharing website. Metadata homepage URL: source URL: license: GPLv3 platforms: Linux
to confirm you are keen on getting the fork, not original tool packaged:
Yes.
Change:
is_nixenv = "False"; is_virtualenv = "False"; }; <del> } // lib.optionalAttrs (!python.isPyPy) { </del> <ins> } // lib.optionalAttrs (!python.isPyPy && !stdenv.isDarwin) { </ins> # Use virtualenv with symlinks from a Nix env. <ins> # Fails on darwin with #   virtualenv: error: argument dest: the destination . is not write-able at /nix/store </ins> nixenv-virtualenv-links = rec { env = runCommand "${python.name}-virtualenv-links" {} '' ${pythonVirtualEnv.interpreter} -m virtualenv --system-site-packages --symlinks --no-seed $out

Discussion:
Package name: python3, python312 Latest released version: 3.11.9, 3.12.3 <!-- Search your package here: --- Current version on the unstable channel: 3.11.8, 3.12.2 Current version on the stable/release channel: 3.11.8, 3.12.2 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
You could have found the PR for 3.11.9.
I assume python3 and python3.12 updated at same time because updated at same time. Thank you for your message, I'll check two time when I create issue.
fixed issue
Change:
''; installCheckPhase = '' <del> if [[ "$("$out/bin/vagrant" --version)" == "Vagrant ${version}" ]]; then echo 'Vagrant smoke check passed' else echo 'Vagrant smoke check failed' return 1 fi </del> <ins> HOME="$(mktemp -d)" $out/bin/vagrant init --output - > /dev/null </ins> ''; # `patchShebangsAuto` patches this one script which is intended to run

Discussion:
Describe the bug Vagrant no longer works; every operation fails with an error . I bisected this regression to commit “ruby: rubygems 3.0.6 -3.1.2” (). To Reproduce Expected behavior Metadata Maintainer information: cc
I note that the “smoke test” in was not sufficient to catch this problem, although would have. Perhaps would be even better?
Just took a look at this as well (please note that I'm not a ruby developer, so I may be missing something). 3.1.x seems to require bundler now[1] and vendors bundler 2.1.2[2] in version 3.1.2, however ruby 2.6 vendors bundler 1.17, so there's probably some kind of mismatch when using rubygems 3.1.2. Not sure, but would it make sense to add different rubygems versions for different ruby versions? [1] [2]