* Re: buildserver
2010-11-19 10:42 ` buildserver Yury Bushmelev
@ 2010-11-19 11:24 ` Martin Jansa
2010-11-19 12:21 ` buildserver Frans Meulenbroeks
2010-11-19 11:55 ` buildserver Klaus Schwarzkopf
` (2 subsequent siblings)
3 siblings, 1 reply; 18+ messages in thread
From: Martin Jansa @ 2010-11-19 11:24 UTC (permalink / raw)
To: openembedded-devel
On Fri, Nov 19, 2010 at 01:42:27PM +0300, Yury Bushmelev wrote:
> 2010/11/19 Klaus Schwarzkopf <schwarzkopf@sensortherm.de>:
> > Hi,
> >
> > i have some problems with the ti recipes, see my emails on the list.
> >
> > The two problems are:
> > * the recipes are out of date and don't work.
> > * the recipes can't download the source files.
> >
> > My idea is, to have an buildserver. On every commit (every night or every
> > week), the buildserver download the sources and build the recipe.
>
> For which DISTRO/MACHINE and image should it build? :)
> What to do with commits while building is in process?
> What to do with non-recipes commits (classes, conf, contrib)
>
> > If the server builds the recipe successful, it copy the source files to the
> > webserver.
> >
> > If the builds fails, the person how committed the recipe recieve a email
> > with the log files.
> >
> > What do you think about my idea?
>
> Just remember that OE have a lot of distros, machines and images.
> Ideal case is to test all combinations, but, let's try to imagine how
> long this will be.
>
> We have following number of distros, machines and images:
> $ ls conf/distro/*.conf | wc -l
> 32
> $ ls conf/machine/*.conf | wc -l
> 297
> $ ls recipes/images/*.bb | wc -l
> 99
>
> My testbuilder (phenom II x6) is building one image in about 2 hours.
> So, 32 * 297 * 99 * 2 = 1881792 hours. It is about 214 years if I
> calculate right.
But you assume every recipe MACHINE_ARCH or removing tmpdir for every build from scratch.
If you have 1 tmpdir per distro you have it all built in maybe one
week or so.
Regards,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: buildserver
2010-11-19 11:24 ` buildserver Martin Jansa
@ 2010-11-19 12:21 ` Frans Meulenbroeks
0 siblings, 0 replies; 18+ messages in thread
From: Frans Meulenbroeks @ 2010-11-19 12:21 UTC (permalink / raw)
To: openembedded-devel
2010/11/19 Martin Jansa <martin.jansa@gmail.com>:
> On Fri, Nov 19, 2010 at 01:42:27PM +0300, Yury Bushmelev wrote:
>> 2010/11/19 Klaus Schwarzkopf <schwarzkopf@sensortherm.de>:
>>
>> We have following number of distros, machines and images:
>> $ ls conf/distro/*.conf | wc -l
>> 32
>> $ ls conf/machine/*.conf | wc -l
>> 297
>> $ ls recipes/images/*.bb | wc -l
>> 99
Lots of these are stale/orphaned/unused/whatever.
For distro I made an overview last jul/aug. See ML archive.
frans
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: buildserver
2010-11-19 10:42 ` buildserver Yury Bushmelev
2010-11-19 11:24 ` buildserver Martin Jansa
@ 2010-11-19 11:55 ` Klaus Schwarzkopf
2010-11-19 12:04 ` buildserver Dvorkin Dmitry
2010-11-20 13:49 ` buildserver Klaus Schwarzkopf
3 siblings, 0 replies; 18+ messages in thread
From: Klaus Schwarzkopf @ 2010-11-19 11:55 UTC (permalink / raw)
To: openembedded-devel
Am 19.11.2010 11:42, schrieb Yury Bushmelev:
> 2010/11/19 Klaus Schwarzkopf<schwarzkopf@sensortherm.de>:
>> Hi,
>>
>> i have some problems with the ti recipes, see my emails on the list.
>>
>> The two problems are:
>> * the recipes are out of date and don't work.
>> * the recipes can't download the source files.
>>
>> My idea is, to have an buildserver. On every commit (every night or every
>> week), the buildserver download the sources and build the recipe.
>
> For which DISTRO/MACHINE and image should it build? :)
> What to do with commits while building is in process?
> What to do with non-recipes commits (classes, conf, contrib)
>
>> If the server builds the recipe successful, it copy the source files to the
>> webserver.
>>
>> If the builds fails, the person how committed the recipe recieve a email
>> with the log files.
>>
>> What do you think about my idea?
>
> Just remember that OE have a lot of distros, machines and images.
> Ideal case is to test all combinations, but, let's try to imagine how
> long this will be.
>
> We have following number of distros, machines and images:
> $ ls conf/distro/*.conf | wc -l
> 32
> $ ls conf/machine/*.conf | wc -l
> 297
> $ ls recipes/images/*.bb | wc -l
> 99
>
> My testbuilder (phenom II x6) is building one image in about 2 hours.
> So, 32 * 297 * 99 * 2 = 1881792 hours. It is about 214 years if I
> calculate right. Well, cluster of 32 alike machines can reduce this
> time to 6 years :)
>
OK, it takes a long time ;-)
> It would be great to have buildserver that will rebuild some most
> frequently used combinations once per day. Probably, qemu machines +
> automated testing under qemu.
> Or even create some distributed build system (buildbot?) with server
> (should give tasks to clients) and clients (should build tasks given
> by server).
Good idea.
>
> Other good idea is to have sanity checker running once per day too. It
> may do next things:
> - check recipes syntax
> - check thath recipes SRC_URI can be fetched
> - check recipes for security flaws (we have tool already)
> - ...
> - PROFIT! :) (sorry, just can't not to write this :)
>
Even better idea!
Is it a problem (webspace, license) to host then the source files on
project webspace?
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: buildserver
2010-11-19 10:42 ` buildserver Yury Bushmelev
2010-11-19 11:24 ` buildserver Martin Jansa
2010-11-19 11:55 ` buildserver Klaus Schwarzkopf
@ 2010-11-19 12:04 ` Dvorkin Dmitry
2010-11-20 13:49 ` buildserver Klaus Schwarzkopf
3 siblings, 0 replies; 18+ messages in thread
From: Dvorkin Dmitry @ 2010-11-19 12:04 UTC (permalink / raw)
To: openembedded-devel
simplest solution, I think, is to have a flag in OE local.conf:
"send_build_report = true" :)
19.11.2010 13:42, Yury Bushmelev пишет:
> 2010/11/19 Klaus Schwarzkopf<schwarzkopf@sensortherm.de>:
>
>> Hi,
>>
>> i have some problems with the ti recipes, see my emails on the list.
>>
>> The two problems are:
>> * the recipes are out of date and don't work.
>> * the recipes can't download the source files.
>>
>> My idea is, to have an buildserver. On every commit (every night or every
>> week), the buildserver download the sources and build the recipe.
>>
> For which DISTRO/MACHINE and image should it build? :)
> What to do with commits while building is in process?
> What to do with non-recipes commits (classes, conf, contrib)
>
>
>> If the server builds the recipe successful, it copy the source files to the
>> webserver.
>>
>> If the builds fails, the person how committed the recipe recieve a email
>> with the log files.
>>
>> What do you think about my idea?
>>
> Just remember that OE have a lot of distros, machines and images.
> Ideal case is to test all combinations, but, let's try to imagine how
> long this will be.
>
> We have following number of distros, machines and images:
> $ ls conf/distro/*.conf | wc -l
> 32
> $ ls conf/machine/*.conf | wc -l
> 297
> $ ls recipes/images/*.bb | wc -l
> 99
>
> My testbuilder (phenom II x6) is building one image in about 2 hours.
> So, 32 * 297 * 99 * 2 = 1881792 hours. It is about 214 years if I
> calculate right. Well, cluster of 32 alike machines can reduce this
> time to 6 years :)
>
> It would be great to have buildserver that will rebuild some most
> frequently used combinations once per day. Probably, qemu machines +
> automated testing under qemu.
> Or even create some distributed build system (buildbot?) with server
> (should give tasks to clients) and clients (should build tasks given
> by server).
>
> Other good idea is to have sanity checker running once per day too. It
> may do next things:
> - check recipes syntax
> - check thath recipes SRC_URI can be fetched
> - check recipes for security flaws (we have tool already)
> - ...
> - PROFIT! :) (sorry, just can't not to write this :)
>
>
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: buildserver
2010-11-19 10:42 ` buildserver Yury Bushmelev
` (2 preceding siblings ...)
2010-11-19 12:04 ` buildserver Dvorkin Dmitry
@ 2010-11-20 13:49 ` Klaus Schwarzkopf
2010-11-21 18:08 ` buildserver Chris Larson
3 siblings, 1 reply; 18+ messages in thread
From: Klaus Schwarzkopf @ 2010-11-20 13:49 UTC (permalink / raw)
To: openembedded-devel
> Other good idea is to have sanity checker running once per day too. It
> may do next things:
> - check recipes syntax
> - check thath recipes SRC_URI can be fetched
I think, bitbake can easily integrate this two features.
For example the new options:
--download-only only download the source files for the given recipe
--download-only-with-depencies only download the source files for the
given recipe and its depencies
--check-syntax check recipes syntax
What do you think?
Greetings,
Klaus
> - check recipes for security flaws (we have tool already)
> - ...
> - PROFIT! :) (sorry, just can't not to write this :)
>
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: buildserver
2010-11-20 13:49 ` buildserver Klaus Schwarzkopf
@ 2010-11-21 18:08 ` Chris Larson
2010-11-22 8:38 ` buildserver Klaus Schwarzkopf
0 siblings, 1 reply; 18+ messages in thread
From: Chris Larson @ 2010-11-21 18:08 UTC (permalink / raw)
To: openembedded-devel
On Sat, Nov 20, 2010 at 6:49 AM, Klaus Schwarzkopf <
schwarzkopf@sensortherm.de> wrote:
>
> Other good idea is to have sanity checker running once per day too. It
>> may do next things:
>> - check recipes syntax
>> - check thath recipes SRC_URI can be fetched
>>
>
> I think, bitbake can easily integrate this two features.
>
> For example the new options:
>
> --download-only only download the source files for the
> given recipe
>
> --download-only-with-depencies only download the source files for the
> given recipe and its depencies
>
> --check-syntax check recipes syntax
This seems pretty foolish and unnecessary to me. This can be easily done in
the metadata -- there's no need to modify bitbake for this at all.
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: buildserver
2010-11-21 18:08 ` buildserver Chris Larson
@ 2010-11-22 8:38 ` Klaus Schwarzkopf
2010-11-22 8:56 ` buildserver Frans Meulenbroeks
0 siblings, 1 reply; 18+ messages in thread
From: Klaus Schwarzkopf @ 2010-11-22 8:38 UTC (permalink / raw)
To: openembedded-devel
Am 21.11.2010 19:08, schrieb Chris Larson:
> On Sat, Nov 20, 2010 at 6:49 AM, Klaus Schwarzkopf<
> schwarzkopf@sensortherm.de> wrote:
>
>>
>> Other good idea is to have sanity checker running once per day too. It
>>> may do next things:
>>> - check recipes syntax
>>> - check thath recipes SRC_URI can be fetched
>>>
>>
>> I think, bitbake can easily integrate this two features.
>>
>> For example the new options:
>>
>> --download-only only download the source files for the
>> given recipe
>>
>> --download-only-with-depencies only download the source files for the
>> given recipe and its depencies
>>
>> --check-syntax check recipes syntax
>
>
>
> This seems pretty foolish and unnecessary to me. This can be easily done in
> the metadata -- there's no need to modify bitbake for this at all.
Hi Chris,
you are right! I don't see this function.
I wrote some commands, to download the source files:
export MACHINE=dm355-evm # can be for all machines
find /home/klaus/development/oe/openembedded/ -name '*.bb' -type f -exec
bitbake -c fetch -b '{}' 2>&1 > fetch.log \;
egrep -n 'ERROR.*bb..failed' fetch.log
It is not perfect, but it shows some errors.
Can somebody test it?
Greetings
Klaus
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: buildserver
2010-11-22 8:38 ` buildserver Klaus Schwarzkopf
@ 2010-11-22 8:56 ` Frans Meulenbroeks
2010-11-22 15:14 ` buildserver Klaus Schwarzkopf
0 siblings, 1 reply; 18+ messages in thread
From: Frans Meulenbroeks @ 2010-11-22 8:56 UTC (permalink / raw)
To: openembedded-devel
2010/11/22 Klaus Schwarzkopf <schwarzkopf@sensortherm.de>:
> Am 21.11.2010 19:08, schrieb Chris Larson:
>>
>> On Sat, Nov 20, 2010 at 6:49 AM, Klaus Schwarzkopf<
>> schwarzkopf@sensortherm.de> wrote:
>>
>>>
>>> Other good idea is to have sanity checker running once per day too. It
>>>>
>>>> may do next things:
>>>> - check recipes syntax
>>>> - check thath recipes SRC_URI can be fetched
>>>>
>>>
>>> I think, bitbake can easily integrate this two features.
>>>
>>> For example the new options:
>>>
>>> --download-only only download the source files for the
>>> given recipe
>>>
>>> --download-only-with-depencies only download the source files for the
>>> given recipe and its depencies
>>>
>>> --check-syntax check recipes syntax
>>
>>
>>
>> This seems pretty foolish and unnecessary to me. This can be easily done
>> in
>> the metadata -- there's no need to modify bitbake for this at all.
>
>
> Hi Chris,
>
> you are right! I don't see this function.
>
> I wrote some commands, to download the source files:
>
>
> export MACHINE=dm355-evm # can be for all machines
>
> find /home/klaus/development/oe/openembedded/ -name '*.bb' -type f -exec
> bitbake -c fetch -b '{}' 2>&1 > fetch.log \;
>
> egrep -n 'ERROR.*bb..failed' fetch.log
>
>
> It is not perfect, but it shows some errors.
>
> Can somebody test it?
You can also do
bitbake -c fetchall world (although this has a little bit less
coverage as it will not handle older versions).
I'm not too good in find syntax so instead of your find cmd I would
probably use something like:
for i in recipes/*/*bb
do
bitbake -c fetch $i
done > fetch.log 2>&1
Enjoy! Frans
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: buildserver
2010-11-22 8:56 ` buildserver Frans Meulenbroeks
@ 2010-11-22 15:14 ` Klaus Schwarzkopf
2010-11-22 17:25 ` buildserver Frans Meulenbroeks
0 siblings, 1 reply; 18+ messages in thread
From: Klaus Schwarzkopf @ 2010-11-22 15:14 UTC (permalink / raw)
To: openembedded-devel
Am 22.11.2010 09:56, schrieb Frans Meulenbroeks:
> 2010/11/22 Klaus Schwarzkopf<schwarzkopf@sensortherm.de>:
>> Am 21.11.2010 19:08, schrieb Chris Larson:
>>>
>>> On Sat, Nov 20, 2010 at 6:49 AM, Klaus Schwarzkopf<
>>> schwarzkopf@sensortherm.de> wrote:
>>>
>>>>
>>>> Other good idea is to have sanity checker running once per day too. It
>>>>>
>>>>> may do next things:
>>>>> - check recipes syntax
>>>>> - check thath recipes SRC_URI can be fetched
>>>>>
>>>>
>>>> I think, bitbake can easily integrate this two features.
>>>>
>>>> For example the new options:
>>>>
>>>> --download-only only download the source files for the
>>>> given recipe
>>>>
>>>> --download-only-with-depencies only download the source files for the
>>>> given recipe and its depencies
>>>>
>>>> --check-syntax check recipes syntax
>>>
>>>
>>>
>>> This seems pretty foolish and unnecessary to me. This can be easily done
>>> in
>>> the metadata -- there's no need to modify bitbake for this at all.
>>
>>
>> Hi Chris,
>>
>> you are right! I don't see this function.
>>
>> I wrote some commands, to download the source files:
>>
>>
>> export MACHINE=dm355-evm # can be for all machines
>>
>> find /home/klaus/development/oe/openembedded/ -name '*.bb' -type f -exec
>> bitbake -c fetch -b '{}' 2>&1> fetch.log \;
>>
>> egrep -n 'ERROR.*bb..failed' fetch.log
>>
>>
>> It is not perfect, but it shows some errors.
>>
>> Can somebody test it?
>
> You can also do
> bitbake -c fetchall world (although this has a little bit less
> coverage as it will not handle older versions).
>
> I'm not too good in find syntax so instead of your find cmd I would
> probably use something like:
>
> for i in recipes/*/*bb
> do
> bitbake -c fetch $i
> done> fetch.log 2>&1
>
> Enjoy! Frans
>
Hi Frans,
this script looks good. I try it on the next run.
My script isn't finished yet, maybe tomorrow, but i post the results. I
hope this helps a little.
Download the fetch.log, to see the error
http://fbi.hooster.de/download/sonstiges/oe/fetch.log.tar.gz
The first number is the row number.
klaus@ubuntu:~/development/oe$ egrep -n 'ERROR.*bb..failed' fetch.log
413:ERROR:
'/home/klaus/development/oe/openembedded/recipes/samsung-soc-utils/s3c2410-boot-usb-native_svn.bb'
failed
4090:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opensync/libopensync-plugin-syncml-client-plugin_0.1.bb'
failed
4274:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opensync/libopensync_0.22.bb'
failed
4301:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opensync/libopensync-plugin-file_0.18.bb'
failed
4367:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opensync/libopensync-plugin-irmc-sync_0.22.bb'
failed
4434:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opensync/syncml-client_0.1.bb'
failed
4480:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opensync/libopensync-plugin-gpe_0.18.bb'
failed
4619:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opensync/msynctool_svn.bb'
failed
5066:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opensync/libopensync-plugin-irmc_0.18.bb'
failed
6325:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opensync/libopensync-plugin-evo2-sync_0.22.bb'
failed
6392:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opensync/msynctool_0.22.bb'
failed
6419:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opensync/libopensync-plugin-file-sync_0.22.bb'
failed
6761:ERROR:
'/home/klaus/development/oe/openembedded/recipes/openjdk/openjdk-6_6b18-1.8.bb'
failed
8551:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-tinykate/opie-tinykate_cvs.bb'
failed
8749:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-alarm/opie-alarm_cvs.bb'
failed
9027:ERROR:
'/home/klaus/development/oe/openembedded/recipes/openocd/openocd-native_svn.bb'
failed
9057:ERROR:
'/home/klaus/development/oe/openembedded/recipes/openocd/openocd_svn.bb'
failed
9380:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-sounds/opie-sounds_cvs.bb'
failed
9915:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-sfcave/opie-sfcave_cvs.bb'
failed
10038:ERROR:
'/home/klaus/development/oe/openembedded/recipes/howl/howl_0.9.7.bb' failed
10337:ERROR:
'/home/klaus/development/oe/openembedded/recipes/snes232/snes232_cvs.bb'
failed
12069:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-multikeyapplet/opie-multikeyapplet_cvs.bb'
failed
12154:ERROR:
'/home/klaus/development/oe/openembedded/recipes/dhcdbd/dhcdbd_1.14.bb'
failed
14505:ERROR:
'/home/klaus/development/oe/openembedded/recipes/fltk/fltk_1.1.4.bb' failed
14662:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-recorder/opie-recorder_cvs.bb'
failed
15214:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-style-fresh/opie-style-fresh_cvs.bb'
failed
15279:ERROR:
'/home/klaus/development/oe/openembedded/recipes/nis/ypbind-mt_1.18.bb'
failed
15425:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-launcher-settings/opie-launcher-settings_cvs.bb'
failed
15473:ERROR:
'/home/klaus/development/oe/openembedded/recipes/dircproxy/dircproxy_1.1.0.bb'
failed
15779:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-clipboardapplet/opie-clipboardapplet_cvs.bb'
failed
16689:ERROR:
'/home/klaus/development/oe/openembedded/recipes/openmoko-projects/tichy_git.bb'
failed
17314:ERROR:
'/home/klaus/development/oe/openembedded/recipes/upnp/gupnp-tools_0.8.bb' failed
17487:ERROR:
'/home/klaus/development/oe/openembedded/recipes/upnp/gupnp-vala_0.6.2.bb'
failed
17600:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-deco-liquid/opie-deco-liquid_cvs.bb'
failed
17841:ERROR:
'/home/klaus/development/oe/openembedded/recipes/gtkhtml/gtkhtml-2.0_2.6.3.bb'
failed
18027:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-aboutapplet/opie-aboutapplet_cvs.bb'
failed
18273:ERROR:
'/home/klaus/development/oe/openembedded/recipes/tsclient/tsclient_0.132.bb'
failed
18309:ERROR:
'/home/klaus/development/oe/openembedded/recipes/tsclient/tsclient_0.140.bb'
failed
18424:ERROR:
'/home/klaus/development/oe/openembedded/recipes/dgen/dgen-sdl_1.23.bb'
failed
19321:ERROR:
'/home/klaus/development/oe/openembedded/recipes/spca5xx/spca5xx_20060501.bb'
failed
19431:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-today/opie-today_cvs.bb'
failed
19542:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-wellenreiter/opie-wellenreiter_cvs.bb'
failed
19613:ERROR:
'/home/klaus/development/oe/openembedded/recipes/exmap-console/exmap-console_svn.bb'
failed
20528:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-search/opie-search_cvs.bb'
failed
21801:ERROR:
'/home/klaus/development/oe/openembedded/recipes/gtk2-ssh-askpass/gtk2-ssh-askpass_0.3.bb'
failed
21887:ERROR:
'/home/klaus/development/oe/openembedded/recipes/ntfs-3g/ntfs-3g_1.0.bb'
failed
22281:ERROR:
'/home/klaus/development/oe/openembedded/recipes/mailx/mailx_8.1.2-0.20020411cvs.bb'
failed
22326:ERROR:
'/home/klaus/development/oe/openembedded/recipes/mailx/mailx_8.1.2-0.20040524cvs.bb'
failed
35676:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-sshkeys/opie-sshkeys_cvs.bb'
failed
35991:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-restartapplet2/opie-restartapplet2_cvs.bb'
failed
36572:ERROR:
'/home/klaus/development/oe/openembedded/recipes/hibernate-script/hibernate-script_1.12.bb'
failed
37113:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-calculator/opie-calculator_cvs.bb'
failed
37227:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-todo/opie-todo_cvs.bb'
failed
37376:ERROR:
'/home/klaus/development/oe/openembedded/recipes/disko/disko_1.6.0.bb'
failed
37443:ERROR:
'/home/klaus/development/oe/openembedded/recipes/libeina/libeina_0.96.5.bb'
failed
37515:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-backgammon/opie-backgammon_cvs.bb'
failed
37891:ERROR:
'/home/klaus/development/oe/openembedded/recipes/openh323/openh323_1.13.5.4.bb'
failed
38358:ERROR:
'/home/klaus/development/oe/openembedded/recipes/scummvm/opie-scummvm_1.0.1.bb'
failed
38854:ERROR:
'/home/klaus/development/oe/openembedded/recipes/libxsettings/libxsettings_svn.bb'
failed
38949:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-login/opie-login_cvs.bb'
failed
39319:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-sysinfo/opie-sysinfo_cvs.bb'
failed
39595:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-clockapplet/opie-clockapplet_cvs.bb'
failed
41354:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-examples/opie-examples_cvs.bb'
failed
42746:ERROR:
'/home/klaus/development/oe/openembedded/recipes/kismet/kismet_2007-10-R1.bb'
failed
42776:ERROR:
'/home/klaus/development/oe/openembedded/recipes/kismet/kismet-newcore_svn.bb'
failed
42806:ERROR:
'/home/klaus/development/oe/openembedded/recipes/kismet/kismet_svn.bb'
failed
43284:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-zsame/opie-zsame_cvs.bb'
failed
43446:ERROR:
'/home/klaus/development/oe/openembedded/recipes/ica/ica-bin_8.0.bb' failed
43518:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-fifteen/opie-fifteen_cvs.bb'
failed
43704:ERROR:
'/home/klaus/development/oe/openembedded/recipes/waimea/waimea_cvs.bb'
failed
45019:ERROR:
'/home/klaus/development/oe/openembedded/recipes/alsa/alsa-scenario_git.bb'
failed
45574:ERROR:
'/home/klaus/development/oe/openembedded/recipes/juce/juce_1.29.bb' failed
46448:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-unikeyboard/opie-unikeyboard_cvs.bb'
failed
46784:ERROR:
'/home/klaus/development/oe/openembedded/recipes/gnome/gnome-games_2.30.2.bb'
failed
47212:ERROR:
'/home/klaus/development/oe/openembedded/recipes/gnome/libbacon_svn.bb'
failed
49123:ERROR:
'/home/klaus/development/oe/openembedded/recipes/neuros-public/neuros-app-vplayer_git.bb'
failed
49159:ERROR:
'/home/klaus/development/oe/openembedded/recipes/neuros-public/neuros-mainmenu_git.bb'
failed
49195:ERROR:
'/home/klaus/development/oe/openembedded/recipes/neuros-public/neuros-qt-plugins_git.bb'
failed
49231:ERROR:
'/home/klaus/development/oe/openembedded/recipes/neuros-public/neuros-lib-widgets_git.bb'
failed
49267:ERROR:
'/home/klaus/development/oe/openembedded/recipes/neuros-public/neuros-nwm_git.bb'
failed
49303:ERROR:
'/home/klaus/development/oe/openembedded/recipes/neuros-public/neuros-lib-gui_git.bb'
failed
49339:ERROR:
'/home/klaus/development/oe/openembedded/recipes/neuros-public/neuros-app-photoalbum_git.bb'
failed
49581:ERROR:
'/home/klaus/development/oe/openembedded/recipes/soundtracker/soundtracker-gtk2_0.6.7.bb'
failed
49672:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-tonleiter/opie-tonleiter_cvs.bb'
failed
49803:ERROR:
'/home/klaus/development/oe/openembedded/recipes/chillispot/chillispot_0.98.bb'
failed
49839:ERROR:
'/home/klaus/development/oe/openembedded/recipes/chillispot/chillispot_1.0RC3.bb'
failed
50286:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-remote/opie-remote_cvs.bb'
failed
50380:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-securityplugins/opie-securityplugin-notice_cvs.bb'
failed
50412:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-securityplugins/opie-securityplugin-dummy_cvs.bb'
failed
50550:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-securityplugins/opie-securityplugin-pin_cvs.bb'
failed
50603:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-securityplugins/opie-securityplugin-blueping_cvs.bb'
failed
50630:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-help-en/opie-help-en_1.2.4.bb'
failed
50663:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-help-en/opie-help-en_cvs.bb'
failed
50691:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-help-en/opie-help-en_1.2.3.bb'
failed
50785:ERROR:
'/home/klaus/development/oe/openembedded/recipes/libqanava/libqanava_0.0.7.bb'
failed
51053:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-gutenbrowser/opie-gutenbrowser_cvs.bb'
failed
51131:ERROR:
'/home/klaus/development/oe/openembedded/recipes/minipredict/dictionary_en-GB.bb'
failed
51512:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-zsafe/opie-zsafe_cvs.bb'
failed
51605:ERROR:
'/home/klaus/development/oe/openembedded/recipes/redfang/redfang.bb' failed
51696:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-ftplib/opie-ftplib_cvs.bb'
failed
51877:ERROR:
'/home/klaus/development/oe/openembedded/recipes/xffm/xffm_4.3.99.2.bb'
failed
52016:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-aqpkg/opie-aqpkg_cvs.bb'
failed
52068:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-pimconverter/opie-pimconverter_cvs.bb'
failed
52135:ERROR:
'/home/klaus/development/oe/openembedded/recipes/agg/agg-minimal_2.5.bb'
failed
52341:ERROR:
'/home/klaus/development/oe/openembedded/recipes/treecc/treecc_0.3.6.bb'
failed
52376:ERROR:
'/home/klaus/development/oe/openembedded/recipes/treecc/treecc-native_0.3.6.bb'
failed
52680:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-symlinker/opie-symlinker_cvs.bb'
failed
52805:ERROR:
'/home/klaus/development/oe/openembedded/recipes/xcb/xcb-proto_0.9.bb'
failed
54628:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-mediaplayer1-libmadplugin/opie-mediaplayer1-libmadplugin_cvs.bb'
failed
54716:ERROR:
'/home/klaus/development/oe/openembedded/recipes/frotz/frotz_2.42.bb' failed
54836:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-systemtime/opie-systemtime_cvs.bb'
failed
55022:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-cardapplet/opie-cardapplet_cvs.bb'
failed
55264:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-lockapplet/opie-lockapplet_cvs.bb'
failed
57179:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-keyview/opie-keyview_cvs.bb'
failed
57367:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-parashoot/opie-parashoot_cvs.bb'
failed
57413:ERROR:
'/home/klaus/development/oe/openembedded/recipes/qc-usb/qc-usb-messenger_1.1.bb'
failed
57440:ERROR:
'/home/klaus/development/oe/openembedded/recipes/qc-usb/qc-usb-messenger_0.8.bb'
failed
57860:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-sheet/opie-sheet_cvs.bb'
failed
59282:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-textedit/opie-textedit_cvs.bb'
failed
59392:ERROR:
'/home/klaus/development/oe/openembedded/recipes/cxcrypt/cxcrypt_1.0.bb'
failed
59446:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-memoryapplet/opie-memoryapplet_cvs.bb'
failed
59596:ERROR:
'/home/klaus/development/oe/openembedded/recipes/tslib/tslib_git.bb' failed
59708:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-examples-python/opie-examples-python_cvs.bb'
failed
59932:ERROR:
'/home/klaus/development/oe/openembedded/recipes/cdtool/cdtool_2.1.8.bb'
failed
59984:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-write/opie-write_cvs.bb'
failed
60132:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-qss/opie-qss_cvs.bb'
failed
60785:ERROR:
'/home/klaus/development/oe/openembedded/recipes/pimlico/dates_svn.bb'
failed
60872:ERROR:
'/home/klaus/development/oe/openembedded/recipes/pimlico/contacts_svn.bb' failed
60902:ERROR:
'/home/klaus/development/oe/openembedded/recipes/pimlico/tasks_svn.bb'
failed
61101:ERROR:
'/home/klaus/development/oe/openembedded/recipes/libsvdrp/libsvdrp_hg.bb' failed
61550:ERROR:
'/home/klaus/development/oe/openembedded/recipes/inkspill/inkspill_0.1.bb'
failed
61577:ERROR:
'/home/klaus/development/oe/openembedded/recipes/gnet/gnet_cvs.bb' failed
62827:ERROR:
'/home/klaus/development/oe/openembedded/recipes/hal/hal_git.bb' failed
63659:ERROR:
'/home/klaus/development/oe/openembedded/recipes/binutils/binutils_2.18.atmel.1.0.1.bb'
failed
63883:ERROR:
'/home/klaus/development/oe/openembedded/recipes/binutils/mingw-binutils_2.20.bb'
failed
64242:ERROR:
'/home/klaus/development/oe/openembedded/recipes/binutils/mingw-binutils-canadian-cross_2.20.bb'
failed
77703:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-sh/opie-sh_cvs.bb'
failed
77777:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-drawpad/opie-drawpad_cvs.bb'
failed
79285:ERROR:
'/home/klaus/development/oe/openembedded/recipes/maxima/maxima_5.21.1.bb' failed
79709:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-networkapplet/opie-networkapplet_cvs.bb'
failed
80410:ERROR:
'/home/klaus/development/oe/openembedded/recipes/opie-keytabs/opie-keytabs_cvs.bb'
failed
80495:ERROR:
'/home/klaus/development/oe/openembedded/recipes/gpsdrive/gpsdrive-pda_2.10pre2.bb'
failed
What means KeyError?
Traceback (most recent call last):
File "/home/klaus/development/oe/bitbake/bin/bitbake", line 143, in
<module>
main()
File "/home/klaus/development/oe/bitbake/bin/bitbake", line 140, in main
cooker.cook()
File "/home/klaus/development/oe/bitbake/lib/bb/cooker.py", line 608,
in cook
if not self.buildFile(self.configuration.buildfile):
File "/home/klaus/development/oe/bitbake/lib/bb/cooker.py", line 488,
in buildFile
self.status.task_deps[fn]['depends'] = {}
KeyError:
'/home/klaus/development/oe/openembedded/recipes/linux/linux-handhelds-2.6_2.6.17-hh4.bb'
Greetings
Klaus
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: buildserver
2010-11-22 15:14 ` buildserver Klaus Schwarzkopf
@ 2010-11-22 17:25 ` Frans Meulenbroeks
2010-11-22 17:31 ` buildserver Eric Bénard
0 siblings, 1 reply; 18+ messages in thread
From: Frans Meulenbroeks @ 2010-11-22 17:25 UTC (permalink / raw)
To: openembedded-devel
Note that some of the errors Klaus reported are due to the outage of
www.handhelds.org.
Frans
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: buildserver
2010-11-22 17:25 ` buildserver Frans Meulenbroeks
@ 2010-11-22 17:31 ` Eric Bénard
2010-11-22 18:21 ` buildserver Frans Meulenbroeks
0 siblings, 1 reply; 18+ messages in thread
From: Eric Bénard @ 2010-11-22 17:31 UTC (permalink / raw)
To: openembedded-devel
On 22/11/2010 18:25, Frans Meulenbroeks wrote:
> Note that some of the errors Klaus reported are due to the outage of
> www.handhelds.org.
>
as a workaround, here adding this to the local.conf works :
INHERIT += "own-mirrors"
SOURCE_MIRROR_URL = "http://sources.openembedded.org/"
Can peoples having problem with update-rc.d try this and report here if that
solves their problem ?
Thanks,
Eric
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: buildserver
2010-11-22 17:31 ` buildserver Eric Bénard
@ 2010-11-22 18:21 ` Frans Meulenbroeks
2010-11-22 18:41 ` buildserver Eric Bénard
0 siblings, 1 reply; 18+ messages in thread
From: Frans Meulenbroeks @ 2010-11-22 18:21 UTC (permalink / raw)
To: openembedded-devel
2010/11/22 Eric Bénard <eric@eukrea.com>:
> On 22/11/2010 18:25, Frans Meulenbroeks wrote:
>>
>> Note that some of the errors Klaus reported are due to the outage of
>> www.handhelds.org.
>>
> as a workaround, here adding this to the local.conf works :
>
> INHERIT += "own-mirrors"
> SOURCE_MIRROR_URL = "http://sources.openembedded.org/"
>
> Can peoples having problem with update-rc.d try this and report here if that
> solves their problem ?
After discussing things with Philip (the maintainer of update-rc.d) I
already pushed the change to have the update-rc.d file local (with his
ack).
We can try with other recipes.
One other question: can I have two mirrors? I already have our local
mirror in my list.
Frans.
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: buildserver
2010-11-22 18:21 ` buildserver Frans Meulenbroeks
@ 2010-11-22 18:41 ` Eric Bénard
0 siblings, 0 replies; 18+ messages in thread
From: Eric Bénard @ 2010-11-22 18:41 UTC (permalink / raw)
To: openembedded-devel
On 22/11/2010 19:21, Frans Meulenbroeks wrote:
> After discussing things with Philip (the maintainer of update-rc.d) I
> already pushed the change to have the update-rc.d file local (with his
> ack).
fine, this is a better fix.
> We can try with other recipes.
>
> One other question: can I have two mirrors? I already have our local
> mirror in my list.
>
this should be possible by adding your own my-mirrors.bbclass in your overlay
and filling :
PREMIRRORS_append () { or MIRRORS_append () {
as in several classes/*mirrors*
Eric
^ permalink raw reply [flat|nested] 18+ messages in thread