On Wed, 2008-05-07 at 11:48 -0300, Rodrigo Vivi wrote: > > Is there output about "already staged" packages in the output from > > bitbake -DDD when this happens? If so, it might be worth trying the > > patch below... > > No, there is no "already staged" message... > I tried this patch (just in case) and it didn't solve my problem... > > > If that doesn't help I'll look into it further. > Thanks for your help!
Well, I've looked into it and I can confirm its totally broken. I used a test case of having both: nano_2.0.6.bb nano_2.0.7.bb and then bitbake nano-2.0.6 and it does indeed build both when it shouldn't. The problem is in providers.py and taskdata.py which rate the lastest version over the commandline appended version. bitbake knows something is wrong, hence the message about multiple providers but it doesn't understand what. Looking at the code, I can't see an easy fix for this problem. "Versioned dependencies" have been on the todo list for a long time and both problems are very related. Both look to need a rewrite of the providers logic though which is going to be painful since that code is full of subtle issues :/. Please file a bug in the bugzilla against bitbake and hopefully someone will look into and fix this at some point but it might not be soon. Note that if you do something like "PREFERRED_VERSION_nano=2.0.6 bitbake nano", it will work. Cheers, Richard _______________________________________________ Bitbake-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bitbake-dev
