This commit https://git.openembedded.org/bitbake/commit/?id=fdc55bb649cb77456d0ac48a9600ef289a52af18 seems to have introduced a regression where the cache file (local_srcrevisions.dat) is never actually written out to disk. This can be observed by creating a clean poky build with master, running 'bitbake -c unpack m4-native', and looking in build/cache: alex@Zen2:/srv/storage/alex/yocto/build-test-cache$ ls cache/ bb_codeparser.dat bb_unihashes.dat hashserv.db hashserv.db-shm hashserv.db-wal local_file_checksum_cache.dat sanity_info This should be addressed by calling bb.fetch2.fetcher_parse_save() bb.fetch2.fetcher_parse_done() during bitbake shutdown but I'm not sure why it isn't happening.
You'd need to have something actually needing a stored revision to write out the cache file (i.e. using AUTOREV)? I doubt it would write an empty file.
Right, if I add PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-dev" then the file appears. False alarm then.