all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Guix-devel <guix-devel@gnu.org>
Subject: Re: Releasing 0.9.1
Date: Wed, 09 Mar 2016 14:14:54 +0100	[thread overview]
Message-ID: <871t7jeqsx.fsf@gnu.org> (raw)
In-Reply-To: <8737sg65lb.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Thu, 25 Feb 2016 18:51:44 +0100")

So!  It seems that this time releasing is really hard.  :-)

I’d like to do a rebuild without any package replacements, in the hope
that the release itself has no or few grafts in place, mostly because:

  • performance is currently degraded in the presence of grafts, in
    particular the repeated “updating the list of substitutes” (I have a
    rough idea on how to fix, but we’d rather not hold our breath);

  • they increase disk usage, so the USB images would be bigger.

So, on this branch, I’d incorporate:

  dbus and dbus/activation
  eudev and eudev-with-blkid
  graphite2 and its replacement
  perl and its replacement
  openssl and its replacement

I don’t want to base it on ‘core-updates’ because there are potentially
disrupting changes in there.

Thoughts?

Ludo’.

  parent reply	other threads:[~2016-03-09 13:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-05 13:46 Releasing 0.9.1 Ludovic Courtès
2016-02-05 13:51 ` Andreas Enge
2016-02-07 12:13 ` Ben Woodcroft
2016-02-07 12:48   ` Ricardo Wurmus
2016-02-07 20:44     ` Ludovic Courtès
2016-02-07 20:54       ` Ben Woodcroft
2016-02-08 21:21 ` Mathieu Lirzin
2016-02-25 17:51 ` Ludovic Courtès
2016-02-25 18:04   ` Ricardo Wurmus
2016-02-25 19:27   ` Leo Famulari
2016-02-26 23:15     ` Ludovic Courtès
2016-02-25 20:11   ` Andreas Enge
2016-02-26 23:16     ` Ludovic Courtès
2016-03-09 13:14   ` Ludovic Courtès [this message]
2016-03-09 14:41     ` Ludovic Courtès
2016-03-10 16:23       ` 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=871t7jeqsx.fsf@gnu.org \
    --to=ludo@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.