Message from discussion
[Backport93 - Backport #6314][Closed] Backport r35374 and r35375
Received: by 10.52.29.193 with SMTP id m1mr3742520vdh.4.1336969269008;
Sun, 13 May 2012 21:21:09 -0700 (PDT)
X-BeenThere: ruby-core-google@googlegroups.com
Received: by 10.220.149.145 with SMTP id t17ls634653vcv.9.gmail; Sun, 13 May
2012 21:21:08 -0700 (PDT)
Received: by 10.52.178.166 with SMTP id cz6mr3545727vdc.1.1336969268972;
Sun, 13 May 2012 21:21:08 -0700 (PDT)
Received: by 10.52.178.166 with SMTP id cz6mr3545726vdc.1.1336969268962;
Sun, 13 May 2012 21:21:08 -0700 (PDT)
Return-Path: <florgro+caf_=ruby-core-google-garchive-1974=googlegroups....@gmail.com>
Received: from mail-vb0-f50.google.com (mail-vb0-f50.google.com [209.85.212.50])
by gmr-mx.google.com with ESMTPS id ee5si1576068vdb.0.2012.05.13.21.21.08
(version=TLSv1/SSLv3 cipher=OTHER);
Sun, 13 May 2012 21:21:08 -0700 (PDT)
Received-SPF: pass (google.com: domain of florgro+caf_=ruby-core-google-garchive-1974=googlegroups....@gmail.com designates 209.85.212.50 as permitted sender) client-ip=209.85.212.50;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of florgro+caf_=ruby-core-google-garchive-1974=googlegroups....@gmail.com designates 209.85.212.50 as permitted sender) smtp.mail=florgro+caf_=ruby-core-google-garchive-1974=googlegroups....@gmail.com
Received: by vbal1 with SMTP id l1so3161672vba.9
for <ruby-core-google-garchive-1974@googlegroups.com>; Sun, 13 May 2012 21:21:08 -0700 (PDT)
Received: by 10.220.214.8 with SMTP id gy8mr4221192vcb.45.1336969268548;
Sun, 13 May 2012 21:21:08 -0700 (PDT)
X-Forwarded-To: ruby-core-google-garchive-1974@googlegroups.com
X-Forwarded-For: flor...@gmail.com ruby-core-google-garchive-1974@googlegroups.com
Delivered-To: flor...@gmail.com
Received: by 10.52.169.197 with SMTP id ag5csp143982vdc;
Sun, 13 May 2012 21:21:07 -0700 (PDT)
Received: by 10.68.226.129 with SMTP id rs1mr18458662pbc.29.1336969267046;
Sun, 13 May 2012 21:21:07 -0700 (PDT)
Return-Path: <ruby-core-ad...@ruby-lang.org>
Received: from carbon.ruby-lang.org (carbon.ruby-lang.org. [221.186.184.68])
by mx.google.com with ESMTP id py8si1829703pbb.227.2012.05.13.21.21.05;
Sun, 13 May 2012 21:21:07 -0700 (PDT)
Received-SPF: pass (google.com: best guess record for domain of ruby-core-ad...@ruby-lang.org designates 221.186.184.68 as permitted sender) client-ip=221.186.184.68;
Received: from beryllium.ruby-lang.org (beryllium.ruby-lang.org [127.0.0.1])
by carbon.ruby-lang.org (Postfix) with ESMTP id 7A3483C21EB43;
Mon, 14 May 2012 13:20:49 +0900 (JST)
Received: from fluorine.ruby-lang.org (www.rubyist.net [210.251.121.216])
by carbon.ruby-lang.org (Postfix) with ESMTP id 9CD323C21EBB7
for <ruby-c...@ruby-lang.org>; Mon, 14 May 2012 13:20:44 +0900 (JST)
Received: from ruby-lang.org (localhost [127.0.0.1])
by fluorine.ruby-lang.org (Postfix) with ESMTP id 8E0E23ED30
for <ruby-c...@ruby-lang.org>; Mon, 14 May 2012 13:20:44 +0900 (JST)
Delivered-To: ruby-c...@ruby-lang.org
Date: Mon, 14 May 2012 13:20:45 +0900
Posted: Mon, 14 May 2012 13:20:44 +0900
From: "naruse (Yui NARUSE)" <nar...@airemix.jp>
Reply-To: ruby-c...@ruby-lang.org
Subject: [ruby-core:45028] [Backport93 - Backport #6314][Closed] Backport r35374 and r35375
To: ruby-c...@ruby-lang.org
Message-Id: <redmine.journal-26612.20120514132...@ruby-lang.org>
References: <redmine.issue-6314.20120418114...@ruby-lang.org>
X-ML-Name: ruby-core
X-Mail-Count: 45028
X-MLServer: fml [fml 4.0.3 release (20011202/4.0.3)]; post only (only members can post)
X-ML-Info: If you have a question, send e-mail with the body
"help" (without quotes) to the address ruby-core-...@ruby-lang.org;
help=<mailto:ruby-core-...@ruby-lang.org?body=help>
X-Mailer: Redmine
X-Spam-Checker-Version: SpamAssassin 3.1.7-deb3 (2006-10-05) on
carbon.ruby-lang.org
X-Spam-Level:
X-Spam-Status: No, score=0.6 required=7.0 tests=BAYES_50,CONTENT_TYPE_PRESENT,
FAKEDWORD_BACKQUOTE,FORGED_RCVD_HELO,X_MAILER_PRESENT
autolearn=disabled version=3.1.7-deb3
X-Redmine-Issue-Author: drbrain
X-Auto-Response-Suppress: OOF
X-Redmine-Issue-Id: 6314
X-Redmine-Mailinglistintegration-Message-Ids: 15153
X-Redmine-Project: ruby-193
Auto-Submitted: auto-generated
X-Redmine-Site: Ruby Issue Tracking System
X-Redmine-Host: bugs.ruby-lang.org
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Precedence: bulk
Lines: 123
List-Id: ruby-core.ruby-lang.org
List-Software: fml [fml 4.0.3 release (20011202/4.0.3)]
List-Post: <mailto:ruby-c...@ruby-lang.org>
List-Owner: <mailto:ruby-core-ad...@ruby-lang.org>
List-Help: <mailto:ruby-core-...@ruby-lang.org?body=help>
List-Unsubscribe: <mailto:ruby-core-...@ruby-lang.org?body=unsubscribe>
Issue #6314 has been updated by naruse (Yui NARUSE).
Status changed from Open to Closed
Backported at r35402
----------------------------------------
Backport #6314: Backport r35374 and r35375
https://bugs.ruby-lang.org/issues/6314#change-26612
Author: drbrain (Eric Hodel)
Status: Closed
Priority: Normal
Assignee:
Category:
Target version:
=begin
This will update 1.9.3 to RubyGems 1.8.22 which is primarily bug fixes or interoperability and performance enhancements. The full list of updates since 1.8.11 follows:
=== 1.8.22 / 2012-04-13
* 4 bug fixes:
* Workaround for psych/syck YAML date parsing issue
* Don't trust the encoding of ARGV. Fixes #307
* Quiet default warnings about missing spec variables
* Read a binary file properly (windows fix)
=== 1.8.21 / 2012-03-22
* 2 bug fixes:
* Add workaround for buggy yaml output from 1.9.2
* Force 1.9.1 to remove it's prelude code. Fixes #305
=== 1.8.20 / 2012-03-21
* 4 bug fixes:
* Add --force to `gem build` to skip validation. Fixes #297
* Gracefully deal with YAML::PrivateType objects in Marshal'd gemspecs
* Treat the source as a proper url base. Fixes #304
* Warn when updating the specs cache fails. Fixes #300
=== 1.8.19 / 2012-03-14
* 3 bug fixes:
* Handle loading psych vs syck properly. Fixes #298
* Make sure Date objects don't leak in via Marshal
* Perform Date => Time coercion on yaml loading. Fixes #266
=== 1.8.18 / 2012-03-11
* 4 bug fixes:
* Use Psych API to emit more compatible YAML
* Download and write inside `gem fetch` directly. Fixes #289
* Honor sysconfdir on 1.8. Fixes #291
* Search everywhere for a spec for `gem spec`. Fixes #288
* Fix Gem.all_load_path. Fixes #171
=== 1.8.17 / 2012-02-17
* 2 minor enhancements:
* Add MacRuby to the list of special cases for platforms (ferrous26)
* Add a default for where to install rubygems itself
* 3 bug fixes:
* Fixed gem loading issue caused by dependencies not resolving.
* Fixed umask error when stdlib is required and unresolved dependencies exist.
* Shebang munging would only take one arg after the cmd
* Define SUCKAGE better, ie only MRI 1.9.2
* Propagate env-shebang to the pristine command if set for install.
=== 1.8.16 / 2012-02-12
* 3 bug fixes:
* Fix gem specification loading when encoding is not UTF-8. #146
* Allow group writable if umask allows it already.
* Uniquify the spec list based on directory order priority
=== 1.8.15 / 2012-01-06
* 1 bug fix:
* Don't eager load yaml, it creates a bad loop. Fixes #256
=== 1.8.14 / 2012-01-05
* 2 bug fixes:
* Ignore old/bad cache data in Version
* Make sure our YAML workarounds are loaded properly. Fixes #250.
=== 1.8.13 / 2011-12-21
* 1 bug fix:
* Check loaded_specs properly when trying to satisfy a dep
* 2 minor enhancements:
* Remove using #loaded_path? for performance
* Remove Zlib workaround for Windows build.
=== 1.8.12 / 2011-12-02
* Bug fix:
* Handle more cases where Syck's DefaultKey showed up in requirements
and wasn't cleaned out.
=end
--
http://bugs.ruby-lang.org/