From: Janne Grunau <janne-x264@jannau.net>
To: Mailing list for x264 developers <x264-devel@videolan.org>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [x264-devel] [Repo Issue] x264: Unable to find revision
Date: Wed, 4 Jun 2014 15:38:50 +0200 [thread overview]
Message-ID: <20140604133849.GG3630@jannau.net> (raw)
In-Reply-To: <4D2B74E594FF4C4A97424079247E473A17DC8258@PGSMSX104.gar.corp.intel.com>
On 2014-05-30 09:39:46 +0000, Chong, Hui Qing wrote:
> Hi, I am working on Yocto Project 1.6, Daisy branch. Previously I am able to build the image successfully, but now I have errors as follow:
>
> ERROR: Fetcher failure: Unable to find revision 585324fee380109acd9986388f857f413a60b896 in branch master even from upstream
> ERROR: Function failed: Fetcher failure for URL: 'git://git.videolan.org/x264.git'. Unable to fetch URL from any source.
>
> In the x264_git.bb file, the SRC_URI and SRCREV are:
>
> SRC_URI = "git://git.videolan.org/x264.git \
> file://don-t-default-to-cortex-a9-with-neon.patch \
> "
> SRCREV = "585324fee380109acd9986388f857f413a60b896"
>
> Does anyone notice this and is there any solution for this error? Thank you.
The git tree got rewritten, 585324fee380109acd9986388f857f413a60b896 has to
be replaced by the corrosponding hash:
ffc3ad4945da69f3caa2b40e4eed715a9a8d9526
http://sprunge.us/dGOU has a full map of old and new hashes
HTH
Janne
prev parent reply other threads:[~2014-06-04 13:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-30 9:39 [Repo Issue] x264: Unable to find revision Chong, Hui Qing
2014-06-04 13:38 ` Janne Grunau [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=20140604133849.GG3630@jannau.net \
--to=janne-x264@jannau.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=x264-devel@videolan.org \
--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.