From: Marius Bakke <mbakke@fastmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: Preparing for 0.12.0
Date: Wed, 30 Nov 2016 18:48:15 +0100 [thread overview]
Message-ID: <878ts0uae8.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <20161130162747.GA8341@jasmine>
[-- Attachment #1: Type: text/plain, Size: 1279 bytes --]
Leo Famulari <leo@famulari.name> writes:
> 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!
Done! I took the liberty of merging 'master' as well to get the recent
cairo graft. Luckily no conflicts. Also updated dbus to the latest
stable '1.10.14' (from 1.10.12).
Apparently ruby was already ungrafted.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2016-11-30 17:48 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
2016-11-30 17:48 ` Marius Bakke [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878ts0uae8.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me \
--to=mbakke@fastmail.com \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).