From owner-freebsd-ruby@FreeBSD.ORG Sat Sep 17 12:54:44 2011 Return-Path: Delivered-To: ruby@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BD9D51065670 for ; Sat, 17 Sep 2011 12:54:44 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from mouf.net (unknown [IPv6:2607:fc50:0:4400:216:3eff:fe69:33b2]) by mx1.freebsd.org (Postfix) with ESMTP id 811208FC16 for ; Sat, 17 Sep 2011 12:54:44 +0000 (UTC) Received: from meatwad.mouf.net (cpe-065-190-149-241.nc.res.rr.com [65.190.149.241]) (authenticated bits=0) by mouf.net (8.14.4/8.14.4) with ESMTP id p8HCsgJH062306 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT) for ; Sat, 17 Sep 2011 08:54:43 -0400 (EDT) (envelope-from swills@FreeBSD.org) Message-ID: <4E749892.5070704@FreeBSD.org> Date: Sat, 17 Sep 2011 08:54:42 -0400 From: Steve Wills User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110531 Thunderbird/3.1.10 MIME-Version: 1.0 To: ruby@FreeBSD.org X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (mouf.net [204.109.58.86]); Sat, 17 Sep 2011 08:54:43 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.97.2 at mouf.net X-Virus-Status: Clean Cc: Subject: rails update X-BeenThere: freebsd-ruby@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Ruby discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Sep 2011 12:54:44 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 While working on my gems patching, I discovered that we need to update the builder rubygem, which started a lot of yak shaving which led to this: http://people.freebsd.org/~swills/rails31/ which updates rails to 3.1.0. There are some cross site scripting issues with activesupport and actionpack, so I guess it would be good to do this soon. Any testing or feedback on this would be appreciated. And of course, there's the code injection issue with ruby-gems, but that's a different story (I'm currently working on at least build testing an update from ruby-gems 1.8.7 to 1.8.10). Steve -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (FreeBSD) iQEcBAEBAgAGBQJOdJiSAAoJEPXPYrMgexuhFT8H/23aqBNlK3EklPf2immK/5So EaYAxLaATob1RDOqPNpqTFxwKfF6hNbJ4b/SzX4yY6uhqRVL/vKnjkeVRrPFfIQk lbnAXtvUaQhSjp5aTVXsUidzOsTqXpealVN+sRHAYobNqMm58Bh7vFRQCjx5rD2h MTo7s3LYBKFDTryqi5Qv55IkShxOLjFWKJf1mHLi+jWeourVGG/ak6UzbsnnTx+6 zxh9h3iwXxVA2dgAVDsET1Ma5KCKhhfa23X9zl/dQpohgzVPpxe/y0u1LomaDj9B ciuscOfDTMUa/CsAFKTHhaYVP455qyVVtRnDYGMbM1tWEsHQG3kqzpLMz/1cvgI= =Qf0s -----END PGP SIGNATURE-----