From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: 33180@debbugs.gnu.org
Subject: bug#33180: guix pull fails in a directory with scm files
Date: Sat, 27 Oct 2018 23:56:27 +0200 [thread overview]
Message-ID: <20181027235627.4397c5ed@alma-ubu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1385 bytes --]
When my current working directory is within a guix checkout, it goes
wrong (I suppose this can happen with any scheme code?)
which guix
/home/bjoern/.config/guix/current/bin/guix
# In guix/guix is my Guix checkout:
me:~/guix/guix/gnu/packages$ guix pull
;;; note: source file texinfo.scm
;;; newer than compiled /gnu/store/p9wm67w3rfw3hlb9iljgvsfn84mz4w9d-guile-2.2.4/lib/guile/2.2/ccache/texinfo.go
Backtrace:
In ice-9/boot-9.scm:
222:29 19 (map1 _)
222:29 18 (map1 _)
222:29 17 (map1 _)
222:29 16 (map1 _)
222:29 15 (map1 _)
222:29 14 (map1 _)
222:29 13 (map1 _)
222:29 12 (map1 _)
222:29 11 (map1 _)
222:29 10 (map1 _)
222:29 9 (map1 _)
222:29 8 (map1 _)
222:29 7 (map1 _)
222:29 6 (map1 _)
222:29 5 (map1 _)
222:29 4 (map1 _)
222:29 3 (map1 _)
222:17 2 (map1 (((texinfo)) ((texinfo plain-text)) ((texinfo …))))
2803:6 1 (resolve-interface _ #:select _ #:hide _ #:prefix _ # _ …)
In unknown file:
0 (scm-error misc-error #f "~A ~S" ("no code for modu…" …) …)
ERROR: In procedure scm-error:
no code for module (texinfo)
cd
me:~$ guix pull
Updating channel 'guix-chromium' from Git repository at 'https://gitlab.com/mbakke/guix-chromium.git'...
Updating channel 'guix' from Git repository at 'https://git.savannah.gnu.org/git/guix.git'...
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next reply other threads:[~2018-10-27 21:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-27 21:56 Björn Höfling [this message]
2018-10-28 6:36 ` bug#33180: guix pull fails in a directory with scm files Julien Lepiller
2018-10-30 10:05 ` Björn Höfling
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=20181027235627.4397c5ed@alma-ubu \
--to=bjoern.hoefling@bjoernhoefling.de \
--cc=33180@debbugs.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).