Yeah, I am sorry for that. It was intentional, but I discovered there is a bug 
in the upstream that prevents me from using this feature properly.
https://github.com/tpm2-software/tpm2-tss/issues/2571

I thought it will be fixed quickly, but it wasn't. Let me fix this.

-----Original Message-----
From: Peter Kjellerstedt <[email protected]> 
Sent: Friday, April 21, 2023 8:07 PM
To: Petr Gotthard <[email protected]>
Cc: [email protected]
Subject: RE: [meta-security][PATCH] tpm2-tss: upgrade 3.2.0 -> 4.0.1

You introduce a new feature "policy", but then you set the default for 
PACKAGECONFIG to "vendor", which does not exist. Was this intentional? If so it 
should have been mentioned in the commit message as it causes a warning unless 
you override the default PACKAGECONFIG:

  WARNING: tpm2-tss-4.0.1-r0 do_configure: QA Issue: tpm2-tss: invalid
  PACKAGECONFIG: vendor [invalid-packageconfig]


//Peter
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59757): https://lists.yoctoproject.org/g/yocto/message/59757
Mute This Topic: https://lists.yoctoproject.org/mt/97035270/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to