From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: Julien Lepiller <julien@lepiller.eu>,
guix-devel@gnu.org, Josselin Poiret <dev@jpoiret.xyz>,
Guix Devel <guix-devel@gnu.org>
Subject: Re: Time travel accident
Date: Tue, 11 Apr 2023 17:20:59 +0200 [thread overview]
Message-ID: <m1wn2ifns4.fsf@fastmail.net> (raw)
In-Reply-To: <C54D7C22-131B-485B-B003-E24057075E34@lepiller.eu>
Julien Lepiller <julien@lepiller.eu> writes:
> If you're able to find the derivation, you could set your system time
> and guix build /gnu/store/that.drv. this should not require network at
> all, so guix shouldn't complain.
Sounds good. The error message contains the path to the derivation,
so... let's just do it!
A few minutes later: I can't do anything at all with time-machine on
that commit any more. Maybe my attempt to build with a modified system
time broke something in the store?
$ guix time-machine --commit=ce35dc84a10b05dc891bfae03f613b907337945e --
shell --pure python -- python3
...
building /gnu/store/6126jqfx0rk9cccm518f53li2nj1q1h0-inferior-script.scm.drv...
building package cache...
building profile with 1 package...
;;; WARNING: loading compiled file /gnu/store/41zsnwsk02549kqb5njd3fadgnmkzww8-guix-module-union/lib/guile/3.0/site-ccache/guix/ui.go failed:
;;; In procedure load-thunk-from-memory: incompatible bytecode kind
...
;;; WARNING: loading compiled file /gnu/store/41zsnwsk02549kqb5njd3fadgnmkzww8-guix-module-union/lib/guile/3.0/site-ccache/guix/licenses.go failed:
;;; In procedure load-thunk-from-memory: incompatible bytecode kind
WARNING: Use of `load' in declarative module (guix ui). Add #:declarative? #f to your define-module invocation.
Backtrace:
5 (primitive-load "/home/hinsen/.cache/guix/inferiors/wisrwo5p2aq7o6r…")
In ice-9/eval.scm:
619:8 4 (_ #(#(#<directory (guix ui) 7f7fc35115a0>) "/home/hinsen/.cache…" …))
619:8 3 (_ #(#(#<directory (guix ui) 7f7fc35115a0>)))
159:9 2 (_ #(#(#<directory (guix ui) 7f7fc35115a0>)))
223:20 1 (proc #(#(#<directory (guix ui) 7f7fc35115a0>)))
In unknown file:
0 (%resolve-variable (7 . _IOLBF) #<directory (guix ui) 7f7fc35115a0>)
ERROR: In procedure %resolve-variable:
_IOLBF: unbound variable
In an attempt to clean up, I deleted ~/.cache/guix/inferiors, and then
did a "guix gc". But that makes no difference.
Time travelers live dangerously!
Cheers,
Konrad.
next prev parent reply other threads:[~2023-04-11 16:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 7:47 Time travel accident Konrad Hinsen
2023-04-07 8:30 ` Josselin Poiret
2023-04-07 10:07 ` Julien Lepiller
2023-04-07 16:10 ` Konrad Hinsen
2023-04-07 17:39 ` Julien Lepiller
2023-04-11 15:20 ` Konrad Hinsen [this message]
2023-04-12 10:17 ` Konrad Hinsen
2023-04-12 14:09 ` Simon Tournier
2023-04-13 8:14 ` Konrad Hinsen
2023-04-12 11:03 ` Simon Tournier
2023-04-12 12:53 ` Konrad Hinsen
2023-04-07 17:26 ` Simon Tournier
2023-04-17 13:32 ` Ludovic Courtès
2023-04-17 17:50 ` Simon Tournier
2023-04-17 22:16 ` Vagrant Cascadian
2023-04-18 9:39 ` Simon Tournier
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=m1wn2ifns4.fsf@fastmail.net \
--to=konrad.hinsen@fastmail.net \
--cc=dev@jpoiret.xyz \
--cc=guix-devel@gnu.org \
--cc=julien@lepiller.eu \
/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).