all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Preparing for 0.12.0
Date: Wed, 30 Nov 2016 11:27:47 -0500	[thread overview]
Message-ID: <20161130162747.GA8341@jasmine> (raw)
In-Reply-To: <87d1hdt7u9.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me>

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

On Wed, Nov 30, 2016 at 02:28:46PM +0100, Marius Bakke wrote:
> Ludovic Courtès <ludo@gnu.org> writes:
> > So what are the next steps?  I think mainly we should be freezing
> > ‘staging’ today (let’s see if there are packages to “ungraft”!) and
> > start building it in the hope of merging it next week.  If everything
> > goes well, we can release after that.

Yes, let's stick the schedule :)

> A quick grep for 'replacement' digs up these grafts:
> 
> * cairo      (1059 rebuilds)
> * curl       (1356 rebuilds)
> * cyrus-sasl (1360 rebuilds)
> * dbus       (1187 rebuilds)
> * guile@2.0  (1457 rebuilds)
> * libtiff    (1672 rebuilds)
> * libxslt    (2765 rebuilds)
> * pixman     (1061 rebuilds)
> * ruby       (344 rebuilds)
> 
> There is probably a fair bit of overlap between cairo, dbus and pixman.
> Are these OK for staging? Ruby is an obvious candidate, I'll do that.

I think it's okay to ungraft those packages on staging. Thanks Marius!

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

  reply	other threads:[~2016-11-30 16:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-30 12:44 Preparing for 0.12.0 Ludovic Courtès
2016-11-30 12:57 ` David Craven
2016-11-30 13:28 ` Marius Bakke
2016-11-30 16:27   ` Leo Famulari [this message]
2016-11-30 17:48     ` Marius Bakke
2016-11-30 20:46       ` Leo Famulari

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=20161130162747.GA8341@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=mbakke@fastmail.com \
    /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.