From: EuAndreh <eu@euandre.org>
To: Leo Famulari <leo@famulari.name>, divoplade <d@divoplade.fr>
Cc: help-guix@gnu.org
Subject: Re: Can't serve a custom channel on a HTTPS repository
Date: Sun, 08 Aug 2021 14:49:07 -0300 [thread overview]
Message-ID: <162844494799.195169.5544877138905416641@localhost> (raw)
In-Reply-To: <YQAks2Ue37PtydWe@jasmine.lan>
After searching a bit through the archives, all I found was message [0] of
divoplade themself talking about this issue.
However, isn't the Guix main channel an HTTPS bare repository itself? Being
so, it may be more an issue with my installation than an issue with Guix or an
underlying Git library.
From the description of Git protocols [1], I understood that the main Guix
channel is served via the "Dumb HTTP" protocol. I'm just not yet sure how it
does it, and how I can replicate.
So it may be that the a Git repository served via the "Dumb HTTP" protocol can
work as a Guix channel, but I just don't know how yet. I couldn't identify any
special header or file in the Guix bare repository on Savannah [2], so that's
why I'm stuck at this point.
[0]: https://yhetil.org/guix/db1fe1b8a41fdc3784d4f5156e61682c19628121.camel@divoplade.fr/t/#u
[1]: https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols
[2]: https://git.savannah.gnu.org/git/guix.git/
next prev parent reply other threads:[~2021-08-08 17:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 17:36 Can't serve a custom channel on a HTTPS repository EuAndreh
2021-07-26 22:37 ` divoplade
2021-07-27 0:15 ` EuAndreh
2021-07-30 14:59 ` EuAndreh
2021-08-04 1:54 ` EuAndreh
2021-07-27 15:22 ` Leo Famulari
2021-08-08 17:49 ` EuAndreh [this message]
2021-08-08 22:21 ` Leo Famulari
2021-08-09 13:41 ` EuAndreh
2021-08-09 16:35 ` Leo Famulari
2021-08-15 17:06 ` EuAndreh
2021-08-24 16:13 ` EuAndreh
2021-09-15 17:00 ` EuAndreh
2021-09-15 17:34 ` EuAndreh
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=162844494799.195169.5544877138905416641@localhost \
--to=eu@euandre.org \
--cc=d@divoplade.fr \
--cc=help-guix@gnu.org \
--cc=leo@famulari.name \
/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).