On Thu, Feb 01, 2018 at 07:00:31AM +0200, John Found wrote: > On Wed, 31 Jan 2018 20:19:06 -0500 > Richard Hipp <d...@sqlite.org> wrote: > > > On 1/31/18, John Found <johnfo...@asm32.info> wrote: > > > > > > "fossil chan" for these two files display: > > > > > > SYMLINK activity0.tpl > > > SYMLINK activity1.tpl > > > > > > These two files are actually symlinks to "../Wasp/activity0.tpl" and > > > "../Wasp/activity1.tpl". > > > > > > This way, I can't commit my work at all. Is it a bug? Or expected > > > behavior? > > > How to commit now? > > > > Try running "fossil changes --hash" and afterwards trying to commit > > again. It might help. (Or it might not, but it is worth a try.) > > > > -- > > D. Richard Hipp > > d...@sqlite.org > > _______________________________________________ > > fossil-users mailing list > > fossil-users@lists.fossil-scm.org > > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > No, unfortunately, no difference. :( I am attaching the full output of > fossil in hope will be helpful. Also, the command created a bunch of > "file-RANDOM_STRING" in the checkout. >
I could reproduce it. I didn't have much time to investigate it for now but I have attached a simple shell script that reproduce the problem starting from scratch. Just put the shell script on an empty directory and execute it. Regards -- Martin G.
symlink_bug.sh
Description: Bourne shell script
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
