all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eric Bavier <ericbavier@centurylink.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, julien@lepiller.eu, guix-commits@gnu.org
Subject: Re: 02/02: import: Update opam importer.
Date: Wed, 19 Dec 2018 17:19:45 -0600	[thread overview]
Message-ID: <20181219171945.2b7429ac@centurylink.net> (raw)
In-Reply-To: <875zvpwoj9.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1059 bytes --]

On Wed, 19 Dec 2018 15:59:22 +0100
Ludovic Courtès <ludo@gnu.org> wrote:

> Hi Eric,
> 
> Eric Bavier <ericbavier@centurylink.net> skribis:
> 
> >> commit cce654fabdf09cac7d18f9bad842ba8445aa022c
> >> Author: Julien Lepiller <address@hidden>
> >> Date:   Mon Dec 17 21:05:35 2018 +0100
> >> 
> >>     import: Update opam importer.
> >>     
> >>     * guix/import/opam.scm: Update importer for opam 2.
> >>     * tests/opam.scm: Update tests for the opam 2 importer.  
> 
> [...]
> 
> > This commit breaks Guix compatibility with Guile 2.0:
> >
> >   $ guix build -K --with-commit=guile2.0-guix=cce654fabf guile2.0-guix  
> 
> [...]
> 
> >    ?: 0 [scm-error misc-error #f "~A ~S" ("no code for module" (ice-9 peg)) #f]  
> 
> As discussed earlier, I’ll propose soon (like real soon!) a patch to
> remove support for 2.0.  In that spirit, I think we can leave it as is.

That's fine with me.

> Besides, I’m glad you thought about using ‘--with-commit’ for this use
> case.  :-)

It's very useful indeed!

`~Eric

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2018-12-19 23:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-19  3:26 02/02: import: Update opam importer Eric Bavier
2018-12-19 14:59 ` Ludovic Courtès
2018-12-19 23:19   ` Eric Bavier [this message]

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=20181219171945.2b7429ac@centurylink.net \
    --to=ericbavier@centurylink.net \
    --cc=guix-commits@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=julien@lepiller.eu \
    --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.