unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 30411-done@debbugs.gnu.org
Subject: [bug#30411] [PATCH] gnu: ldc: Update to 1.7.0.
Date: Fri, 23 Feb 2018 18:10:08 +0100	[thread overview]
Message-ID: <20180223171008.GA6186@thebird.nl> (raw)
In-Reply-To: <20180223125932.146ef945@scratchpost.org>

On Fri, Feb 23, 2018 at 12:59:32PM +0100, Danny Milosavljevic wrote:
> Hi Pjotr,
> 
> On Thu, 22 Feb 2018 02:42:30 +0100
> Pjotr Prins <pjotr.public12@thebird.nl> wrote:
> 
> > If you think this patch looks OK, I can resubmit it.
> > 
> > Again, I'll start chasing fixes with upstream. They are pretty
> > receptive.
> 
> Yeah, I've applied it to master with some small changes a few days
> ago.  It builds and tests fine now.

Thanks! Does this mean it can go into the new Guix release?

i686 and armhf failing on lit-tests looking for make. I'll
take a look when I have time in the coming days.

We should consider changing the name of ldc.scm to dlang.scm. There
are two other D compilers which are libre. Including a GNU one ;). At
the same time the packages could be re-indented. wdyt?

Pj.

-- 

  reply	other threads:[~2018-02-23 17:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-10 14:12 [bug#30411] [FIXME] Dlang ldc and dub packages fail on core-updates Pjotr Prins
2018-02-18  6:09 ` [bug#30411] [PATCH] gnu: ldc: Update to 1.7.0 pjotr.public12
2018-02-18 12:34   ` Danny Milosavljevic
2018-02-18 21:58     ` Pjotr Prins
     [not found]     ` <20180218214110.GB9488@thebird.nl>
2018-02-20  9:47       ` Danny Milosavljevic
2018-02-21  1:26         ` Pjotr Prins
2018-02-22  1:42           ` Pjotr Prins
2018-02-23 11:59             ` bug#30411: " Danny Milosavljevic
2018-02-23 17:10               ` Pjotr Prins [this message]
2018-02-23 17:31                 ` [bug#30411] " 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=20180223171008.GA6186@thebird.nl \
    --to=pjotr.public12@thebird.nl \
    --cc=30411-done@debbugs.gnu.org \
    --cc=dannym@scratchpost.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).