all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: 32871@debbugs.gnu.org
Cc: guix-devel@gnu.org
Subject: Re: Ruby 2.5, pushing to staging?
Date: Fri, 12 Oct 2018 22:16:12 +0100	[thread overview]
Message-ID: <87d0se6f37.fsf@cbaines.net> (raw)
In-Reply-To: <87in2g0zlm.fsf@cbaines.net>

[-- Attachment #1: Type: text/plain, Size: 891 bytes --]


Christopher Baines <mail@cbaines.net> 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?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 962 bytes --]

  parent reply	other threads:[~2018-10-12 21:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-05 22:59 Ruby 2.5, pushing to staging? Christopher Baines
2018-10-06  3:04 ` Ruby 2.5, pushing to staging? [UNSCANNED] Benjamin Woodcroft
2018-10-06 11:22   ` Christopher Baines
2018-10-06 11:49     ` Benjamin Woodcroft
2018-10-06 11:53     ` Ricardo Wurmus
2018-10-06 19:50       ` Christopher Baines
2018-10-12 21:16 ` Christopher Baines [this message]
2018-10-15  9:05   ` [bug#32871] Ruby 2.5, pushing to staging? Ludovic Courtès
2018-10-19 14:51     ` Christopher Baines
2018-12-08 18:16   ` Christopher Baines
2018-12-08 22:53     ` Marius Bakke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d0se6f37.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=32871@debbugs.gnu.org \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.