Control: retitle -1 sbuild unshare mode unhappy about symlink'd zstd tarballs
Hi, Quoting Alper Nebi Yasak (2024-12-23 10:32:39) > > thank you for both outputs. My hunch was that the symlink was broken and > > that's why it failed. I am still wondering where the message you see is > > from. This made me find this here: > > > > https://sources.debian.org/src/libzstd/1.5.6+dfsg-1/programs/zstdcli.c/?hl=1328#L1328 > > > > Could you try switching the compression of your tarball (or use no > > compression) > > and check if the problem persists? If not, maybe something special has to be > > done with zstd compressed tarballs? > Looks like zstd ignores symlinks unless --force is passed [1]. Editing > the command in ChrootUnshare.pm [2] to add it makes it work for me, but > it may be too lenient with the file? From the zstd man page: > > > -f, --force: disable input and output checks. Allows overwriting ex‐ > > isting files, input from console, output to stdout, operating on > > links, block devices, etc. During decompression and when the output > > destination is stdout, pass-through unrecognized formats as-is. > > [1] > https://github.com/facebook/zstd/commit/680e4e0953bf7c895165e41098a37c3279870c1f commits without any rationale behind them are the best </scarcasm> This also reminds me of #1089105 which comes down to zstd not accepting compressed data on stdin and writing the uncompressed result to stdout without also passing --force. Seems entirely unintuitive to me... Thank you for having found this. Maybe we should just call zstd with '--force' and call it a dway... Thanks! cheers, josch
signature.asc
Description: signature
