CVMFSRemoteSync.fetch_symlinks() currently creates a different package layout. It creates:
INSTALLROOT/<hash>/<arch>/<package>/
and links the contents of the CVMFS version directory directly into it. The expected path is:
INSTALLROOT/<hash>/<arch>/<package>/<full_version>/
The suggested solution is to include full_version in the destination paths and create the version directory before linking the package contents.
Most package contents are still symlinks back to CVMFS. When the synthetic tarball is reused, relocation tries to modify these files using operations such as sed -i. Since the targets are on the read-only CVMFS mount, the build fails with Read-only file system:
2026-07-30@14:48:10:DEBUG:LCG:LCG:0: sed: couldn't open temporary file /builds/zWVH0Cj2o/0/sft/stacks/bits/lcg.bits-empty/lcg.bits/INSTALLROOT/4160b36bc6b071d7dd56020110a6a28ad0d6462e/x86_64-el9-clang19-dbg/Python/3.13.11-1/lib/pkgconfig/sedoBxbWS: Read-only file system
CVMFSRemoteSync.fetch_symlinks()currently creates a different package layout. It creates:and links the contents of the CVMFS version directory directly into it. The expected path is:
The suggested solution is to include full_version in the destination paths and create the version directory before linking the package contents.
Most package contents are still symlinks back to CVMFS. When the synthetic tarball is reused, relocation tries to modify these files using operations such as
sed -i. Since the targets are on the read-only CVMFS mount, the build fails with Read-only file system: