Re: [OE-core] Broken "bitbake -S printdiff" in current OE

2016-08-23 Thread Ulf Magnusson
On Tue, Aug 23, 2016 at 8:18 AM, Mike Looijmans wrote: > Was attempting to figure out why something wasn't being grabbed from the > sstate-cache, but running "bitbake -S printdiff qt4-embedded" only yields > tons > of lines like this: > > WARNING: /home/mike/.../bitbake/lib/bb/runqueue.py:1347: R

Re: [OE-core] Broken "bitbake -S printdiff" in current OE

2016-08-22 Thread Mike Looijmans
On 23-08-16 08:18, Mike Looijmans wrote:> Was attempting to figure out why something wasn't being grabbed from the> sstate-cache, but running "bitbake -S printdiff qt4-embedded" only yields tons> of lines like this:>> WARNING: /home/mike/.../bitbake/lib/bb/runqueue.py:1347: ResourceWarning:> uncl

[OE-core] Broken "bitbake -S printdiff" in current OE

2016-08-22 Thread Mike Looijmans
Was attempting to figure out why something wasn't being grabbed from the sstate-cache, but running "bitbake -S printdiff qt4-embedded" only yields tons of lines like this:WARNING: /home/mike/.../bitbake/lib/bb/runqueue.py:1347: ResourceWarning: unclosed file <_io.BufferedReader name='/home/mike/.