From: Michael Halstead <mhalstead@linuxfoundation.org>
To: Paul Eggleton <paul.eggleton@linux.intel.com>,
Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Yocto discussion list <yocto@yoctoproject.org>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: Yocto Project Status WW07'19
Date: Thu, 14 Feb 2019 01:13:39 -0800 [thread overview]
Message-ID: <6cc49be5-a9f3-bf38-2570-b12048dc4471@linuxfoundation.org> (raw)
In-Reply-To: <1634479.1jWiZZ8UfD@localhost.localdomain>
The regular 3 hour update wasn't installed on the new server. I have
repaired that and added the RRS updates as well..
The update has been run several times in testing and I'm curious if RRS
has caught up as expected.
On 2/12/19 5:57 PM, Paul Eggleton wrote:
> Hi Alex
>
> On Wednesday, 13 February 2019 6:22:23 AM NZDT Alexander Kanavin wrote:
>> On Tue, 12 Feb 2019 at 17:10, <sjolley.yp.pm@gmail.com> wrote:
>>> The recipe reporting system integration with the layer index is available
>>> at: https://layers.openembedded.org/rrs/recipes/OE-Core/2.7/M3/ and the
>>> historical data has now been imported.
>> Sadly the new RRS still seems to be suffering from the 'outdated info'
>> problem. For example glibc, or python3 recipes have been updated to
>> latest versions, yet RRS still shows that they haven't been.
> We're reliant upon the layer index updating and it appears that's not working
> at the moment. I have asked Michael to look into it. Thanks for the report,
> I'll reply back here when things are sorted out.
>
> Cheers,
> Paul
>
--
Michael Halstead
Linux Foundation / SysAdmin
next prev parent reply other threads:[~2019-02-14 9:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 16:10 Yocto Project Status WW07'19 sjolley.yp.pm
2019-02-12 17:22 ` Alexander Kanavin
2019-02-13 1:57 ` Paul Eggleton
2019-02-14 9:13 ` Michael Halstead [this message]
2019-02-14 10:27 ` Alexander Kanavin
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=6cc49be5-a9f3-bf38-2570-b12048dc4471@linuxfoundation.org \
--to=mhalstead@linuxfoundation.org \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox