From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ben Woodcroft Subject: [PATCH 0/1]: Replace ruby with ruby-2.3.2. Date: Sat, 19 Nov 2016 09:32:08 +1000 Message-ID: <20161118233209.28746-1-donttrustben@gmail.com> Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33767) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c7sfs-00068Z-L6 for guix-devel@gnu.org; Fri, 18 Nov 2016 18:34:29 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c7sfp-0003zw-Hn for guix-devel@gnu.org; Fri, 18 Nov 2016 18:34:28 -0500 Received: from mail-pg0-x244.google.com ([2607:f8b0:400e:c05::244]:36823) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1c7sfp-0003zR-C5 for guix-devel@gnu.org; Fri, 18 Nov 2016 18:34:25 -0500 Received: by mail-pg0-x244.google.com with SMTP id x23so21850317pgx.3 for ; Fri, 18 Nov 2016 15:34:24 -0800 (PST) Received: from localhost.localdomain ([103.25.181.216]) by smtp.googlemail.com with ESMTPSA id f14sm20383262pfk.5.2016.11.18.15.34.20 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 18 Nov 2016 15:34:22 -0800 (PST) List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: guix-devel@gnu.org Hi there, Ruby 2.3.2 was just released, and since it entails >300 rebuilds it is a good candidate for staging I think. I do not know of an easy way to check exactly which security fixes have been applied beyond text searching the CHANGELOG, which isn't optimal so I believe there are other fixes that have been applied beyond the one mentioned in the commit message. In pushing the update to staging, to avoid problems during the merge, is it best to push this patch and then a second doing the actual update to staging? Thanks, ben