From: Andreas Enge <andreas@enge.fr>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org
Subject: Re: Nginx service fails
Date: Mon, 5 Mar 2018 08:48:20 +0100 [thread overview]
Message-ID: <20180305074820.GB7822@jurong> (raw)
In-Reply-To: <20180304234335.GA24376@jurong>
Hello,
On Mon, Mar 05, 2018 at 12:43:35AM +0100, Andreas Enge wrote:
> $ guix system reconfigure AE/clementi.scm
> guix system: error: failed to load 'AE/clementi.scm':
> AE/clementi.scm:5:0: In procedure allocate-struct: Wrong type argument in position 2: 25
I think I know the answer: .cache contains the compiled file for the operating
system declaration (clementi.go), and with the recent changes to how these are
parsed, it is incompatible.
> Is this normal? How are users supposed to know they should delete .cache?
Hopefully, this does not occur with "guix pull", and then it might be
considered normal... Is .cache actually necessary, since we generally
recompile from make files? Or is it needed since the make files do not
encode the precise dependency graph of the modules, as they usually do
for C code? If it is not necessary, could it be disabled by the project?
Andreas
next prev parent reply other threads:[~2018-03-05 7:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-04 22:27 Nginx service fails Andreas Enge
2018-03-04 23:06 ` Andreas Enge
2018-03-05 7:23 ` bug#30706: " Ricardo Wurmus
2018-03-05 7:43 ` Andreas Enge
2018-03-05 7:43 ` Andreas Enge
2018-03-05 10:09 ` Ludovic Courtès
2018-03-06 16:24 ` Danny Milosavljevic
2018-03-10 15:30 ` Ludovic Courtès
2018-03-10 15:30 ` Ludovic Courtès
2018-03-05 10:09 ` Ludovic Courtès
2018-03-04 23:07 ` Danny Milosavljevic
2018-03-04 23:43 ` Andreas Enge
2018-03-04 23:57 ` Andreas Enge
2018-03-05 7:48 ` Andreas Enge [this message]
2018-03-05 10:00 ` Ludovic Courtès
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=20180305074820.GB7822@jurong \
--to=andreas@enge.fr \
--cc=dannym@scratchpost.org \
--cc=guix-devel@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.