We were: Sujith, Brian and Belén ARs:
Brian - send to Michael the result of his ic-6 digging Ed - review last version of Sujith's build cancellation patches Belén - suggest design changes needed to handle mismatch between package information in build history and image customisation Belén - design undo feature for image customisation Updates: Sujith: made some changes to the build cancellation patches based on Ed's comments, and pushed to his development branch in poky-contrib. Ed suggested to use the bitbake controller, but it kept on throwing exceptions and errors. Waiting for a new review from Ed. Brian: reviewed the issues Belén found in the latest version of the image customisation branch (ic-6) and found the cause of the mismatches in the packages list data between build history and image customisation. 1. Kernel modules never appear in the image customisation package list. This according to Brian is a bug 2. Dependencies brought in by a package you add manually don't seem to appear in the image customisation package list after building. This, according to Brian, is also a bug. 3. The locale packages are not shown in the image customisation package list. This is not a bug: it is due to the weird way the locale packages are generated. 4. Package groups are shown as any other installed package by the build history data, but are not shown at all in the image customisation package list. This is a bug in the build history data: package groups are not an installed package, so they should not be shown as such in the build history. Both Brian and Belén agreed we need to handle these differences and make the 2 package lists match. Users will never understand the source of the differences, so doing otherwise will just cause enormous confusion. Issues 1 and 2 need to be fixed in ic-6, but 3 and 4 will require some changes in the way we present package information. Belén will look into this next week. We also discussed the removal of package dependencies, which should probably also remove the full dependency chain as originally designed. This action, however, cannot be easily reversed without having an 'undo' feature. Brian suggested we version the custom images with every package change so that we can roll back. We reset the versions after each build. Note that the undo feature only needs to allow you to roll back once (undo the latest action). It is just a way of helping users recover from errors, not a full blown snapshot / history feature. Brian: if I've missed anything, please comment. Cheers Belén On 30/12/2015 10:31, "[email protected] on behalf of Barros Pena, Belen" <[email protected] on behalf of [email protected]> wrote: >The weekly call for Toaster contributors happens: > >Wednesday, Dec. 30, 2015 8:00 AM US Pacific Time > >Call Details: > >Tel: 1-888-875-9370/916-356-2663 >Bridge: 4 >Passcode: 2881477 > >Agenda: > >Team Member Update >Triage Toaster bugs >https://wiki.yoctoproject.org/wiki/Bug_Triage#YP_Toaster_Bugs_needing_ >AR's Review >Opens > >-- >_______________________________________________ >toaster mailing list >[email protected] >https://lists.yoctoproject.org/listinfo/toaster -- _______________________________________________ toaster mailing list [email protected] https://lists.yoctoproject.org/listinfo/toaster
