unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nils Gillmann <ng0@n0.is>
To: guix-devel@gnu.org
Cc: Nils Gillmann <ng0@n0.is>
Subject: Re: [bug#31076] gnurl 7.59.0
Date: Sun, 8 Apr 2018 21:28:20 +0000	[thread overview]
Message-ID: <20180408212820.m7bt3juprgl5tfsr@abyayala> (raw)
In-Reply-To: <87po39todl.fsf@gnu.org>

Ludovic Courtès transcribed 474 bytes:
> Hi,
> 
> Nils Gillmann <ng0@n0.is> skribis:
> 
> > Seems like ftp.gnu.org is currently either very slow or having troubles
> > with the actual software distribution. The signatures landed on there,
> > the rest has yet to materialize.
> 
> I think you made a mistake:
> 
>    gnurl-7.59.0.tar.gz.sig
>    gnurl-7.59.0.tar.gz.sig.sig
> 
> You’ll have to reupload without the extra .sig.  :-)

There were (are?) some issues on FTP side, they applied my new key
before realizing my new is too recent for their gpg. I'm currently
waiting on the result of the thread about this.
Furthermore it seems like the system can not cope very well with
anything that is not gpg and uses .sig ;) My signify signatures are
.sig, my gpg signatures are .asc ..
Anyway, we have to resolve some issues and archive some files in our
directory.

Thanks :)

> I’ve applied the patch since there’s a fallback URL anyway.
> 
> Thanks,
> Ludo’.

I'm looking into switching gnurl to bmake + mk-config. I've already got the
tools on my side.
Do you want me to continue the native autotools support for Guix in gnurl,
derived from curl? Or would it be okay to switch guix over to bmake +
mk-config if it works out for gnurl?

I'm asking because I could manage to support 2 build-system, it just would
be a bit unconvenient for me.

       reply	other threads:[~2018-04-08 21:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180406122457.dg5mvmgmuotfslho@abyayala>
     [not found] ` <87po39todl.fsf@gnu.org>
2018-04-08 21:28   ` Nils Gillmann [this message]
2018-04-09 16:51     ` [bug#31076] gnurl 7.59.0 Nils Gillmann
2018-04-09 20:49       ` Ricardo Wurmus
2018-04-10  9:41         ` Nils Gillmann

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=20180408212820.m7bt3juprgl5tfsr@abyayala \
    --to=ng0@n0.is \
    --cc=guix-devel@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).