From: Darren Hart <dvhart@linux.intel.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: the proper way to report bitbake fetch errors?
Date: Fri, 15 Jul 2011 11:22:56 -0700 [thread overview]
Message-ID: <4E208580.3030505@linux.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1107141957320.4687@localhost6.localdomain6>
On 07/14/2011 05:01 PM, Robert P. J. Day wrote:
>
> just so i'm doing this the right way, what is the appropriate way to
> report bitbake fetch errors? with a fully-updated git repo, i just
> ran:
>
> $ bitbake -c fetchall -k core-image-sato
>
> and got fetch errors for both of:
>
> * sat-solver
> * linux-libc-headers
>
> should i post the more detailed output of the command? the contents
> of the log files? etc, etc.
I would check the log files and verify it isn't a local network issue.
After that, sharing the relevant bits of the log.do_fetch logs for the
failed recipes is a good way to report them.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2011-07-15 18:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 0:01 the proper way to report bitbake fetch errors? Robert P. J. Day
2011-07-15 18:22 ` Darren Hart [this message]
2011-07-15 19:12 ` Robert P. J. Day
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=4E208580.3030505@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=rpjday@crashcourse.ca \
--cc=yocto@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.