David Rodríguez 88e46cf6b8 [rubygems/rubygems] Remove all syck traces from rubygems ... After reading [this blog post](https://blog.rubygems.org/2011/08/31/shaving-the-yaml-yak.html), published almost 10 years ago already, my understanding is that this problem could come up in two ways: * Rubygems.org serving corrupted gemspecs". As far as I understand this was fixed in rubygems.org a lot time ago, since https://github.com/rubygems/rubygems.org/pull/331. * Clients having a ten years old gemspec cache with some of these bad gemspecs. In this case, there's no easy solution but I think ten years is enough and rebuilding the cache should do the trick. So, I think it's time we remove this. afcb15d556		2021-07-27 09:25:56 +09:00
..
gem-private_key.pem
gem-public_cert.pem
null-required-ruby-version.gemspec.rz
null-required-rubygems-version.gemspec.rz
null-type.gemspec.rz	[rubygems/rubygems] Remove all syck traces from rubygems	2021-07-27 09:25:56 +09:00