From: nick <xerofoify@gmail.com>
To: Sven Ebenfeld <sven.ebenfeld@gmail.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: Angstrom Build Failing
Date: Fri, 31 Oct 2014 14:41:13 -0400 [thread overview]
Message-ID: <5453D7C9.2040805@gmail.com> (raw)
In-Reply-To: <CAD0=qkKpRpoP_uuYiSdGNrN+SyrJy_sFkCw+iJhPfM7UdrWNCQ@mail.gmail.com>
Thanks Sven,
I will git pull later and see if it's up again just wasn't sure if this was
a network error or a misconfiguration on my part.
Cheers Nick
On 14-10-31 02:29 PM, Sven Ebenfeld wrote:
> It looks like meta-kde on gitorious is currently down. Manually cloning its
> mirror on github in sources directory worked for me.
> Am 31.10.2014 18:49 schrieb "nick" <xerofoify@gmail.com>:
>
>> Greetings,
>> I am getting a failing build after cloning the angstrom build scripts. My
>> build log is pasted below.
>> Cheers Nick
>> nick@nick-System-Product-Name:/media/nick/Build_Drive/setup-scripts$
>> MACHINE=beaglebone ./oebb.sh update
>> Processing bitbake: Current branch 1.20 is up to date.
>> Processing meta-angstrom: Current branch angstrom-v2013.12-yocto1.5 is up
>> to date.
>> Processing meta-openembedded: Current branch angstrom-staging-yocto1.5 is
>> up to date.
>> Processing meta-beagleboard: Current branch dora is up to date.
>> Processing meta-ti: Current branch angstrom-staging-yocto1.5 is up to date.
>> Processing meta-ettus: Fixed to revision
>> 5a6a642f6707dc42a5210dbbf01d2bdfd869d4b0, skipping update
>> Processing meta-fsl-arm: Current branch angstrom-staging-yocto1.5 is up to
>> date.
>> Processing meta-fsl-arm-extra: Current branch dora is up to date.
>> Processing meta-nslu2: Fixed to revision
>> bdcb4297ddb22f4eecddd4d8436cf9b6c6111922, skipping update
>> Processing meta-smartphone: Fixed to revision
>> 537d0c2ab41284012e1ba79716b085a861a6812a, skipping update
>> Processing meta-intel: Current branch dora is up to date.
>> Processing meta-xilinx: Fixed to revision
>> 21c3cd3f058d736742ebc23a7a954f23456fbea5, skipping update
>> Processing meta-openpandora: Fixed to revision
>> 53ad3e60e4ed4fc7b946a2130da4bb9a8671341c, skipping update
>> Processing meta-raspberrypi: Current branch dora is up to date.
>> Processing meta-atmel: Current branch angstromv2013.12-staging is up to
>> date.
>> Processing meta-handheld: Fixed to revision
>> 5b5e68a93aae1016f5ac1d057a721b2dbf30b8d8, skipping update
>> Processing meta-opie: Fixed to revision
>> b241408b31c2ffd941b8b38bd385136ef675a703, skipping update
>> Processing meta-java: Current branch dora is up to date.
>> Processing meta-browser: Fixed to revision
>> fc3969f63bda343c38c40a23f746c560c4735f3e, skipping update
>> Processing meta-mono: Fixed to revision
>> ac286b1682e6bcc486ceb30ef90a936949bbfeab, skipping update
>> layer repository name: meta-kde
>> layer uri: git://gitorious.org/openembedded-core-layers/meta-kde.git
>> layer branch/revision: master/f45abfd4d87b0132a2565499392d2d49f465d847
>>
>> Layer checkout missing at
>> /media/nick/Build_Drive/setup-scripts/sources/meta-kde, creating one
>> Cloning into '/media/nick/Build_Drive/setup-scripts/sources/meta-kde'...
>> fatal: protocol error: expected sha/ref, got '
>> ----------------------------------------------
>> Cannot find repository /openembedded-core-layers/meta-kde.git
>> ----------------------------------------------'
>> /media/nick/Build_Drive/setup-scripts/scripts/layerman: line 19: cd:
>> /media/nick/Build_Drive/setup-scripts/sources/meta-kde: No such file or
>> directory
>> fatal: Could not parse object 'f45abfd4d87b0132a2565499392d2d49f465d847'.
>> Layers present in repository:
>> find: `/media/nick/Build_Drive/setup-scripts/sources/meta-kde': No such
>> file or directory
>>
>> Processing meta-kde:
>> /media/nick/Build_Drive/setup-scripts/scripts/layerman: line 79: cd:
>> /media/nick/Build_Drive/setup-scripts/sources/meta-kde: No such file or
>> directory
>> Processing meta-linaro: Current branch dora is up to date.
>> Processing meta-minnow: Current branch dora is up to date.
>> Processing meta-sunxi: Fixed to revision
>> f1e777d5526ea7c7a4f3a828b21d26c2c0650b83, skipping update
>> Processing meta-qt5: Current branch dora is up to date.
>> Processing meta-ros: Fixed to revision
>> 64c8b5edb221263e7fac7c03629c730ade422dff, skipping update
>> Processing meta-uav: Fixed to revision
>> 6f663cc32532ae66dd6c06d3d79c0f3578975a6c, skipping update
>> Processing meta-dominion: Current branch master is up to date.
>> Processing meta-exynos: Fixed to revision
>> ac21b106ce5c4c928f62e8f72ebeac9b02d113e2, skipping update
>> Processing meta-telephony: Fixed to revision
>> f71f5ea031d96a5a84bde4531974542ae49f8bee, skipping update
>> Processing meta-qt5: Current branch dora is up to date.
>> Processing openembedded-core: Current branch angstrom-staging-yocto1.5 is
>> up to date.
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>
next prev parent reply other threads:[~2014-10-31 18:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 17:44 Angstrom Build Failing nick
2014-10-31 18:29 ` Sven Ebenfeld
2014-10-31 18:41 ` nick [this message]
2014-11-05 12:52 ` Samuel Stirtzel
2014-11-05 13:01 ` nick
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=5453D7C9.2040805@gmail.com \
--to=xerofoify@gmail.com \
--cc=sven.ebenfeld@gmail.com \
--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.