git pull instead of mtn pull. No arguments needed, if you've created a '--track' branch.

btw, if you're using the wrapper makefile, just use 'make openembedded-update', just like with the mtn wrapper makefile.

what do you mean, it doesn't work?
Does the pull fail?
Does the build fail?

If you mean that e2 is still pulled from cvs instead of git, and therefore you don't get the latest commits, I suggest you change the SRC_URI, or use obi's branch for instance http://git.opendreambox.org/?p=obi/opendreambox-1.5.git

...and without monotone (through CVS) it was even easier...
Now it's only a nightmare...
Why no one make a clear and simple howto for building and updating an image (and in english, not german...)?
I don't mean theory (wich is always important) but some practical examples to help people who wants going on building own images!
Wich files have to be modified, and how?
Wich branches are to be followed?
Wich commands are to be executed?
Thx

can't you just wait until all issues are sorted out?
btw, currently opendreambox 1.5 uses a svn copy of the git repository for enigma2, so incrementing the srcdate in enigma2.bb as before should be sufficient...

oh, and git/mtn don't have anything to do with it

Zitat

Originally posted by ritzMo
can't you just wait until all issues are sorted out?
btw, currently opendreambox 1.5 uses a svn copy of the git repository for enigma2, so incrementing the srcdate in enigma2.bb as before should be sufficient...

oh, and git/mtn don't have anything to do with it

Thx for your answer!
Surely and with pleasure we will wait until all issues were sorted out, but when all this stuff begun it would be so simple to say "Don't warry and be patient, we will explain you as soon as we were ready"
On the contrary no one said a word, and the unavoidable questions were replayed vaguely, often in german, leaving lot of people into the nightmare to be suddently unable to compile a single image...
Anyway, thank you: we are all waiting for the "revelation"

first you should update the tree before altering it locally - just to prevent merging errors (but as you most likely won't change them back to their original state before doing the new pull that does not really apply ;)).

but besides of that it looks fine (though cleaning the tree is questionable in your scenario - after all packages with a new version should get (re)build anyways and if you have enough storage so you can keep more than one copy of some packages around you might as well just leave it out (or do at least again: do it after you update your tree because if the version changes bitbake will try to clean the new version which was not yet build anyways)).

are you checking out trunk or enigma2_rel24?

hi eagle,
ritzmo has wrote to you that you must change the source date in enigma2.bb.
the file is in openembedded/packages/enigma2

this it the same way in Monotone when you wont a new enigma2 you must change the source date in enigma2.bb

you must also activate the 2.5 branche in the enigma2.bb and enigma2-plugins.bb default is 2.4

i hope that helps you.

nobody611

when you build an image for a dm8000, you use the 2.5 tree automaticly.
but i have trouble to checkout the latest sources.

Zitat

NOTE: package enigma2-2.5git20081108: started
NOTE: package enigma2-2.5git20081108-r0: task do_fetch: started
NOTE: Update svn://git.opendreambox.org/enigma2;module=trunk;date=20081108
svn: No such revision 17727
NOTE: Task failed: Fetch failed: trunk
NOTE: package enigma2-2.5git20081108-r0: task do_fetch: failed
ERROR: TaskFailed event exception, aborting
NOTE: package enigma2-2.5git20081108: failed
ERROR: Build of dreambox-image failed

Alles anzeigen

does somebody else have this problems? everything works fine on wednesday but since thursday i only get this errormessages.

hi OoZoon,
i had the same problem i has removed in sources/svn/ the enigma2 directory and it works again.
it looks like that they changed the revision id in the svn

nobody611

yes, this work but now it tries to build a linux kernel for the 8000 with the bb of the 800 which for shure won't work. but this also happen when i trie to build an image for the 600. i hate this change to git. maybe monotone was slow, but it works......

eagle
can you attach your enigma2.bb

nobody611