ca-certificates like ./tmp/sysroots/x86_64-linux/usr/share/ca-certificates/mozilla/AC_Raíz_Certicámara_S.A..crt cause toaster to dump a traceback since the í in the filename is not an ascii character and buildinfohelper freaks. the error is in toaster_ui.log on a core-image-sato build. It looks like: ERROR: 'ascii' codec can't decode byte 0xc3 in position 40: ordinal not in range(128) Traceback (most recent call last): followed by a traceback and a lot of: ERROR: Error data dump [....
I've been able to reproduce this, I'm afraid, by building a core-image-sato image with toaster-next (cf1cebf59f5bb00f92401d29e3ab8490fdd32d57). I've attached the build log.
Created attachment 3021 [details] toaster_ui.log
I can't see the error in the log if I build only ca-certificates
The exception is thrown during handling of the ImagePkgList MetadataEvent, so not triggering during build of the single recipe does make sense. I was able to work around this by converting the paths in ORMWrapper's save_target_file_information() method to instances of the unicode type. I'm going to propose a patch which does so for inclusion in the 2.1 timeframe. For the next release we should probably look at better supporting unicode in Toaster. This should be made much easier if the proposal to switch BitBake to Python 3 goes ahead.
Workaround merged to bitbake: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=7a309d964a86f3474eaab7df6d438ed797f935c0 I've filed https://bugzilla.yoctoproject.org/show_bug.cgi?id=9395 to track better supporting unicode in Toaster.
Verified on master.