All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: bitbake-devel@lists.openembedded.org,
	Horace Cheung <Horace.Cheung@Arthrex.com>
Cc: "joe_macdonald@mentor.com" <joe_macdonald@mentor.com>,
	Geoffrey Parker <Geoffrey.Parker@Arthrex.com>,
	"rongqing.li@windriver.com" <rongqing.li@windriver.com>
Subject: [1.26][backport-request] Mercurial fetcher fix Was: Inquiry about why vim_7.4.481.bb doesn't have checksum
Date: Mon, 27 Jul 2015 20:02:26 +0200	[thread overview]
Message-ID: <20150727180226.GF307@jama> (raw)
In-Reply-To: <A25829B3236F8A42BEC026E5505D82F31C81E5@inc-s-exc001.arthrex.local>

[-- Attachment #1: Type: text/plain, Size: 5071 bytes --]

On Mon, Jul 27, 2015 at 04:12:56PM +0000, Horace Cheung wrote:
> Martin,
> 
> I have 1 more request. We're currently using fido branch to prototype & test OE our build system migration. Since this is only 1 file change (lib/bb/fetch2/hg.py): https://github.com/openembedded/bitbake/commit/378647281ae883dd726f1e1b775dd35ef6a0e8d1
> 
> Is there anyway you can cherry-pick this change back to fido branch so that all future poky download (https://www.yoctoproject.org/downloads/yocto-project) can include this change then? (if there is any procedure I can help to make this happen, pls let me know and I can make it happen as well :)). 

This belongs to bitbake-devel ML with [1.26] tag.

I believe it's this commit which fixes your issue:
commit 0e2f7e7663309daa46716e274fd85e9011120a7f
Author: Ash Charles <ashcharles@gmail.com>
Date:   Fri May 22 08:39:30 2015 -0700

    fetch/hg: Disable checksums for archived downloads

Please test it in your environment and confirm, if it's not enough, then
there are 3 more mercurial fetcher commits in bitbake/master which are missing in 1.26:

3786472 bitbake: fetch2/hg.py: fix unpack error and mirror tarball
2df35a2 fetch/hg: Disable checksums for archived downloads
0276330 fetch2/hg.py: add clean function
f002b1c fetch/hg: support submodules

Regards,

> 
> Thanks!
> Horace
> ________________________________________
> From: Horace Cheung
> Sent: Monday, July 27, 2015 8:43 AM
> To: Martin Jansa
> Cc: rongqing.li@windriver.com; joe_macdonald@mentor.com; Geoffrey Parker
> Subject: RE: Inquiry about why vim_7.4.481.bb doesn't have checksum
> 
> Thanks Martin. I'll check the commit history of mercurial fetcher in bitbake and update the bitbake version and retest then.
> 
> Regards,
> Horace
> 
> ________________________________________
> From: Martin Jansa [martin.jansa@gmail.com]
> Sent: Sunday, July 26, 2015 3:31 PM
> To: Horace Cheung
> Cc: rongqing.li@windriver.com; joe_macdonald@mentor.com; Geoffrey Parker
> Subject: Re: Inquiry about why vim_7.4.481.bb doesn't have checksum
> 
> On Mon, Jul 20, 2015 at 11:58:49PM +0000, Horace Cheung wrote:
> > Hello Rong, Joe and Martin,
> >
> > This is Horace Cheung (DevOps engineer) from Arthrex. We're currently working to transition using poky as the latest bulld version. During our prototype build test, we've encountered a specific checksum error message on VIM package:
> >
> > ERROR: No checksum specified for /home/horace/sw-dev/yocto/poky/build/downloads/vim_vim.googlecode.com_.hg._v7-4-481.tar.gz, please add at least one to the recipe:
> > SRC_URI[md5sum] = "16591d520c75375570db53101afd48c9"
> > SRC_URI[sha256sum] = "c9120bdf0701eec9c3cfec9a16c783f68fe24708aa58b25979304271f190dbad"
> > ERROR: Function failed: Fetcher failure for URL: 'http://downloads.yoctoproject.org/mirror/sources/vim_vim.googlecode.com_.hg._v7-4-481.tar.gz;protocol=https;module=vim'. Missing SRC_URI checksum
> > ERROR: Logfile of failure stored in: /home/horace/sw-dev/yocto/poky/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/vim/7.4.481-r0/temp/log.do_fetch.5797
> > ERROR: Task 645 (/home/horace/sw-dev/yocto/poky/meta-openembedded/meta-oe/recipes-support/vim/vim_7.4.481.bb, do_fetch) failed with exit code '1'
> >
> > Can you guys clarify why for this specific recipe, there is no need to capture the md5sum & sha256sum (i.e. SRC_URI[xxx]) into the recipe? What's the recommendation from the upstream community to get rid of this error without specifying the SRC_URI checksum into the recipe?
> 
> All recipes with SRC_URI pointing to some SCM aren't using checksums.
> 
> mercurial fetcher in bitbake was broken for a while, you need to upgrade
> bitbake to get the fix for mercurial fetcher incorrectly requiring the
> checksums.
> 
> >
> > Thanks & Best Regards,
> > Horace Cheung
> > 460 Ward Drive, Santa Barbara, CA 93111
> > horace.cheung@Arthrex.com | Office: (800) 933 – 7001 ext. 79206 | Cell: (805) 403 – 5712
> >
> > This e-mail and any files transmitted with it are the property of Arthrex, Inc. and/or its affiliates, are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender at 239-643-5553 and delete this message immediately from your computer. Any other use, retention, dissemination forwarding, printing or copying of this e-mail is strictly prohibited. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, while Arthrex uses virus protection, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
> 
> --
> Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

           reply	other threads:[~2015-07-27 18:02 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <A25829B3236F8A42BEC026E5505D82F31C81E5@inc-s-exc001.arthrex.local>]

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=20150727180226.GF307@jama \
    --to=martin.jansa@gmail.com \
    --cc=Geoffrey.Parker@Arthrex.com \
    --cc=Horace.Cheung@Arthrex.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=joe_macdonald@mentor.com \
    --cc=rongqing.li@windriver.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.