From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: poky@yoctoproject.org
Subject: Re: Workaround for fetching files
Date: Fri, 27 May 2016 16:59:25 +0300 [thread overview]
Message-ID: <574852BD.3050200@linux.intel.com> (raw)
In-Reply-To: <trinity-200ddab3-0fb2-41ea-8c38-37f5f1195f5e-1464356891340@3capp-gmx-bs01>
On 05/27/2016 04:48 PM, Arno wrote:
> My question: Can I download some files that gives errors fetching during the build process and a new bitbake will recognise it? Probably it is not so simple, due to all this fancy stuff with timestamps .....
> But - is there a way?
>
> I am in a company network, due to strict rules I am often faced with problems fetching file.
> So I am not able to use git protocol, most http(s) is the workaround.
>
> Sometimes I can access files by browser (sources.openembedded.org/git2_git.yoctoproject.org.yocto-kernel-tools.git.tar.gz)
> but the yocto build process can't and gives errors.
Did you study this?
https://wiki.yoctoproject.org/wiki/Working_Behind_a_Network_Proxy
Alex
next prev parent reply other threads:[~2016-05-27 13:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-27 13:48 Workaround for fetching files Arno
2016-05-27 13:59 ` Alexander Kanavin [this message]
2016-05-30 8:49 ` Arno
2016-06-01 11:36 ` 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=574852BD.3050200@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=poky@yoctoproject.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.