From: Olof Johansson <olof.johansson@axis.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Peter Kjellerstedt <pkj@axis.com>,
"bitbake-devel@lists.openembedded.org"
<bitbake-devel@lists.openembedded.org>
Subject: Re: [PATCH 1/1] bitbake: Disable pseudo in runfetchcmd()
Date: Fri, 21 Mar 2014 09:27:23 +0100 [thread overview]
Message-ID: <20140321082723.GC16597@axis.com> (raw)
In-Reply-To: <1395328459.3808.180.camel@ted>
Thanks for you quick reply,
On 14-03-20 16:14 +0100, Richard Purdie wrote:
> The log helps immensely since it shows its "Failure expanding variable
> do_patch" so its not running do_patch, it is trying to expand the
> variable for some reason when writing the rpm in do_package_write_rpm.
>
> Are you generating some kind of srpm differently from the normal
> usecases?
No we don't, as far as I know (is there something I should look
for?). If this isn't something we are doing, what makes it a
problem for us is the fetching of kernel sources from git over
ssh with key authentication. Not sure how common that is.
--
olofjn
next prev parent reply other threads:[~2014-03-21 8:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 14:55 [PATCH 0/1] Avoid problem with Git fetcher hanging Peter Kjellerstedt
2014-02-20 14:55 ` [PATCH 1/1] bitbake: Disable pseudo in runfetchcmd() Peter Kjellerstedt
2014-02-20 15:42 ` Mark Hatle
2014-02-22 11:24 ` Richard Purdie
2014-03-20 15:03 ` Olof Johansson
2014-03-20 15:14 ` Richard Purdie
2014-03-21 8:27 ` Olof Johansson [this message]
2014-03-22 10:12 ` Richard Purdie
2014-03-24 12:45 ` Olof Johansson
-- strict thread matches above, loose matches on Subject: below --
2014-02-21 10:10 Peter Kjellerstedt
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=20140321082723.GC16597@axis.com \
--to=olof.johansson@axis.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=pkj@axis.com \
--cc=richard.purdie@linuxfoundation.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.