From: alexander.kanavin@linux.intel.com
To: "Jussi Kukkonen" <jussi.kukkonen@intel.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 6/7] gnupg.org-hosted recipes: Change SRC_URI to https site
Date: Thu, 26 May 2016 12:34:52 +0300 (EEST) [thread overview]
Message-ID: <61959.10.252.8.31.1464255292.squirrel@linux.intel.com> (raw)
In-Reply-To: <CAHiDW_G9jEcP6MSB4+zGh_PPTBc87+C+5HBcGbEhFEoBNqVnoQ@mail.gmail.com>
> I could add a UPSTREAM_CHECK_URI for the ftp site... except I can't
> actually test that since the server has not really responded to me in
> days (apparently a known issue for the gupnp.org people).
Can you say which URL you cannot open? Everything works for me both behind
and outside of proxy, and the RRS server is reporting upstream versions
correctly as well:
http://recipes.yoctoproject.org/rrs/recipes/2.2/M1/
> I'll see about using http://gnutls.org/download.html page for that but
> in my opinion the patch is a clear improvement as it is...
You can't use http://gnutls.org/download.html because it doesn't have the
latest version anywhere on it.
And https://www.gnupg.org/ftp/gcrypt/gnutls/index.html has another issue:
it's out of date and doesn't have v3.5 directory listed at all, even
though it's there (visible via ftp and linked to from the downloads page).
How can you be sure that other index.html files aren't similarly out of
date? We should stick to the ftp directory listings for upstream checks
until the upstream sorts this. I'm not sure if the patch should be held
off altogether, or fixed so that the upstream check uri explicitly points
to ftp for each affected recipe.
Alex
next prev parent reply other threads:[~2016-05-26 8:47 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
2016-05-26 7:09 ` Jussi Kukkonen
2016-05-26 9:34 ` alexander.kanavin [this message]
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=61959.10.252.8.31.1464255292.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox