From: Martin Jansa <martin.jansa@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: File conflicts in DL_DIR
Date: Wed, 12 Oct 2016 21:29:47 +0200 [thread overview]
Message-ID: <20161012192947.GG2923@jama> (raw)
In-Reply-To: <CAJTo0LaCUJpq5MV3kGtnOz53Mv1V1hr581A7=bBt2yFR8W5CKQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1214 bytes --]
On Wed, Oct 12, 2016 at 08:11:57PM +0100, Burton, Ross wrote:
> On 12 October 2016 at 18:30, Martin Jansa <martin.jansa@gmail.com> wrote:
>
> > Github archives are regenerated from time to time and then the checksums
> > are changed, so 3rd option is to use git fetcher with SRCREV matching the
> > has of v${PV} tag.
> >
>
> Note that Github maintain that this isn't the case for .tar.gz archives.
I've checked git log of my layers and from last 3 cases where I was
replacing github archive with git SRC_URI it was .tar.gz in two cases and
.zip in one (and they were really failing to fetch because checksums
mismatch).
They might maintain that they don't regenerate them anymore, but if you have
older recipe with checksums which were valid 2 years ago you can still
be surprised by new checksums (I was 3 times in last year by github.com,
last month from few more cases which were still using googlecode.com and
direct release URL stopped working).
Unfortunately this always happens close (or worse shortly after) our
internal release when we switch to different premirror directory and
recipes start failing to fetch.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 169 bytes --]
next prev parent reply other threads:[~2016-10-12 19:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 17:01 File conflicts in DL_DIR Phil Blundell
2016-10-12 17:30 ` Martin Jansa
2016-10-12 19:11 ` Burton, Ross
2016-10-12 19:29 ` Martin Jansa [this message]
2016-10-12 17:45 ` Christopher Larson
2016-10-12 18:03 ` Matt Madison
2016-10-13 21:03 ` Phil Blundell
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=20161012192947.GG2923@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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.