Hi all,

This is a review request for the package detail views.  

Bugzilla Spec: https://bugzilla.yoctoproject.org/show_bug.cgi?id=4328

Branch: lerner/package-detail-views 
(NOTE DISCONTINUED BRANCH NOT YET DELETED: lerner/package-detail-views-bz4328)

Known defects and issues:
1) The link from package installed files is noop'd because the target 
information directory view was not found.
2) The calculation of the package footprint as a percentage of the total image 
works but only if the orm_total.file_size field is non-zero.  It seems to be 
zero which may be a bug during population.
3) There is a documented bug on the license file(s) field population in the 
database.  The Package Information data can't show the data until the database 
is populated.
4) There is a known problem with the package layer field which only shows the 
last directory in the layer path.  There are outstanding issues on how to map 
that to a known oe-core layer.
5) The bulk of my testing was done with a database populated 9 days ago.  After 
rebasing and rebuilding two test builds:
        qemux86 core-image-minimal
        genericx86 core-image-minimal core-image-basic
it seemed that the Packages view changed to only show installed packages.  This 
makes it impossible to view 'built' but not 'installed' packages.  However, 
this could be a workflow issue; my development database also had a sato image.  

Testing Summary:
After I resolve (5), trying to add a sato build, to see if I can populate the 
tables with packages that are not installed, I will post a detailed test plan. 
I felt it was important to make the commit tonight to give others a full day of 
examination on Friday, before the review on Monday.  As I noted, testing will 
continue, as will additional commits if necessary.

A summary of the testing done during development follows.

* All package dependency sets were validated at least once for all known cases, 
although further regression testing will be done tomorrow and as necessary 
during the weekend if (3) above is resolved.

* All pages, and sub-cases of pages, were html 5 validated using the w3c 
validator.

* All pages, and sub-cases of pages, were displayed as source html and visually 
compared with the source html of the yoctoproject.org/toaster to verify that 
classes and class hierarchies of the production pages matched the example pages.

Regards,
Dave
_______________________________________________
toaster mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/toaster

Reply via email to