summaryrefslogtreecommitdiffstats
path: root/meta/recipes-extended/shadow
diff options
context:
space:
mode:
authorPaul Eggleton <paul.eggleton@linux.microsoft.com>2020-06-17 20:44:09 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2020-06-23 12:31:02 +0100
commit514494152a8c7c5373ea4c299f058246e88a7fb6 (patch)
tree458622b00c28372b3f143d8d35da4b98bbd041a1 /meta/recipes-extended/shadow
parent89bf9f6e61aae97f8c7876ec38b362f841e0374a (diff)
downloadpoky-514494152a8c7c5373ea4c299f058246e88a7fb6.tar.gz
dpkg-native: rebase and reinstate fix for "tar: file changed as we read it"
In OE-Core rev 8ee36a5f2f9367550d28bf271afc53bca6ff3d5f a patch was added for dpkg to ignore a return of 1 from dpkg's calls to tar (which indicates that files changed in some way while tar was operating) we were observing failures on the autobuilder due to changes to link counts in hard-linked file trees. The patch was subsequently rebased and then later removed during an upgrade in 3812f58b3a438ae533c282170416cdd1681868e0 on the assumption that the fix had been applied upstream, however that was not the case. I am now occasionally seeing these errors in my builds without any apparent material change to the files, so rebase and reinstate the patch. Fixes [YOCTO #13913]. (From OE-Core rev: 3f871fae96e72afa49b9d6a05c96af49173b8a60) Signed-off-by: Paul Eggleton <paul.eggleton@linux.microsoft.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-extended/shadow')
0 files changed, 0 insertions, 0 deletions