From: "Ludovic Courtès" <ludo@gnu.org>
To: Mark H Weaver <mhw@netris.org>
Cc: 35034@debbugs.gnu.org
Subject: bug#35034: guile2.0-git rewrites libgit2 input to use guile-2.0
Date: Fri, 29 Mar 2019 16:29:30 +0100 [thread overview]
Message-ID: <87imw1aecl.fsf@gnu.org> (raw)
In-Reply-To: <871s2qd5k1.fsf@netris.org> (Mark H. Weaver's message of "Thu, 28 Mar 2019 17:58:27 -0400")
Hi Mark,
Mark H Weaver <mhw@netris.org> skribis:
> retitle 35034 guile2.0-git rewrites libgit2 input to use guile-2.0
> thanks
>
> It turns out that this problem is not specific to armhf. 'guile2.0-git'
> recently started failing to build on all Hydra-supported systems.
>
> I see now what's going on. The problem was introduced by:
>
> commit 03fb5ff6ae01a680c786d9ee148839543c519411
> Author: Danny Milosavljevic <dannym@scratchpost.org>
> Date: Thu Mar 21 23:28:43 2019 +0100
>
> gnu: libgit2: Avoid Python.
[...]
> The 'guile-git' package has 'libgit2' as an input. The 'guile2.0-git'
> variant package uses 'package-for-guile-2.0' to rewrite 'guile-git' to
> use 'guile-2.0'. Unfortunately, this rewrites more deeply than we
> probably want. In this case, the rewriting extends into 'libgit2',
> changing its native-input from 'guile-2.2' to 'guile-2.0'. However, the
> Guile code that Danny wrote doesn't work with 'guile-2.0', because it
> uses the (ice-9 textual-ports) module, which doesn't exist in Guile 2.0.
I’m tempted to sidestep the problem by removing “guile2.0-git”, which I
think is of little use.
WDYT?
Ludo’.
prev parent reply other threads:[~2019-03-29 15:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-28 20:38 bug#35034: One libgit2 derivation fails on armhf, another succeeds Mark H Weaver
2019-03-28 21:40 ` Danny Milosavljevic
2019-03-28 21:58 ` bug#35034: guile2.0-git rewrites libgit2 input to use guile-2.0 (was: One libgit2 derivation fails on armhf, another succeeds) Mark H Weaver
2019-03-29 15:29 ` Ludovic Courtès [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
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=87imw1aecl.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=35034@debbugs.gnu.org \
--cc=mhw@netris.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).