From: "Ludovic Courtès" <ludo@gnu.org>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: 65740@debbugs.gnu.org
Subject: bug#65740: No fallback to SWH for .guix-channel dependencies
Date: Fri, 08 Sep 2023 22:40:27 +0200 [thread overview]
Message-ID: <87wmx01jr8.fsf@gnu.org> (raw)
In-Reply-To: <875y4pq2zw.fsf@gmail.com> (Simon Tournier's message of "Mon, 04 Sep 2023 19:09:39 +0200")
Hi,
Simon Tournier <zimon.toutoune@gmail.com> skribis:
> The main reason is because the channel bimsb contains the file
> .guix-channel which reads,
>
> (channel
> (version 0)
> (dependencies
> (channel
> (name guix-past)
> (url "https://gitlab.inria.fr/guix-hpc/guix-past"))
> (channel
> (name guix-science)
> (url "https://github.com/guix-science/guix-science.git"))))
>
> And Guix is not able to fallback to SWH for these channels.
Yes, but that’s expected: we’re not specifying any commit, only the URL,
so there cannot be any sort of fallback.
> Corollary, even if it was able, what is the correct revision of
> the guix-past or guix-science channels?
>
> This report is about two bugs:
>
> 1. transparent fallback to SWH for .guix-channel dependencies
>
> 2. pin all channels when running “guix describe”, even the ones from
> .guix-channel dependencies.
#1 happens, but only when channels are pinned (returned by ‘guix
#describe’).
Re #2, I don’t think there’s such a bug, is there? In the example
below, ‘guix describe’ shows 4 channels (including dependencies), not 2:
--8<---------------cut here---------------start------------->8---
$ ./pre-inst-env guix time-machine -C <(echo '(cons (channel (name (quote bimsb)) (url "https://github.com/BIMSBbioinfo/guix-bimsb.git")) %default-channels)') -- describe -f channels
[...]
(list (channel
(name 'guix)
(url "https://git.savannah.gnu.org/git/guix.git")
(branch "master")
(commit
"4dd33fc62899134606f36f92594cf160b972f685")
(introduction
(make-channel-introduction
"9edb3f66fd807b096b48283debdcddccfea34bad"
(openpgp-fingerprint
"BBB0 2DDF 2CEA F6A8 0D1D E643 A2A0 6DF2 A33A 54FA"))))
(channel
(name 'bimsb)
(url "https://github.com/BIMSBbioinfo/guix-bimsb.git")
(branch "master")
(commit
"240a599f77dab7dcb8d2ed091b90056e58a46c51"))
(channel
(name 'guix-science)
(url "https://github.com/guix-science/guix-science.git")
(branch "master")
(commit
"1ad5192cff0d7b34a2f74592c6896f901d1c9ccd"))
(channel
(name 'guix-past)
(url "https://gitlab.inria.fr/guix-hpc/guix-past")
(branch "master")
(commit
"1e25b23faa6b1716deaf7e1782becb5da6855942")))
--8<---------------cut here---------------end--------------->8---
Thanks,
Ludo’.
next prev parent reply other threads:[~2023-09-08 20:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 17:09 bug#65740: No fallback to SWH for .guix-channel dependencies Simon Tournier
2023-09-08 20:40 ` Ludovic Courtès [this message]
2023-09-09 10:04 ` 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=87wmx01jr8.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=65740@debbugs.gnu.org \
--cc=zimon.toutoune@gmail.com \
/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).