| Summary: | PKGSIZE is reported relative to host disk space | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Alexandru Damian <alexandru.damian> |
| Component: | core | Assignee: | Paul Eggleton <bluelightning> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | bluelightning, dvhart, meta.mr.watcher, meta.watcher |
| Version: | unspecified | ||
| Target Milestone: | 1.6 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Alexandru Damian
2013-10-10 11:13:50 UTC
I think you are refering to IMAGESIZE which uses du -k, This could also invalid existing data contained in the history. PGKSIZE is using pyhton's os.lstat(), which is already bytes. This is about PKGSIZE in package.bbclass, which uses def get_directory_size() which executes `du -sk `. Maybe this should be a more general bug for usage of `du` in host context ? Fix merged to master: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=f4e91404f8722b4fb1700e4c9fe13f0dfd7ebda3 http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=f4e91404f8722b4fb1700e4c9fe13f0dfd7ebda3 The fix was to drop use of "du" and instead use the sum of lstat() on each file. |