summaryrefslogtreecommitdiffstats
path: root/meta/recipes-support/libgcrypt/libgcrypt_1.10.1.bb
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2022-05-08 12:26:33 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2022-05-08 23:50:34 +0100
commit122b8e0ceade6876efce7496a0c0873db48eb024 (patch)
tree47426aba73fd49da632bb68715086d30ba39bbbe /meta/recipes-support/libgcrypt/libgcrypt_1.10.1.bb
parenta2e3d6c21d021f4927eadf6bbc6f7414dcfb6385 (diff)
downloadpoky-122b8e0ceade6876efce7496a0c0873db48eb024.tar.gz
package: Ensure we track whether PRSERV was active or not
Currently the signatures for do_packagedata don't reflect whether PRServ was active or not. This means that if you have mxiing of PRServ usage and non PRServ usage against the same sstate cache it can rarely become corrupted with one referencing the other. This likely doesn't happen in general but does on the autobuilder as PRServ is tested. Add in some variables to ensure the binary state of PRServ being enabled or disabled is tracked (but not the server value). We continue to assume one PRServ is used per sstate cache. (From OE-Core rev: dd660e5c3fb74f7c4b7b8e863f7143066ae22813) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-support/libgcrypt/libgcrypt_1.10.1.bb')
0 files changed, 0 insertions, 0 deletions