unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: guix pull via cgit odd behavior or [guile-git] limitations?
Date: Tue, 12 Sep 2017 10:20:26 +0200	[thread overview]
Message-ID: <87fubs1g6t.fsf@gnu.org> (raw)
In-Reply-To: <87bmmgpkvi.fsf@gnu.org> (Jan Nieuwenhuizen's message of "Tue, 12 Sep 2017 07:05:21 +0200")

Jan Nieuwenhuizen <janneke@gnu.org> skribis:

> ng0 writes:
>
>>   guix pull: error: Git error: invalid Content-Type: text/plain; charset=UTF-8
>>
>> so that I have to use git:// instead (which succeeds)? Is guile-git limited in
>> that aspect?
>
> I am struggling* to get going again with Cuirrass and suspect a similar
> thing.  On http:// urls with Cuirrass I now get
>
>     Git error: no Content-Type header in response

Weird, I wonder why libgit2 insists on having Content-Type.

> janneke
>
> * cuirass' guix envronment -l guix.scm is broken, cuirass package runs a
>   script before patch-shebanging; the spec examples in the manual lacks
>   a (list (quote ..)...

Please report these issues and/or send a patch!  :-)

Ludo’.

  reply	other threads:[~2017-09-12  8:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-11 20:58 guix pull via cgit odd behavior or limitations? ng0
2017-09-12  5:05 ` guix pull via cgit odd behavior or [guile-git] limitations? Jan Nieuwenhuizen
2017-09-12  8:20   ` Ludovic Courtès [this message]
2017-09-12 18:49     ` Jan Nieuwenhuizen
2017-09-12 18:57       ` ng0
2017-09-17 19:39       ` Ludovic Courtès

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=87fubs1g6t.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=janneke@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 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).