From: zimoun <zimon.toutoune@gmail.com>
To: Phil <phil@beadling.co.uk>, help-guix@gnu.org
Subject: Re: Channel details of profile generation
Date: Wed, 30 Dec 2020 14:41:53 +0100 [thread overview]
Message-ID: <86o8ibs95q.fsf@gmail.com> (raw)
In-Reply-To: <857dp1yg0f.fsf@beadling.co.uk>
Hi,
On Mon, 28 Dec 2020 at 17:52, Phil <phil@beadling.co.uk> wrote:
> guix pull -p my-profile -l
>
> But this seems to crash:
I am surprised.
> blah@phil:~$ guix pull -p my-profile -l
> \Generation 1 Dec 22 2020 17:24:53\
> my-test-repo 1.49-3.f08de71
> \Generation 2 Dec 22 2020 17:50:28\
> guix 13d532a
> repository URL: https://git.savannah.gnu.org/git/guix.git
> branch: master
> commit: \13d532a91178be7b6919b85685b150f941116dfc\
> foo-packages 8fc6134
> repository URL: ssh://git@localgit:7999/foo/foo-packages.git
> branch: master
> commit: 3dc613449f59ba8a8fdc35cadb7667ddaaf7fd9b
> Backtrace:
> 11 (primitive-load "/home/blah/.config/guix/current/bin/…")
> In guix/ui.scm:
> 2127:12 10 (run-guix-command _ . _)
> In ice-9/boot-9.scm:
> 1736:10 9 (with-exception-handler _ _ #:unwind? _ # _)
> 1731:15 8 (with-exception-handler #<procedure 7fa030b82b40 at ic…> …)
> 1731:15 7 (with-exception-handler #<procedure 7fa030b82b10 at ic…> …)
> 1731:15 6 (with-exception-handler #<procedure 7fa030c46390 at ic…> …)
> In guix/scripts/pull.scm:
> 636:4 5 (_)
> In guix/memoization.scm:
> 100:0 4 (_ #<hash-table 7fa030b4c780 0/31> "guix-profiles/py-t…" …)
> In guix/scripts/pull.scm:
> 538:21 3 (_)
> In guix/inferior.scm:
> 256:2 2 (inferior-available-packages #f)
> 251:13 1 (send-inferior-request (defined? (quote #)) #f)
> In ice-9/boot-9.scm:
> 1669:16 0 (raise-exception _ #:continuable? _)
>
> ice-9/boot-9.scm:1669:16: In procedure raise-exception:
> In procedure struct-vtable: Wrong type argument in position 1 (expecting struct): #f
Could you share how you generated the profile ’my-profile’?
> Os there not already a cannonical way to do this in Guix? If yes,
> what is it?
Well, I am missing what you want to achieve.
> If no is my approach below sane, or is what I'm trying to achieve
> ill-conceived in any way?
The profile used by ’pull’, by default ~/.config/guix/current, is
somehow special compared to other profiles as ~/.guix-profile.
> Finally, what's the intended difference between 'source and
> 'provenance?
Compare:
cat ~/.config/guix/current/manifest | grep -E '(source|provenance)'
cat ~/.guix-profile/manifest | grep -E '(source|provenance)'
It is my understanding and maybe someone will correct me: 'source is the
“properties“ tracking the channels from where the “pull” comes and
'provenance is the “properties” tracking the channel from where the
packages come from.
Well, 'source is used by “guix describe” but 'provenance is not used––it
is by “guix pack --save-provenance” but that’s another story.
> To my mind - If a profile generation has a manifest which contains
> branch/commit details of the branches packages were created with - it
> seems reasonable and useful to report that information?
Report where?
Hope that helps,
simon
next prev parent reply other threads:[~2020-12-30 13:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-28 17:52 Channel details of profile generation Phil
2020-12-30 13:41 ` zimoun [this message]
2021-01-04 17:29 ` Phil
2021-01-05 17:01 ` zimoun
2021-01-09 13:34 ` Phil
2021-01-11 17:34 ` zimoun
2021-01-12 19:16 ` Phil
2021-01-13 14:28 ` Phil
2021-01-13 20:15 ` zimoun
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=86o8ibs95q.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=help-guix@gnu.org \
--cc=phil@beadling.co.uk \
/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.
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).