Created attachment 3010 [details] bblayers.conf Steps to reproduce: 1. Create new project (qemu) 2. Import layer 3. Build image included in layer Expected result: Successful build Observed result: Bitbake failure: Error executing a python function in exec_python_func() autogenerated: The stack trace of python calls that resulted in this exception/failure was: File: 'exec_python_func() autogenerated', lineno: 2, function: <module> 0001: *** 0002:poky_update_bblayersconf(d) 0003: File: '/media/md126p1/yocto/hbruce/master/toaster/_toaster_clones/_git___git.yoctoproject.org_meta-yocto_master/meta-yocto/../meta-poky/classes/poky-sanity.bbclass', lineno: 8, function: poky_update_bblayersconf 0004: current_version = int(d.getVar('POKY_BBLAYERS_CONF_VERSION', True) or -1) 0005: latest_version = int(d.getVar('REQUIRED_POKY_BBLAYERS_CONF_VERSION', True) or -1) 0006: 0007: # No version transitions here yet *** 0008: raise NotImplementedError("You need to update bblayers.conf manually for this version transision") 0009:} 0010: 0011:# Prepend to ensure our function runs before the OE-Core one 0012:BBLAYERS_CONF_UPDATE_FUNCS =+ "conf/bblayers.conf:POKY_BBLAYERS_CONF_VERSION:REQUIRED_POKY_BBLAYERS_CONF_VERSION:poky_update_bblayersconf" Exception: NotImplementedError: You need to update bblayers.conf manually for this version transision bblayers.conf is attached
Thanks for the report, it looks like you are using master. It appears to be due to the meta-yocto -> meta-poky rename and some old state being left behind. I see in your bblayers.conf that you have a layer in your project called meta-yocto, you will need to update your toaster by running lsupdates (layer source update) to get the new meta-poky layer. # Stop toaster michael@minos:~/poky/build$ source toaster stop # Update the database to get the new meta-poky layer michael@minos:~/poky/build$ ../bitbake/lib/toaster/manage.py lsupdates # Start toaster michael@minos:~/poky/build$ source toaster start Then remove meta-yocto from your project and add the new layer meta-poky. If all else fails you can reset toaster (this will lose all project data) by stopping toaster, delete build/conf directory, delete build/toaster.sqlite, source oe-init-build-env, and source toaster start If you want more stability then poky master is probably not for you.
Michael, many thanks for looking into this. I missed the meta-poky addition to poky. I think I'll got for your reset option. I'm using master as jethro does not build with toaster (bug 8958). I'm getting up to speed with toaster right now, what poky branch or tag do you I advise I use?
You could use the Toaster released with Jethro, which builds Jethro and Fido.
I'd prefer to keep working with master so I have access to the latest toaster features and don't ask for some thing that's already there. Also another set of eyes of the latest code is a good thing. If there's a specific poky revision you'd like me to use, let me know. I've switched to working with the local build which keeps things simple. I think you can close this issue.
As per the last comment. The meta-yocto to meta-poky rename should not be causing trouble any more.