From: "jgart" <jgart@dismail.de>
To: guix-devel@gnu.org
Cc: "Guillaume Le Vaillant" <glv@posteo.net>
Subject: Re: Is this a bug in guix refresh with respect to Common Lisp packages?
Date: Sat, 07 Oct 2023 04:16:28 +0000 [thread overview]
Message-ID: <68c2f4d056d4cef5d92d2cac537cc934@dismail.de> (raw)
In-Reply-To: <5447de021d72c7486b45ef09319d6114@dismail.de>
Yep, this looks broken:
[jgart@fedora guix] [env]$ make -j6 && ./pre-inst-env guix refresh -l sbcl-enhanced-eval-when ecl-enhanced-eval-when
make all-recursive
make[1]: Entering directory '/home/jgart/Code/guix'
Making all in po/guix
make[2]: Entering directory '/home/jgart/Code/guix/po/guix'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/home/jgart/Code/guix/po/guix'
Making all in po/packages
make[2]: Entering directory '/home/jgart/Code/guix/po/packages'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/home/jgart/Code/guix/po/packages'
make[2]: Entering directory '/home/jgart/Code/guix'
Compiling Scheme modules...
Compiling Scheme modules...
Compiling Scheme modules...
Compiling Scheme modules...
Compiling Scheme modules...
Compiling Scheme modules...
Compiling Scheme modules...
Compiling Scheme modules...
make[2]: Leaving directory '/home/jgart/Code/guix'
make[1]: Leaving directory '/home/jgart/Code/guix'
Building the following 2 packages would ensure 10 dependent packages are rebuilt: cl-definitions-systems@2.0.1 ecl-definitions-systems@2.0.1
This email is gluten-free, vegan, and 100% organic,
jgart
next prev parent reply other threads:[~2023-10-07 4:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-07 4:04 Is this a bug in guix refresh with respect to Common Lisp packages? jgart
2023-10-07 4:16 ` jgart [this message]
2023-10-09 18:17 ` Charles
2023-10-07 8:51 ` Ricardo Wurmus
2023-10-07 13:08 ` jgart
2023-10-08 16:17 ` Ricardo Wurmus
2023-10-08 16:21 ` jgart
2023-10-10 8:19 ` Guillaume Le Vaillant
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=68c2f4d056d4cef5d92d2cac537cc934@dismail.de \
--to=jgart@dismail.de \
--cc=glv@posteo.net \
--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.