From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Michael Halstead <mhalstead@linuxfoundation.org>, poky@yoctoproject.org
Subject: Re: Yocto 2.5 and problem with pseudo-native-1.9.0
Date: Wed, 16 May 2018 22:43:26 +0100 [thread overview]
Message-ID: <1526507006.8937.21.camel@linuxfoundation.org> (raw)
In-Reply-To: <ba4fc516-f02d-683e-2fb7-0a8441cae5cf@linuxfoundation.org>
On Wed, 2018-05-16 at 14:12 -0700, Michael Halstead wrote:
>
> On 05/16/2018 07:05 AM, Arno Steffens wrote:
> >
> > Checking the log file it seem that a file is missing in Yocto
> > project:
> >
> > https://git.yoctoproject.org/pseudo/
> >
> > And the file that is downloaded ...
> > http://downloads.yoctoproject.org/mirror/sources/git2_git.yoctoproj
> > ect.org.pseudo.tar.gz
> > .. it has not .git folder and it has been compressed (date in file
> > is July 2016)
> These sources are preserved once uploaded to prevent the copy used in
> the initial (working) from being overwritten by corrupt/altered
> copies
> in the future. Back when this was set up the sources pretty much all
> had
> version numbers in the file name so it worked well.
>
> I don't know what should happen with this file.
That is a problem as these files do change as new revisions get added
to the repositories. We do need to updated the git2_* files with newer
files which should in theory just contain more data. We'd need to make
the updates atomic (mv the files into place).
Cheers,
Richard
prev parent reply other threads:[~2018-05-16 21:43 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
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 [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=1526507006.8937.21.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=mhalstead@linuxfoundation.org \
--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.