Hi, Quoting Antoine Beaupré (2024-12-23 02:32:25) > On 2024-12-22 22:59:22, Johannes Schauer Marin Rodrigues wrote: > > Quoting Antoine Beaupré (2024-12-22 22:39:12) > >> On 2024-12-22 22:21:22, Johannes Schauer Marin Rodrigues wrote: > >> > Hi, > >> > > >> > Quoting Antoine Beaupre (2024-12-22 21:34:14) > >> >> I'm getting this if I use symlinks for tarballs in unshare mode: > >> >> > >> >> Warning : > >> >> /home/anarcat/.cache/sbuild/UNRELEASED-amd64.tar.zst is a symbolic > >> >> link, ignoring > >> >> > >> >> I'm not sure why this is happening, but it's quite inconvenient as I > >> >> need to build a new chroot just for that UNRELEASED thing... > >> > > >> > can you show me a more complete log? I wonder what is producing this > >> > error > >> > message. I grepped for it in the sbuild source and cannot find what emits > >> > it. > > > > can you give me the output of this: > > > > $ file /home/anarcat/.cache/sbuild/UNRELEASED-amd64.tar.zst > > /home/anarcat/.cache/sbuild/UNRELEASED-amd64.tar.zst: symbolic link to > unstable-amd64.tar.zst > > Or do you mean: > > $ file -L /home/anarcat/.cache/sbuild/UNRELEASED-amd64.tar.zst > /home/anarcat/.cache/sbuild/UNRELEASED-amd64.tar.zst: Zstandard compressed > data (v0.8+), Dictionary ID: None
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? Thanks! cheers, josch
signature.asc
Description: signature
