From: "Eric Bénard" <eric@eukrea.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] bitbake: lib/bb/fetch/hg: fix fetching from a mercurial repository
Date: Mon, 06 Sep 2010 21:25:08 +0200 [thread overview]
Message-ID: <4C854014.4040001@eukrea.com> (raw)
In-Reply-To: <AANLkTi=deo+Lhpy1UCwkzi15dPuUE=6K7cx+qKaPE4t4@mail.gmail.com>
Le 06/09/2010 21:20, Frans Meulenbroeks a écrit :
> 2010/9/6 Eric Bénard<eric@eukrea.com>:
>> * without this fix, we get :
>> updating working directory
>> 74 files updated, 0 files merged, 0 files removed, 0 files unresolved
>> abort: There is no Mercurial repository here (.hg not found)!
>>
>> Signed-off-by: Eric Bénard<eric@eukrea.com>
>> Tested-by: Frans Meulenbroeks<fransmeulenbroeks@gmail.com>
>> ---
>> lib/bb/fetch/hg.py | 1 +
>> 1 files changed, 1 insertions(+), 0 deletions(-)
>>
>> diff --git a/lib/bb/fetch/hg.py b/lib/bb/fetch/hg.py
>> index d075638..bb156ed 100644
>> --- a/lib/bb/fetch/hg.py
>> +++ b/lib/bb/fetch/hg.py
>> @@ -138,6 +138,7 @@ class Hg(Fetch):
>> # Even when we clone (fetch), we still need to update as hg's clone
>> # won't checkout the specified revision if its on a branch
>> updatecmd = self._buildhgcommand(ud, d, "update")
>> + os.chdir(ud.moddir)
>> bb.msg.debug(1, bb.msg.domain.Fetcher, "Running %s" % updatecmd)
>> runfetchcmd(updatecmd, d)
>>
>> --
>> 1.6.3.3
>
> I understood from Eric that even with this patch one needs mercurial
> installed on the host.
> I did install it before, and have not tested without it, but with
> mercurial installed and this patch hg recipes (like ushare) work.
>
if mercurial is not installed on the host, the error is :
/usr/bin/env: hg: No such file or directory
Eric
prev parent reply other threads:[~2010-09-06 19:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-06 18:51 [PATCH] bitbake: lib/bb/fetch/hg: fix fetching from a mercurial repository Eric Bénard
2010-09-06 19:20 ` Frans Meulenbroeks
2010-09-06 19:25 ` Eric Bénard [this message]
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=4C854014.4040001@eukrea.com \
--to=eric@eukrea.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox