From: Vagrant Cascadian <vagrant@debian.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 47978@debbugs.gnu.org
Subject: bug#47978: guix/import/go.scm: Dependency on guile-lib >= 0.2.7
Date: Wed, 28 Apr 2021 15:29:04 -0700 [thread overview]
Message-ID: <87lf92vya7.fsf@yucca> (raw)
In-Reply-To: <87o8dyozy3.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1320 bytes --]
On 2021-04-28, Ludovic Courtès wrote:
> Vagrant Cascadian <vagrant@debian.org> skribis:
>
>> When building guix (with commit cb3f9696f6251ad382febad33290fed929c176b4
>> from branch version-1.3.0) on Debian, it fails with the following error
>> with guile-library (a.k.a. guile-lib) version 0.2.6.1-2:
>>
>> ice-9/eval.scm:293:34: error: %strict-tokenizer?: unbound variable
>> hint: Did you forget a `use-modules' form?
>>
>> [ 10%] LOAD guix/import/go.scm
>> ;;; Failed to autoload semver-range-contains? in (semver ranges):
>> ;;; missing interface for module (semver ranges)
>> ...
>> ;;; Failed to autoload semver<? in (semver):
>> ;;; missing interface for module (semver)
>> ice-9/eval.scm:293:34: error: %strict-tokenizer?: unbound variable
>> hint: Did you forget a `use-modules' form?
>>
>>
>> Installing guile-library version 0.2.7 works fine.
>
> 34db952a4b655cca9d5dc7158e9a8552d389cbcf fixes it by making Guile-Lib a
> “soft” dependency as was intended. But yes, 0.2.7 is required if you
> want to use ‘guix import go’.
Makes sense.
Some (e.g. guile-ssh) of the "optional" dependencies are or were
similarly required to build guix in the past ... I should probably file
bugs when I encounter them, sounds like. :)
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2021-04-28 22:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 18:50 bug#47978: guix/import/go.scm: Dependency on guile-lib >= 0.2.7 Vagrant Cascadian
2021-04-28 21:35 ` Ludovic Courtès
2021-04-28 22:29 ` Vagrant Cascadian [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=87lf92vya7.fsf@yucca \
--to=vagrant@debian.org \
--cc=47978@debbugs.gnu.org \
--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 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).