Bug 4522

Summary: danny: After building an image, Hob reports the estimated image size in the "Edit Packages" screen
Product: [Build System, Metadata & Runtime] Hob Reporter: Stoicescu Cornel <corneliux.stoicescu>
Component: hobAssignee: Cristiana Voicu <cristiana.voicu>
Status: RESOLVED WONTFIX QA Contact:
Severity: normal    
Priority: Low CC: andreea.b.proca, belen.barros.pena, cristian.iorga, poky.bs.watcher, poky.watcher, richard.purdie, sgw, sjolley.yp.pm, valentin.popa
Version: 1.4.2   
Target Milestone: 1.4.2   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Stoicescu Cornel 2013-05-21 13:56:44 UTC
This bug was fixed in 1.5 master: bug 4388 

Steps to reproduce:

1. Launch Hob
2. Select a machine and base image (for example, atom-pc and core-image-minimal) 
3. Build the image
4. The Image details screen will come up and show a total image size (see screenshot 29pckg-22.1MB.png)
5. Click the "edit packages" button

Outcome: the "Edit packages" screen will show a different total image size to the one displayed in the "Image details" screen (see screenshot 29pckgs-8.6MB.png).
Comment 1 Saul Wold 2013-05-30 07:31:13 UTC
Do you know the patch that fixed it in 1.5?  Is this still a problem for 1.4?
Comment 2 Cristiana Voicu 2013-05-30 07:35:50 UTC
Hi Saul,
Here is the patch:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=d98419ae706c33f2d031598cb0914616bc7dfaa0

Cristiana
Comment 3 Stoicescu Cornel 2013-05-30 08:47:37 UTC
According to the last Hob test run for dylan(1.4_M6_RC2), this was present in the dylan branch:
https://bugzilla.yoctoproject.org/tr_show_run.cgi?run_id=495
dylan:87eb70243749e0e2431f98770746fa42002f4441

If the patch was not submitted after this commit then this is still an issue.
Comment 4 Richard Purdie 2013-09-26 14:13:27 UTC
We're unlikely to fix this in 1.3 at this point. Re-targetting at 1.4 where we need to assess if its much effort to fix there or not.
Comment 5 Stephen K Jolley 2014-04-23 15:24:29 UTC
Fix is in 1.5, no more 1.4 releases planned.