All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andre McCurdy <armccurdy@gmail.com>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 07/10] mirrors: replace references to archive.apache.org
Date: Tue, 22 Dec 2015 11:52:26 -0800	[thread overview]
Message-ID: <CAJ86T=V721kLwWtqLEWmTvJPj-LSw93uoM=s9afOH8xiZKd5Rg@mail.gmail.com> (raw)
In-Reply-To: <56794E98.3050605@linux.intel.com>

On Tue, Dec 22, 2015 at 5:22 AM, Alexander Kanavin
<alexander.kanavin@linux.intel.com> wrote:
> On 12/22/2015 12:21 AM, Andre McCurdy wrote:
>>>
>>> -http://www.apache.org/dist  http://archive.apache.org/dist \n \
>>> +http://www.eu.apache.org/dist  http://www.us.apache.org/dist \n \
>>
>>
>> Is this change correct? Shouldn't mirrors.bbclass provide a fallback
>> to the historical releases URL (so that things keep working if the
>> oe-core version of an apache.org package is no longer a current
>> version) ?
>
> When I have checked, archive.apache.org did not have the latest releases of
> subversion, so it can't be relied on as a primary upstream source. On the
> other hand, primary mirrors only keep the latest releases, and remove
> anything else. So the right thing would be to first try to use those primary
> mirrors, and fall back to archive if those mirrors no longer have the
> version we need.

Yes, that's what I was getting at - there should be a fallback to the
archives since oe-core releases typically won't be using the latest
release versions. Your new patch looks good.

Checking subversion on http://archive.apache.org/dist today though,
the archive site does seem to have copies of the latest versions, so
not sure what was happening when you looked.

> This problem also shows up with debian upstream.
>
> Alex
>


  reply	other threads:[~2015-12-22 19:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-09 14:40 [PATCH 00/10] Recipe version updates Alexander Kanavin
2015-12-09 14:40 ` [PATCH 01/10] openssl: update to 1.0.2e Alexander Kanavin
2015-12-09 19:52   ` akuster808
2015-12-10 10:50     ` Alexander Kanavin
2015-12-10 23:13       ` Paul Eggleton
2015-12-11 12:18         ` Alexander Kanavin
2015-12-14 14:34   ` Otavio Salvador
2015-12-15  0:49     ` Khem Raj
2015-12-09 14:40 ` [PATCH 02/10] gnutls: update to 3.4.7 Alexander Kanavin
2015-12-10 22:27   ` Burton, Ross
2015-12-09 14:40 ` [PATCH 03/10] python-setuptools: update to 18.7.1 Alexander Kanavin
2015-12-09 14:40 ` [PATCH 04/10] nspr: update to 4.11 Alexander Kanavin
2015-12-09 14:40 ` [PATCH 05/10] mobile-broadband-provider-info: update to current commit Alexander Kanavin
2015-12-09 14:40 ` [PATCH 06/10] puzzles: " Alexander Kanavin
2015-12-09 14:40 ` [PATCH 07/10] mirrors: replace references to archive.apache.org Alexander Kanavin
2015-12-21 22:21   ` Andre McCurdy
2015-12-22 13:22     ` Alexander Kanavin
2015-12-22 19:52       ` Andre McCurdy [this message]
2015-12-09 14:40 ` [PATCH 08/10] json-c: add manual upstream version check Alexander Kanavin
2015-12-09 14:40 ` [PATCH 09/10] subversion: update to 1.9.2 Alexander Kanavin
2015-12-09 14:40 ` [PATCH 10/10] slang: update upstream URI to (official) jedsoft.org Alexander Kanavin

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='CAJ86T=V721kLwWtqLEWmTvJPj-LSw93uoM=s9afOH8xiZKd5Rg@mail.gmail.com' \
    --to=armccurdy@gmail.com \
    --cc=alexander.kanavin@linux.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.