All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Müller" <schnitzeltony@googlemail.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: Openembedded layer index stopped updating
Date: Wed, 18 Jan 2017 00:20:03 +0100	[thread overview]
Message-ID: <CALbNGRS19rA8k=awGLH3p=MKoV+vtqH0BhjF2yhGcANYym7MSA@mail.gmail.com> (raw)
In-Reply-To: <70703025.YBBEieGfxA@peggleto-mobl.ger.corp.intel.com>

On Tue, Jan 17, 2017 at 11:21 PM, Paul Eggleton
<paul.eggleton@linux.intel.com> wrote:
> On Fri, 13 Jan 2017 11:02:20 Andreas Müller wrote:
>> On Fri, Jan 13, 2017 at 9:55 AM, Paul Eggleton
>> <paul.eggleton@linux.intel.com> wrote:
>> > On Fri, 13 Jan 2017 08:56:47 Andreas Müller wrote:
>> >> again me... sorry but I use index regularly to check if somebody else
>> >> already created a recipe I am interested in.
>> >>
>> >> I think it was caused by maintenance changes.
>> >
>> > You're right, we have just done an upgrade and as a result we are
>> > currently dealing with an issue updating the index, as yet I don't know
>> > what has caused it exactly because we aren't actually seeing any errors -
>> > the update process only manages to update some of the layers before it
>> > stalls and then eventually gets killed. We're working on it, apologies for
>> > the inconvenience.
>>
>> Thanks and there is no inconvenience - was just a ping
>
> FYI everything should be back to a working state now. I'll send a separate
> email describing recent enhancements.
>
> Cheers,
> Paul
>
Thanks a lot!

Andreas


      reply	other threads:[~2017-01-17 23:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-13  7:56 Openembedded layer index stopped updating Andreas Müller
2017-01-13  8:55 ` Paul Eggleton
2017-01-13 10:02   ` Andreas Müller
2017-01-17 22:21     ` Paul Eggleton
2017-01-17 23:20       ` Andreas Müller [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='CALbNGRS19rA8k=awGLH3p=MKoV+vtqH0BhjF2yhGcANYym7MSA@mail.gmail.com' \
    --to=schnitzeltony@googlemail.com \
    --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 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.