13356 2019-05-20 22:07:05 +0000 oe-core.xml in thud branch refers to wrong bitbake version 2019-06-11 08:30:41 +0000 1 1 7 Build System, Metadata & Runtime Toaster toaster 5.99 All Multiple RESOLVED FIXED also backport to Thud (2.6) and Warrior (2.7) Medium+ normal 2.8 M1 1 typeof david.reyna jessica.zhang stanciux.mihail toaster --- --- No (bug/feature does not impact docs) oldest_to_newest 83865 0 typeof 2019-05-20 22:07:05 +0000 I have come across a problem when building an rpi image with thud in toaster (or any image really). http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/bitbake/lib/toaster/orm/fixtures/oe-core.xml?h=thud#n56 On line 56, you see that the ORM refers to bitbake_version_id 1, which is 1.38. It should be 4, which is 1.40. Not sure how to submit a patch. The error is : build rpi-basic-image : OE-core's config sanity checker detected a potential misconfiguration. Either fix the cause of this error or at your own risk disable the checker (see sanity.conf). Following is the list of potential problems / advisories: Bitbake version 1.39.1 is required and version 1.38.0 was found After I changed the sqlite db to use bitbake_version_id 4 in "orm_release" table , the problem was fixed. 84122 1 david.reyna 2019-06-10 00:52:36 +0000 Ports for 2.6 and 2.7 submitted upstream. 84123 2 david.reyna 2019-06-10 00:58:34 +0000 Note: I am not submitting this for master (2.8) because Thud will fall off the list at that time, but I am forewarned about watching this non-obvious link for the future (i.e. Zeus). This issue does not affect Warrior because the meta-information in Bitbake link "1" happened to point to the bitbake warrior branch (when sumo was replaced by warrior). 84136 3 david.reyna 2019-06-11 08:30:41 +0000 2.6: (Bitbake rev: f8a23ad4f8f0336470a5d5b074b7a2d02ec94631) 2.7: (Bitbake rev: 7cda98d64693d978ad1387fed05a83aaa681e097) master: (Bitbake rev: 7d0ab11a0d1a2510515d7ebab66b922fbfc411c3)