From: "Eric Bénard" <eric@eukrea.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: ushare_hg (the leading ushare recipe) does not fetch
Date: Sun, 05 Sep 2010 11:02:06 +0200 [thread overview]
Message-ID: <4C835C8E.1000008@eukrea.com> (raw)
In-Reply-To: <AANLkTi=j4E6ZLet=qemx-Ec1CaySKLCuzZMDriX9WQ=T@mail.gmail.com>
Hi Frans,
Le 05/09/2010 10:41, Frans Meulenbroeks a écrit :
> I tried to build ushare, but it fails to fetch the source.
> This source is at http://hg.geexbox.org/ushare/summary
>
> II'm not a mercurial wiz, still tried a few things, but can't seem to
> be able to resolve it.
> Can someone with more hg knowledge peek into this?
>
> Meanwhile, I suggest adding a DP of -1 to the hg version. The 1.1a
> version still builds properly.
>
does the attached patch to bitbake fix this for you ?
(you need to delete the directory in downloads :hg/hg.geexbox.org/ushare
before).
Eric
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)
next prev parent reply other threads:[~2010-09-05 9:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-05 8:41 ushare_hg (the leading ushare recipe) does not fetch Frans Meulenbroeks
2010-09-05 9:02 ` Eric Bénard [this message]
2010-09-05 9:21 ` Frans Meulenbroeks
2010-09-05 9:31 ` Eric Bénard
2010-09-06 6:25 ` Frans Meulenbroeks
2010-09-06 16:59 ` Frans Meulenbroeks
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=4C835C8E.1000008@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 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.