summaryrefslogtreecommitdiff
path: root/scripts/lib/compatlayer/context.py
diff options
context:
space:
mode:
authorMing Liu <liu.ming50@gmail.com>2019-04-05 16:22:15 +0200
committerArmin Kuster <akuster808@gmail.com>2019-05-07 07:00:32 -0700
commit6351f52609af51055786f7b3b24aee722b4dcea4 (patch)
tree7af15b9b636a6eeff76ac24de4119d1167742648 /scripts/lib/compatlayer/context.py
parent9c63433010aae6891149a7605a637bee879dc4ef (diff)
downloadopenembedded-core-6351f52609af51055786f7b3b24aee722b4dcea4.tar.gz
openembedded-core-6351f52609af51055786f7b3b24aee722b4dcea4.tar.bz2
openembedded-core-6351f52609af51055786f7b3b24aee722b4dcea4.zip
opkg-utils: backport a patch to fix a sstate timestamp issue
When using sstate, two parallel builds can produce two packages with the same mtime but different checksums. When later one of those two builds fetches the others ipk, the package index does not get udpated properly (since mtime matches). This ends up with messages such as: Downloading file:/../tmp/work/../image/...ipk. Removing corrupt package file /../sysroot/../var/cache/opkg/volatile/...ipk However, in that case, ctime is different. Use ctime instead of mtime to prevent failures like this. Signed-off-by: Ming Liu <liu.ming50@gmail.com> Signed-off-by: Armin Kuster <akuster808@gmail.com>
Diffstat (limited to 'scripts/lib/compatlayer/context.py')
0 files changed, 0 insertions, 0 deletions