Vít Ondruch

Just for explanation, on Fedora, we typically execute the test suite without Bundler mainly to reduce the dependencies (e.g. RuboCop, which has huge dependency chain and is not important for...

@dwaite I am just curious, wouldn't it be possible to takeover the original project and keep the name?

Just to close the loop, I believe this was fixed by #1763

I also have reservation against this PR. Not because I think that RubyGems should not be faster, but because the default gems would deserve rework such as #2909. If that...

> but don't understand why those big projects should block quick wins like this, unless there are any real downsides of doing this, which I have not yet heard of....

I have pushed rebase. However, there are some test failures. Mainly these two: ~~~ .F =============================================================================== Failure: test_install_default_bundler_gem(TestGemCommandsSetupCommand): was expected to not exist /home/runner/work/rubygems/rubygems/test/rubygems/test_gem_commands_setup_command.rb:210:in `test_install_default_bundler_gem' 207: assert_path_exist File.join(Gem.dir, "specifications", "bundler-audit-1.0.0.gemspec")...

And not sure what are the `test_realworld_*` test failures :thinking: I hoped that is just my environment. I'll need to investigate

> And not sure what are the `test_realworld_*` test failures thinking I hoped that is just my environment. I'll need to investigate I have addressed these two, but I cannot...

Please note this has been already documented by #3115

This is my naive implementation: ~~~bash $ cat rename-patch #!/usr/bin/bash mv $1 $(sed -ne '/^Subject: /{ s/^Subject: *\[PATCH[^]]*\] *//; s/[^a-zA-Z0-9]/-/g; s/--*/-/g; s/$/\.patch/; p; q; }' $1) ~~~