unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: guix-devel <guix-devel@gnu.org>
Subject: Re: Planning for 0.8.2
Date: Tue, 21 Apr 2015 23:33:40 +0200	[thread overview]
Message-ID: <87pp6xyxmz.fsf@gnu.org> (raw)
In-Reply-To: <87k2xx88in.fsf@inria.fr> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22\?\= \=\?utf-8\?Q\?'s\?\= message of "Tue, 31 Mar 2015 17:57:20 +0200")

ludo@gnu.org (Ludovic Courtès) skribis:

> It’s about time to prepare for 0.8.2.  Here’s what I think should be
> completed by then:
>
>   • ‘wip-build-systems-gexp’ merged in ‘core-updates’, although if that
>     turns out to involve more work than expected, I’m happy to delay it
>     until the next release.

This is postponed until after the release.

>   • New phase to validate NEEDED against RUNPATH (see
>     <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=20039#11>; we're
>     almost there.)
>
>   • ‘guix publish’ merged in (I think it's ready now, right?)
>
>   • ‘guix import hackage’ and ‘haskell-build-system’.
>
>   • LibreOffice (anyone?), Hydra(?).

All of this is OK, except LibreOffice.

>   • Addressing the bug reports that have accumulated since the last
>     release.  Many are packaging and usability issues that are easily
>     addressed, I think.  I invite everyone to look at them.  A bug fix a
>     day, keeps the doctor away!

There are still some left, notably newly introduced ones.  :-)

For those I’ve just reopened core-updates with the intent of freezing it
in a couple of days or so.  The changes should be limited to:

  1. ld-wrapper bugs fixed (just pushed);

  2. libstdc++ not having libgcc_s in its RUNPATH (bug #20358);

  3. #:validate-runpath? turned on by default for all the build systems
     (currently it’s only gnu-build-system); more broken packages will
     become apparent as a result;

  4. libc’s own message catalogs are installed (just pushed).

I think Eric has a small Perl patch that would be welcome, but that’s
about it.

Thoughts?

Ludo’.

  parent reply	other threads:[~2015-04-21 21:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-31 15:57 Planning for 0.8.2 Ludovic Courtès
2015-03-31 16:43 ` Andreas Enge
2015-04-01 20:06   ` Ludovic Courtès
2015-04-01 20:57   ` Ricardo Wurmus
2015-04-02 12:51     ` Ludovic Courtès
2015-04-06 16:11       ` Andreas Enge
2015-04-06 20:04         ` Ludovic Courtès
2015-04-07 11:45         ` John Darrington
2015-03-31 17:07 ` Mark H Weaver
2015-03-31 17:35 ` Eric Bavier
2015-03-31 18:36 ` Mark H Weaver
2015-03-31 20:19   ` Taylan Ulrich Bayırlı/Kammer
2015-04-21 21:33 ` Ludovic Courtès [this message]
2015-04-23 22:39   ` Ludovic Courtès
2015-04-24  8:51     ` Taylan Ulrich Bayırlı/Kammer
2015-05-02 20:49   ` Ludovic Courtès
2015-05-07 20:39   ` Ludovic Courtès
2015-05-09  5:05     ` Mark H Weaver
2015-05-09 13:43       ` 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

  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=87pp6xyxmz.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 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).