Bug 2784

Summary: license.bbclass failing on autobuilder
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Ross Burton <ross.burton>
Component: coreAssignee: Saul Wold <sgw>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: Undecided CC: bluelightning, meta.mr.watcher, meta.watcher, richard.purdie
Version: unspecified   
Target Milestone: ---   
Hardware: x86   
OS: Multiple   
Whiteboard: (autobuilder)
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---

Description Ross Burton 2012-07-18 09:26:10 UTC 
| ls: cannot access /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-x86/build/build/tmp/pkgdata/*/runtime/dbus-1: No such file or directory
| ls: cannot access /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-x86/build/build/tmp/pkgdata/*/runtime/kernel-3.4.4-yocto-standard: No such file or directory
| ls: cannot access /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-x86/build/build/tmp/pkgdata/*/runtime/libacl1: No such file or directory
...

(more at http://autobuilder.yoctoproject.org:8010/builders/nightly-x86/builds/586/steps/shell_25/logs/stdio)

Paul says:

It seems to me the problem is that the pkgdata is in non-debian renamed format
whereas license.bbclass by virtue of using the final list of installed packages
is expecting to use the post-rename names (e.g. pkgdata/*/runtime contains
zlib-dev whereas the installed package is called libz-dev). Given that this
renaming happens much earlier in the process, I'm not sure how my change could
have triggered this or why it would only be a problem sometimes.
Comment 1 Richard Purdie 2012-07-18 21:41:28 UTC 
I think these are always there, the other failures just highlighted them.

To fix this, we might need to add another pkgdata directory alongside runtime which has the renamed package versions symlinked to the runtime directory. The license code can then reference this.
Comment 2 Saul Wold 2012-07-19 14:37:45 UTC 
Andrei may have had a patch.

*** This bug has been marked as a duplicate of bug 2638 ***