From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Guile 2.0.13
Date: Wed, 12 Oct 2016 16:30:32 -0400 [thread overview]
Message-ID: <20161012203032.GA11690@jasmine> (raw)
In-Reply-To: <87mvi9mikz.fsf@gnu.org>
On Wed, Oct 12, 2016 at 10:13:32PM +0200, Ludovic Courtès wrote:
> Leo Famulari <leo@famulari.name> skribis:
>
> > On Wed, Oct 12, 2016 at 02:38:26PM +0200, Ludovic Courtès wrote:
> >> Given that core-updates with Guile 2.0.12 is on its way and that master
> >> is still at 2.0.11, I’d suggest to leave master as-is and focus on
> >> core-updates.
> >>
> >> There we have 2 options:
> >>
> >> 1. Changing ‘guile-2.0/fixed’ to 2.0.13, but 1,310 packages depend on it.
> >>
> >> 2. Grafting 2.0.13, which is doable since 2.0.12 and .13 have the same ABI.
> >
> > Considering that 2.0.13 fixes a bug that is exposed by grafting,
>
> That *was* exposed by grafting; commit
> d72267863382041b84a9712eea354882be72ef55 works around the problem, so
> that’s fine.
Oh, right!
> > We could always un-graft it between releases if Hydra isn't busy.
>
> Yeah. I was thinking that we’d want to finish this core-updates cycle
> and then later do an ungrafting round or something.
>
> WDYT?
That sounds good. I think we should try doing some more specific
"updates" branches in between releases, assuming we have the compute
power and the motivation.
And we could also have some periodic ungrafting rebuilds when necessary
and feasible.
So, we would graft guile-2.0, make guile-2.0/fixed use 2.0.12, and set
replacement #f in guile-next? Anything else?
next prev parent reply other threads:[~2016-10-12 20:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 12:38 Guile 2.0.13 Ludovic Courtès
2016-10-12 16:20 ` Christopher Allan Webber
2016-10-12 16:35 ` Leo Famulari
2016-10-12 18:26 ` Christopher Allan Webber
2016-10-12 20:13 ` Ludovic Courtès
2016-10-12 20:30 ` Leo Famulari [this message]
2016-10-13 21:11 ` Ludovic Courtès
2016-10-15 17:13 ` Efraim Flashner
2016-10-15 19:46 ` Leo Famulari
2016-10-18 14:26 ` Ludovic Courtès
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=20161012203032.GA11690@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=ludo@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.