All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleksandr Kravchuk <open.source@oleksandr-kravchuk.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>,
	Oleksandr Kravchuk <open.source@oleksandr-kravchuk.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [meta-oe][PATCH 1/2] chrpath: fix SRC_URI
Date: Sat, 2 Jun 2018 15:45:24 +0200	[thread overview]
Message-ID: <d9184760-664e-9d92-b607-53511e8bb1c1@sashko.rv.ua> (raw)
In-Reply-To: <CANNYZj8VhXbaD93SpM130mx4v4b1Hjfr7fe8F30g+MR-+FaQxw@mail.gmail.com>

On 02/06/18 07:24, Alexander Kanavin wrote:
> 2018-06-02 1:14 GMT+03:00 Oleksandr Kravchuk
> <open.source@oleksandr-kravchuk.com>:
>> -SRC_URI = "https://alioth.debian.org/frs/download.php/file/3979/chrpath-0.16.tar.gz \
>> +SRC_URI = "https://src.fedoraproject.org/lookaside/extras/chrpath/chrpath-0.16.tar.gz/2bf8d1d1ee345fc8a7915576f5649982/chrpath-0.16.tar.gz \
>>              file://standarddoc.patch"
> It's better to stick with debian, the tarball is still available
> through ${DEBIAN_MIRROR}:
> http://http.debian.net/debian/pool/main/c/chrpath/chrpath_0.16.orig.tar.gz
>
> Can you also investigate the other instances of alioth, namely shadow
> and minicom please?
>
> Alex

This is a subjective statement. Having mirrors is great, but having a 
working SRC_URI in the recipe and mirrors five times great: I have seen 
both original source and the mirror being inaccessible for a period of 
time multiple times.


  reply	other threads:[~2018-06-02 13:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-01 22:14 [meta-oe][PATCH 1/2] chrpath: fix SRC_URI Oleksandr Kravchuk
2018-06-01 22:14 ` [meta-oe][PATCH 2/2] iso-codes: " Oleksandr Kravchuk
2018-06-02  5:19   ` Alexander Kanavin
2018-06-02 13:35     ` Oleksandr Kravchuk
2018-06-02 21:35       ` Alexander Kanavin
2018-06-02 21:38         ` Oleksandr Kravchuk
2018-06-02  5:24 ` [meta-oe][PATCH 1/2] chrpath: " Alexander Kanavin
2018-06-02 13:45   ` Oleksandr Kravchuk [this message]
2018-06-02 21:40     ` 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=d9184760-664e-9d92-b607-53511e8bb1c1@sashko.rv.ua \
    --to=open.source@oleksandr-kravchuk.com \
    --cc=alex.kanavin@gmail.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.