All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bas Mevissen <abuse@basmevissen.nl>
To: Arno Steffens <star@gmx.li>
Cc: poky@yoctoproject.org
Subject: Re: Yocto 2.5 and problem with pseudo-native-1.9.0
Date: Wed, 16 May 2018 11:12:43 +0200	[thread overview]
Message-ID: <1fd67bfccb82049ff75349a65d5bc81c@basmevissen.nl> (raw)
In-Reply-To: <trinity-22dc1a63-7fa8-41fd-bc2f-e011b698d3c6-1526461333500@3c-app-gmx-bs71>

On 2018-05-16 11:02, Arno Steffens wrote:
>> Gesendet: Dienstag, 15. Mai 2018 um 16:14 Uhr
>> Von: "Bas Mevissen" <abuse@basmevissen.nl>
>> An: "Arno Steffens" <star@gmx.li>
>> Cc: "Richard Purdie" <richard.purdie@linuxfoundation.org>, 
>> poky@yoctoproject.org
>> Betreff: Re: Aw: Re: [poky] Yocto 2.5 and problem with 
>> pseudo-native-1.9.0
>> 
>> On 2018-05-15 14:30, Arno Steffens wrote:
>> >> Gesendet: Dienstag, 15. Mai 2018 um 13:24 Uhr
>> >> Von: "Richard Purdie" <richard.purdie@linuxfoundation.org>
>> >> An: "Arno Steffens" <star@gmx.li>, "Bas Mevissen"
>> >> <abuse@basmevissen.nl>
>> >> Cc: poky@yoctoproject.org
>> >> Betreff: Re: [poky] Yocto 2.5 and problem with pseudo-native-1.9.0
>> >>
>> >> On Tue, 2018-05-15 at 13:17 +0200, Arno Steffens wrote:
>> >> > 
>> >> > 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?
>> >>
>> >> Try adding ";protocol=https" to the url, something like:
>> >>
>> >> git://git.yoctoproject.org/pseudo;protocol=https
>> >>
>> >> Our mirrors should have http tarballs of the git repos which should
>> >> work for this but clearly something isn't working quite correctly with
>> >> the backup archives :(. Adding https to the url should work though.
>> >>
>> >> Cheers,
>> >>
>> >> Richard
>> >>
>> >
>> > Thanks for your patience with me.
>> > Cleared the hole structure for building and even download folder and
>> > started with just
>> > bitbake pseudo-navtive
>> > but get same error again :(
>> >
>> > Regards
>> > Arno
>> >
>> > WARNING: pseudo-native-1.9.0+gitAUTOINC+fddbe854c9-r0 do_fetch: Failed
>> > to fetch URL git://git.yoctoproject.org/pseudo;protocol=https,
>> > attempting MIRRORS if available
>> > 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/yocto25/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/sp/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.5398
>> > 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 57 tasks of which 0 didn't need to be
>> > rerun and 1 failed.
>> 
>> Can you try "git clone https://git.yoctoproject.org/git/pseudo && git
>> checkout fddbe854c9db058d5a05830d3bcdd4233d95ee2e" to make sure your
>> connection is OK? I tried this here and that went fine.
>> 
>> If that works, manually copy the contents to the work directory of
>> pseudo-native and try again.
>> 
>> -- Bas.
> 
> Do be sure it has nothing to do with my project I did steps from 
> scratch.
> 
> Doing commands manually seems to work. But I have to cd into the
> cloned directory, right?

Yes, forgot to add that.

> user@vb:~/y/yocto25/tmp$ git clone 
> https://git.yoctoproject.org/git/pseudo
> Cloning into 'pseudo'...
> remote: Counting objects: 3399, done.
> remote: Compressing objects: 100% (1011/1011), done.
> remote: Total 3399 (delta 2559), reused 3208 (delta 2369)
> Receiving objects: 100% (3399/3399), 662.75 KiB | 154.00 KiB/s, done.
> Resolving deltas: 100% (2559/2559), done.
> Checking connectivity... done.
> user@vb:~/y/yocto25/tmp$ cd pseudo/
> user@vb:~/y/yocto25/tmp/pseudo$ git checkout
> fddbe854c9db058d5a05830d3bcdd4233d95ee2e
> Note: checking out 'fddbe854c9db058d5a05830d3bcdd4233d95ee2e'.
> 
> You are in 'detached HEAD' state. You can look around, make 
> experimental
> changes and commit them, and you can discard any commits you make in 
> this
> state without impacting any branches by performing another checkout.
> 
> If you want to create a new branch to retain commits you create, you 
> may
> do so (now or later) by using -b with the checkout command again. 
> Example:
> 
>   git checkout -b <new-branch-name>
> 
> HEAD is now at fddbe85... Fix symlink following errors
> 
> -------------------------
> 
> If I am doing as advices in one line command it ends up with:
> 
> git clone https://git.yoctoproject.org/git/pseudo && git checkout
> fddbe854c9db058d5a05830d3bcdd4233d95ee2e
> Cloning into 'pseudo'...
> remote: Counting objects: 3399, done.
> remote: Compressing objects: 100% (1011/1011), done.
> remote: Total 3399 (delta 2560), reused 3207 (delta 2369)
> Receiving objects: 100% (3399/3399), 662.47 KiB | 291.00 KiB/s, done.
> Resolving deltas: 100% (2560/2560), done.
> Checking connectivity... done.
> fatal: Not a git repository (or any parent up to mount point 
> /home/user/y)
> Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not 
> set).
> 
> -------------------------
> 

That line should have read:

git clone https://git.yoctoproject.org/git/pseudo && cd pseudo && git 
checkout

> Ok, but what I see even with the original recipe (git), I get the git
> repo (see it in
> /home/user/y/yocto25/build/downloads/git2/git.yoctoproject.org.pseudo)
> but it keeps in head and doesn't checkout this special tag?!?
> 
> So again, warning is just the warning - obviously it gets data from
> mirror. The "checkout" doesn't work.
> 

If the mirror is not current, it does not contain commit 
fddbe854c9db058d5a05830d3bcdd4233d95ee2e, which is at the HEAD of the 
master branch.

> And I don't know what and where to copy things manually and "fake"
> that this step has been succesful.


Assuming you made the protocol=https addition as suggested by Richard in 
the right place, I would say that

bitbake -c cleanall pseudo-native
bitbake pseudo-native

should do the trick.

Regards,

Bas.


  reply	other threads:[~2018-05-16  9:12 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
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 [this message]
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=1fd67bfccb82049ff75349a65d5bc81c@basmevissen.nl \
    --to=abuse@basmevissen.nl \
    --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.