To reproduce the bug: configure your build add INHERIT += "blacklist" to local.conf bitbake <some recipe> edit conf/local.conf add: PNBLACKLIST[<some recipe>] = "reason" bitbake <some recipe> It will try to build <some recipe>, instead it should tell you it's been blacklisted. rm -rf cache tmp/cache bitbake <some recipe> Will now tell you that recipe has been blacklisted.
I just tried this with master (7d02de844c00d55189673a6eed9197bcbc5b2720) and wasn't able to reproduce this. Can you confirm you're still seeing the problem with master?
I've found the key to reproducing, you need multiple entries and it doesn't notice when a single entry changes if more than one exist!
Fixed in master: http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=353212a5330040a24945fb7d10ae8b6a124355f6
Verified with dora:a02280f99f05b1c21de2a78de9222a2f62a0dabc (1.5 M5 RC6) which contains the fixing commit. After blacklisting man: bitbake man Parsing recipes: 100% |##################################################################################################################################| Time: 00:00:18 Parsing of 875 .bb files complete (0 cached, 875 parsed). 1206 targets, 43 skipped, 0 masked, 0 errors. ERROR: Nothing PROVIDES 'man' ERROR: man was skipped: Recipe is blacklisted: reason Summary: There was 1 ERROR message shown, returning a non-zero exit code.