All of lore.kernel.org
 help / color / mirror / Atom feed
From: Klaus Schwarzkopf <schwarzkopf@sensortherm.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: I've downloaded oe
Date: Thu, 25 Nov 2010 12:58:25 +0100	[thread overview]
Message-ID: <4CEE4F61.3060401@sensortherm.de> (raw)
In-Reply-To: <AANLkTinhykFBHcgJR5suXU8Q7op+FOxofExY-d42XmYw@mail.gmail.com>

Am 23.11.2010 21:19, schrieb Khem Raj:
> On Tue, Nov 23, 2010 at 12:03 PM, Klaus Schwarzkopf
> <schwarzkopf@sensortherm.de>  wrote:
>> Hi,
>>
>> i've downloaded oe with this script (thanks frans):
>>
>> #!/bin/sh
>>
>> export OE=/home/klaus/development/oe/
>> export BBPATH=${OE}build:${OE}openembedded
>> export PATH=${OE}bitbake/bin:${PATH}
>> export MACHINE=dm355-evm
>>
>> RECIPES="${OE}/openembedded/recipes"
>> LOGFILE="fetchsrc.log"
>>
>> #Find recipes how changed this week
>> #FIND_OPTIONS="-atime 7"
>>
>> for i in $(find ${RECIPES} -name '*.bb' -type f ${FIND_OPTIONS} | sort )
>> do
>>         echo $i
>>         bitbake -c fetch -b $i
>> done>  ${LOGFILE} 2>&1
>>
>> egrep -n 'ERROR.*bb..failed' ${LOGFILE}
>> egrep -n 'KeyError' ${LOGFILE}
>>
>>
>>
>>
>>
>> I found a lot of errors, see attachment! The whole logfile is on my
>> homepage:
>> http://fbi.hooster.de/download/sonstiges/oe/fetchsrc.log.tar.gz
>>
>> How can i/we fix this errors?
>>
>
> You should ignore nonworking and obsolete dirs and some errors are due
> to hh.org going AWOL too
>


egrep -n 'ERROR.*bb..failed' fetchsrc.log | egrep -v 'nonworking' | 
egrep -v 'obsolete' | wc -l
434

egrep -n 'ERROR.*bb..failed' fetchsrc.log | egrep -v 'nonworking' | 
egrep -v 'obsolete' | egrep -v 'opie.*cvs' | wc -l
253


I know, that the opie recipes missing the cvs server on hh.org.

What is the best way to fix the missing download files?
Move the recipes to nonworking directory?
Find the missing files in the internet and upload the files to 
sources.openembedded.org?

A combination: If we could not find the files, move the recipes to 
nonworking.

Greetings

Klaus








  parent reply	other threads:[~2010-11-25 12:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-23 20:03 I've downloaded oe Klaus Schwarzkopf
2010-11-23 20:19 ` Khem Raj
2010-11-24  7:52   ` Frans Meulenbroeks
2010-11-24  8:07     ` Martin Jansa
2010-11-24  9:18       ` Frans Meulenbroeks
2010-11-25 12:07         ` Klaus Schwarzkopf
2010-11-25 12:44           ` Frans Meulenbroeks
2010-11-25 13:01             ` Martin Jansa
2010-11-25 11:58   ` Klaus Schwarzkopf [this message]
2010-11-25 12:43     ` Frans Meulenbroeks

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=4CEE4F61.3060401@sensortherm.de \
    --to=schwarzkopf@sensortherm.de \
    --cc=openembedded-devel@lists.openembedded.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.