TaskFailed when using MokoMakefile

Rod Whitby rod at whitby.id.au
Wed Feb 20 07:11:56 CET 2008

Erin Yueh wrote:
> your svn version r3801 is too old and i am using r4082 to build
> linux-openmoko package. There are two conf files related to svn numbers
> for bitbake. You may check this svn number first.
> moko/openembedded/conf/distro/include/sane-srcrevs.inc
> SRCREV_pn-linux-openmoko ?= "3801"
> moko/openembedded/conf/distro/include/moko-autorev.inc
> SRCREV_pn-linux-openmoko ?= "${AUTOREV}"
> if you include this 'moko-autorev.inc' in your 'local.conf', it should
> retrieve the latest svn number like mine. if you don't want to use the
> latest version, you can just specify the revision number in
> 'sane-srcrevs.inc'. For this case, you may change it to 4082, but i
> suggest to use ${AUTOREV} from svn server.

The person who changed the stable openmoko repo to use the 2.6.24 kernel
should have changed the sane-srcrevs file at the same time.  To not do
so is to break the stable openmoko branch, causing pain for hundreds of
openmoko developers.

It's either a stable branch or it's not.

If it is going to be a stable branch, then the person doing the mtn pull
from OE to OM must *not* use moko-autorev but *must* use sane-srcrevs only.

If it's not going to be a stable branch (i.e. if OpenMoko engineers are
not going to honor the requirement to make sure that sane-srcrevs does
actually configure a working build and a booting phone), then just drop
the whole separate OM repository idea altogether and use OE.dev directly.

-- Rod

More information about the device-owners mailing list