On 24 May 2020, at 00:50, Norbert Preining <norb...@preining.info> wrote: > > Package: cowdancer > Version: 0.88 > Severity: important > > Hi all, > > we use cow-shell on our server to build update and test the TeX Live > network distribution on a daily basis, but be aware, this is not Debian > but CentOS. But since cow-shell is useful outside Debian, too, and > upstream seems to be Debian now, I report this error here. > > We have moved recently to a new server (hardware) while the software > stack hasn't changed. But we are seeing the following in our setup: > When the rebuild and test of TL fails, the cow-shell is exited and we > do not publish the changes, and the source directory should not be > changed. > > But we see changes in the source directory! > > Basically what we do > mkdir target > for i in source/* ; do > cp -al $i target > done > cow-shell <<EOF > # do lots of things, updates, tests > # if it fails exit 1 > EOF > Unfortunately, at this point files have changed in "source". > > I have tried to reproduce this with a small example, unsuccessfully. > OTOH, we can reproduce it with the full TeX Live tlnet directory > (about 5Gb). > > Is there any way how to debug/test/fix this?
My initial suggestion would be to capture what system call is being used using strace. Pick one of the files that changes, and run the entire cow-shell under `strace -o log -f -P target/file`. Hopefully strace doesn't interfere and it's obvious from the system calls what's going on... Jess
