Thus said Warren Young on Sun, 14 Feb 2016 20:49:19 -0700: > > http://www.fossil-scm.org/index.html/info/fea4d80ee7b880bb > > On the Linux machine I originally saw the problem on, I get a new > symptom which may illuminate the cause of the assertion failure. On > ``stash save'' it now says:
Just to solidify this in my mind... are you saying that after updating to [fea4d80ee7b880bb] you no longer see the assertion failure, but instead see only the unique constrain violation? What happens if you run 2 different builds (one with [fea4d80ee7b880bb] and one with trunk) of Fossil against the same state in the repository? Also, with respect to the constraint, what does this give you if you run it from within the checkout where the problem happens? $ echo "ATTACH '.fslckout' AS '.fslckout'; SELECT origname,stashid FROM stashfile WHERE stashid = 3;" | fossil sql Not that this matters, but who knows... what filesystem does your Linux system have in place? Andy -- TAI64 timestamp: 4000000056c27204 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
