All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Arno Steffens" <star@gmx.li>
To: "Bas Mevissen" <abuse@basmevissen.nl>
Cc: poky@yoctoproject.org
Subject: Re: Yocto 2.5 and problem with pseudo-native-1.9.0
Date: Tue, 15 May 2018 13:17:28 +0200	[thread overview]
Message-ID: <trinity-c6098955-a734-46bf-a321-e8d24473dc5d-1526383048370@3c-app-gmx-bs12> (raw)
In-Reply-To: <63ef6b8aff254ed7dc38d9bee7623d4d@basmevissen.nl>



> Gesendet: Dienstag, 15. Mai 2018 um 12:50 Uhr
> Von: "Bas Mevissen" <abuse@basmevissen.nl>
> An: "Arno Steffens" <star@gmx.li>
> Cc: "Peter Kjellerstedt" <peter.kjellerstedt@axis.com>, poky@yoctoproject.org
> Betreff: Re: [poky] Yocto 2.5 and problem with pseudo-native-1.9.0
>
> On 2018-05-15 12:43, Arno Steffens wrote:
> >> Gesendet: Dienstag, 15. Mai 2018 um 12:11 Uhr
> >> Von: "Peter Kjellerstedt" <peter.kjellerstedt@axis.com>
> >> An: "Arno Steffens" <star@gmx.li>, "poky@yoctoproject.org" 
> >> <poky@yoctoproject.org>
> >> Betreff: RE: [poky] Yocto 2.5 and problem with pseudo-native-1.9.0
> >> 
> >> > -----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
> > 
> > Thanks Peter,
> > I am still confused.
> > 
> > While bitbake I get a warning:
> > WARNING: pseudo-native-1.9.0+gitAUTOINC+fddbe854c9-r0 do_fetch: Failed
> > to fetch URL git://git.yoctoproject.org/pseudo, attempting MIRRORS if
> > available
> > 
> > Looking into recipe the only source given for it is GIT. GIT is
> > blocked in my company network :( - don't ask my why.
> 
> That will make your life as developer with open source quite difficult 
> :-(
> 
> > Usually this is no problem, as sources are also available via http(s).
> 
> You can change the source to use https://git.yoctoproject.org/git/pseudo 
> instead. Not ideal, but it gets you going.
> 
> > And I see in the
> > 
> > /home/user/y/yocto25/sp/tmp/work/x86_64-linux/pseudo-native/1.9.0+gitAUTOINC+fddbe854c9-r0
> > 
> > folder a lot of files in the git subfolder ....
> > A
> > bitbake pseudo-native -c cleanall
> > bitbake pseudo-native
> > 
> > creates same error again :(
> > Arno
> 
> That was to be expected if no other source than git (protocol) is given.
> 
> -- Bas.

Dear Bas,

Yeah - I know, I am handicapped  :(
But a change from 
git://git.yoctoproject.org/pseudo
to
https://git.yoctoproject.org/git/pseudo
doesn't solve the issue.

Compared to yocto 2.3 and 2.4 I miss in the recipes a file like
pseudo_1.8.2.bb

Now there is just
pseudo_git.bb
and 
pseudo.inc

Also in the download I found a file:
git2_git.yoctoproject.org.pseudo.tar.gz.done

Do we dig at wrong side?


  reply	other threads:[~2018-05-15 11:17 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
2018-05-15 10:43   ` Arno Steffens
2018-05-15 10:50     ` Bas Mevissen
2018-05-15 11:17       ` Arno Steffens [this message]
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=trinity-c6098955-a734-46bf-a321-e8d24473dc5d-1526383048370@3c-app-gmx-bs12 \
    --to=star@gmx.li \
    --cc=abuse@basmevissen.nl \
    --cc=poky@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.