On Thu, 2020-07-23 at 17:04 +0300, Vitaly Chikunov wrote: > Mimi, > > On Thu, Jul 23, 2020 at 02:29:34PM +0200, Petr Vorel wrote: > > Hi Mimi, > > > > ... > > > > Thanks for fixing it. foreign flavor fits our needs better than gnu. > > > > Autotools "features" like this (having strange gnu flavor as the default) > > > > explain why people keep introducing new build systems like Meson (which brings > > > > other problems). > > > > > Changing the autotools flavor solved the problem, but I wasn't sure > > > that it was the correct solution. Thank you for validating the flavor > > > change. > > yw :). > > > > BTW could you also merge your .travis.yml from next-testing-travis to next (and > > preferably also to master)? Even if you have no way to setup automatic mirror to > > some travis account, it help to run it sometimes or at least before release. > > Also, it's useful to packagers to see that there is tests and how to run > them. > > Thanks, > > > > > Also, having docker based travis setup helps to test build against other distros > > (we have it in LTP). The existing travis.yml is a first attempt at using travis. (Hint: help with cleaning it up would be much appreciated.) Should this travis.yml be included now in 1.3.1 or deferred to 1.3.2? Let's sync up on what should be included when. Additional suggestions are welcome. 1.3.1 release (~1 week): - minor fixes Proposed 1.3.2 features (~3 months): - Travis integration - Support providing the TPM 2.0 PCRs as a file (--pcrs option). - Walking the TPM 2.0 event log as the basis for calculating the "boot_aggregate". thanks, Mimi
