Thus said Warren Young on Wed, 17 Feb 2016 08:10:51 -0700: > > are you saying that after updating > > to [fea4d80ee7b880bb] you no longer see the assertion failure, but > > instead see only the unique constrain violation? > > Yes.
Are you doing more than just ``fossil mv'' because the only way that I can see that the error can happen is if there is a rename and an add for the same filename. > > $ echo "ATTACH '.fslckout' AS '.fslckout'; SELECT origname,stashid FROM > > stashfile WHERE stashid = 3;" | fossil sql > > That gives me a complaint about needing -R. It has to be run from within an open checkout of the repository that is having a problem. .fslckout is the open checkout database that tracks local changes, it is not part of the Fossil repository proper, and hence -R will not work with it. > There is one item currently in the stash on one of those Fossils. So, > when does that table get created? It gets created the first time you stash something, but as I said, it isn't part of the Fossil repository, it's part of the checkout. ls /path/to/checkout/.fslckout It may also be called _FOSSIL_ if the checkout happened with an older version of Fossil. Andy -- TAI64 timestamp: 4000000056c48f2d _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
