Further testing makes me think that it's a problem only with recent versions of fuse3 (on Debian/amd64, at least). I tested all the Debian package versions from 0.7.11 to now:
tup_0.7.11-1_amd64.deb tup_0.7.11-2_amd64.deb tup_0.7.11-3_amd64.deb tup_0.7.11-4_amd64.deb tup_0.7.11-5_amd64.deb tup_0.7.11-6_amd64.deb tup_0.8-1_amd64.deb tup_0.8-1+b1_amd64.deb [FAILED!] Only the last package failed. The only difference between it and the previous one (0.8-1) is that 0.8-1+b1 was compiled against fuse3 v3.17.2, whereas 0.8-1 was compiled against fuse3 v3.14.0. I've filed a Debian bug report: <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1109719> In short, I'm now not sure whether the problem is in tup or in fuse3 (or in a recent change in the fuse3 interface that tup hasn't accounted for). -Sanjoy -- -- tup-users mailing list email: [email protected] unsubscribe: [email protected] options: http://groups.google.com/group/tup-users?hl=en --- You received this message because you are subscribed to the Google Groups "tup-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/tup-users/87cy9s1ias.fsf%40mit.edu.
