9443 2016-04-12 13:15:48 +0000 lsb_release output should be sanitised before usage 2016-04-14 13:05:38 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core unspecified All Multiple RESOLVED FIXED Undecided normal --- 1 silbe ross.burton meta.mr.watcher meta.watcher --- --- Don't know oldest_to_newest 61087 0 silbe 2016-04-12 13:15:48 +0000 Some downstream distributions use special characters in some of the lsb_release output fields. That's unusual, but not expressly forbidden by the LSB specification [1]. poky currently uses the output of "lsb_release -ir" more or less as-is for generating some paths (e.g. SSTATE_EXTRAPATH). Since many parts of poky (including most recipes) don't properly quote / escape paths, this causes the build to fail horribly. The distro name should be sanitised to only contain characters that cannot cause any trouble when used unquoted ("whitelist" approach). The existing replacements in meta/lib/oe/lsb.py only cover two specific cases ("blacklist" approach). Encountered with fido (in my case the distribution id contained double quotes), but the code in master looks very similar. [1] https://refspecs.linuxfoundation.org/LSB_5.0.0/LSB-Core-generic/LSB-Core-generic/lsbrelease.html 61095 1 ross.burton 2016-04-12 15:39:24 +0000 For testing, what distribution is known to be broken like this? 61102 2 ross.burton 2016-04-12 16:51:12 +0000 Specifically, if we ran the distribution name through re.sub(r'\W', '', name) so that everything apart from numbers and letters were removed, would that fix the problem without causing other issues? 61105 3 ross.burton 2016-04-12 17:05:10 +0000 Can you see if this patch works for you? http://patchwork.openembedded.org/patch/120135/ 61136 4 ross.burton 2016-04-13 11:45:55 +0000 Merged in oe-core 8a96a7207561e00eb92e4fb69e7340f20bfa2053. 61201 5 silbe 2016-04-14 13:05:38 +0000 I haven't tried the patch yet, but running the regex replacement on the problematic lsb_release output sanitised the name properly (as expected). Thanks!