From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH] vim: add checksum
Date: Sun, 22 Mar 2015 16:55:13 +0100 [thread overview]
Message-ID: <20150322155513.GN4738@jama> (raw)
In-Reply-To: <550E94BF.50908@videolan.org>
[-- Attachment #1: Type: text/plain, Size: 1974 bytes --]
On Sun, Mar 22, 2015 at 11:09:03AM +0100, Rafaël Carré wrote:
> Hello,
>
> I couldn't reproduce the checksum error with a fresh build with an empty
> downloads/ folder.
>
> So this patch is apparently needed only when populating downloads/
> folder before fetching vim.
>
> I will investigate a bit more, I think the patch should actually be in
> bitbake
> (missing supports_checksum for Hg.py)
Should bitbake support checksums for hg? We don't use them for any other
SCM like git or svn, if we do that for hg, what will be included in th
checksum? Whole directory with hg checkout? Is it stable (e.g. doesn't
hg fetch everything and then checkout required revision like git does?)
I've included this patch in master-next, but now when I see that it's
fetched from hg I'll drop it.
> On 03/20/2015 03:20 PM, Rafaël Carré wrote:
> > ---
> > meta-oe/recipes-support/vim/vim_7.4.481.bb | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/meta-oe/recipes-support/vim/vim_7.4.481.bb b/meta-oe/recipes-support/vim/vim_7.4.481.bb
> > index afdea84..ac59077 100644
> > --- a/meta-oe/recipes-support/vim/vim_7.4.481.bb
> > +++ b/meta-oe/recipes-support/vim/vim_7.4.481.bb
> > @@ -10,6 +10,10 @@ SRC_URI = "hg://vim.googlecode.com/hg/;protocol=https;module=vim \
> > file://disable_acl_header_check.patch;patchdir=.. \
> > file://vim-add-knob-whether-elf.h-are-checked.patch;patchdir=.. \
> > "
> > +
> > +SRC_URI[md5sum] = "5fd5d754581a673a25733c12367cf9d2"
> > +SRC_URI[sha256sum] = "e2cc416dabea503e9e5631afc21bb00dcbfb9d05481641b75f247fd89ff4d7e8"
> > +
> > SRCREV = "v7-4-481"
> >
> > S = "${WORKDIR}/vim/src"
> >
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2015-03-22 15:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 14:20 [meta-oe][PATCH] vim: add checksum Rafaël Carré
2015-03-22 10:09 ` Rafaël Carré
2015-03-22 15:55 ` Martin Jansa [this message]
2015-03-22 17:23 ` Rafaël Carré
2015-04-27 10:51 ` Martin Jansa
2015-05-22 15:39 ` [PATCH] fetch/hg: Disable checksums for archived downloads Ash Charles
2015-05-22 15:39 ` Ash Charles
2015-05-29 1:49 ` [oe] " Robert Yang
2015-05-29 1:49 ` Robert Yang
2015-05-29 5:46 ` [oe] " Ash Charles
2015-05-29 5:46 ` [bitbake-devel] " Ash Charles
2015-05-29 9:18 ` [oe] " Martin Jansa
2015-05-29 9:18 ` [bitbake-devel] " Martin Jansa
2015-06-02 0:08 ` [oe] " Ash Charles
2015-06-02 0:08 ` [bitbake-devel] " Ash Charles
2015-06-02 4:38 ` [oe] " Robert Yang
2015-06-02 4:38 ` [bitbake-devel] " Robert Yang
2015-08-06 10:54 ` [oe] " Steffen Sledz
2015-08-06 10:54 ` [bitbake-devel] " Steffen Sledz
-- strict thread matches above, loose matches on Subject: below --
2015-03-20 14:15 [meta-oe][PATCH] vim: add checksum Rafaël Carré
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=20150322155513.GN4738@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@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.