Permalink
Commits on Jun 8, 2015
  1. Update History and version for release

    drbrain committed Jun 8, 2015
Commits on May 18, 2015
Commits on May 14, 2015
  1. Set version

    drbrain committed May 14, 2015
  2. Add CVE-2015-3900 to History

    drbrain committed May 14, 2015
  3. Update History.txt for 2.0.16

    evanphx committed May 14, 2015
Commits on Dec 21, 2014
  1. Prepare for release

    luislavena committed Dec 21, 2014
Commits on Nov 11, 2014
  1. Backport: Newer Root CA for rubygems.org

    Due sunsetting of certificates with SHA1 signature, rubygems.org
    is upgrading, which requires RubyGems (the software) be ugpraded
    too.
    luislavena committed Nov 11, 2014
Commits on Mar 15, 2014
  1. Merge pull request #833 from nagachika/backport_fix_for_concurrent_re…

    …quires
    
    Backport a fix for concurrent requires
    zzak committed Mar 15, 2014
Commits on Feb 20, 2014
  1. Backport 16fc8e8 to 2.0 branch.

    Restore concurrent requires
    
    When #8374 was fixed all requires were serialized, so one thread would
    be blocked waiting for gem resolution (if any) and require in another
    thread.  This is undesirable for JRuby, in particular.
    
    The monitor protecting the RubyGems internals only needs to cover gem
    activation and modifying $LOAD_PATH, not requiring files.
    
    Now the monitor is released before calling the original Kernel#require
    which allows other threads to require files without waiting for
    RubyGems.
    
    Fixes #640
    
    See also #637
    nagachika committed Feb 20, 2014
Commits on Nov 24, 2013
  1. Update History for 1.8.29

    drbrain committed Nov 24, 2013
Commits on Nov 12, 2013
  1. Set release version and date

    drbrain committed Nov 12, 2013
  2. Remove 1.8.7 and other maintainers for 2.0 branch

    1.8.7 builds have been broken forever, I run them manually now.
    
    No other maintainer needs to care about failures on this branch.
    drbrain committed Nov 12, 2013
  3. Add #706 to History

    drbrain committed Nov 5, 2013
  4. Choose test server port reliably

    Specify :Port => 0 for WEBrick::HTTPServer.new and
    obtain the port actually bound.
    akr committed with drbrain Nov 5, 2013
  5. Restore wildcard handling when installing gems

    RubyGems 1.8.x inadvertently expanded glob patterns when installing
    gems.  This allowed `gem install *.gem` to work on JRuby and Windows,
    which broke after the glob expansion was removed.
    
    This restores glob expansion allowing RubyGems to work on JRuby again.
    
    Fixes #697
    drbrain committed Oct 28, 2013
  6. Add #689 to History.txt

    drbrain committed Oct 25, 2013
  7. Add failing test for bug #698

    We do not have any lock on the specifications directory, so we should
    not assume that this is the only process modifying the contents of the
    directory.
    drbrain committed Oct 25, 2013
  8. Test Specification::remove_spec

    drbrain committed Oct 25, 2013
  9. Remove raise on specification removal

    The gemspec is removed from the filesystem prior to removing from the
    Specification list, so there is an order dependence here.
    tmacedo committed with drbrain Oct 25, 2013
Commits on Oct 25, 2013
  1. Set release version and date

    drbrain committed Oct 25, 2013
  2. Refactor resetting gems to a method

    This makes it more clear what we're doing with Specification::dirs=
    drbrain committed Oct 24, 2013
  3. Use user-provided directories in `gem server`

    Previously Gem::Server would reset the gem list for certain requests.
    This was designed to always provide the latest installed gems for
    installation.
    
    When the --dir option was used, resetting the gem list would also revert
    to the standard gem directories.  This meant the user-provided
    directories would always be ignored.
    
    Now the reset includes the gem directories the user provided to
    eliminate this problem.
    
    Fixes #696
    drbrain committed Oct 24, 2013
  4. Install gems when $HOME does not exist

    During gem installation RubyGems caches files in the home directory.  If
    the home directory did not exist or was unwritable RubyGems would raise
    an exception even though it had the ability to avoid updating the cache.
    
    Now, when checking to see if the cache should be updated, RubyGems
    no longer raises an exception.
    
    Fixes #689
    drbrain committed Oct 18, 2013
Commits on Oct 15, 2013
  1. Added #674 to History

    drbrain committed Oct 10, 2013
  2. Compare self, not self.class to input

    Fix bug in my patch cought by the test. Per drbrain.
    Since this is a class method self.class is Class, which is unhelpful.
    jkanywhere committed with drbrain Oct 8, 2013
  3. Fix test for Gem::Version.create change

    Test changes due to intentional code behavior change.
    
    The comment "FIX: For "legacy reasons," any object that responds to +version+ is
    returned unchanged. I'm not certain why." is no longer applicable as I removed
    that functionality in my previous patch. I was not certain why either :)
    
    Instead objects of type Gem::Version are simply not cast by Gem::Version.create.
    jkanywhere committed with drbrain Oct 8, 2013
  4. Bug fix Gem::Version.create

    Do not assume an object is of type Gem::Version just because it responds to
    :version
    jkanywhere committed with drbrain Oct 8, 2013
Commits on Oct 14, 2013
  1. Do not publish RubyGems 2.0.x documentation

    RubyGems 2.1.x is the current release series
    drbrain committed Oct 14, 2013
  2. Do not upload RubyGems 2.0.x to rubyforge

    We no longer do that
    drbrain committed Oct 14, 2013
  3. Update @7e61e0a for ruby 1.8

    Ruby 1.8 does not have URI.encode_www_form_component, so use
    CGI.escape/unescape instead.
    
    See #668, ruby bug #8979
    drbrain committed Oct 14, 2013