Bug 6684

Summary: The content of the license column shouldn't be 4.0k.
Product: [Build System, Metadata & Runtime] Toaster Reporter: Yuan Sun <Yuan.Sun2>
Component: toasterAssignee: Michael Wood <michael.g.wood>
Status: VERIFIED WONTFIX QA Contact: Mihail Stanciu <stanciux.mihail>
Severity: normal    
Priority: Medium CC: alexandru.c.georgescu, alexandru.damian, belen.barros.pena, cristiana.voicu, jessica.zhang, stanciux.mihail
Version: 1.7   
Target Milestone: 1.7.1   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
screenshot none

Description Yuan Sun 2014-09-05 06:30:50 UTC
Created attachment 2107 [details]
screenshot

The content of the license column shouldn't be 4.0k.
Wrong content in license column, Size column, Size over total(%) column.
Comment 1 Belen Barros Pena 2014-09-05 13:16:07 UTC
This seems to happen only when you display the License AND the Size or Size over total columns. When you are only showing the License column, it's ok.
Comment 2 Yuan Sun 2014-09-09 01:28:10 UTC
(In reply to comment #1)
> This seems to happen only when you display the License AND the Size or Size
> over total columns. When you are only showing the License column, it's ok.

Yes. You are right, Belen.
Comment 3 Michael Wood 2014-10-29 17:50:35 UTC
Looks like a simple issue of the table data order not matching the column headers order as supplied by the context tablecols

https://lists.yoctoproject.org/pipermail/toaster/2014-October/001460.html
Comment 4 Mihail Stanciu 2014-12-09 14:18:23 UTC
Verified on master: b813bdebb36501500e86fea5f7e15b4b15ea0902
Comment 5 Mihail Stanciu 2015-01-08 09:49:09 UTC
Issue still present on 1.7.1_RC1: 6dd21a9f152a93e2df1178d7a5bd903d7edcf4be
Comment 6 Alexandru Damian 2015-01-08 11:22:04 UTC
Will not be fixed in 1.7.1
Comment 7 Mihail Stanciu 2015-02-11 13:41:17 UTC
Verified.
Comment 8 Alexandru Georgescu 2015-03-23 09:27:18 UTC
(In reply to comment #6)
> Will not be fixed in 1.7.1

I guess the same for 1.6.x