summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authortaca <taca@pkgsrc.org>2012-06-13 15:16:50 +0000
committertaca <taca@pkgsrc.org>2012-06-13 15:16:50 +0000
commit417e0aeae08967f2f9d9a5b4c4b1b1b1976ebe01 (patch)
tree184c0fc9a622d050168dc8e4126888ade5fbb48e
parente456118fec1dfaa50cebc95aeb66dd40920af142 (diff)
downloadpkgsrc-417e0aeae08967f2f9d9a5b4c4b1b1b1976ebe01.tar.gz
Update ruby-activerecord32 to 2.3.6.
## Rails 3.2.6 (Jun 12, 2012) ## * protect against the nesting of hashes changing the table context in the next call to build_from_hash. This fix covers this case as well. CVE-2012-2695 * Revert earlier 'perf fix' (see 3.2.4 changelog / GH #6289). This change introduced a regression (GH #6609). assoc.clear and assoc.delete_all have loaded the association before doing the delete since at least Rails 2.3. Doing the delete without loading the records means that the `before_remove` and `after_remove` callbacks do not get invoked. Therefore, this change was less a fix a more an optimisation, which should only have gone into master. *Jon Leighton*
-rw-r--r--databases/ruby-activerecord32/distinfo8
1 files changed, 4 insertions, 4 deletions
diff --git a/databases/ruby-activerecord32/distinfo b/databases/ruby-activerecord32/distinfo
index 290ce1ee720..5894e0c763f 100644
--- a/databases/ruby-activerecord32/distinfo
+++ b/databases/ruby-activerecord32/distinfo
@@ -1,5 +1,5 @@
-$NetBSD: distinfo,v 1.3 2012/06/02 01:41:02 taca Exp $
+$NetBSD: distinfo,v 1.4 2012/06/13 15:16:50 taca Exp $
-SHA1 (activerecord-3.2.5.gem) = 209df4e1cd6f4b2c1bd96e22ff5786a1c5045b65
-RMD160 (activerecord-3.2.5.gem) = a6136508d075e49cb7c05897707587b026dbce3f
-Size (activerecord-3.2.5.gem) = 388096 bytes
+SHA1 (activerecord-3.2.6.gem) = dbca1a7d6e48395dd7a804d3e08422bc332a1e08
+RMD160 (activerecord-3.2.6.gem) = 3d41cf81deb3348b3d5cf4fb52b518bccae711d9
+Size (activerecord-3.2.6.gem) = 388608 bytes