All of lore.kernel.org
 help / color / mirror / Atom feed
From: alexander.kanavin@linux.intel.com
To: "Jussi Kukkonen" <jussi.kukkonen@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 6/7] gnupg.org-hosted recipes: Change SRC_URI to https site
Date: Wed, 25 May 2016 17:42:10 +0300 (EEST)	[thread overview]
Message-ID: <52090.10.252.8.31.1464187330.squirrel@linux.intel.com> (raw)
In-Reply-To: <285302afb2b9fb0a868aeda0cbfa3ea956702793.1464176988.git.jussi.kukkone n@intel.com>

> Change gnutls to use GNUPG_MIRROR as well: they have their own domain
> but the ftp site is the slow, unreliable gnupg.org one.

Doesn't work for gnutls I'm afraid:

https://www.gnupg.org/ftp/gcrypt/gnutls/v3.4/

Alex


  parent reply	other threads:[~2016-05-25 13:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-25 13:29 [PATCH 0/7] upgrades + gnupg.org SRC_URI change Jussi Kukkonen
2016-05-25 13:29 ` [PATCH 1/7] clutter-1.0: Upgrade 1.24.2 -> 1.26.0 Jussi Kukkonen
2016-05-25 13:29 ` [PATCH 2/7] clutter-gst-3.0: Upgrade 3.0.16 -> 3.0.18 Jussi Kukkonen
2016-05-25 13:29 ` [PATCH 3/7] gtk+: Upgrade 2.24.29 -> 2.24.30 Jussi Kukkonen
2016-05-25 13:29 ` [PATCH 4/7] dosfstools: Upgrade 3.0.28 -> 4.0 Jussi Kukkonen
2016-05-25 13:29 ` [PATCH 5/7] libevdev: Upgrade 1.4.6 -> 1.5.1 Jussi Kukkonen
2016-05-25 13:29 ` [PATCH 6/7] gnupg.org-hosted recipes: Change SRC_URI to https site Jussi Kukkonen
     [not found]   ` <285302afb2b9fb0a868aeda0cbfa3ea956702793.1464176988.git.jussi.kukkone n@intel.com>
2016-05-25 14:42     ` alexander.kanavin [this message]
2016-05-26  7:09       ` Jussi Kukkonen
2016-05-26  9:34         ` alexander.kanavin
2016-05-26  9:56           ` alexander.kanavin
2016-05-26 12:30             ` Jussi Kukkonen
2016-05-26 13:01   ` Olof Johansson
2016-05-26 13:10     ` Jussi Kukkonen
2016-05-25 13:29 ` [PATCH 7/7] libgpg-error: Upgrade 1.21 -> 1.22 Jussi Kukkonen

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52090.10.252.8.31.1464187330.squirrel@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=jussi.kukkonen@intel.com \
    --cc=openembedded-core@lists.openembedded.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.