mirror of
https://git.yoctoproject.org/poky
synced 2026-07-24 16:17:45 +02:00
6ccffb86e8
When moving the updated CVE database file to the downloads directory, ensure that it has a different inode number to the previous version of this file. We have seen "sqlite3.DatabaseError: database disk image is malformed" exceptions on our autobuilder when trying to read the CVE database in do_cve_check tasks. The context here is that the downloads directory (where the updated database file is copied to) is shared between workers as an NFS mount. Different autobuilder workers were seeing different checksums for the database file, which indicates that a mix of both new and stale data was being read. Forcing each new version of the database file to have a different inode number will prevent stale data from being read from local caches. This should fix [YOCTO #16086]. (From OE-Core rev: 8aca19cff468c5f15c919c973c46be58e020af46) Signed-off-by: Paul Barker <paul@pbarker.dev> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit f63622bbec1cfaca6d0b3e05e11466e4c10fa86e) [YC: removed cve-update-db-native part, file was removed in 17eb0788514 (cve-update-db-native: remove, 2023-06-23)] Signed-off-by: Yoann Congal <yoann.congal@smile.fr> Signed-off-by: Paul Barker <paul@pbarker.dev>