[Announcement] MokoMakefile updated for switch to git

Rod Whitby rod at whitby.id.au
Wed May 21 16:18:58 CEST 2008


David Samblas Martinez wrote:
> I try to execute the new moko file doing a  "make update all" on a clean 
> install after a "make setup"
> but if fails even in the update
> #make update all
> ( cd bitbake && \
>           ( git branch | egrep -e ' bitbake-om$' > /dev/null || \
>             git checkout -b bitbake-om --track origin/bitbake-om ))
> ( cd bitbake && \
>           git checkout bitbake-om && \
>           git fetch && \
>           git rebase origin/bitbake-om )
> fatal: Needed a single revision
> invalid upstream origin/bitbake-om
> make: *** [update-bitbake] Error 1
> 
> any help will be wellcome

That's strange, when I do make setup followed by make update I get the 
following behaviour for bitbake:

> $ make setup
> (  [ -e stamps/bitbake ] && \
>           [ -e bitbake/.git ] ) || \
>         ( git clone -n git://git.openmoko.org/git/bitbake.git bitbake )
> Initialized empty Git repository in /home/moko/foo/bitbake/.git/
> remote: Generating pack...
> remote: Done counting 6083 objects.
> remote: Deltifying 6083 objects.
> remote:
> Indexing 6083 objects...
> remote: Total 6083, written 6083 (delta 3540), reused 0 (delta 0)
>  100% (6083/6083) done
> Resolving 3540 deltas...
>  100% (3540/3540) done
> ( cd bitbake && \
>           ( git branch | egrep -e ' bitbake-om$' > /dev/null || \
>             git checkout -b bitbake-om --track origin/bitbake-om ))
> ( cd bitbake && git checkout bitbake-om )
> Already on branch "bitbake-om"
> [ -d stamps ] || mkdir stamps
> touch stamps/bitbake
...
> $ make update
> ( cd bitbake && \
>           ( git branch | egrep -e ' bitbake-om$' > /dev/null || \
>             git checkout -b bitbake-om --track origin/bitbake-om ))
> ( cd bitbake && \
>           git checkout bitbake-om && \
>           git fetch && \
>           git rebase origin/bitbake-om )
> Already on branch "bitbake-om"
> Current branch bitbake-om is up to date.

So I can't reproduce your problem.

-- Rod



More information about the openmoko-devel mailing list