From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Arno Steffens <star@gmx.li>,
"poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: Yocto 2.5 and problem with pseudo-native-1.9.0
Date: Tue, 15 May 2018 10:11:17 +0000 [thread overview]
Message-ID: <28b5dd854c864d1fa0149916706f2434@XBOX02.axis.com> (raw)
In-Reply-To: <trinity-fe84c674-2df9-449b-8b6a-53f1b7cf21d2-1526375104797@3c-app-gmx-bs15>
> -----Original Message-----
> From: poky-bounces@yoctoproject.org [mailto:poky-
> bounces@yoctoproject.org] On Behalf Of Arno Steffens
> Sent: den 15 maj 2018 11:05
> To: poky@yoctoproject.org
> Subject: [poky] Yocto 2.5 and problem with pseudo-native-1.9.0
>
> I get an error while building my rootfs, but doesn't have a clue what
> the error message will tell me:
> below:
>
> Same with the log file, I don't get the point. How can I understand
> this better?
>
> ERROR: pseudo-native-1.9.0+gitAUTOINC+fddbe854c9-r0 do_unpack: Fetcher
> failure: Fetch command export PSEUDO_DISABLED=1; export
> DBUS_SESSION_BUS_ADDRESS="unix:abstract=/tmp/dbus-
> qFLYbSsFJF,guid=c8cffdaaccadb737f94547ed5afa68f2"; export
> SSH_AGENT_PID="1886"; export
> SSH_AUTH_SOCK="/run/user/1000/keyring/ssh"; export
> PATH="/home/user/y/yocto25/poky/scripts/native-
> intercept:/home/user/y/yocto25/sp/tmp/sysroots-uninative/x86_64-
> linux/usr/bin:/home/user/y/yocto25/poky/scripts:/home/user/y/yocto25/sp
> /tmp/work/x86_64-linux/pseudo-native/1.9.0+gitAUTOINC+fddbe854c9-
> r0/recipe-sysroot-native/usr/bin/x86_64-
> linux:/home/user/y/yocto25/sp/tmp/work/x86_64-linux/pseudo-
> native/1.9.0+gitAUTOINC+fddbe854c9-r0/recipe-sysroot-
> native/usr/bin:/home/user/y/yocto25/sp/tmp/work/x86_64-linux/pseudo-
> native/1.9.0+gitAUTOINC+fddbe854c9-r0/recipe-sysroot-
> native/usr/sbin:/home/user/y/yocto25/sp/tmp/work/x86_64-linux/pseudo-
> native/1.9.0+gitAUTOINC+fddbe854c9-r0/recipe-sysroot-
> native/usr/bin:/home/user/y/yocto
> 25/sp/tmp/work/x86_64-linux/pseudo-native/1.9.0+gitAUTOINC+fddbe854c9-
> r0/recipe-sysroot-native/sbin:/home/user/y/yocto25/sp/tmp/work/x86_64-
> linux/pseudo-native/1.9.0+gitAUTOINC+fddbe854c9-r0/recipe-sysroot-
> native/bin:/home/user/y/yocto25/poky/bitbake/bin:/home/user/y/yocto25/s
> p/tmp/hosttools"; export HOME="/home/user"; git -c
> core.fsyncobjectfiles=0 checkout -B master
> fddbe854c9db058d5a05830d3bcdd4233d95ee2e failed with exit code 128,
> output:
> fatal: reference is not a tree:
> fddbe854c9db058d5a05830d3bcdd4233d95ee2e
>
> ERROR: pseudo-native-1.9.0+gitAUTOINC+fddbe854c9-r0 do_unpack: Function
> failed: base_do_unpack
> ERROR: Logfile of failure stored in:
> /home/user/y/yocto25/sp/tmp/work/x86_64-linux/pseudo-
> native/1.9.0+gitAUTOINC+fddbe854c9-r0/temp/log.do_unpack.14717
> ERROR: Task (virtual:native:/home/user/y/yocto25/poky/meta/recipes-
> devtools/pseudo/pseudo_git.bb:do_unpack) failed with exit code '1'
> NOTE: Tasks Summary: Attempted 154 tasks of which 151 didn't need to be
> rerun and 1 failed.
Your Git clone of the pseudo repository is missing the fddbe854 commit.
This can happen if there has been any problems when updating the repository.
Try `bitbake pseudo-native -c cleanall && bitbake pseudo-native` which
should give you a fresh clone.
//Peter
next prev parent reply other threads:[~2018-05-15 10:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 9:05 Yocto 2.5 and problem with pseudo-native-1.9.0 Arno Steffens
2018-05-15 10:11 ` Peter Kjellerstedt [this message]
2018-05-15 10:43 ` Arno Steffens
2018-05-15 10:50 ` Bas Mevissen
2018-05-15 11:17 ` Arno Steffens
2018-05-15 11:24 ` Richard Purdie
2018-05-15 12:30 ` Arno Steffens
2018-05-15 14:14 ` Bas Mevissen
2018-05-16 9:02 ` Arno Steffens
2018-05-16 9:12 ` Bas Mevissen
2018-05-16 10:22 ` Arno Steffens
2018-05-16 14:05 ` Arno Steffens
2018-05-16 14:41 ` Bas Mevissen
2018-05-17 6:58 ` Arno Steffens
2018-05-17 7:33 ` Bas Mevissen
2018-05-17 10:35 ` Arno Steffens
2018-05-17 10:32 ` Alexander Kanavin
2018-05-17 10:49 ` Bas Mevissen
[not found] ` <ba4fc516-f02d-683e-2fb7-0a8441cae5cf@linuxfoundation.org>
2018-05-16 21:43 ` Richard Purdie
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=28b5dd854c864d1fa0149916706f2434@XBOX02.axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=poky@yoctoproject.org \
--cc=star@gmx.li \
/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.