From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 4EBF7E00405; Fri, 13 Jan 2017 00:56:06 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -2.3 RCVD_IN_DNSWL_MED RBL: Sender listed at http://www.dnswl.org/, * medium trust * [134.134.136.20 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id EAB0BE003C1; Fri, 13 Jan 2017 00:56:05 -0800 (PST) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga101.jf.intel.com with ESMTP; 13 Jan 2017 00:56:04 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,221,1477983600"; d="scan'208";a="1093580564" Received: from hhteoh-mobl1.gar.corp.intel.com (HELO peggleto-mobl.ger.corp.intel.com) ([10.255.157.122]) by fmsmga001.fm.intel.com with ESMTP; 13 Jan 2017 00:55:38 -0800 From: Paul Eggleton To: Andreas =?ISO-8859-1?Q?M=FCller?= Date: Fri, 13 Jan 2017 21:55:35 +1300 Message-ID: <2102802.MZXjXepLX7@peggleto-mobl.ger.corp.intel.com> Organization: Intel Corporation User-Agent: KMail/4.14.10 (Linux/4.8.13-100.fc23.x86_64; KDE/4.14.20; x86_64; ; ) In-Reply-To: References: MIME-Version: 1.0 Cc: yocto@yoctoproject.org Subject: Re: Openembedded layer index stopped updating X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jan 2017 08:56:06 -0000 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" Hi Andreas, On Fri, 13 Jan 2017 08:56:47 Andreas M=FCller wrote: > again me... sorry but I use index regularly to check if somebody else= > already created a recipe I am interested in. >=20 > I think it was caused by maintenance changes. You're right, we have just done an upgrade and as a result we are curre= ntly=20 dealing with an issue updating the index, as yet I don't know what has = caused=20 it exactly because we aren't actually seeing any errors - the update pr= ocess=20 only manages to update some of the layers before it stalls and then eve= ntually=20 gets killed. We're working on it, apologies for the inconvenience. Cheers, Paul --=20 Paul Eggleton Intel Open Source Technology Centre