From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marius Bakke Subject: Re: Ruby 2.5, pushing to staging? Date: Sat, 08 Dec 2018 23:53:31 +0100 Message-ID: <87y38zsk9g.fsf@fastmail.com> References: <87in2g0zlm.fsf@cbaines.net> <87d0se6f37.fsf@cbaines.net> <87k1kjx4s5.fsf@cbaines.net> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:45471) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gVlTf-0004T7-Dx for guix-devel@gnu.org; Sat, 08 Dec 2018 17:53:40 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gVlTc-0005PG-8Z for guix-devel@gnu.org; Sat, 08 Dec 2018 17:53:39 -0500 Received: from out1-smtp.messagingengine.com ([66.111.4.25]:48317) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gVlTc-0005P2-2L for guix-devel@gnu.org; Sat, 08 Dec 2018 17:53:36 -0500 In-Reply-To: <87k1kjx4s5.fsf@cbaines.net> 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: Christopher Baines Cc: guix-devel@gnu.org --=-=-= Content-Type: text/plain Christopher Baines writes: > Christopher Baines writes: > >> Christopher Baines writes: >> >>> A new minor version of Ruby has been out for a while, and it would be >>> good to get Ruby 2.5 in to Guix. >>> >>> I've put up a patch here [1], and tried it locally. I've pushed some >>> fixes to master to make some packages compatible [2], and while I do get >>> some failures when building the 958 (according to guix refresh -l) >>> dependant packages, I'm unsure how many of these are down to the Ruby >>> upgrade. >>> >>> 1: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=32871 >>> 2: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=32870 >>> >>> Anyway, looking at the contributing guide this is possibly too big of a >>> change to push directly to master, so should I push this to the staging >>> branch? >> >> I've now gone ahead and pushed to staging. Not really sure what happens >> now.... will berlin and hydra pick this up automatically, and start >> building packages? > > So, I'm still interested in pushing Ruby 2.5 forward. I've now pushed an > upgrade from 2.5.1 to 2.5.3 to the staging branch, as that seemed > sensible. Thank you for taking care of Ruby :-) > I can see that ci.guix.info (berlin) has picked this up (I think here > [1]), but I'm not sure what to do next...? I can start this branch on Hydra tomorrow or Monday (it's busy currently). If there are no regressions, it should be safe to merge. We need to synchronize the build farms until users have migrated to Berlin, since many users probably only have Hydra still. PS: Staging is currently at ~3500 rebuilds[*], which is way more than the usual ~1200 rebuilds. If there are other heavy-impact patches pending that does not significantly increase this number, we might be able to squeeze them in. [*] According to "guix refresh -l -e '(@@ (gnu packages build-tools) meson-for-build)' boost ruby eudev mesa wayland imagemagick openblas nss" --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAlwMS2sACgkQoqBt8qM6 VPqg9QgAjsMuFzBWlVRomwFSSphYR7hv+ZS9LSkqrs3gvco3X/8Sv9o/dxhbPISN S17JTP2CaR3T+bWWWB8qcZR9oyWcsfFu/5rPvxP8xC8H99yf+n0ZQ01DjUDCC0VX Tih0Kq7xToUrRlJ494/0N1pP6/bWsbqA0u3wctv8fTMlO6DGJ+0TXCoxiKr+zJYg /h7DwwH2AI+40h45ahE+2MNvt8sE2M2BURdVnQvsYZMao8P16Ikn4zRb9XFaAdZu 97SUqBhPAxzcykusOlbYAOjQ7UbK7ZZ6YfHYt12C25M8KVGrEy2aHz2YxGfML8vD /K/5+OQokS9y7DsMe7WM6MCS2iuRcQ== =15Rz -----END PGP SIGNATURE----- --=-=-=--